-----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? - -john Christian Schulte wrote: | Emmanuel Venisse schrieb: | |> |> |> Julien Stern a écrit : |> |>> On Thu, Nov 17, 2005 at 01:38:03PM +0100, Christian Schulte wrote: |>> |>>> Hi, |>>> |>>> what is the reason for the META-INF/maven content in the jar files |>>> produced by maven 2 ? Is there a possibility to avoid the creation |>>> of these entries in the jar ? |>> |>> |>> |>> |>> I had the same issue. It seems that it is not currently possible |>> to avoid this creation, but that this "feature" is needed by several |>> people. I guess we should create a JIRA entry for it and vote :) |> |> |> |> yes, it's the better solution. :-) |> |> Emmanuel |> | | So there is no reason why it is added to the jars ? It's really not used | anywhere and is just there to be there ? | -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (GNU/Linux) iD8DBQFDfKQ8K3h2CZwO/4URAtx4AJ9nICPtAN7qTkNdqoFm3UwG6wZ31wCbBvVG m6CfVwyd7RP7svxbZEWLpeo= =ic49 -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
