It seems that some "API" which was used only a handful of times in the codebase was removed, and it's 3 callers were redirected to an already-existing API. In addition, as was my policy for this major release, dependencies were moved up to the most recent versions of eclipse plugins. This was done in archives and JMX, as an effort to set a new "base" from which versions would only change in the future if needed. It seems that was a bit over-reaching for archives and jmx, which changed very little and used no new API.
Either way, because of the removal of what was basically internal api, I would suggest that the recent release should have been 3.2.100 and not 3.2.1. I then believe trunk should be 3.2.200, since no major plans for revisions exist.
It seems that some "API" which was used only a handful of times in the codebase was removed, and it's 3 callers were redirected to an already-existing API. In addition, as was my policy for this major release, dependencies were moved up to the most recent versions of eclipse plugins. This was done in archives and JMX, as an effort to set a new "base" from which versions would only change in the future if needed. It seems that was a bit over-reaching for archives and jmx, which changed very little and used no new API.
Either way, because of the removal of what was basically internal api, I would suggest that the recent release should have been 3.2.100 and not 3.2.1. I then believe trunk should be 3.2.200, since no major plans for revisions exist.