Well, when our deployment team wants to install eg a new version of a component, they just download it from the repo. And they don't run maven, for them the repo is just a download server, which is kind of natural, or? Why keep another copy of all artifact versions etc? Is this a very unusual way of using a maven repo?
On 23/10/2008, Stephen Connolly <[EMAIL PROTECTED]> wrote: > But why are you pulling them from your repo by hand. > > When we need to get the artifact we copy it out of the local repo with > either the dependencies:copy goal in a little project, or with maven ant > tasks > > Both of these allow us to control the name. > > 2008/10/23 Kent Närling <[EMAIL PROTECTED]> > >> Exactly what we wanted too! >> >> But when I do this, the filename in the repository gets the default name >> anyway!! >> >> When running it locally for instance, I get the following message: >> [INFO] Installing >> >> C:\Workspaces\main\requestparser\requestparser-servlet\target\requestparser-servletxx.war >> to C:\Documents and >> >> Settings\kent\.m2\repository\com\seamless\ers\requestparser-servlet\1.0rc3-SNAPSHOT\requestparser-servlet-1.0rc3-SNAPSHOT.war >> >> ie, it seems the install plugin simply ignores the <finalName> tag?!? >> >> I mean, obviously it is nice to have a war file have a fixed name since it >> usually dictates the default path to the context in the container and you >> don't want the version in that?!? >> >> Naturally it is possible to manually re-name it, but that kind of defeats >> the purpose of a company repository if you have to re-name the files >> before >> you use them?!? >> >> 2008/10/23 Stephen Connolly <[EMAIL PROTECTED]> >> >> > For us we use it to ensure that the war file in target is always the >> same, >> > so that other scripts we have can pick it up irrespective of the >> > version. >> > >> > If you are pulling the file out of the repo, you can always specify the >> > name >> > to pull it out of the repo as >> > >> > 2008/10/23 Kent Närling <[EMAIL PROTECTED]> >> > >> > > What IS really the purpose of <finalName>? >> > > >> > > Apparently, the install plugin ignores the artifact name when >> > > deploying >> > it >> > > to the repository anyway?? >> > > >> > > We would like to have a version-less filename on the artifact in the >> > > repository (the version is in the path anyway), is this possible? >> > > >> > > If not, what is the real purpose of <finalName> if it is not used for >> the >> > > name of the artifact/file in the end anyway... ? >> > > >> > > Best regards >> > > Kent >> > > >> > >> >> >> >> -- >> Kent Närling >> >> System Architect >> SEAMLESS >> Dalagatan 100, 8 tr, 113 43 Stockholm, Sweden >> Phone: +46 8 5648 7800, fax: +46 8 5648 7823 >> Mobile: +46 70 836 9925 >> Mail: [EMAIL PROTECTED] >> www.seamless.se >> > -- Kent Närling System Architect SEAMLESS Dalagatan 100, 8 tr, 113 43 Stockholm, Sweden Phone: +46 8 5648 7800, fax: +46 8 5648 7823 Mobile: +46 70 836 9925 Mail: [EMAIL PROTECTED] www.seamless.se --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
