> Another way to handle this might be to set the conflicting libraries as
> "provided" on both systems and make up run-time jars that are installed
> in the container's (tomcat or Websphere) shared library.
> This way you could run the same WARs on both environments.
> You would just need an assem
message in context:
http://maven.40175.n5.nabble.com/how-to-copy-dependencies-related-to-one-profile-tp5668047p5670743.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubsc
ow-to-copy-dependencies-related-to-one-profile-tp5668047p5670743.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: us
alesky wrote:
> I did some test
>
> and i undestant that it take always the dependences of the profile that is
> configured has default
>
>
> true
>
>
> in fact if i change the activation default in the production environment
> are copied only that dependences
>
> but this doesn't resolve my
> but this doesn't resolve my problem becouse i have to change every time the
> pom file to generate the production version and put back after the
> generation.
Perhaps instead of using profiles and 1 project, you should set this
up to use more than 1 project (one for dev, one for prod) and get ri
s based on the profile?
thanks
--
View this message in context:
http://maven.40175.n5.nabble.com/how-to-copy-dependencies-related-to-one-profile-tp5668047p5668047.html
Sent from the Maven - Users mailing list archive at
have to change every time the
pom file to generate the production version and put back after the
generation.
--
View this message in context:
http://maven.40175.n5.nabble.com/how-to-copy-dependencies-related-to-one-profile-tp5668047p5668094.html
Sent from the Maven - Users mailing list archi
