RE: deploying jars without version information
I searched the mail archives because of the following problem: 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 Ok, i found a solution which works for me with maven 1. In your maven.xml file define a pregoal for the war plugin: this removes the version part when copying the files. Hope this will help, or give you a new idea how to find a solution Uli
Re: deploying jars without version information
On 7/25/06, Max Cooper <[EMAIL PROTECTED]> wrote: Some production environments have similar issues. For example, some webapps are deployed expanded. And the new version is simply dumped in over the old version. Requesting to have files deleted during a deployment in these schemes is overhead, and error-prone. I think that is a lousy way to setup a production deployment, but I have had to live with this kind of thing on more than one occasion in my professional career. I am sure I'm not the only one. Bingo. In theory the idea of jars with version names in them is great, and when you have 100% control of the application not a problem. This would work out great if only the rest of the java community followed suit! However, in the real world end-users of maven are faced with potentially very complex J2EE applications that have conventions or restrictions that don't fit this notion of versions in jar names. Best practices aside, sometimes we're stuck with the pile built by someone else. I will investigate some of the suggestions you kind folks have made in this thread, thanks for that. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: deploying jars without version information
Having the version number in filenames can be problematic in some environments. For instance, when doing local development it is nice to strip the version number from the war/ear name so that you don't end up with two deployments if the version number changes. Some production environments have similar issues. For example, some webapps are deployed expanded. And the new version is simply dumped in over the old version. Requesting to have files deleted during a deployment in these schemes is overhead, and error-prone. I think that is a lousy way to setup a production deployment, but I have had to live with this kind of thing on more than one occasion in my professional career. I am sure I'm not the only one. I think the OP just wants to be able to build his war in such a way that the jars that maven puts into the WEB-INF/lib directory DO NOT have the version number in the filenames. Does anyone know how to do that? Off the top of my head, this might work: * Set the scope of the dependencies to "provided" so that Maven doesn't copy them to WEB-INF/lib * Use the maven-dependency-plugin to copy the jars, stripping the version number in the process However, that adds a lot of work to configure all the scopes and setup the copy for each dependency. Maybe there is a better way. -Max Mike Perham wrote: Can you guarantee that every jar in the maven repo has a manifest with its version in it? I certainly don't believe so. Not every jar in the repo was even built with maven. We recently realized we were packaging two versions of wstx-asl, because the groupIds changed and so maven considered them different artifacts. Now if you renamed the jar without the version, you won't know (a) you have a problem, (b) which version was chosen without some deep digging. Being able to see your resolved deps and their versions at a glance is a good thing. -Original Message- From: Ian Springer [mailto:[EMAIL PROTECTED] Sent: Tuesday, July 25, 2006 4:40 PM To: Maven Users List Subject: RE: deploying jars without version information Isn't that what MANIFEST.MF files are for? | -Original Message- | From: Mike Perham [mailto:[EMAIL PROTECTED] | Sent: Tuesday, July 25, 2006 2:23 PM | To: Maven Users List | Subject: RE: deploying jars without version information | | 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: deploying jars without version information
Can you guarantee that every jar in the maven repo has a manifest with its version in it? I certainly don't believe so. Not every jar in the repo was even built with maven. We recently realized we were packaging two versions of wstx-asl, because the groupIds changed and so maven considered them different artifacts. Now if you renamed the jar without the version, you won't know (a) you have a problem, (b) which version was chosen without some deep digging. Being able to see your resolved deps and their versions at a glance is a good thing. -Original Message- From: Ian Springer [mailto:[EMAIL PROTECTED] Sent: Tuesday, July 25, 2006 4:40 PM To: Maven Users List Subject: RE: deploying jars without version information Isn't that what MANIFEST.MF files are for? | -Original Message- | From: Mike Perham [mailto:[EMAIL PROTECTED] | Sent: Tuesday, July 25, 2006 2:23 PM | To: Maven Users List | Subject: RE: deploying jars without version information | | 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]
RE: deploying jars without version information
| -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]
RE: deploying jars without version information
Isn't that what MANIFEST.MF files are for? | -Original Message- | From: Mike Perham [mailto:[EMAIL PROTECTED] | Sent: Tuesday, July 25, 2006 2:23 PM | To: Maven Users List | Subject: RE: deploying jars without version information | | 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]
Re: deploying jars without version information
Use the Antrun plugin: http://maven.apache.org/plugins/maven-antrun-plugin/ to run an Ant script, and attach that to the package phase of your Maven build. - Stephen On 7/25/06, Trent Albright <[EMAIL PROTECTED]> wrote: > 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! =) > 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. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Stephen Duncan Jr www.stephenduncanjr.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
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! =) 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. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: deploying jars without version information
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]
RE: deploying jars without version information
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]
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]
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]
RE: deploying jars without version information
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]
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]
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]
deploying jars without version information
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
