Thanks Patrick, that helps
Le vendredi 24 novembre 2023 à 17:04:55 UTC+1, Patrik Karlström
<pat...@trixon.se> a écrit :
I asked the very same thing earlier on this list and I ended up using standard
maven profiles.It's good for excluding modules too, and adding closed source
modules to an open source pom. The reference will be visible but not the
content.
Note that you have to select the correct profile in both parent and application
project if used.If you would like to use more than one profile you can add a
custom with multiple profiles, or add it to your maven command with -P profile1
-P profile2.
Hopefully you can find some information
here:https://github.com/trixon/mapton/blob/00e194cdae8fa7f4892298af8997c7e37ae6597a/pom.xml#L567https://github.com/trixon/mapton/blob/00e194cdae8fa7f4892298af8997c7e37ae6597a/application/pom.xml#L336
As you can see there is an unstable profile too for the brave. :)
/Patrik
Den ons 22 nov. 2023 kl 21:25 skrev Jerome Lelasseux
<lelass...@yahoo.com.invalid>:
Hello,
I have 2 variants A and B of my NB platform app. B is just variant A + 2
additional modules and some branding.
With Ant it was easy to setup. B only contained the 2 extra modules+branding
and I just had to update cluster.path in B's platform.properties to also
include variant A's cluster:
cluster.path=${nbplatform.active.dir}/platform:../variantA/build/cluster
I ported the app to Maven, but it's not clear to me how can achieve the same
mechanism with Maven. Any recommandation?
Jerome
