Maven must use it's own naming scheme within the repo, that's why it only affects packaging. Note you can change the names of jars/wars within an ear so that the module URI in the application.xml does not need to change with every version increment.
As Chris mentioned, the best way is to add a copy step after the fact which renames the file to your legacy format and uploads to the server. mike -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Trent Albright Sent: Tuesday, July 25, 2006 1:43 PM To: Maven Users List Subject: Re: deploying jars without version information Yes, it's true that you can use the plug in configuration section to force a generated jar or war to have a certain name. As far as I can tell, this only affects the "package" phase. Am I on the wrong track here thinking that maven2 is suitable for creating official releases, for deploying to integration test servers? If it is appropriate to use maven2 for this purpose, how would you recommend I get around the naming issue? (Again, not in the repository, rather during integration testing and product release). --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
