March 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-13673) jenkins jobs for components and aggregates should set overrides for TARGET_PLATFORM_VERSION and TARGET_PLATFORM_VERSION-maximum so we ensure that builds use the correct TP regardless of their root pom's included parent pom version

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13673?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-13673 at 3/12/13 11:37 AM: -------------------------------------------------------------- Not sure what you mean by "in the Maven executors". Anyway, I've updated the jobs in the 40x, 41x and trunk/master branches adding these to the invocation of maven. Could have added these into the MAVEN_FLAGS variable, but this is a change that happens globally anyway, not per-job, so making it harder to see in the job's configure page doesn't bother me. And not all the affected jobs use that, so this is better. :) for 40x: {code}-DTARGET_PLATFORM_VERSION=4.20.6.Final-SNAPSHOT -DTARGET_PLATFORM_VERSION-maximum=4.22.1.Final-SNAPSHOT{code} for 41x: {code}-DTARGET_PLATFORM_VERSION=4.30.5.Alpha -DTARGET_PLATFORM_VERSION-maximum=4.30.5.Alpha{code} for trunk/master: {code}-DTARGET_PLATFORM_VERSION=4.30.5.Alpha -DTARGET_PLATFORM_VERSION-maximum=4.30.5.Alpha2-SNAPSHOT{code} was (Author: nickboldt): Not sure what you mean by "in the Maven executors". Anyway, I've updated the jobs in the 40x, 41x and trunk/master branches adding these to the invocation of maven. Could have added these into the MAVEN_FLAGS variable, but this is a change that happens globally anyway, not per-job, so making it harder to see in the job's configure page doesn't bother me. And not all the affected jobs use that, so this is better. :) for 40x: {code}-DTARGET_PLATFORM_VERSION=4.20.6.Final-SNAPSHOT -DTARGET_PLATFORM_VERSION-maximum=4.22.1.Final-SNAPSHOT{code} for 41x/trunk/master: {code}-DTARGET_PLATFORM_VERSION=4.30.5.Alpha -DTARGET_PLATFORM_VERSION-maximum=4.30.5.Alpha{code} > jenkins jobs for components and aggregates should set overrides for TARGET_PLATFORM_VERSION and TARGET_PLATFORM_VERSION-maximum so we ensure that builds use the correct TP regardless of their root pom's included parent pom version > -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-13673 > URL: https://issues.jboss.org/browse/JBIDE-13673 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Build/Releng > Affects Versions: 4.1.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.1.0.Alpha2 > > > jenkins jobs for components and aggregates should set overrides for TARGET_PLATFORM_VERSION and TARGET_PLATFORM_VERSION-maximum so we ensure that builds use the correct TP regardless of their root pom's included parent pom version -- 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13673) jenkins jobs for components and aggregates should set overrides for TARGET_PLATFORM_VERSION and TARGET_PLATFORM_VERSION-maximum so we ensure that builds use the correct TP regardless of their root pom's included parent pom version

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13673?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-13673: ------------------------------------ Not sure what you mean by "in the Maven executors". Anyway, I've updated the jobs in the 40x, 41x and trunk/master branches adding these to the invocation of maven. Could have added these into the MAVEN_FLAGS variable, but this is a change that happens globally anyway, not per-job, so making it harder to see in the job's configure page doesn't bother me. And not all the affected jobs use that, so this is better. :) for 40x: {code}-DTARGET_PLATFORM_VERSION=4.20.6.Final-SNAPSHOT -DTARGET_PLATFORM_VERSION-maximum=4.22.1.Final-SNAPSHOT{code for 41x/trunk/master: {code}-DTARGET_PLATFORM_VERSION=4.30.5.Alpha -DTARGET_PLATFORM_VERSION-maximum=4.30.5.Alpha{code} > jenkins jobs for components and aggregates should set overrides for TARGET_PLATFORM_VERSION and TARGET_PLATFORM_VERSION-maximum so we ensure that builds use the correct TP regardless of their root pom's included parent pom version > -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-13673 > URL: https://issues.jboss.org/browse/JBIDE-13673 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Build/Releng > Affects Versions: 4.1.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.1.0.Alpha2 > > > jenkins jobs for components and aggregates should set overrides for TARGET_PLATFORM_VERSION and TARGET_PLATFORM_VERSION-maximum so we ensure that builds use the correct TP regardless of their root pom's included parent pom version -- 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13673) jenkins jobs for components and aggregates should set overrides for TARGET_PLATFORM_VERSION and TARGET_PLATFORM_VERSION-maximum so we ensure that builds use the correct TP regardless of their root pom's included parent pom version

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13673?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-13673: ---------------------------------------- > Need max value for tests. Because at some point min won't be the same as max, and we test w/ max while building w/ min. Right But setting the -DTARGET_PLATFORM_VERSION value simply overrides any other setting of target platform (such as profile or TARGET_PLATFORM_VERSION-maximum. What about removing the minimal and maximal profiles from CI jobs and set TARGET_PLATFORM_VERSION with different values (minimal and maximal) in the Maven executors? > jenkins jobs for components and aggregates should set overrides for TARGET_PLATFORM_VERSION and TARGET_PLATFORM_VERSION-maximum so we ensure that builds use the correct TP regardless of their root pom's included parent pom version > -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-13673 > URL: https://issues.jboss.org/browse/JBIDE-13673 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Build/Releng > Affects Versions: 4.1.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.1.0.Alpha2 > > > jenkins jobs for components and aggregates should set overrides for TARGET_PLATFORM_VERSION and TARGET_PLATFORM_VERSION-maximum so we ensure that builds use the correct TP regardless of their root pom's included parent pom version -- 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13673) jenkins jobs for components and aggregates should set overrides for TARGET_PLATFORM_VERSION and TARGET_PLATFORM_VERSION-maximum so we ensure that builds use the correct TP regardless of their root pom's included parent pom version

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13673?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-13673: ------------------------------------ Need max value for tests. Because at some point min won't be the same as max, and we test w/ max while building w/ min. Having a select box for the version doesn't provide any more value than setting it as a hardcoded value in the job config. The top listed option is always selected when the build runs on schedule or when upstream change fires it. Why would you want to build one project w/ 4.30.5.Alpha and another with 4.30.5.Alpha2-SNAPSHOT ? That would just cause confusion and force you to have to READ the logs to know what was used. IMHO it's better if all jobs for a given stream use the same TP for building (and a different one for testing). Besides, anyone who wants to edit the job to run once w/ a different TP can do so from the configure menu. > jenkins jobs for components and aggregates should set overrides for TARGET_PLATFORM_VERSION and TARGET_PLATFORM_VERSION-maximum so we ensure that builds use the correct TP regardless of their root pom's included parent pom version > -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-13673 > URL: https://issues.jboss.org/browse/JBIDE-13673 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Build/Releng > Affects Versions: 4.1.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.1.0.Alpha2 > > > jenkins jobs for components and aggregates should set overrides for TARGET_PLATFORM_VERSION and TARGET_PLATFORM_VERSION-maximum so we ensure that builds use the correct TP regardless of their root pom's included parent pom version -- 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13673) jenkins jobs for components and aggregates should set overrides for TARGET_PLATFORM_VERSION and TARGET_PLATFORM_VERSION-maximum so we ensure that builds use the correct TP regardless of their root pom's included parent pom version

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13673?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-13673: ---------------------------------------- I suggest we add a checkbox to select a version of the TP. When a new version of TP is released we update that checkbox. See https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-openshift... WDYT? > jenkins jobs for components and aggregates should set overrides for TARGET_PLATFORM_VERSION and TARGET_PLATFORM_VERSION-maximum so we ensure that builds use the correct TP regardless of their root pom's included parent pom version > -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-13673 > URL: https://issues.jboss.org/browse/JBIDE-13673 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Build/Releng > Affects Versions: 4.1.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.1.0.Alpha2 > > > jenkins jobs for components and aggregates should set overrides for TARGET_PLATFORM_VERSION and TARGET_PLATFORM_VERSION-maximum so we ensure that builds use the correct TP regardless of their root pom's included parent pom version -- 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13673) jenkins jobs for components and aggregates should set overrides for TARGET_PLATFORM_VERSION and TARGET_PLATFORM_VERSION-maximum so we ensure that builds use the correct TP regardless of their root pom's included parent pom version

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13673?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-13673: ---------------------------------------- Just setting -DTARGET_PLATFORM_VERSION would be enough. When setting -DTARGET_PLATFROM_VERSION from command-line, the value becomes immutable, so that maximal and other profiles won't change it. > jenkins jobs for components and aggregates should set overrides for TARGET_PLATFORM_VERSION and TARGET_PLATFORM_VERSION-maximum so we ensure that builds use the correct TP regardless of their root pom's included parent pom version > -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-13673 > URL: https://issues.jboss.org/browse/JBIDE-13673 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Build/Releng > Affects Versions: 4.1.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.1.0.Alpha2 > > > jenkins jobs for components and aggregates should set overrides for TARGET_PLATFORM_VERSION and TARGET_PLATFORM_VERSION-maximum so we ensure that builds use the correct TP regardless of their root pom's included parent pom version -- 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTIS-26) Cannot install bpel from update site

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-26?page=com.atlassian.jira.plugin.s... ] Andrej Podhradsky commented on JBTIS-26: ---------------------------------------- I'm trying to install JBoss BPEL Editor of version 1.2.1.Final-v20130225-1413-B89 > Cannot install bpel from update site > ------------------------------------ > > Key: JBTIS-26 > URL: https://issues.jboss.org/browse/JBTIS-26 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: releng > Reporter: Andrej Podhradsky > Attachments: bpel-error.txt > > > I'm not able to install JBoss BPEL Editor into Eclipse Juno JEE (see the attached file) from JBTIS update site > http://download.jboss.org/jbosstools/updates/integration/juno/integration... > Maybe there is something wrong with the aggregation definition because I'm able to install the same BPEL editor from > http://download.jboss.org/jbosstools/updates/integration/juno/integration... -- 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13772) Provide a dialog to configure the LiveReload embedded server

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13772?page=com.atlassian.jira.plugi... ] Xavier Coulon commented on JBIDE-13772: --------------------------------------- Dialog window that appears when the user clicks on the "LiveReload..." command on the server contextual menu > Provide a dialog to configure the LiveReload embedded server > ------------------------------------------------------------ > > Key: JBIDE-13772 > URL: https://issues.jboss.org/browse/JBIDE-13772 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: JBossAS/Servers > Affects Versions: 4.1.0.Alpha2 > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Fix For: 4.1.0.Alpha2 > > Attachments: LiveReload startup config dialog.bmml, LiveReload startup config dialog.png > > > Provide a dialog to configure the LiveReload embedded server when the user starts the LiveReload feature from the Server context menu. -- 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTIS-26) Cannot install bpel from update site

by Andrej Podhradsky (JIRA)

Andrej Podhradsky created JBTIS-26: -------------------------------------- Summary: Cannot install bpel from update site Key: JBTIS-26 URL: https://issues.jboss.org/browse/JBTIS-26 Project: JBoss Tools Integration Stack Issue Type: Bug Security Level: Public (Everyone can see) Components: releng Reporter: Andrej Podhradsky Attachments: bpel-error.txt I'm not able to install JBoss BPEL Editor into Eclipse Juno JEE (see the attached file) from JBTIS update site http://download.jboss.org/jbosstools/updates/integration/juno/integration... Maybe there is something wrong with the aggregation definition because I'm able to install the same BPEL editor from http://download.jboss.org/jbosstools/updates/integration/juno/integration... -- 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTIS-26) Cannot install bpel from update site

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-26?page=com.atlassian.jira.plugin.s... ] Andrej Podhradsky updated JBTIS-26: ----------------------------------- Attachment: bpel-error.txt > Cannot install bpel from update site > ------------------------------------ > > Key: JBTIS-26 > URL: https://issues.jboss.org/browse/JBTIS-26 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: releng > Reporter: Andrej Podhradsky > Attachments: bpel-error.txt > > > I'm not able to install JBoss BPEL Editor into Eclipse Juno JEE (see the attached file) from JBTIS update site > http://download.jboss.org/jbosstools/updates/integration/juno/integration... > Maybe there is something wrong with the aggregation definition because I'm able to install the same BPEL editor from > http://download.jboss.org/jbosstools/updates/integration/juno/integration... -- 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

13 years, 1 month

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues March 2013