[jbosstools-issues] [JBoss JIRA] (JBIDE-10401) externalize URL for Central directory.xml file so it can be passed in via commandline when building or at runtime

[Nick Boldt (JIRA)]

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

Nick Boldt edited comment on JBIDE-10401 at 2/21/12 1:11 PM:
-------------------------------------------------------------

The above plan is in place. Awaiting respin of JBT agg build [1] to verify that new -Ptrunk profile works as expected. 

[1] https://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_trunk.aggregate/ >=4191

Doc'd here: https://anonsvn.jboss.org/repos/jbosstools/trunk/central/plugins/org.jboss.tools.central/template/README.txt

TO VERIFY IN TRUNK:
1. install fresh Indigo JEE
2. point at http://download.jboss.org/jbosstools/updates/nightly/core/trunk/ >=4191
 -> https://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_trunk.component--central/ >=400
    -> https://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_trunk.aggregate/ >=4191
3. install central feature, restart
4. verify that central plugin points at nightly site content

TO VERIFY after we branch for Beta1:

1. install fresh Indigo JEE
2. point at http://download.jboss.org/jbosstools/updates/nightly/core/3.3.indigo/ >=80
 -> https://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_stable_branch.component--central/ >=43
    -> https://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_stable_branch.aggregate/ >=80
3. install central feature, restart
4. verify that central plugin points at M5 (previous milestone) site content

TO VERIFY, check the Software/Update tab in Central and look at the Google Plugin + Web Toolkit installable:

If described as "Google Plugin for Eclipse (GPE) + Google Web Toolkit SDK (GWT)" we're reading from the trunk site.
If described as "Google Plugin for Eclipse (GPE) 2.5.1 + Google Web Toolkit SDK (GWT) 2.4.0" we're reading from the tip of Beta1 branch
If described as "Google Plugin for Eclipse (GPE) + Google Web Toolkit SDK 2.4.0 (GWT)" we're reading from from previous milestone site (M5).

                
      was (Author: nickboldt):
    The above plan is in place. Awaiting respin of JBT agg build [1] to verify that new -Ptrunk profile works as expected. 

[1] https://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_trunk.aggregate/ >=4169

Doc'd here: https://anonsvn.jboss.org/repos/jbosstools/trunk/central/plugins/org.jboss.tools.central/template/README.txt

TO VERIFY IN TRUNK:
1. install fresh Indigo JEE
2. point at http://download.jboss.org/jbosstools/updates/nightly/core/trunk/ >=4169
 -> https://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_trunk.component--central/ >=400
    -> https://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_trunk.aggregate/ >=4191
3. install central feature, restart
4. verify that central plugin points at nightly site content

TO VERIFY after we branch for Beta1:

1. install fresh Indigo JEE
2. point at http://download.jboss.org/jbosstools/updates/nightly/core/3.3.indigo/ >=80
 -> https://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_stable_branch.component--central/ >=43
    -> https://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_stable_branch.aggregate/ >=80
3. install central feature, restart
4. verify that central plugin points at M5 (previous milestone) site content

TO VERIFY, check the Software/Update tab in Central and look at the Google Plugin + Web Toolkit installable:

If described as "Google Plugin for Eclipse (GPE) + Google Web Toolkit SDK (GWT)" we're reading from the trunk site.
If described as "Google Plugin for Eclipse (GPE) 2.5.1 + Google Web Toolkit SDK (GWT) 2.4.0" we're reading from the tip of Beta1 branch
If described as "Google Plugin for Eclipse (GPE) + Google Web Toolkit SDK 2.4.0 (GWT)" we're reading from from previous milestone site (M5).

                  
> externalize URL for Central directory.xml file so it can be passed in via commandline when building or at runtime 
> ------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBIDE-10401
>                 URL: https://issues.jboss.org/browse/JBIDE-10401
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: Build/Releng, central, updatesite
>    Affects Versions: 3.3.0.M5
>            Reporter: Nick Boldt
>            Assignee: Nick Boldt
>            Priority: Critical
>             Fix For: 3.3.0.Beta1
>
>
> 1. Need to replace hardcoded variable
> {code}
>         private static final String JBOSS_DISCOVERY_DIRECTORY_3_3_0_XML = "http://download.jboss.org/jbosstools/updates/nightly/core/trunk/jbosstools-directory.xml"; // published URL
> {code}
> with value in plugin.properties. This will allow the plugin to be "fixed" when releasing it to point at a different URL.
> 2. Need to allow passing in the URL as a commandline variable at build-time so that we can have the same code overridden when built in stable branch for a milestone vs. in trunk.
> This could be done via Maven calling Ant in the pom.xml to do a simple XSLT on the build.properties file. (If you can't figure out another way, assign this part to me and I'll do this -- already have 80% of the code for such a transform in place.) This would allow overrides to be set in the parent/pom.xml or via commandline -D flags.
> 3. We could also set 4 variables in the plugin.properties file (for the 4 possible URLs) and have the -D flag be a simple switch between GA, milestone, nightly stable, and nightly trunk, without having to actually state the URL via the commandline.

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