But Maven can filter application.xml so it isn't a problem. Seriously I can understand when you deploy in a external location but why would you want to mess up Maven in his local respository? How do you want Maven to manage your artifact if you don't give him the informations it needs to do its work. It's like asking Eclipse to run based upon your own project descriptor.
A Maven repository should only be used by Maven and so follow it conventions. If you need to keep the jar in another format or to follow certain constraints for some reasons copy or link the file elsewhere in the filesystem. Simple as that. This what I always do and it works fine. On 4/24/06, Mike Perham <[EMAIL PROTECTED]> wrote: > Usually because you have something like a reference by name in something > like EAR's application.xml and don't want to update that file every time > the version changes. Having changes ripple to modules downstream is a > nightmare to deal with and so referring without version solves that > problem. > > I agree that removing the version "just because" is a poor decision. > > -----Original Message----- > From: Wayne Fay [mailto:[EMAIL PROTECTED] > Sent: Monday, April 24, 2006 1:40 PM > To: Maven Users List > Subject: Re: Removing version when creating a jar > > I've never understood this desire to remove version numbers from Jars > built by Maven... In fact, I can't stand it when I run across a jar with > no version number and have to dig into it to find a version either in a > manifest or other random file. > > Wayne > > On 4/24/06, Arik Kfir <[EMAIL PROTECTED]> wrote: > > sorry for butting in - but why would you want to do that? > > > > On 4/24/06, Nic Holbrook <[EMAIL PROTECTED]> wrote: > > > > > > What I do to get around this is let maven do its thing then when I > > > deploy the jars, I use an ant task to copy the correct file out to > > > my server using the name minus the version. > > > > > > RobJac wrote: > > > > > > >I can actually remove the version when i package, but when i > > > >execute mvn installl for the project it again places the > > > >project-version.jar in my localrepository under the following > > > >folder path > > > ><localRepository>/{groupId}/{version}/project-version.jar. I am > > > >facing an issue when i am trying to create an EAR. Since all the > > > >projects are > > > getting > > > >created from the the local repository all the projects are getting > > > appended > > > >with version number which I want to avoid. Please let me know how i > > > > >can avoid gettuing the version number appended when i execute mvn > > > >install > > > for a > > > >project or Can i over ride the name of the dependency project jars > > > > >when they are fetched from the repository? > > > >-- > > > >View this message in context: > > > http://www.nabble.com/Removing-version-when-creating-a-jar-t1438924. > > > html#a4012162 > > > >Sent from the Maven - Users forum at Nabble.com. > > > > > > > > > > > >------------------------------------------------------------------- > > > >-- To unsubscribe, e-mail: [EMAIL PROTECTED] > > > >For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > >[tch] > > > > > > > > > > > > > > > > > > > > > -------------------------------------------------------------------- > > > - To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > -- > > ______________________________________ > > Cheers, > > Arik Kfir [EMAIL PROTECTED] > > Linux user, number 415067 - http://counter.li.org/ > > http://corleon.dnsalias.org > > > > > --------------------------------------------------------------------- > 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]
