This looks to me like a bug (or at least an oversight) in the dependency
plugin. I presume this is what you are using to copy all the jars into a
directory before building your installer?
Duplicate artifactIds are not normally a problem for maven; the classpath it
builds for compiling,
Hi Jeff,
Thanks for this but it is something we already tried. Although that does
change the name of the
generated jar file, the name is lost when it gets placed into the maven
repository. When it gets installed,
the name reverts to ${artifactId}-${version}.jar in a directory mad from
Thanks Lee... I had a feeling this would be the case :D So I have
witten myself a perl script to go around all the poms and change the
artifactId's for all the dependancies. The joy of legacy code :)
Lee Meador wrote:
1 isn't going to work because of how Maven finds files in the repo by
If it did that, it would be marvellous :)
Simon Kitching wrote:
This looks to me like a bug (or at least an oversight) in the dependency plugin. I
presume this is what you are using to copy all the jars into a directory before building
your installer?
Duplicate artifactIds are not normally a
I'd imagine that this would cause an issue when making a distribution, or a
war, also.
On Jan 30, 2008 3:42 AM, Simon Kitching [EMAIL PROTECTED] wrote:
This looks to me like a bug (or at least an oversight) in the dependency
plugin. I presume this is what you are using to copy all the jars
Hi all,
I have two separate systems that I build using maven.
One has groupId:com.volantis.synergetics artifactId:repository-api
version:5.0-SNAPSHOT. This system consists of around 50 artifacts.
The second has groupId:com.volantis.mcs artifactId:repository-api
version:5.0-SNAPSHOT.
1 isn't going to work because of how Maven finds files in the repo by
tracing down the file system path based on the group id and then going down
the path some more based on the artifact id and expecting the jar file to
have a matching name.
The real solution is to change the artifactId, which
Steve,
you can change the name of the JAR being generated through the finalName
tag: it specifies the name of the file being generated. By default, it is
equal to ${artifactId}-${version}.${packaging} so you may change it to:
${groupId}-${artifactId}-${version}.${packaging} for your purpose.
