> A branch called 4.0.2 should not contain 4.0.3-SNAPSHOT, regardless of how it was created.
I also don't think that EE4J_8 should have a SNAPSHOT version in it. It is 4.0.2, so it should be at 4.0.2 - no SNAPSHOT.
This is what almost all if not all jobs are using. They take the SNAPSHOT version from the EE4J_8 branch. Both for spec and impl projects:
Well other projects doing it still does not make it desirable.
So essentially that says the EE4J_8 branch is a development branch of which multiple releases will be pulled.... except the incremented development version is ending up back in the the release branch and not back in EE4J_8 branch? It just does not make sense however you cut it. Oh well, I guess we are at the whim of other EE4J_8 projects and it is best to go with the other projects. Hopefully they will eventually see sense.
Still, no reason to not keep master up to date. So we should at the very least merge 4.0.2 to master so it has all changes and is setup for 4.0.3-SNAPSHOT. I'd still prefer it to be called 4.0.x so that any more significant work can be done in branches called 4.1.x or 5.0.x
regards
