| -----Original Message----- | From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On | Behalf Of Trent Albright | Sent: Tuesday, July 25, 2006 3:41 PM | To: Maven Users List | Subject: Re: deploying jars without version information | | > 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. | How? Do tell! =)
See http://maven.apache.org/plugins/maven-ear-plugin/howto.html, "Customizing a module file name" and "Customizing a module uri" sections. | > 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. | What is the "maven2 way" of doing this? Creating a custom script that | is executed from instructions in the POM after a certain phase? Or are | you suggesting I write a script to be run completely seperate from the | execution of the maven2 build? I'm new to maven so if you could point | me in the general direction, I can read up and take it from there. At least for renaming modules within EARs, the Maven2 way would be as described in the link above. The means for renaming dependency artifacts in other M2 plugins seems to vary. Ian --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
