between 3.2.x and 3.3.0.GA streams, the vast majority of the 650+ line diff file is configuration files, build.xml, pom.xml, etc. Other changes include a 1 line change to an extension schema (changing minOccurs), the creation of one new API (duplicates an old API but adds a HashMap for extensions), The creation of one other api (duplicates a previous but adds an MBeanServerConnection as a parameter to prevent a new connection for each request), some null checks, and the creation of an error root if a connection has failed.

What this means is that users of jmxtools can easily install 3.3.x jmxtools into 3.2.x (or it appears so from the diff). With no APIs removed, any old extenders (3.2.x astools for example) will have all of their required APIs in tact and unchanged.

However, newer versions of astools cannot use 3.2.x jmx tools, so that's a lack of backwards compatibility.

I propose that 3.3.x should have had a jmx version of 1.2.100, since it is backwards compatible with previous versions, and since the number of changes is extremely small. (I do not know when the last time jmxtools' version was changed. It's possible it's had an unchanging version string for several releases, which would be bad, but in the past.)

I would therefore suggest that we change maintenance version to 1.2.100 and trunk to 1.2.200, since there are no expected large-scale changes or revisions to be made to JMX any time soon.