[jbosstools-issues] [JBoss JIRA] (JBIDE-13599) externalize Central site URL into a Preference within Eclipse/JDBS so that testing or mirroring is easier

[Nick Boldt (JIRA)]

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

Nick Boldt commented on JBIDE-13599:
------------------------------------

The usecase I need for testing is simply this:

{code}
./jbdevstudio -Dcentral.URL=http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio.product_70/central/
{code}
which would cause this in the plugin.xml:
{code}
<siteUrl="$\{central.URL\}">
{code}
to become this:
{code}
<siteUrl="http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio.product_70/central/">
{code}

But if I don't pass in a value for central.URL, I would instead get the default value set in plugin.properties:

{code}central.URL=http://download.jboss.org/jbosstools/updates/stable/kepler/central/core/ {code}
or
{code}central.URL=https://devstudio.jboss.com/updates/7.0/central/core/{code}

Isn't that simpler than this prop1/prop2/suffix stuff? 

*Just need a default value in .properties file w/ option to override via commandline.*
                
> externalize Central site URL into a Preference within Eclipse/JDBS so that testing or mirroring is easier
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: JBIDE-13599
>                 URL: https://issues.jboss.org/browse/JBIDE-13599
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: central
>    Affects Versions: 4.1.0.Alpha1
>            Reporter: Nick Boldt
>            Assignee: Snjezana Peco
>             Fix For: 4.1.0.Alpha2
>
>
> As discussed in https://issues.jboss.org/browse/JBDS-2469?focusedCommentId=12755106&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-12755106 testing Central is tricky if it's not properly bootstrapped, and bootstrapping is hard when we're on an early Alpha and don't want bits to be public before they've passed QE.
> A better approach than having the update site URL used in Central's discovery plugin.xml hardcoded into that file would be to have it read from a Preference in Eclipse or JBDS. This would allow it to be overwritten/overridden should a user want to test installation from a different URL than the default value. 
> This might even make it possible to have the same discovery plugin used for JBT and JBDS (assuming the list of connectors were the same, and certification was to appear for both instances) simply by having the preference changed to a different default URL when installing JBT or JBDS BYOE.

--
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