[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
[
https://issues.jboss.org/browse/JBIDE-10401?page=com.atlassian.jira.plugi...
]
Nick Boldt edited comment on JBIDE-10401 at 2/21/12 1:07 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/ >=4169
Doc'd here:
https://anonsvn.jboss.org/repos/jbosstools/trunk/central/plugins/org.jbos...
TO VERIFY IN TRUNK:
1. install fresh Indigo JEE
2. point at http://download.jboss.org/jbosstools/updates/nightly/core/trunk/ >=4169
3. install central feature, restart
4. verify that central plugin points at nightly site content
Google feature group should be described as "Google Plugin for Eclipse (GPE) + Google
Web Toolkit SDK (GWT)" if we're reading from the trunk site.
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/ >=62
3. install central feature, restart
4. verify that central plugin points at M5 (previous milestone) site content
Google feature group should be described as "Google Plugin for Eclipse (GPE) 2.5.1 +
Google Web Toolkit SDK (GWT) 2.4.0" if we're reading from the tip of Beta1
branch, or "Google Plugin for Eclipse (GPE) + Google Web Toolkit SDK 2.4.0
(GWT)" if reading from previous milestone site.
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.jbos...
TO VERIFY IN TRUNK:
1. install fresh Indigo JEE
2. point at http://download.jboss.org/jbosstools/updates/nightly/core/trunk/ >=4169
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/ >=62
3. install central feature, restart
4. verify that central plugin points at M5 (previous milestone) site content
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