> Probably, the same thing should be done for Jakarta Commons. There are way too many Commons-This and Commons-That.
Agreed. The Maven <dependency> elements support this for obtaining the dependencies, but I don't know what changes we'd need to make to the project.xml files to get the deploy to deal with that. Hopefully someone on the Commons list will know.
I'm not sure if I understand the question. If it's simply "how to construct project.xml so that a JAR is deployed correctly with maven jar:deploy", then the answer is also simple. The EL project.xml is set up correctly:
<project> ... <id>struts-el</id> <groupId>struts</groupId> .... </project>
Joe
--
Joe Germuska [EMAIL PROTECTED] http://blog.germuska.com "Narrow minds are weapons made for mass destruction" -The Ex
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
