Hi, > As I added the release stuff to the build to the develop branch after the 4.2 > release, I doubt I could actually safely release 4.2 revision with this. I > would much more think that eventually releasing a 4.2.1 with maven artifacts > instead and pack in the changes you and Alex provided since the release.
If we're got fixes that need to be there in order to make a working mavin release then we should make a 4.2.1 (or 4.3) release at some point. Re publishing the 4.2 jars as they are now, IMO it would be counter productive to publish stuff that's (slightly) broken. Given the changes since 4.2 are minimal and easily reviewed why not just go with a new release sooner rather than later? Thanks, Justin
