[
https://issues.jboss.org/browse/JBIDE-15252?page=com.atlassian.jira.plugi...
]
Mickael Istria commented on JBIDE-15252:
----------------------------------------
I don't think we want to have locus depending on a release train. It only depends on
some Orbit bundles (none is a singleton) which will be forever available and some Maven
artifacts, there is nothing at all which makes that locus depends on a release train.
I really think we need versioned URLs, such as
http://download.jboss.org/jbosstools/updates/stable/locus/1.0.0.Final , and why not a
shortcut to the latest one in
http://download.jboss.org/jbosstools/updates/stable/locus/latest . Those URLs are only
meant to be used in target-platform definitions; however we clearly prevent
target-platforms to use URLs with mutable content because it may break build repeatability
if content of site changes whereas older TP does not. So I don't see a big value in a
"latest" URL neither.
Agree on a release URL for locus
--------------------------------
Key: JBIDE-15252
URL:
https://issues.jboss.org/browse/JBIDE-15252
Project: Tools (JBoss Tools)
Issue Type: Task
Components: locus
Reporter: Mickael Istria
Fix For: 1.0.0-LOCUS
In order to make it release URL easy to remember and predictable, we need to agree on a
pattern for Locus releases.
--
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