dependencyManagement and classifier

[nicolas de loof]

Hello,

I'd like to force a dependency to be used with a classifier.

Here is my use case :

My business domain model (project-domain) creates a second artifact with
classifier instrumented based on Hibernate InstrumentTask.
All my project modules depends on domain
In my webapp, I'd like to replace the base domain.jar with the instrumented
one.

Using dependencyManagement works to force a version of dependencies, but has
no effect on classifier. Is there any way to avoid multiple exclusions on
all modules dependencies ?

Re: dependencyManagement and classifier

[nicolas de loof]

I've found a (not so ugly) solution :

dependencyManagement is used to force domain jar scope to provided, so
that it is excluded from the war, and a dependency is added to
domain-instrumented.jar with scope runtime.

Nicolas


2008/7/21 nicolas de loof [EMAIL PROTECTED]:

 Hello,

 I'd like to force a dependency to be used with a classifier.

 Here is my use case :

 My business domain model (project-domain) creates a second artifact with
 classifier instrumented based on Hibernate InstrumentTask.
 All my project modules depends on domain
 In my webapp, I'd like to replace the base domain.jar with the instrumented
 one.

 Using dependencyManagement works to force a version of dependencies, but
 has no effect on classifier. Is there any way to avoid multiple exclusions
 on all modules dependencies ?