April 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-24380) new default in parent pom: set jbosstools.test.jre.* = ${JAVA_HOME}

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24380?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-24380: ------------------------------- Description: In order to be able to more easily run server and webservices projects' tests, I suggest we set default values in parent pom: {code} - <jbosstools.test.jre.5></jbosstools.test.jre.5> - <jbosstools.test.jre.6></jbosstools.test.jre.6> - <jbosstools.test.jre.7></jbosstools.test.jre.7> - <jbosstools.test.jre.8></jbosstools.test.jre.8> + <jbosstools.test.jre.5>${JAVA_HOME}</jbosstools.test.jre.5> + <jbosstools.test.jre.6>${JAVA_HOME}</jbosstools.test.jre.6> + <jbosstools.test.jre.7>${JAVA_HOME}</jbosstools.test.jre.7> + <jbosstools.test.jre.8>${JAVA_HOME}</jbosstools.test.jre.8> {code} This way, depending on what your system's definition of JAVA_HOME happens to be, you get a different effective pom, for your required JDK: {code} $ export JAVA_HOME=/opt/jdk1.8.0/ $ /opt/maven3/bin/mvn help:effective-pom | grep jbosstools.test.jre <jbosstools.test.jre.5>/opt/jdk1.8.0/</jbosstools.test.jre.5> <jbosstools.test.jre.6>/opt/jdk1.8.0/</jbosstools.test.jre.6> <jbosstools.test.jre.7>/opt/jdk1.8.0/</jbosstools.test.jre.7> <jbosstools.test.jre.8>/opt/jdk1.8.0/</jbosstools.test.jre.8> (or, to use the JAVA_HOME set by alternatives...) $ export JAVA_HOME=$(alternatives --display java | grep bin/java | grep link | sed -e "s#.\+ $.\+$bin/java#\1#") $ /opt/maven3/bin/mvn help:effective-pom | grep jbosstools.test.jre <jbosstools.test.jre.5>/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.121-8.b14.fc24.x86_64/jre/</jbosstools.test.jre.5> <jbosstools.test.jre.6>/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.121-8.b14.fc24.x86_64/jre/</jbosstools.test.jre.6> <jbosstools.test.jre.7>/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.121-8.b14.fc24.x86_64/jre/</jbosstools.test.jre.7> <jbosstools.test.jre.8>/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.121-8.b14.fc24.x86_64/jre/</jbosstools.test.jre.8> {code} was: In order to be able to more easily run server and webservices projects' tests, I suggest we set default values in parent pom: {code} - <jbosstools.test.jre.5></jbosstools.test.jre.5> - <jbosstools.test.jre.6></jbosstools.test.jre.6> - <jbosstools.test.jre.7></jbosstools.test.jre.7> - <jbosstools.test.jre.8></jbosstools.test.jre.8> + <jbosstools.test.jre.5>${JAVA_HOME}</jbosstools.test.jre.5> + <jbosstools.test.jre.6>${JAVA_HOME}</jbosstools.test.jre.6> + <jbosstools.test.jre.7>${JAVA_HOME}</jbosstools.test.jre.7> + <jbosstools.test.jre.8>${JAVA_HOME}</jbosstools.test.jre.8> {code} > new default in parent pom: set jbosstools.test.jre.* = ${JAVA_HOME} > ------------------------------------------------------------------- > > Key: JBIDE-24380 > URL: https://issues.jboss.org/browse/JBIDE-24380 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.5.0.AM1 > Reporter: Nick Boldt > Fix For: 4.5.0.AM1 > > > In order to be able to more easily run server and webservices projects' tests, I suggest we set default values in parent pom: > {code} > - <jbosstools.test.jre.5></jbosstools.test.jre.5> > - <jbosstools.test.jre.6></jbosstools.test.jre.6> > - <jbosstools.test.jre.7></jbosstools.test.jre.7> > - <jbosstools.test.jre.8></jbosstools.test.jre.8> > + <jbosstools.test.jre.5>${JAVA_HOME}</jbosstools.test.jre.5> > + <jbosstools.test.jre.6>${JAVA_HOME}</jbosstools.test.jre.6> > + <jbosstools.test.jre.7>${JAVA_HOME}</jbosstools.test.jre.7> > + <jbosstools.test.jre.8>${JAVA_HOME}</jbosstools.test.jre.8> > {code} > This way, depending on what your system's definition of JAVA_HOME happens to be, you get a different effective pom, for your required JDK: > {code} > $ export JAVA_HOME=/opt/jdk1.8.0/ > $ /opt/maven3/bin/mvn help:effective-pom | grep jbosstools.test.jre > <jbosstools.test.jre.5>/opt/jdk1.8.0/</jbosstools.test.jre.5> > <jbosstools.test.jre.6>/opt/jdk1.8.0/</jbosstools.test.jre.6> > <jbosstools.test.jre.7>/opt/jdk1.8.0/</jbosstools.test.jre.7> > <jbosstools.test.jre.8>/opt/jdk1.8.0/</jbosstools.test.jre.8> > (or, to use the JAVA_HOME set by alternatives...) > $ export JAVA_HOME=$(alternatives --display java | grep bin/java | grep link | sed -e "s#.\+ $.\+$bin/java#\1#") > $ /opt/maven3/bin/mvn help:effective-pom | grep jbosstools.test.jre > <jbosstools.test.jre.5>/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.121-8.b14.fc24.x86_64/jre/</jbosstools.test.jre.5> > <jbosstools.test.jre.6>/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.121-8.b14.fc24.x86_64/jre/</jbosstools.test.jre.6> > <jbosstools.test.jre.7>/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.121-8.b14.fc24.x86_64/jre/</jbosstools.test.jre.7> > <jbosstools.test.jre.8>/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.121-8.b14.fc24.x86_64/jre/</jbosstools.test.jre.8> > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24380) new default in parent pom: set jbosstools.test.jre.* = ${JAVA_HOME}

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24380?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-24380: ------------------------------------ If you forget to set these variables... {code} -Djbosstools.test.jre.5=/path/to/jdk5/or/equivalent -Djbosstools.test.jre.6=/path/to/jdk6/or/equivalent -Djbosstools.test.jre.7=/path/to/jdk7/or/equivalent -Djbosstools.test.jre.8=/path/to/jdk8/or/equivalent {code} ... on commandline, you get test failures like this: {code} [ERROR] com.sun.tools.javac.Main is not available in the classpath, requires Suns JDK version 5.0 or latter. unknown location compilation failed, errors should have been reported{code} ... buried inside a *jbosstools-webservices/tests/org.jboss.tools.ws.creation.core.test/target/work/data/.metadata/.log* file. So by defaulting to JAVA_HOME (which is likely Sun or Open JDK 8), you at least get the tests to succeed. Surely that's a good thing? > new default in parent pom: set jbosstools.test.jre.* = ${JAVA_HOME} > ------------------------------------------------------------------- > > Key: JBIDE-24380 > URL: https://issues.jboss.org/browse/JBIDE-24380 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.5.0.AM1 > Reporter: Nick Boldt > Fix For: 4.5.0.AM1 > > > In order to be able to more easily run server and webservices projects' tests, I suggest we set default values in parent pom: > {code} > - <jbosstools.test.jre.5></jbosstools.test.jre.5> > - <jbosstools.test.jre.6></jbosstools.test.jre.6> > - <jbosstools.test.jre.7></jbosstools.test.jre.7> > - <jbosstools.test.jre.8></jbosstools.test.jre.8> > + <jbosstools.test.jre.5>${JAVA_HOME}</jbosstools.test.jre.5> > + <jbosstools.test.jre.6>${JAVA_HOME}</jbosstools.test.jre.6> > + <jbosstools.test.jre.7>${JAVA_HOME}</jbosstools.test.jre.7> > + <jbosstools.test.jre.8>${JAVA_HOME}</jbosstools.test.jre.8> > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24380) new default in parent pom: set jbosstools.test.jre.* = ${JAVA_HOME}

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24380?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-24380: ------------------------------- Fix Version/s: 4.5.0.AM1 > new default in parent pom: set jbosstools.test.jre.* = ${JAVA_HOME} > ------------------------------------------------------------------- > > Key: JBIDE-24380 > URL: https://issues.jboss.org/browse/JBIDE-24380 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.5.0.AM1 > Reporter: Nick Boldt > Fix For: 4.5.0.AM1 > > > In order to be able to more easily run server and webservices projects' tests, I suggest we set default values in parent pom: > {code} > - <jbosstools.test.jre.5></jbosstools.test.jre.5> > - <jbosstools.test.jre.6></jbosstools.test.jre.6> > - <jbosstools.test.jre.7></jbosstools.test.jre.7> > - <jbosstools.test.jre.8></jbosstools.test.jre.8> > + <jbosstools.test.jre.5>${JAVA_HOME}</jbosstools.test.jre.5> > + <jbosstools.test.jre.6>${JAVA_HOME}</jbosstools.test.jre.6> > + <jbosstools.test.jre.7>${JAVA_HOME}</jbosstools.test.jre.7> > + <jbosstools.test.jre.8>${JAVA_HOME}</jbosstools.test.jre.8> > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24380) new default in parent pom: set jbosstools.test.jre.* = ${JAVA_HOME}

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-24380: ---------------------------------- Summary: new default in parent pom: set jbosstools.test.jre.* = ${JAVA_HOME} Key: JBIDE-24380 URL: https://issues.jboss.org/browse/JBIDE-24380 Project: Tools (JBoss Tools) Issue Type: Bug Components: build Affects Versions: 4.5.0.AM1 Reporter: Nick Boldt In order to be able to more easily run server and webservices projects' tests, I suggest we set default values in parent pom: {code} - <jbosstools.test.jre.5></jbosstools.test.jre.5> - <jbosstools.test.jre.6></jbosstools.test.jre.6> - <jbosstools.test.jre.7></jbosstools.test.jre.7> - <jbosstools.test.jre.8></jbosstools.test.jre.8> + <jbosstools.test.jre.5>${JAVA_HOME}</jbosstools.test.jre.5> + <jbosstools.test.jre.6>${JAVA_HOME}</jbosstools.test.jre.6> + <jbosstools.test.jre.7>${JAVA_HOME}</jbosstools.test.jre.7> + <jbosstools.test.jre.8>${JAVA_HOME}</jbosstools.test.jre.8> {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4383) Add support for installing EAP from devsuite installers

by Nick Boldt (JIRA)

Nick Boldt created JBDS-4383: -------------------------------- Summary: Add support for installing EAP from devsuite installers Key: JBDS-4383 URL: https://issues.jboss.org/browse/JBDS-4383 Project: Red Hat JBoss Developer Studio (devstudio) Issue Type: Bug Components: integration-platform Affects Versions: 11.0.0.AM1 Reporter: Nick Boldt Related to JBDS-4362, when we eliminate the EAP bundled installer jar, we need to also add support to the devsuite installer to install EAP from there instead. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4383) Add support for installing EAP from devsuite installers

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4383?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-4383: ----------------------------- Fix Version/s: 11.0.0.AM1 > Add support for installing EAP from devsuite installers > ------------------------------------------------------- > > Key: JBDS-4383 > URL: https://issues.jboss.org/browse/JBDS-4383 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: integration-platform > Affects Versions: 11.0.0.AM1 > Reporter: Nick Boldt > Fix For: 11.0.0.AM1 > > > Related to JBDS-4362, when we eliminate the EAP bundled installer jar, we need to also add support to the devsuite installer to install EAP from there instead. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4383) Add support for installing EAP from devsuite installers

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4383?page=com.atlassian.jira.plugin.... ] Nick Boldt reassigned JBDS-4383: -------------------------------- Assignee: Nick Boldt > Add support for installing EAP from devsuite installers > ------------------------------------------------------- > > Key: JBDS-4383 > URL: https://issues.jboss.org/browse/JBDS-4383 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: integration-platform > Affects Versions: 11.0.0.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 11.0.0.AM1 > > > Related to JBDS-4362, when we eliminate the EAP bundled installer jar, we need to also add support to the devsuite installer to install EAP from there instead. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24376) Include patch feature version of wtp.common in JBT/devstudio Oxygen target platform (4.70.x)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24376?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-24376: ---------------------------------- Assignee: Paul Leacu (was: Nick Boldt) > Include patch feature version of wtp.common in JBT/devstudio Oxygen target platform (4.70.x) > -------------------------------------------------------------------------------------------- > > Key: JBIDE-24376 > URL: https://issues.jboss.org/browse/JBIDE-24376 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: target-platform > Affects Versions: 4.4.4.AM2 > Reporter: Aurélien Pupier > Assignee: Paul Leacu > Fix For: 4.5.0.AM1 > > > Oxygen.0.M6 contains a regression which is impacting a lot of m2e users and prevents Fuse Tooling to migrate to Oxygen safely > I provided a patch to fix it and hope to have a new version of the plugin available soon, see > https://bugs.eclipse.org/bugs/show_bug.cgi?id=511793#c9 > We will need to include this new version in the TP for JBoss Tools 4.5.0 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24376) Include patch feature version of wtp.common in JBT/devstudio Oxygen target platform (4.70.x)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24376?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-24376: ------------------------------------ My part's done here. Assigning to Paul for the next part. > Include patch feature version of wtp.common in JBT/devstudio Oxygen target platform (4.70.x) > -------------------------------------------------------------------------------------------- > > Key: JBIDE-24376 > URL: https://issues.jboss.org/browse/JBIDE-24376 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: target-platform > Affects Versions: 4.4.4.AM2 > Reporter: Aurélien Pupier > Assignee: Paul Leacu > Fix For: 4.5.0.AM1 > > > Oxygen.0.M6 contains a regression which is impacting a lot of m2e users and prevents Fuse Tooling to migrate to Oxygen safely > I provided a patch to fix it and hope to have a new version of the plugin available soon, see > https://bugs.eclipse.org/bugs/show_bug.cgi?id=511793#c9 > We will need to include this new version in the TP for JBoss Tools 4.5.0 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24379) javaee tests failing for linux, windows and osx

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24379?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-24379: ------------------------------- Component/s: batch seam2 (was: jsp/jsf/xml/html-source-editing) > javaee tests failing for linux, windows and osx > ----------------------------------------------- > > Key: JBIDE-24379 > URL: https://issues.jboss.org/browse/JBIDE-24379 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: batch, jsf, seam2 > Affects Versions: 4.5.0.AM1 > Reporter: Nick Boldt > Priority: Blocker > Fix For: 4.5.0.AM1 > > Attachments: javaee-test-failures.png, javaee-test-failures_last_pass_jan26.png > > > JavaEE tests have been failing for months. > Please investigate. > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 7 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues April 2017