[
https://issues.jboss.org/browse/JBIDE-13316?page=com.atlassian.jira.plugi...
]
Mickael Istria commented on JBIDE-13316:
----------------------------------------
Also not really keen to change stuff that works in the Juno stream.
Why wouldn't we refactor/fix/improve this for Kepler, then MAYBE backport changes to
6.0.1/6.0.2 if needed? This issue is targeted for Kepler (4.1.0.Alpha1) but you're
making changes that affect the 6.x stream. :confused:
This is for sure something I want to change for Kepler. But our Kepler 6.x stream is
currently using the same targets as our Juno stream. jbosstools-build repo is already
branch for 5.0.x so making changes in master is not that critical as long as we can build
the 5.0.x branch.
I personally don't like "tp-" as a prefix, as it's
vague. Why not "target-" or "target-platform-"
Ok with "target-platforms-".
--
The issue is that we actively maintain 2 streams of Target Platforms. Those streams are
fully independent one from the other, and independent from parent. So it's not very
clear why some versions are in master whereas they may not be the one available in
parent.
That's why I'm suggesting such a change.
About making local diffs, it would mean that we'd need to rename the target/REPO
folder locally to checkout another branch and then compare. I don't think it's
that complicated.
Improve 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