While migrating projects at my company, I've taken a bit of an Ant/Maven hybrid approach. I've been able to Mavenize a couple of projects, but some other projects need to refer to those jars with their original names. In those cases, I've modified the Ant builds in those projects to use the Ant tasks for Maven to copy the files from the repository and rename them for local use.
Chris Hilton > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On > Behalf Of Trent Albright > Sent: Tuesday, 25 July, 2006 13:43 > To: Maven Users List > Subject: Re: deploying jars without version information > > Ironic. I was just getting ready to ask a similar question. > Although I'm fine with the versioning that occurs in the > repository, I need the ability for the jar name to not > contain this version string in it when I create a release or > deploy the project to the integration server for testing. > > In my case I'm extending a pre-existing J2EE commercial application. > It expects jars, even ones especially created for end-user > customization, to follow certain naming conventions. It's > just not feasible for these jars to be renamed to something > else (yaddayadda-1.0-SNAPSHOT.jar). > > 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). > > > On 7/25/06, Mike Perham <[EMAIL PROTECTED]> wrote: > > Why? Removing version info is very dangerous. You then > have no idea > > which version was actually selected by Maven by looking in the > > artifact after the fact. > > > > -----Original Message----- > > From: LaCasse, John [mailto:[EMAIL PROTECTED] > > Sent: Tuesday, July 25, 2006 12:57 PM > > To: Maven Users List > > Subject: RE: deploying jars without version information > > > > I'm talking about the second case; in the > target\webapp\WEB-INF\lib. > > All compile and runtime scoped dependant jars that get put > into this > > location; I would like the war plugin not to include the > version info > > on all the jars it includes in this location. > > > > -----Original Message----- > > From: Alexandre Poitras [mailto:[EMAIL PROTECTED] > > Sent: Tuesday, July 25, 2006 10:53 AM > > To: Maven Users List > > Subject: Re: deploying jars without version information > > > > What do you means by deploting? Deploying on a maven > repository or on > > a application server ? In the first case, the answer is no because > > Maven needs those metadatas to be able to manage > dependencies. In the > > other case, yes it's possible just change the name in your war/jar > > plugin configuration section. > > > > On 7/25/06, LaCasse, John <[EMAIL PROTECTED]> wrote: > > > Hi, > > > > > > > > > > > > Does anybody know if you can have Maven deploy the jars > that end up > > > in webapp/WEB-INF/lib without the version information in > the filename? > > > > > > > > > > > > Thanks, > > > > > > Jpl > > > > > > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
