[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=12664837#comment-12664837 ] 

Nick Boldt edited comment on JBIDE-10401 at 2/7/12 12:17 PM:
-------------------------------------------------------------

For the second part, Max & I propose this:

1. In the Central component job & Aggregate jobs' config.xml files, enable a new profile which sets a different URL for the directory.xml file (to use /nightly/trunk/ instead of /development/indigo/)

2. In central/pom.xml, create a new profile which sets a property for the URL for the directory.xml file (to use /nightly/trunk/ instead of /development/indigo/)

3. In central/pom.xml, enable copy-resources w/ filtering to resolve the <property> :: http://maven.apache.org/plugins/maven-resources-plugin/examples/copy-resources.html

Note that I've assumed that we should set /development/indigo/ as the default URL until we're about to GA, whereupon it would change to /stable/indigo/. 

Using this mechanism, QE can still override the URL via commandline when testing, and nightly builds will correctly point at the nightly site.
                
      was (Author: nickboldt):
    For the second part, Max & I propose this:

1. In the Central component job & Aggregate jobs' config.xml files, enable a new profile which sets a different URL for the directory.xml file (to use nightly/trunk instead of development/indigo)

2. In central/pom.xml, create a new profile which sets a property for the URL for the directory.xml file (to use nightly/trunk instead of development/indigo)

3. In central/pom.xml, enable copy-resources w/ filtering to resolve the <property> :: http://maven.apache.org/plugins/maven-resources-plugin/examples/copy-resources.html

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