Community
Participate
Working Groups
When exporting a jar file from a project, eclipse should offer previous export configurations as options. Having to redescribe the items to include/exclude is very error-prone. UI to name export configurations, just as can be done for run-configurations seems appropriate. I have also become very fond of JBuilder's jar configuration options, which include the option to always rebuild jar files when rebuilding source. This may not be entirely appropriate given eclipse's incremental build approach, but an option to always re-export jars before running would be great. This along with an option to then run from the created jars, would greatly improve the ability to test within eclipse from the actual runtime files.
Jar export is provided by UI.
you can already store a JAR configuration. See the option "Save a description of this JAR in the workspace. Support for a "post JAR builder" has currently a lower priority
You can store an export configuration in a so called JAR description file (see JAR Exporter's Option page). This will generate a file with .jardesc extension. To recreate the same JAR simply select the .jardesc file and select "Create JAR" from the context menu. Of course you can also open the JAR Exporter for a given .jardesc file. Afer 2.2 we might provide support to generate an ANT build file out of an existing .jardesc or investigate if we can register .jardesc as an external builder.
No further action planned. You can either store in a jardesc file or use ant and an external builder to build the Jar file on very compile/build.
