Bug 28898 - Change the jar export wizard to create ant build.xml
Summary: Change the jar export wizard to create ant build.xml
Status: RESOLVED DUPLICATE of bug 117762
Alias: None
Product: JDT
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 2.1   Edit
Hardware: All All
: P3 enhancement with 1 vote (vote)
Target Milestone: ---   Edit
Assignee: Dani Megert CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-12-29 05:01 EST by Oyvind Harboe CLA
Modified: 2008-01-07 08:18 EST (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Oyvind Harboe CLA 2002-12-29 05:01:11 EST 
Just a suggestion:

It isn't immediately obvious to me why there needs to be a .jardesc file 
format, when it seems to me that ant will do all and more. 

The immedidate advantage for me with ant build.xml files is that they can be 
configured to build a jar file out of all the .class files in the project. 
jardesc files need to be updated every time I add or remove .java files from 
the project.

Perhaps this is possible with .jardesc files, but it isn't immediately obvious.

My solution: dump .jardesc and only learn ant build.xml files.
Comment 1 Darin Wright CLA 2003-01-02 10:34:06 EST 
Moving to JDT - this is a feature request for JDT, not ANT.
Comment 2 Dirk Baeumer CLA 2003-01-07 10:32:55 EST 
Daniel, can you comment on the difference of the Jardesc file and ant files. 

And of course you can write your own build.xml file and use that one to export 
a Jar instead of using the export wizard.
Comment 3 Dani Megert CLA 2003-01-07 10:47:01 EST 
That's true you could do more with the ant file (e.g. exclusions) and that's
exactly the problem, e.g. what would you expect the wizard to do if the user
edits the generated ant (build.xml) file and then reopens the wizard?

One possibility could be an action which allows to generate a build.xml either
directly from the wizard or from an existing .jardesc file.

As you can see in bug 3609#c2 we already discussed this.
Comment 4 Dani Megert CLA 2008-01-07 08:18:17 EST 

*** This bug has been marked as a duplicate of bug 117762 ***