November 2017 - jbosstools-issues

[JBoss JIRA] (ERT-533) enable use of tycho-p2-extras-plugin:compare-version-with-baselines and tycho-p2-plugin:attached-p2-metadata to ensure correct plugin and feature versioning between releases [EBZ#527533]

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/ERT-533?page=com.atlassian.jira.plugin.sy... ] Nick Boldt reassigned ERT-533: ------------------------------ Assignee: Nick Boldt > enable use of tycho-p2-extras-plugin:compare-version-with-baselines and tycho-p2-plugin:attached-p2-metadata to ensure correct plugin and feature versioning between releases [EBZ#527533] > ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ > > Key: ERT-533 > URL: https://issues.jboss.org/browse/ERT-533 > Project: Eclipse Release Train > Issue Type: Task > Components: WTP Releng > Reporter: Friendly Jira Robot > Assignee: Nick Boldt > Labels: bzira, releng > Fix For: Photon (4.8) > > > As mentioned on https://dev.eclipse.org/mhonarc/lists/wtp-dev/msg10522.html WTP uses some sort of versioncheck magic to ensure plugins and features are bumped appropriately. > We might want to switch to use the tycho-p2-extras-plugin:compare-version-with-baselines and tycho-p2-plugin:attached-p2-metadata mojos to ensure correct plugin and feature versioning, by settings stable and staging URLs as baselines. > For this to work, we need two things: > a) all components must build with Tycho 1.0 > b) a staging and stable URL must be provided against which to compare versions. > The staging site could be the latest I build or else a committers build, such as one of these, built via the current wtp.releng.aggretor build: > * http://download.eclipse.org/webtools/downloads/drops/R3.10.0/I-3.10.0-201... > * http://build.eclipse.org/webtools/committers/wtp-R3.10.0-I/20171030195222... > It should ultimately be a composite or aggregate site built from the collection of WTP subproject builds. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ERT-531) Maven 3.3.1 doesn't pick up the customized Toolchain for the WTP build [EBZ#472084]

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/ERT-531?page=com.atlassian.jira.plugin.sy... ] Nick Boldt reassigned ERT-531: ------------------------------ Assignee: Nick Boldt > Maven 3.3.1 doesn't pick up the customized Toolchain for the WTP build [EBZ#472084] > ----------------------------------------------------------------------------------- > > Key: ERT-531 > URL: https://issues.jboss.org/browse/ERT-531 > Project: Eclipse Release Train > Issue Type: Task > Components: Community > Reporter: Friendly Jira Robot > Assignee: Nick Boldt > Priority: Critical > Labels: Hudson, bzira > > A few WTP plugins need to build with the old JDK and a WTP toolchains.xml is set up. It works fine with Maven 3.2.5 but fails with Maven 3.3.1. > The current investigation showed that instead of using the WTP specific toolchains.xml which is defined in the Hudson build configuration, a common toolchains /opt/public/common/maven-toolchains.xml is linked as the user toolchains. > genie.gef ~> ll ~/.m2 > [....] > lrwxrwxrwx 1 genie.gef tools.gef 37 23 févr. 04:05 settings.xml -> /opt/public/common/maven-settings.xml > lrwxrwxrwx 1 genie.gef tools.gef 39 23 févr. 04:05 toolchains.xml -> /opt/public/common/maven-toolchains.xml > I wonder how Maven 3.2.5 can pick up the customized toolchains but not 3.3.1. It would be great if Maven 3.3.1 can pick up the customized toolchains as 3.2.5. > At the same time, I wonder whether the common toolchains file can be changed to support IBM JDK 1.4. Its current JDK 1.4 points to the Sun's which is broken and generates compile errors. > <toolchain> > <type>jdk</type> > <provides> > <id>J2SE-1.4</id> > </provides> > <configuration> > <jdkHome>/shared/webtools/apps/IBMJava2-142-SR13FP10/jre</jdkHome> > </configuration> > </toolchain> -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ERT-534) support building with Tycho 1.0 [EBZ#526333]

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/ERT-534?page=com.atlassian.jira.plugin.sy... ] Nick Boldt reassigned ERT-534: ------------------------------ Assignee: Nick Boldt > support building with Tycho 1.0 [EBZ#526333] > -------------------------------------------- > > Key: ERT-534 > URL: https://issues.jboss.org/browse/ERT-534 > Project: Eclipse Release Train > Issue Type: Task > Components: WTP Webservices > Reporter: Friendly Jira Robot > Assignee: Nick Boldt > Labels: 3.10_M4, bzira, jst.ws > Fix For: Photon (4.8) M4 > > > Quick hack to support Tycho 1.0 (instead of <= 0.26.0) is to enable tycho-compiler-plugin's useProjectSettings=false [1] so that things like API restrictions that SHOULD fail the build are allowed. > Ultimately, these API violation should be fixed, but if your Eclipse settings are allowing these to be ignored as warnings instead of errors, then so too should Tycho do the same. > Thus we need to add this to the root pom: > <build> > <plugins> > <plugin> > <groupId>org.eclipse.tycho</groupId> > <artifactId>tycho-compiler-plugin</artifactId> > <version>${tycho.version}</version> > <configuration> > <useProjectSettings>false</useProjectSettings> > </configuration> > </plugin> > </plugins> > </build> > [1] https://wiki.eclipse.org/Tycho/Release_Notes/1.0.0#Compiler > BTW, the Version here should be 3.10, but bugzilla needs to be updated to add that fixversion. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ERT-533) enable use of tycho-p2-extras-plugin:compare-version-with-baselines and tycho-p2-plugin:attached-p2-metadata to ensure correct plugin and feature versioning between releases [EBZ#527533]

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/ERT-533?page=com.atlassian.jira.plugin.sy... ] Nick Boldt updated ERT-533: --------------------------- Fix Version/s: Photon (4.8) > enable use of tycho-p2-extras-plugin:compare-version-with-baselines and tycho-p2-plugin:attached-p2-metadata to ensure correct plugin and feature versioning between releases [EBZ#527533] > ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ > > Key: ERT-533 > URL: https://issues.jboss.org/browse/ERT-533 > Project: Eclipse Release Train > Issue Type: Task > Components: WTP Releng > Reporter: Friendly Jira Robot > Assignee: Nick Boldt > Labels: bzira, releng > Fix For: Photon (4.8) > > > As mentioned on https://dev.eclipse.org/mhonarc/lists/wtp-dev/msg10522.html WTP uses some sort of versioncheck magic to ensure plugins and features are bumped appropriately. > We might want to switch to use the tycho-p2-extras-plugin:compare-version-with-baselines and tycho-p2-plugin:attached-p2-metadata mojos to ensure correct plugin and feature versioning, by settings stable and staging URLs as baselines. > For this to work, we need two things: > a) all components must build with Tycho 1.0 > b) a staging and stable URL must be provided against which to compare versions. > The staging site could be the latest I build or else a committers build, such as one of these, built via the current wtp.releng.aggretor build: > * http://download.eclipse.org/webtools/downloads/drops/R3.10.0/I-3.10.0-201... > * http://build.eclipse.org/webtools/committers/wtp-R3.10.0-I/20171030195222... > It should ultimately be a composite or aggregate site built from the collection of WTP subproject builds. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ERT-532) Overall repo merge issue [EBZ#525342]

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/ERT-532?page=com.atlassian.jira.plugin.sy... ] Nick Boldt updated ERT-532: --------------------------- Sprint: devex #141 December 2017 > Overall repo merge issue [EBZ#525342] > ------------------------------------- > > Key: ERT-532 > URL: https://issues.jboss.org/browse/ERT-532 > Project: Eclipse Release Train > Issue Type: Task > Components: WTP Releng > Reporter: Friendly Jira Robot > Assignee: Nick Boldt > Labels: bzira, releng > Fix For: Photon (4.8) M4 > > > Intent of this issue is to track the work needed to merge the 21 WTP projects [1] down to 8: > * common > * servertools > * sourceediting > * jsdt > * javaee-ejb > * webservices > * jsf > * dali > [1] https://wiki.eclipse.org/WTP_Gerrit_Access#Clone_a_repository_for_develop... > First pass at merging requires these two merge scripts to be run for servertools [2] and sourceediting [3]. > [2] https://bugs.eclipse.org/bugs/show_bug.cgi?id=519780 -> https://gist.github.com/robstryker/e79310e3ca09de45bf62c9264ac506e7 > [3] https://bugs.eclipse.org/bugs/show_bug.cgi?id=520044 -> https://gist.github.com/robstryker/054b9f2315a9bddd0ca76acebbd44610 > Later, once we have consensus on what to do about javaee & ejb, I'll link to that merge script and the downstream ones for ws and jsf. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ERT-532) Overall repo merge issue [EBZ#525342]

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/ERT-532?page=com.atlassian.jira.plugin.sy... ] Nick Boldt reassigned ERT-532: ------------------------------ Assignee: Nick Boldt > Overall repo merge issue [EBZ#525342] > ------------------------------------- > > Key: ERT-532 > URL: https://issues.jboss.org/browse/ERT-532 > Project: Eclipse Release Train > Issue Type: Task > Components: WTP Releng > Reporter: Friendly Jira Robot > Assignee: Nick Boldt > Labels: bzira, releng > Fix For: Photon (4.8) M4 > > > Intent of this issue is to track the work needed to merge the 21 WTP projects [1] down to 8: > * common > * servertools > * sourceediting > * jsdt > * javaee-ejb > * webservices > * jsf > * dali > [1] https://wiki.eclipse.org/WTP_Gerrit_Access#Clone_a_repository_for_develop... > First pass at merging requires these two merge scripts to be run for servertools [2] and sourceediting [3]. > [2] https://bugs.eclipse.org/bugs/show_bug.cgi?id=519780 -> https://gist.github.com/robstryker/e79310e3ca09de45bf62c9264ac506e7 > [3] https://bugs.eclipse.org/bugs/show_bug.cgi?id=520044 -> https://gist.github.com/robstryker/054b9f2315a9bddd0ca76acebbd44610 > Later, once we have consensus on what to do about javaee & ejb, I'll link to that merge script and the downstream ones for ws and jsf. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ERT-532) Overall repo merge issue [EBZ#525342]

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/ERT-532?page=com.atlassian.jira.plugin.sy... ] Nick Boldt updated ERT-532: --------------------------- Fix Version/s: Photon (4.8) M4 > Overall repo merge issue [EBZ#525342] > ------------------------------------- > > Key: ERT-532 > URL: https://issues.jboss.org/browse/ERT-532 > Project: Eclipse Release Train > Issue Type: Task > Components: WTP Releng > Reporter: Friendly Jira Robot > Assignee: Nick Boldt > Labels: bzira, releng > Fix For: Photon (4.8) M4 > > > Intent of this issue is to track the work needed to merge the 21 WTP projects [1] down to 8: > * common > * servertools > * sourceediting > * jsdt > * javaee-ejb > * webservices > * jsf > * dali > [1] https://wiki.eclipse.org/WTP_Gerrit_Access#Clone_a_repository_for_develop... > First pass at merging requires these two merge scripts to be run for servertools [2] and sourceediting [3]. > [2] https://bugs.eclipse.org/bugs/show_bug.cgi?id=519780 -> https://gist.github.com/robstryker/e79310e3ca09de45bf62c9264ac506e7 > [3] https://bugs.eclipse.org/bugs/show_bug.cgi?id=520044 -> https://gist.github.com/robstryker/054b9f2315a9bddd0ca76acebbd44610 > Later, once we have consensus on what to do about javaee & ejb, I'll link to that merge script and the downstream ones for ws and jsf. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ERT-534) support building with Tycho 1.0 [EBZ#526333]

by Friendly Jira Robot (JIRA)

Friendly Jira Robot created ERT-534: --------------------------------------- Summary: support building with Tycho 1.0 [EBZ#526333] Key: ERT-534 URL: https://issues.jboss.org/browse/ERT-534 Project: Eclipse Release Train Issue Type: Task Components: WTP Webservices Reporter: Friendly Jira Robot Fix For: Photon (4.8) M4 Quick hack to support Tycho 1.0 (instead of <= 0.26.0) is to enable tycho-compiler-plugin's useProjectSettings=false [1] so that things like API restrictions that SHOULD fail the build are allowed. Ultimately, these API violation should be fixed, but if your Eclipse settings are allowing these to be ignored as warnings instead of errors, then so too should Tycho do the same. Thus we need to add this to the root pom: <build> <plugins> <plugin> <groupId>org.eclipse.tycho</groupId> <artifactId>tycho-compiler-plugin</artifactId> <version>${tycho.version}</version> <configuration> <useProjectSettings>false</useProjectSettings> </configuration> </plugin> </plugins> </build> [1] https://wiki.eclipse.org/Tycho/Release_Notes/1.0.0#Compiler BTW, the Version here should be 3.10, but bugzilla needs to be updated to add that fixversion. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ERT-531) Maven 3.3.1 doesn't pick up the customized Toolchain for the WTP build [EBZ#472084]

by Friendly Jira Robot (JIRA)

Friendly Jira Robot created ERT-531: --------------------------------------- Summary: Maven 3.3.1 doesn't pick up the customized Toolchain for the WTP build [EBZ#472084] Key: ERT-531 URL: https://issues.jboss.org/browse/ERT-531 Project: Eclipse Release Train Issue Type: Task Components: Community Reporter: Friendly Jira Robot Priority: Critical A few WTP plugins need to build with the old JDK and a WTP toolchains.xml is set up. It works fine with Maven 3.2.5 but fails with Maven 3.3.1. The current investigation showed that instead of using the WTP specific toolchains.xml which is defined in the Hudson build configuration, a common toolchains /opt/public/common/maven-toolchains.xml is linked as the user toolchains. genie.gef ~> ll ~/.m2 [....] lrwxrwxrwx 1 genie.gef tools.gef 37 23 févr. 04:05 settings.xml -> /opt/public/common/maven-settings.xml lrwxrwxrwx 1 genie.gef tools.gef 39 23 févr. 04:05 toolchains.xml -> /opt/public/common/maven-toolchains.xml I wonder how Maven 3.2.5 can pick up the customized toolchains but not 3.3.1. It would be great if Maven 3.3.1 can pick up the customized toolchains as 3.2.5. At the same time, I wonder whether the common toolchains file can be changed to support IBM JDK 1.4. Its current JDK 1.4 points to the Sun's which is broken and generates compile errors. <toolchain> <type>jdk</type> <provides> <id>J2SE-1.4</id> </provides> <configuration> <jdkHome>/shared/webtools/apps/IBMJava2-142-SR13FP10/jre</jdkHome> </configuration> </toolchain> -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ERT-532) Overall repo merge issue [EBZ#525342]

by Friendly Jira Robot (JIRA)

Friendly Jira Robot created ERT-532: --------------------------------------- Summary: Overall repo merge issue [EBZ#525342] Key: ERT-532 URL: https://issues.jboss.org/browse/ERT-532 Project: Eclipse Release Train Issue Type: Task Components: WTP Releng Reporter: Friendly Jira Robot Intent of this issue is to track the work needed to merge the 21 WTP projects [1] down to 8: * common * servertools * sourceediting * jsdt * javaee-ejb * webservices * jsf * dali [1] https://wiki.eclipse.org/WTP_Gerrit_Access#Clone_a_repository_for_develop... First pass at merging requires these two merge scripts to be run for servertools [2] and sourceediting [3]. [2] https://bugs.eclipse.org/bugs/show_bug.cgi?id=519780 -> https://gist.github.com/robstryker/e79310e3ca09de45bf62c9264ac506e7 [3] https://bugs.eclipse.org/bugs/show_bug.cgi?id=520044 -> https://gist.github.com/robstryker/054b9f2315a9bddd0ca76acebbd44610 Later, once we have consensus on what to do about javaee & ejb, I'll link to that merge script and the downstream ones for ws and jsf. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

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