4
Setting:
I have 10 customers, 3 of them use Websphere , 10 use Tomcat, 7 use jboss.
in the pom.xml
<profile>
<id>cliente01</id>
<dependencies>
<!-- depencias para tomcat-->
</dependencies>
</profile>
<profile>
<id>cliente02</id>
<dependencies>
<!-- depencias para tomcat-->
</dependencies>
</profile>
<profile>
<id>cliente03</id>
<dependencies>
<!-- depencias para tomcat-->
</dependencies>
</profile>
<profile>
<id>cliente04</id>
<dependencies>
<!-- depencias para jboss-->
</dependencies>
</profile>
<profile>
<id>cliente04</id>
<dependencies>
<!-- depencias para jboss-->
</dependencies>
</profile>
...
That way it works, but for all customers who use it tomcat
the dependences keep repeating (the same for jboss and Websphere).
There is a more efficient way to do this?
I was expecting something like:
<profile>
<id>jboss</id>
<dependencies>
<!-- depencias para jboss-->
</dependencies>
</profile>
<profile>
<id>tomcat</id>
<dependencies>
<!-- depencias para tomcat-->
</dependencies>
</profile>
<profile>
<id>websphere</id>
<dependencies>
<!-- depencias para websphere-->
</dependencies>
</profile>
<profile>
<id>cliente01</id>
<useProfile>jboss</useProfile>
</profile>
<profile>
<id>cliente02</id>
<useProfile>tomcat</useProfile>
</profile>
...
Because you don’t put the libs that are specific to each server in the libs folder of each server.. and just leaves the libs the application uses in the project pom? so you wouldn’t have more repeated libs..
– LeoCBS
It wouldn’t work. I create a . War and deliver to the client. The client itself is who manages the server, I only deliver application.
– Bruno Rozendo