Where this flack is coming from?
The reason I specifically want to do it, is so I can use the manifest to package extended information about the classes.
I think I said that though... as for not "convincing", that assumes that the way you do things is the right way... I wasn't trying to convince anyone.
I guess I'm surprised that people don't even want the *ability* to package as a JAR instead of in the classes dir. Frankly with my style, I'd package into a jar instead even if I wasn't interested in the manifest just to keep things what I would think of as tidy.
- Brill Pappin
Maczka Michal wrote:
Can you provide at least one valid reason why would like to do that (put jar-----Original Message----- From: Brill Pappin [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 29, 2004 2:38 PM To: Maven Users List Subject: Re: RFE for the war plugin
Yes, I thought of doing that very thing :)
however I then have problems with Eclipse as it doesn't understand multi-project builds, and you really want all the parts of an application in the same place.
Still doable, but less than optimum.
file into WEB-INF/lib folder)?
All the points you mentioned in you original post are either not very
convincing or false (e.g. that size of war thanks to that will be smaller).
Michal
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--
"Any sufficiently advanced magic is indistinguishable from technology."
- Arthur C Anticlarke
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
