externalize list of deployable jars in seam-gen projects
--------------------------------------------------------
Key: JBSEAM-2897
URL:
http://jira.jboss.com/jira/browse/JBSEAM-2897
Project: Seam
Issue Type: Feature Request
Components: Tools
Affects Versions: 2.1.0.A1, 2.0.2.CR1, 2.0.1.GA
Reporter: Dan Allen
Assigned To: Dan Allen
Priority: Minor
Fix For: 2.0.2.CR2, 2.1.0.BETA1
Attachments: JBSEAM-2897-branch20-earproject-v1.txt, JBSEAM-2897-branch20-v1.txt,
JBSEAM-2897-branch20-v2.txt, JBSEAM-2897-trunk-earproject-v1.txt,
JBSEAM-2897-trunk-v1.txt
Original Estimate: 30 minutes
Remaining Estimate: 30 minutes
Adding a new JAR to be included a seam-gen project deployment is a huge pain. You have to
dive down into the middle of the build.xml file and find the inclusion list nested within
the copy-libs target. Try explaining that to a newbie.
Despite plans to redesign the dependency mechanism in seam-gen projects, I think it is
important to fix the smaller issue at hand. Let's externalize the list of deployed
jars and use <includesfile name="deployed-jars.list"/> to include them.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: