You want to potentially use profiles to manage your dependencies. There isn't 
the ability to add new scopes.

-----Original Message-----
From: Uldis Karlovs-Karlovskis [mailto:[email protected]] 
Sent: Monday, April 06, 2009 2:53 AM
To: 'Maven Users List'
Subject: RE: Additional dependecy scope

Hello again. Is anybody going to anser me? :(

Regards,
Uldis, C. T. Co
[email protected]
 

-----Original Message-----
From: Uldis Karlovs-Karlovskis [mailto:[email protected]] 
Sent: piektdiena, 2009. gada 3. aprīlī 12:43
To: [email protected]
Subject: Additional dependecy scope

Hello!

 

>From documentation I see there are scopes for managing dependency artifacts.
However, I need more of them. These are only to manage packaging and control
one tests package, but I have different tests per project (unit,
integration, selenium etc) and every of them should have some different jars
in classpath. Also I`m deploying the same project to tomcat, jboss and
websphere (there may be even different versions of them) so the EAR or WAR
package libraries may differ for any of them. From documentation I found
that Maven offers only a way to specify different libraries for WAR and EAR.

 

What are recommendations? I don`t want to split everything into smaller
projects just to get this functionality.

 

Uldis Karlovs - Karlovskis

Lead SCM Engineer

System Configuration Management

C.T.Co

Mobile: +371 29 345 210

 



---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to