On Aug 8, 2011, at 14:31, Kris Verlaenen wrote:
Aren't those just different plugins for the different versions of jBPM?
Yes, but some are used by both thus doesn't really matter the versions are matching
In theory I guess that we should just have one version on trunk and
all other versions should have been branches.
Why ? then you wouldn't be able to support multiple versions easily :) Tools branching
!= runtime branching.
Since we're not immediatly planning any further releases with
that codebase, do you think it's still worth the effort looking at this?
Well, up to you guys - you are the one having to maintain/bump the versions when doing
Max Rydahl Andersen wrote:
> Hi Kris/Koen,
> jbpm has a bunch of different versions in play:
> Bundle-Version: 1.0.0.qualifier
> Bundle-Version: 1.2.0.qualifier
> Bundle-Version: 1.3.0.qualifier
> Bundle-Version: 3.2.0.qualifier
> Bundle-Version: 3.4.0.qualifier
> Bundle-Version: 4.3.0.qualifier
> Bundle-Version: 4.4.0.qualifier
> Any sense of aligning these so there is a uniform version for the jbpm module ?