[jbosstools-issues] [JBoss JIRA] (JBIDE-11111) create Jenkins jobs to build + publish JBT & JBDS Core Central discovery plugins

[Nick Boldt (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-11111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12736213#comment-12736213 ] 

Nick Boldt commented on JBIDE-11111:
------------------------------------

Already have features - they're used to stick the plugins onto the sites, which is non-ideal when we need to update Central discovery plugin between releases.

* https://github.com/jbosstools/jbosstools-central/tree/master/central/features/org.jboss.tools.central.discovery.feature
* https://svn.jboss.org/repos/devstudio/trunk/product/features/com.jboss.jbds.central.discovery.feature/

What we want instead are two jobs (or one with parameters) that will:

a) build the plugin

* org.jboss.tools.central.discovery_*.jar
* com.jboss.jbds.central.discovery_*.jar

b) publish plugin jar to standard location

* http://download.jboss.org/jbosstools/updates/JBossTools-4.0.0.Beta2.core/plugins/org.jboss.tools.central.discovery_1.1.0.Beta2-v20121114-2258-B36.jar
* https://devstudio.jboss.com/updates/6.0-staging/discovery/com.jboss.jbds.central.discovery_6.0.0.CR1-v20121118-2035-B111.jar

c) (re)generate *discovery.xml to point at updated jar. This step must not simply overwrite the old file, but edit a single line in it so that SOA entry is not wiped out.

* http://download.jboss.org/jbosstools/updates/development/juno/jbosstools-directory.xml
* https://devstudio.jboss.com/updates/6.0-staging/devstudio-directory.xml

* http://download.jboss.org/jbosstools/updates/stable/indigo/jbosstools-directory.xml
* https://devstudio.jboss.com/updates/5.0/devstudio-directory.xml
                
> 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.jboss.tools.central.discovery/
> 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