Here is my final update,
I could not bind to the package phase as described in the documentation.
http://maven.apache.org/plugins/maven-dependency-plugin/usage.html (I copied
the template, set the variables as needed and issued 'mvn package' but the
copy was not triggered)
Maybe someone could shed some light on what I did wrong?
I configured it for use on command line as described in the second part. I
used the following template in my superpom:
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-dependency-plugin</artifactId>
<configuration>
<artifactItems>
<artifactItem>
<groupId>${project.groupId}</groupId>
<artifactId>${project.artifactId}</artifactId>
<version>${project.version}</version>
<type>${project.packaging}</type>
<destFileName>${project.build.finalName}.${project.packaging}</destFileName>
<overWrite>true</overWrite>
</artifactItem>
</artifactItems>
<outputDirectory>/mydirectory</outputDirectory>
</configuration>
</plugin>
Of course I'm setting the finalName for every project - something I had to
do anyway due to unrelated problems.
Thanks,
Dave
On Tue, Jun 22, 2010 at 12:50 PM, D D <[email protected]> wrote:
> I guess the repository is not an issue. I can't deploy the jars/wars/ears
> with artifact-x.z.y-snapshot name formatting.
>
> Since I will not use Maven's deployment mechanism I think I will resort to
> the dependency plugin. It will in a sense mimic what happens now. Artifacts
> are ftp-ed from M1 repository (jars/wars/ears directories) to final
> destination. I will just have one common directory instead of 3.
>
> Thank you Wendy for pointing me to Dependency plugin!
>
> If it works as intended I will share my solution soon.
>
> Thanks,
> Dave
>
>
> On Tue, Jun 22, 2010 at 11:17 AM, Larry Shatzer, Jr. <[email protected]>wrote:
>
>> I've not tried it, but I think Nexus has support for creating a M1
>> "virtual" repository that will "convert" a M2 to look like a M1
>> repository.
>> http://www.sonatype.com/books/nexus-book/reference/config-sect-manage-repo.html
>>
>> On Tue, Jun 22, 2010 at 10:00 AM, D D <[email protected]> wrote:
>> > 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]
>> >>
>> >>
>> >
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [email protected]
>> For additional commands, e-mail: [email protected]
>>
>>
>
