On Thu, Nov 17, 2005 at 10:39:40AM -0500, John Casey wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > There are two general things that go in that directory: plugin > descriptors, and POM information. > > For the former, we need some way of describing a Maven plugin to the > system, to determine how to startup the plugin and execute it. > > For the latter, we were originally attempting to identify that artifact > with something more than merely the filename. This is meant to help with > things like migrating away from an Ant build, where the /lib/*.jar files > don't have versions or groupIds included in the filenames. Assuming we > can take passwords and local paths out of this information (there is a > pending patch to handle some of this), what are the specific concerns > with having this information in the jar?
For the specific concerns: * Someone on the list said it was against his company policy * Generally speaking, informations such as internal computer names, of the SCM repository, names and roles of all the developpers, etc is not something everyone wishes to include for a release version * But most importantly for myself, it is annoying in an heavily size constrained environment. When you only have 20k of storage for a given jar file (think J2ME for instance, or even J2SE on special hardware), every byte count :) Regards, -- Julien --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
