[
https://issues.jboss.org/browse/JBIDE-15401?page=com.atlassian.jira.plugi...
]
Rob Stryker resolved JBIDE-15401.
---------------------------------
Assignee: Rob Stryker
Resolution: Done
In general this is fixed in master, but it's not 100% for me. The only remaining
errors is that apitools is angry that I set 2.4 as the introduction for some new APIs
which exist in maintenance currently. The api's were added for astools 2.4.101 in
maintenance, and, since apitools is comparing master to baseline (jbds7.0.0.GA) it
doesn't like it.
My only options here are to either change the since tags to 2.5 (which would be
innaccurate) or to ignore the few errors that it doesn't like. So, for now, I choose
to ignore those few.
Most of the other complaints were about things like my Messages class being in a public
package, so additions to it count as new API, etc etc. Several small things like this,
but absolutely no critical api breakages.
CLONE - jbosstools-server API Compatibility for master
-------------------------------------------------------
Key: JBIDE-15401
URL:
https://issues.jboss.org/browse/JBIDE-15401
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: server
Affects Versions: 4.1.1.Alpha1
Reporter: Rob Stryker
Assignee: Rob Stryker
Priority: Blocker
Labels: api-compatibility
Fix For: 4.2.0.Alpha1
Verify Latest version from jbosstools-server/master branch has no API Compatibility
problems.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira