Hi Curtis, I don't want to have the URL of my in-house Maven repository manager out in the open.
Regards, -Max On 03/10/2016 12:29 PM, Curtis Rueden wrote:
Hi Max, Why do you need two different parents? What configuration is different between your "wild" parent and your internal one? Would it be sufficient to enclose the internal-specific configuration (e.g., distributionManagement) in a profile? This technique is what my OSS projects do [1]. Regards, Curtis [1] https://github.com/scijava/pom-scijava/blob/pom-scijava-9.6.0/pom.xml#L1686-L1701 On Thu, Mar 10, 2016 at 2:20 PM, Max Spring <m2spr...@springdot.org> wrote:What's the best structure for a (multi-module) Maven project which should build "in the wild" without any Maven repository manager and can easily build within my organization where deployments should happen to my Maven repository manager? Ideally, I would have two different paren POMs for each situation. But unfortunately, I can't use a Maven property to pass the correct value for each situation, because the property expression in the parent POM reference doesn't get interpolated, if I try something like <parent> <groupId>org.example</groupId> <artifactId>${root.pom}</artifactId> <version>1.0-SNAPSHOT</version> <relativePath/> </parent> ... <properties> <root.pom>wild-parent</root.pom> </properties> Added a minimalistic project which shows a crude approach to solve this by patching the parent POM via sed: https://github.com/m2spring/wild-inhouse-hybrid-example -Max --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
--------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
