[
https://issues.jboss.org/browse/JBIDE-11111?page=com.atlassian.jira.plugi...
]
Mickael Istria commented on JBIDE-11111:
----------------------------------------
Main issue here is that we have interlinked versionned URLs.
Maybe we should consider versionned URLs of Discovery, and have a symlink or copy for each
version of JBT.
So jbosstools-discovery.xml for 4.1.0.Alpha1 would point to a
org.jboss.tools.central.discovery_4.1.0.Alpha1.jar that would be a copy or a link to a
concrete version of the jar. That way, we can update discovery without affecting JBT, and
if we want JBT to use the newer version, we only change the copy or the link on the site.
create Jenkins jobs to build + publish JBT & JBDS Core Central
discovery plugins
--------------------------------------------------------------------------------
Key: JBIDE-11111
URL:
https://issues.jboss.org/browse/JBIDE-11111
Project: Tools (JBoss Tools)
Issue Type: Task
Components: Build/Releng, central, updatesite
Affects Versions: 3.3.0.Beta1
Reporter: Nick Boldt
Assignee: Nick Boldt
Priority: Blocker
Fix For: 4.0.0.Alpha1-SOA, 4.0.0.CR1
Instead of tightly coupling the central discovery plugin [1] into the central component
builds, we need a way to respin this single plugin (and matching jbosstools-directory.xml
file) in case there are out-of-band changes needed (eg., remove JRebel because they
release a newer version which breaks in Central).
[1]
https://anonsvn.jboss.org/repos/jbosstools/trunk/central/plugins/org.jbos...
Max would like that we NO LONGER build this plugin as part of the whole central component
/ aggregate sites, but ONLY be buildable separately.
Also need to ensure that update sites no longer include central discovery plugins /
*-directory.xml files so they won't be accidentally installed by a user who
doesn't read instructions.
--
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