Hi,

I just was warned about a strange behaviour in dependency resolution.

Having 3 projets A, B, C

C creates an artifact with a classifier, beeing configured as a user setting
"env" property (using jar-plugin classifier parameter). Running mvn install
on C creates C-1-<env>.jar

B has a dependency on C, with classifier ${env}. Running mvn install on B
works fine, and resolve C-1-<env>.jar

A has a dependency on B. Running mvn install on A fails with :
Missing:
----------
1) test:c:jar:${env}:1


Is this a known bug ? (I can't find one in Jira)
or maybe just a bad practice :)


Nicolas

Reply via email to