[jbosstools-issues] [JBoss JIRA] (JBIDE-13452) investigate removing JBT_VERSION, JBDS_VERSION, and TARGET_PLATFORM_VERSION from parent pom
Nick Boldt (JIRA)
jira-events at lists.jboss.org
Mon Mar 18 17:37:41 EDT 2013
[ https://issues.jboss.org/browse/JBIDE-13452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12760883#comment-12760883 ]
Nick Boldt edited comment on JBIDE-13452 at 3/18/13 5:36 PM:
-------------------------------------------------------------
JBT_VERSION is still used in these files:
*{color:red}
./jbosstools-build/parent/pom.xml
./jbosstools-javaee/site/pom.xml
{color}*
{code}
<JBT_VERSION>4.1.0</JBT_VERSION>
{code}
Cleaned from these files:
*{color:green}
-./jbosstools-build-sites/aggregate/build.xml-
-./jbosstools-build-sites/aggregate/**/pom.xml-
-./jbosstools-build-sites/results/build.xml-
-./jbosstools-build-sites/results/pom.xml-
-./jbosstools-base/site/pom.xml-
-./jbosstools-server/site/pom.xml-
{color}*
Meanwhile, JBDS_VERSION is set in product/pom.xml (devstudio SVN) and used in these files:
./product/installer/build.xml
./product/installer/pom.xml
./product/results/build.xml
./product/results/index-earlyaccess-template.html
./product/results/index-internal-template.html
./product/results/index-local-template.html
./product/results/pom.xml
./product/site/build.xml
./product/site/pom.xml
./product-soa/site/build.xml
./product-soa/site/pom.xml
./product/sources/build.xml
./product/sources/pom.xml
was (Author: nickboldt):
JBT_VERSION is still used in these files:
*{color:green}
./jbosstools-build-sites/aggregate/build.xml
./jbosstools-build-sites/aggregate/**/pom.xml
{color}*
{code}
<property name="JBT_VERSION" value="${project.version}" />
{code}
*{color:red}
./jbosstools-build-sites/results/build.xml
./jbosstools-build-sites/results/pom.xml
{color}*
*{color:red}
./jbosstools-build/parent/pom.xml
{color}*
{code}
<JBT_VERSION>4.1.0</JBT_VERSION>
{code}
*{color:red}
./jbosstools-base/site/pom.xml
./jbosstools-javaee/site/pom.xml
./jbosstools-server/site/pom.xml
{color}*
{code}
<update.site.version>${JBT_VERSION} ${buildQualifier}</update.site.version>
{code}
Meanwhile, JBDS_VERSION is set in product/pom.xml (devstudio SVN) in these files:
./product/installer/build.xml
./product/installer/pom.xml
./product/results/build.xml
./product/results/index-earlyaccess-template.html
./product/results/index-internal-template.html
./product/results/index-local-template.html
./product/results/pom.xml
./product/site/build.xml
./product/site/pom.xml
./product-soa/site/build.xml
./product-soa/site/pom.xml
./product/sources/build.xml
./product/sources/pom.xml
> investigate removing JBT_VERSION, JBDS_VERSION, and TARGET_PLATFORM_VERSION from parent pom
> -------------------------------------------------------------------------------------------
>
> Key: JBIDE-13452
> URL: https://issues.jboss.org/browse/JBIDE-13452
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Build/Releng, target-platform, updatesite
> Affects Versions: 4.1.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
>
> investigate removing JBT_VERSION, JBDS_VERSION, and TARGET_PLATFORM_VERSION (min and max) from parent pom
> Can we switch to using dynamic maven variables like project.version instead?
> Moving forward, jobs will override/set the version of target platform used to build (min) and test (max), and developers will be required to decide when/if to move to a newer parent pom or target platform version(s) if needed. For projects that are released, jobs will run only when TP changes (ie., will watch the jbosstools-target-platforms repo for changes).
--
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
More information about the jbosstools-issues
mailing list