You will be trying to deploy the pom twice (once for each build run) which the release repository policy of your Nexus instance will not let you do. Thus, the build will fail (as it should). But you might be using some tooling will less checking...
/Anders On Thu, Apr 14, 2011 at 16:15, Jörg Schaible <joerg.schai...@scalaris.com>wrote: > Hi Anders, > > Anders Hammar wrote: > > > How are you executing one build run that produces both artifacts? Are you > > really deploying to a repository? I can't see how that would work, but I > > could be missing something. > > Why do you have to? Even for a release you don't have to release the > component in both versions *at once* although it can be of advantage to > keep > the versions in sync. > > For snapshots it depends on your orgnization. For CI I would actually build > two times with a linked build plan, i.e. when the Java 6 version succeeds > proceed with a Java 5 setup. > > See, it is like working on two branches, but with shared code. Since it is > only the version that is different, you have even an automated upgrade > path. > If you Java 5 app is switching to Java 6 you can use the "newer" branch. > It's compile time compatible only, but that does not matter, because the > switch from JDBC 3 to JDBC 4 is also not binary compatible. > > And, yes, I agree that profiles should normally not be used to select > different artifacts, it's just for this case where it gets handy without > doing harm if you control the version in a depMgmt section anyway for the > client project ;-) > > - Jörg > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
