Classifier and dependencies

Hi, I have a project that I need to build for different JDKs; Because we use JAXB on jdk1.4.2, 5 and 6I need to specify different dependencies for the JAXB version from 1.0.6 to 2.0.5. So I have different profiles for each jdk version target. I have set a classifier so that I get 3 different

Re: Classifier and dependencies

Currently, I have set my version tag to : version${parent.version}-${classifier}/version and I set the classifier property in my profiles but this doesn't feel good. 2007/11/19, Emmanuel Hugonnet [EMAIL PROTECTED]: Hi, I have a project that I need to build for different JDKs; Because we use

Re: [m2-b1] classifier-specific dependencies colliding with generic dependencies

On 9/28/05, Brett Porter [EMAIL PROTECTED] wrote: I think its because the project you are depending on is in the reactor, and its probably a bug. Basically, its trying to use the built version of that project, but projects are only identified by group:artifactId Okay - filed issue MNG-1041.

[m2-b1] classifier-specific dependencies colliding with generic dependencies

Folks, It seems like there is a collision between dependencies from the same project but with different classifiers, causing only the main dependency artifact to be present on the compilation classpath. This example will look familiar to anyone following a previous public mock api thread. :-)

Re: [m2-b1] classifier-specific dependencies colliding with generic dependencies

I think its because the project you are depending on is in the reactor, and its probably a bug. Basically, its trying to use the built version of that project, but projects are only identified by group:artifactId - Brett On 9/28/05, John Fallows [EMAIL PROTECTED] wrote: Folks, It seems like