[jbosstools-issues] [JBoss JIRA] (JBIDE-10367) Central's DefaultJBossCentralConfigurator in M5 points at jbosstools-directory.xml from http://download.jboss.org/jbosstools/updates/nightly/core/trunk/jbosstools-directory.xml

[Nick Boldt (Commented) (JIRA)]

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

Nick Boldt commented on JBIDE-10367:
------------------------------------

OK, so when building nightlies we'll need to pass in a parameter from Jenkins to the build to override this, or else we'll keep getting confused jiras asking where the latest Central is (because the nightly build's plugin will always point at the last dev milestone's discovery plugin).

Meanwhile, should the trunk version still point at trunk? If so, then we'll have to keep re-committing this change every time we branch. Yuck.
                
> Central's DefaultJBossCentralConfigurator in M5 points at jbosstools-directory.xml from http://download.jboss.org/jbosstools/updates/nightly/core/trunk/jbosstools-directory.xml
> --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBIDE-10367
>                 URL: https://issues.jboss.org/browse/JBIDE-10367
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: central
>    Affects Versions: 3.3.0.M5
>            Reporter: Nick Boldt
>            Assignee: Max Rydahl Andersen
>            Priority: Blocker
>             Fix For: 3.3.0.M5
>
>
> Where should the M5 version of JBoss Central's DefaultJBossCentralConfigurator class look for the jbosstools-directory.xml file?
> It currently points at http://download.jboss.org/jbosstools/updates/nightly/core/trunk/jbosstools-directory.xml, which is the trunk version.
> It could instead point at http://download.jboss.org/jbosstools/updates/nightly/core/3.3.indigo/jbosstools-directory.xml, the branch version. HOWEVER, once we move this site from nightly/ to development/ that URL won't work anymore.
> So should we point it at the aliased milestone site...
> http://download.jboss.org/jbosstools/updates/development/indigo/jbosstools-directory.xml (currently points at M4's discovery plugin)
> or the actual physical location of the milestone site, eg., 
> http://download.jboss.org/jbosstools/updates/JBossTools-3.3.0.M4/jbosstools-directory.xml

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira