[
https://issues.jboss.org/browse/JBIDE-13316?page=com.atlassian.jira.plugi...
]
Mickael Istria commented on JBIDE-13316:
----------------------------------------
I created 2 branches named "tp-4.2.0.c" and "tp-4.2.1.a" which contain
different versions of target platforms.
See graph here:
https://github.com/jbosstools/jbosstools-build/network
So "miminal" currently becomes referencing branch tp-4.2.0.c and
"maximal" is tp-4.2.1.a.
[~nickboldt] [~maxandersen] Can I have your feedback on this approach? I think this is
starting to show that target-platform and parent pom are now so loosely coupled that it
does not make sense to have them in the same git repository.
Imporve versioning for TP using standard Maven way
--------------------------------------------------
Key: JBIDE-13316
URL:
https://issues.jboss.org/browse/JBIDE-13316
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: target-platform
Reporter: Mickael Istria
Assignee: Mickael Istria
Fix For: 4.1.0.Alpha1
Currently, we deal with explicit versions in folder names that make it confusing to
understand how target-platforms are versioned.
Instead, we should use usual Maven way and Git branches: one Git branch for each version
of TPs.
--
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