Wayne Fay wrote: > > That would be the correct next step. But again, I'm not making any > statements as to whether or not this will actually occur. It will need > to be discussed on the Dev list and in the Jira. > > I can think of an awful lot of reasons why this should not be > implemented -- for one, changing the file name will break the > manifest.mf in the archive and possibly other similar files. And I'm > not sure the positive side effects of such a change would outweigh the > negative ones. >
I created the jira http://jira.codehaus.org/browse/MNG-5037 Regarding the break of the manifest.mf it is already the case: By defaut, and for those that use the class-path entry, the manifest contains references to timestamped jars, but the ear/war contains snapshots jars. So your application won't work. You can bypass this behaviour by configuring the archiver as I said in my previous post. -- View this message in context: http://maven.40175.n5.nabble.com/Issue-with-mvn3-timestamp-snapshots-being-downloaded-in-local-repository-tp3408008p3415143.html Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
