[JBoss JIRA] (JBIDE-10401) externalize URL for Central directory.xml file so it can be passed in via commandline when building or at runtime
11:22 a.m.
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
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
11:26 a.m.
[
https://issues.jboss.org/browse/JBIDE-10401?page=com.atlassian.jira.plugi...
]
Nick Boldt updated JBIDE-10401:
-------------------------------
Release Notes Text:
Reminder here to update the releng guide with the new workflow once it's in place.
https://svn.jboss.org/repos/devstudio/trunk/documentation/Release_Guide/R...
https://svn.jboss.org/repos/devstudio/trunk/documentation/Release_Guide/R...
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: Snjezana Peco
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
10:28 a.m.
[
https://issues.jboss.org/browse/JBIDE-10401?page=com.atlassian.jira.plugi...
]
Nick Boldt updated JBIDE-10401:
-------------------------------
Fix Version/s: 3.3.0.Beta1
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: Snjezana Peco
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
10:18 a.m.
[
https://issues.jboss.org/browse/JBIDE-10401?page=com.atlassian.jira.plugi...
]
Nick Boldt commented on JBIDE-10401:
------------------------------------
First part is done, and we can now pass in different URLs by hand:
{code}
./eclipse -vmargs
-Djboss.discovery.directory.url=http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio-5.0_trunk.updatesite/product/devstudio-directory.xml
{code}
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: Snjezana Peco
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
11:14 a.m.
[
https://issues.jboss.org/browse/JBIDE-10401?page=com.atlassian.jira.plugi...
]
Nick Boldt commented on JBIDE-10401:
------------------------------------
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-reso...
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
11:18 a.m.
[
https://issues.jboss.org/browse/JBIDE-10401?page=com.atlassian.jira.plugi...
]
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-reso...
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-reso...
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
2:48 p.m.
[
https://issues.jboss.org/browse/JBIDE-10401?page=com.atlassian.jira.plugi...
]
Nick Boldt commented on JBIDE-10401:
------------------------------------
The above plan is in place. Awaiting respin of JBT agg build to verify that new -Ptrunk
profile works as expected.
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...
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
10:20 a.m.
[
https://issues.jboss.org/browse/JBIDE-10401?page=com.atlassian.jira.plugi...
]
Nick Boldt edited comment on JBIDE-10401 at 2/9/12 11:19 AM:
-------------------------------------------------------------
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:
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
was (Author: nickboldt):
The above plan is in place. Awaiting respin of JBT agg build to verify that new
-Ptrunk profile works as expected.
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...
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
10:20 a.m.
[
https://issues.jboss.org/browse/JBIDE-10401?page=com.atlassian.jira.plugi...
]
Nick Boldt edited comment on JBIDE-10401 at 2/9/12 11:20 AM:
-------------------------------------------------------------
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
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:
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
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
6:34 a.m.
[
https://issues.jboss.org/browse/JBIDE-10401?page=com.atlassian.jira.plugi...
]
Max Rydahl Andersen updated JBIDE-10401:
----------------------------------------
Priority: Critical (was: Major)
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
12:08 p.m.
[
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
12:12 p.m.
[
https://issues.jboss.org/browse/JBIDE-10401?page=com.atlassian.jira.plugi...
]
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/ >=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
-> https://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_trunk.component--ce...
>=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.compo...
>=43
-> https://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_stable_branch.aggre...
>=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.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.
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
12:12 p.m.
[
https://issues.jboss.org/browse/JBIDE-10401?page=com.atlassian.jira.plugi...
]
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.jbos...
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--ce...
>=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.compo...
>=43
-> https://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_stable_branch.aggre...
>=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.jbos...
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--ce...
>=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.compo...
>=43
-> https://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_stable_branch.aggre...
>=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
9:02 a.m.
[
https://issues.jboss.org/browse/JBIDE-10401?page=com.atlassian.jira.plugi...
]
Nick Boldt resolved JBIDE-10401.
--------------------------------
Resolution: Done
Verified:
{code}
./eclipse/eclipse -clean -showLocation -data /tmp/workspace -consolelog -console -vm
/opt/sun-java2-6.0/bin/java -vmargs -Xms128M -Xmx256M -XX:PermSize=128M
-XX:MaxPermSize=256M
-Djboss.discovery.directory.url=http://download.jboss.org/jbosstools/updates/nightly/core/trunk/jbosstools-directory.xml
| tee "/tmp/eclipse.log.`date`.txt"
./eclipse/eclipse -clean -showLocation -data /tmp/workspace -consolelog -console -vm
/opt/sun-java2-6.0/bin/java -vmargs -Xms128M -Xmx256M -XX:PermSize=128M
-XX:MaxPermSize=256M
-Djboss.discovery.directory.url=http://download.jboss.org/jbosstools/updates/nightly/core/3.3.indigo/jbosstools-directory.xml
| tee "/tmp/eclipse.log.`date`.txt"
{code}
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
9:06 a.m.
[
https://issues.jboss.org/browse/JBIDE-10401?page=com.atlassian.jira.plugi...
]
Nick Boldt updated JBIDE-10401:
-------------------------------
Comment: was deleted
(was: Verified:
{code}
./eclipse/eclipse -clean -showLocation -data /tmp/workspace -consolelog -console -vm
/opt/sun-java2-6.0/bin/java -vmargs -Xms128M -Xmx256M -XX:PermSize=128M
-XX:MaxPermSize=256M
-Djboss.discovery.directory.url=http://download.jboss.org/jbosstools/updates/nightly/core/trunk/jbosstools-directory.xml
| tee "/tmp/eclipse.log.`date`.txt"
./eclipse/eclipse -clean -showLocation -data /tmp/workspace -consolelog -console -vm
/opt/sun-java2-6.0/bin/java -vmargs -Xms128M -Xmx256M -XX:PermSize=128M
-XX:MaxPermSize=256M
-Djboss.discovery.directory.url=http://download.jboss.org/jbosstools/updates/nightly/core/3.3.indigo/jbosstools-directory.xml
| tee "/tmp/eclipse.log.`date`.txt"
{code})
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
1:23 p.m.
[
https://issues.jboss.org/browse/JBIDE-10401?page=com.atlassian.jira.plugi...
]
Nick Boldt commented on JBIDE-10401:
------------------------------------
Prolly broken due to Sneja's refactoring the templated class out of Central and into
Examples. Job fixed (I hope), so that now we'll generate the file in Examples and have
it used by Central and the Aggregate.
Respinning:
https://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_trunk.component--ex... >=577
https://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_trunk.component--ce... >=403
https://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_trunk.aggregate/ >=4193
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
4:16 a.m.
[
https://issues.jboss.org/browse/JBIDE-10401?page=com.atlassian.jira.plugi...
]
Fred Bricon commented on JBIDE-10401:
-------------------------------------
Nick, there's a much much more elegant way to get that dicovery url filtered :
* add a discovery.properties file in the source directory, containing :
discovery.url=${jboss.discovery.directory.url}
* change the pom.xml so that maven-resources-plugin filters that file :
{code:xml}
<build>
<resources>
<resource>
<directory>src</directory>
<includes>
<include>**/discovery.properties</include>
</includes>
<filtering>true</filtering>
</resource>
</resources>
<plugins>
<plugin>
<artifactId>maven-resources-plugin</artifactId>
<version>2.5</version>
<executions>
<execution>
<id>resource-filtering</id>
<!-- Need to execute resource filtering AFTER tycho-compiler-plugin is
executed -->
<phase>process-classes</phase>
<goals>
<goal>resources</goal>
</goals>
</execution>
</executions>
</plugin>
</plugins>
</build>
{code}
* read the properties value in the code (simplified) : String url =
ResourceBundle.getBundle("discovery").get("discovery.url");
This has the advantage to work with m2e within eclipse and most importantly, no need to
duplicate and maintain 2 versions of the DefaultJBossCentralConfigurator (I know, as
I've been hit by that, it's not documented in the original
DefaultJBossCentralConfigurator).
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
7:41 a.m.
[
https://issues.jboss.org/browse/JBIDE-10401?page=com.atlassian.jira.plugi...
]
Nick Boldt commented on JBIDE-10401:
------------------------------------
Sounds great! Do you have time to implement this in trunk?
https://svn.jboss.org/repos/jbosstools/trunk/examples/plugins/org.jboss.t...
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
9:43 a.m.
[
https://issues.jboss.org/browse/JBIDE-10401?page=com.atlassian.jira.plugi...
]
Nick Boldt updated JBIDE-10401:
-------------------------------
Attachment: 10401-branch-prev-milestone-good.png
10401-trunk-good.png
branch: H67-Beta1
!10401-branch-prev-milestone-good.png!
trunk: H419-Beta2
!10401-trunk-good.png!
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
Attachments: 10401-branch-prev-milestone-good.png, 10401-trunk-good.png
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
9:47 a.m.
[
https://issues.jboss.org/browse/JBIDE-10401?page=com.atlassian.jira.plugi...
]
Nick Boldt resolved JBIDE-10401.
--------------------------------
Resolution: Done
Looks good to me. Thanks for the fix, fbricon!
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
Attachments: 10401-branch-prev-milestone-good.png, 10401-trunk-good.png
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
9:47 a.m.
[
https://issues.jboss.org/browse/JBIDE-10401?page=com.atlassian.jira.plugi...
]
Nick Boldt closed JBIDE-10401.
------------------------------
Close.
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
Attachments: 10401-branch-prev-milestone-good.png, 10401-trunk-good.png
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
5143
days inactive
5235
days old
jbosstools-issues@lists.jboss.org
20 comments
5 participants
participants (5)
-
Fred Bricon (JIRA) -
Max Rydahl Andersen (JIRA)
-
Nick Boldt (Created) (JIRA)
-
Nick Boldt (JIRA)
-
Nick Boldt (Updated) (JIRA)