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

Nick Boldt (JIRA) jira-events at lists.jboss.org
Thu Nov 29 16:33:21 EST 2012


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

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

symlinks don't work consistently across devstudio.jboss.com and download.jboss.org; not a good idea.
since the pointer in question is the xml file, we need only publish a new jar, and update the xml file. It's like a symlink but without the danger of it not being read correctly on the server(s).

So, yeah, we already do what you're suggesting: multiple iterations of the discovery plugin, with a single master directory.xml file which refers to the latest/best one (for a given milestone/release).

Sorry about the mixing thing -- figured since these weren't strictly plugins in the sense that they're installed into Eclipse/JBDS and that they don't have source (except for plugin.xml and some images) there'd be little or no legal complaint with them co-existing in the same repo. But of course IANAL.
                
> 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


More information about the jbosstools-issues mailing list