Hi, On Mon, Jul 18, 2011 at 10:49 AM, Fabian Christ <[email protected]> wrote: > ...facing the problem that we may want to exclude some artifacts from a > release we need a way to manage this. I see the problem that at the > moment everything in trunk is aligned to be in a release. How would I > manage to exclude some artifacts and run it through Hudson? This would > change the trunk...
You could just use a Maven profile, so that be default the trunk builds only what's in the release. > Some integration tests may need to be disabled... Those can check if the required bundles are present (either via OSGi console or by making test requests), and disable themselves if not. The best would be for the bundles to supply their own integration tests, but we can probably find an intermediate solution if we don't have time to set this up. > People currently working on code that will not be in the next release > may have the problem that they can't commit their stuff for the time > the trunk is freezed for the release... Using Maven profiles would limit the freeze time to a minimum. > > I read [1] linked from [2] and I'm thinking about creating such a > stable branch for doing releases.... I'd rather just create an svn tag when doing the release (maven release plugin does that anyway), and if we need a branch later we can always create it from that tag. -Bertrand
