Hi,
I've noticed a lot of the Felix poms are using ${pom.groupId} in their
dependencies
this is causing me grief as in some scenarios maven replaces this with my
_local_ project groupId, not org.apache.felix
for example, here it looks for "
my.example.project:org.apache.felix.shell:jar:1.0.0" !
[INFO]
------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO]
------------------------------------------------------------------------
[INFO] Failed to resolve artifact.
Missing:
----------
1) my.example.project:org.apache.felix.shell:jar:1.0.0
Try downloading the file manually from the project website.
Then, install it using the command:
mvn install:install-file -DgroupId=my.example.project -DartifactId=
org.apache.felix.shell \
-Dversion=1.0.0 -Dpackaging=jar -Dfile=/path/to/file
Path to dependency:
1) org.ops4j:maven-pax-plugin:maven-plugin:0.2.0-SNAPSHOT
2) org.apache.felix:maven-bundle-plugin:maven-plugin:1.1.0-SNAPSHOT
3) org.apache.felix:maven-obr-plugin:jar:0.1.0-SNAPSHOT
4) org.apache.felix:org.apache.felix.bundlerepository:jar:1.0.0
5) my.example.project:org.apache.felix.shell:jar:1.0.0
there is not much gain to using ${pom.groupId} as the group is unlikely to
change much, and even if one artifact
decides to change group what happens if some (or all) of its dependencies
want to retain the old group?
IMHO we should avoid using ${pom.*} variables in pom dependencies to be
certain which artifact it will pick up
WDYT?
--
Cheers, Stuart
