[
https://issues.jboss.org/browse/JBIDE-15285?page=com.atlassian.jira.plugi...
]
Denis Golovin edited comment on JBIDE-15285 at 9/11/13 2:48 AM:
----------------------------------------------------------------
Adding new class means changing internal implementation and that leads to version update
anyway not for minor but for service part of version.
I did pushed it because I was not using API Tooling yet at that point and it is not clear
without *.internal.* in package name, that package is actually private.
Updating 1.0.0 to 1.1.0 means you are now free to add any new public API packages in 4.2.x
stream :)
was (Author: dgolovin):
Adding new class means changing internal implementation and that leads to version
update anyway not for minor but for service part of version. So I am going to close PR
request and update description
Increment minor version of jbosstools-base/foundation submodule
---------------------------------------------------------------
Key: JBIDE-15285
URL:
https://issues.jboss.org/browse/JBIDE-15285
Project: Tools (JBoss Tools)
Issue Type: Task
Components: common/jst/core
Affects Versions: 4.2.0.Alpha1
Reporter: Denis Golovin
Assignee: Denis Golovin
Labels: versioning
Fix For: 4.2.0.Alpha1
New class
[
Trace|https://github.com/jbosstools/jbosstools-base/commit/0e97d80209db88...]
was introduced in Public API of foundation submodule, thus minor version should be
incremented.
1.0.0-SNAPSHOT -> 1.1.0-SNAPSHOT
--
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