Um único Jar

Ninguém sabe???

posta teu build file do Ant aeh

[]s

isso?

• Builds, tests, and runs the project Claudir.
• <!-- There exist several targets which are by default empty and which can be used for execution of your tasks. These targets are usually executed before and after some main targets. They are:

  -pre-init:                 called before initialization of project properties
  -post-init:                called after initialization of project properties
  -pre-compile:              called before javac compilation
  -post-compile:             called after javac compilation
  -pre-compile-single:       called before javac compilation of single file
  -post-compile-single:      called after javac compilation of single file
  -pre-compile-test:         called before javac compilation of JUnit tests
  -post-compile-test:        called after javac compilation of JUnit tests
  -pre-compile-test-single:  called before javac compilation of single JUnit test
  -post-compile-test-single: called after javac compilation of single JUunit test
  -pre-jar:                  called before JAR building
  -post-jar:                 called after JAR building
  -post-clean:               called after cleaning build products
  

  (Targets beginning with ‘-’ are not intended to be called on their own.)

  Example of inserting an obfuscator after compilation could look like this:

  <target name="-post-compile">
        <obfuscate>
            <fileset dir="${build.classes.dir}"/>
        </obfuscate>
    </target>
  

  For list of available properties check the imported
  nbproject/build-impl.xml file.

  Another way to customize the build is by overriding existing main targets.
  The targets of interest are:

  -init-macrodef-javac:     defines macro for javac compilation
  -init-macrodef-junit:     defines macro for junit execution
  -init-macrodef-debug:     defines macro for class debugging
  -init-macrodef-java:      defines macro for class execution
  -do-jar-with-manifest:    JAR building (if you are using a manifest)
  -do-jar-without-manifest: JAR building (if you are not using a manifest)
  run:                      execution of project 
  -javadoc-build:           Javadoc generation
  test-report:              JUnit report generation
  

  An example of overriding the target for project execution could look like this:

  <target name="run" depends="Claudir-impl.jar">
        <exec dir="bin" executable="launcher.exe">
            <arg file="${dist.jar}"/>
        </exec>
    </target>
  

  Notice that the overridden target depends on the jar target and not only on
  the compile target as the regular run target does. Again, for a list of available
  properties which you can use, check the target you are overriding in the
  nbproject/build-impl.xml file.

  –>
  

cara, que dá pra fazer isso que tu quer, dá…
mas tu vai ter que mexer no teu build.xml
esse arquivo que vc mandou é uma espécie de “interface” do teu build.xml
em projetos do netbeans o build file real está em <nome_proj>/nbproject/build-impl.xml

eu nao lembro de cabeça como se faz isso, mas dá uma pesquisada sobre o ant…
eu sei que no IntelliJ Idea da pra fazer isso via interface da IDE, informando que tu quer enpacotar tudo junto…

[]s