I'm converting projects from M1 to M2. Due to restrictions imposed from "above" - I'm not allowed to change anything - including names of artifacts. In M1 implementation the artifacts did not contain versions in their names.
At this point I have over 100 artifacts that will be ftp-ed to an application server where those will be picked up and deployed. Actual deployment process is out of my hands - changing names of artifacts could in theory break something on a server side. Any ideas? Thanks, Dave On Tue, Jun 22, 2010 at 10:02 AM, Wendy Smoak <[email protected]> wrote: > On Tue, Jun 22, 2010 at 10:54 AM, D D <[email protected]> wrote: > > Is there an easy way to deploy an artifact such it doesn't include > version > > in its name? > > For example: when moduleA is deployed through 'mvn deploy' I > > get moduleA-X.Y-SNAPSHOT.jar but what I need is moduleA.jar. > > The Maven repo has a fixed structure, so you can't easily change how > the artifact gets deployed. (It's surely _possible_, but probably way > more work than you want to take on!) > > If you tell us what problem you're trying to solve by doing this, most > likely someone can offer a suggestion. > > Without knowing more, the Dependency plugin comes to mind -- the > dependency:copy goal can strip the version as it copies the artifact > to the desired location. > > Then again, it's entirely possible that you don't really *need* the > artifact without the version. :) > > -- > Wendy > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
