Re: [cbi-dev] WTP build failed to compile with latest Maven

[Samuel Wu <samuelwu@xxxxxxxxxx>]

The following are the jdk set in toolchains.xml
    <jdkHome>/shared/webtools/apps/IBMJava2-142-SR13FP10/jre</jdkHome>
    <jdkHome>/shared/common/jdk-1.5.0-22.x86_64/jre</jdkHome>

The following are the error messages in the Maven 3.3.1 build log.
[DEBUG] Toolchain JDK[/opt/public/common/j2sdk1.4.2_19/jre] doesn't match required property: id
[DEBUG] Toolchain JDK[/opt/public/common/jdk1.5.0-latest/jre] doesn't match required property: id

The JDK paths are different from the settings in the WTP toolchains.xml. Is it because the setting from HIPP is ignored by Maven 3.3.1 and the default system toolchains was used?

Best Regards

Samuel Wu

Samuel Wu---07/06/2015 02:20:37 PM---Thank you, Thanh, for the information. Carl told me another way of setting -X as well. Here is the c

From: Samuel Wu/Toronto/IBM@IBMCA
To: Common-build Developers discussion <cbi-dev@xxxxxxxxxxx>
Date: 07/06/2015 02:20 PM
Subject: Re: [cbi-dev] WTP build failed to compile with latest Maven
Sent by: cbi-dev-bounces@xxxxxxxxxxx

---

Thank you, Thanh, for the information. Carl told me another way of setting -X as well. Here is the current status after switching back to the "Invoke Maven 3 build" step.

The Maven 3.2.5 build went back to normal and built successfully(https://hudson.eclipse.org/webtools/job/WTP-R3_7_x_Maintenance_test/15/). Maven 3.3.1 build still failed (https://hudson.eclipse.org/webtools/job/WTP-R3_7_x_Maintenance_test/13/). The following class path was included in the 3.2.5 build, which is the one we want and set in the toolchains.xml.
[DEBUG] Using javaHome: /shared/webtools/apps/IBMJava2-142-SR13FP10/jre

The following one was used in the 3.3.1 build. 
[DEBUG] Using javaHome: /opt/public/common/j2sdk1.4.2_19/jre
It looks that the setting in toolchains.xml was ignored by 3.3.1.

With the following error messages, I wonder whether 3.3.1 had a problem to parse the toolchains.xml.
[DEBUG] Toolchain JDK[/opt/public/common/cbi/ee/CDC-1.0_Foundation-1.0] doesn't match required property: id
[DEBUG] Toolchain JDK[/opt/public/common/cbi/ee/CDC-1.1_Foundation-1.1] doesn't match required property: id
[DEBUG] Toolchain JDK[/opt/public/common/cbi/ee/OSGi_Minimum-1.0] doesn't match required property: id
[DEBUG] Toolchain JDK[/opt/public/common/cbi/ee/OSGi_Minimum-1.1] doesn't match required property: id
[DEBUG] Toolchain JDK[/opt/public/common/cbi/ee/OSGi_Minimum-1.2] doesn't match required property: id
[DEBUG] Toolchain JDK[/opt/public/common/j2sdk1.4.2_19/jre] doesn't match required property: id

It looks more like a bug now.

Best Regards

Samuel Wu

Samuel Wu---07/06/2015 09:52:09 AM---Thank you, Jan/Mikael, for the suggestion. WTP toolchains.xml is contributed through the Hudson buil

From: Samuel Wu/Toronto/IBM@IBMCA
To: Common-build Developers discussion <cbi-dev@xxxxxxxxxxx>
Date: 07/06/2015 09:52 AM
Subject: Re: [cbi-dev] WTP build failed to compile with latest Maven
Sent by: cbi-dev-bounces@xxxxxxxxxxx

---

Thank you, Jan/Mikael, for the suggestion. WTP toolchains.xml is contributed through the Hudson build configuration. I wonder whether you can advise its exact location on the build machine. I checked my personal account on BUILD.ECLIPSE.ORG and failed to find the .m2 folder. I guess it's on the HIPPs of WTP as well. I haven't figured out how to access it yet.

Best Regards

Samuel Wu

Mikael Barbero ---07/06/2015 05:03:54 AM---Every single HIPPs have a toolchains.xml defined in their ~/.m2 folder. It is a symlink: toolchains.

From: Mikael Barbero <mikael@xxxxxxxxxxx>
To: Common-build Developers discussion <cbi-dev@xxxxxxxxxxx>
Date: 07/06/2015 05:03 AM
Subject: Re: [cbi-dev] WTP build failed to compile with latest Maven
Sent by: cbi-dev-bounces@xxxxxxxxxxx

---

Every single HIPPs have a toolchains.xml defined in their ~/.m2 folder. It is a symlink:

toolchains.xml -> /opt/public/common/maven-toolchains.xml

So, AFAIK, it should be taken into account as it is done in ~/.m2, isn't it?

Mikael

> Le 6 juil. 2015 à 09:51, Sievers, Jan <jan.sievers@xxxxxxx> a écrit :
> 
> so it's not related to the maven version.
> 
> from https://hudson.eclipse.org/webtools/job/WTP-R3_7_x_Maintenance_test/10/consoleText :
> 
> [DEBUG] Toolchain JDK[/opt/public/common/cbi/ee/CDC-1.0_Foundation-1.0] doesn't match required property: id
> [DEBUG] Toolchain JDK[/opt/public/common/cbi/ee/CDC-1.1_Foundation-1.1] doesn't match required property: id
> [DEBUG] Toolchain JDK[/opt/public/common/cbi/ee/OSGi_Minimum-1.0] doesn't match required property: id
> [DEBUG] Toolchain JDK[/opt/public/common/cbi/ee/OSGi_Minimum-1.1] doesn't match required property: id
> [DEBUG] Toolchain JDK[/opt/public/common/cbi/ee/OSGi_Minimum-1.2] doesn't match required property: id
> [DEBUG] Toolchain JDK[/opt/public/common/j2sdk1.4.2_19/jre] doesn't match required property: id
> 
> 
> that means your toolchains file you sent earlier does not take effect as the JDK paths are all different.
> 
> Did you specify mvn --toolchains /path/to/toolchains.xml ?
> 
> Jan
> 
> 
> From: cbi-dev-bounces@xxxxxxxxxxx [mailto:cbi-dev-bounces@xxxxxxxxxxx] On Behalf Of Samuel Wu
> Sent: Freitag, 3. Juli 2015 20:29
> To: Common-build Developers discussion
> Subject: Re: [cbi-dev] WTP build failed to compile with latest Maven
> 
> After adding -X option, the build failed now for both Maven 3.3.1 and 3.2.5 with the same compile error message. 
> [ERROR] /jobs/genie.webtools/WTP-R3_7_x_Maintenance_test/workspace/webtools.webservices/bundles/org.eclipse.wst.wsdl/src-wsdl/org/eclipse/wst/wsdl/util/WSDLParser.java:[787]
> [ERROR] catch (IOException exception)
> [ERROR] ^^^^^^^^^^^
> [ERROR] Unreachable catch block for IOException. This exception is never thrown from the try statement body
> 
> The following two properties were set in the 3.3.1 Maven but not in 3.2.5.
> maven.multiModuleProjectDirectory=/jobs/genie.webtools/WTP-R3_7_x_Maintenance_test/workspace,
> env.MAVEN_PROJECTBASEDIR=/jobs/genie.webtools/WTP-R3_7_x_Maintenance_test/workspace, 
> 
> The details can be found in the following two builds.
> (3.3.1) https://hudson.eclipse.org/webtools/job/WTP-R3_7_x_Maintenance_test/10/
> (3.2.5) https://hudson.eclipse.org/webtools/job/WTP-R3_7_x_Maintenance_test/11/
> 
> Best Regards
> 
> Samuel Wu
> "Sievers, Jan" ---07/03/2015 10:32:07 AM---don't replicate the exact commandline generated by the hudson-maven integration as this is where we
> 
> From: "Sievers, Jan" <jan.sievers@xxxxxxx>
> To: Common-build Developers discussion <cbi-dev@xxxxxxxxxxx>
> Date: 07/03/2015 10:32 AM
> Subject: Re: [cbi-dev] WTP build failed to compile with latest Maven
> Sent by: cbi-dev-bounces@xxxxxxxxxxx
> ________________________________________
> 
> 
> 
> don't replicate the exact commandline generated by the hudson-maven integration as this is where we suspect the problem is coming from.
> Remove the arguments added by hudson. Sth like
> 
> /shared/common/apache-maven-latest/bin/mvn clean install -V -B -Dmaven.test.skip=true -Dmaven.test.error.ignore=true -Dmaven.test.failure.ignore=true -Dsurefire.timeout=1800 -DskipWithIssues=false  -Dmaven.repo.local=/home/hudson/genie.webtools/.hudson/jobs/WTP-R3_7_x_Maintenance_test/workspace/.maven/repo -f webtools.webservices/pom.xml -P bree-libs -P eclipse-sign
> 
> Regards
> Jan
> 
> 
> 
> 
> From: cbi-dev-bounces@xxxxxxxxxxx [mailto:cbi-dev-bounces@xxxxxxxxxxx] On Behalf Of Samuel Wu
> Sent: Freitag, 3. Juli 2015 15:46
> To: Common-build Developers discussion
> Subject: Re: [cbi-dev] WTP build failed to compile with latest Maven
> 
> Thank you, Jan, for the suggestion. I've tried to call mvn directly from a Execute shell step in the HUDSON build but it failed with a connection refused error.
> [ERROR] o.h.m.e.DelegatingEventSpy - Init failed
> java.net.ConnectException: Connection refused
> at java.net.PlainSocketImpl.socketConnect(Native Method) ~[na:1.8.0_40]
> at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:345) ~[na:1.8.0_40]
> at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206) ~[na:1.8.0_40]
> at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188) ~[na:1.8.0_40]
> at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392) ~[na:1.8.0_40]
> at java.net.Socket.connect(Socket.java:589) ~[na:1.8.0_40]
> at java.net.Socket.connect(Socket.java:538) ~[na:1.8.0_40]
> at java.net.Socket.<init>(Socket.java:434) ~[na:1.8.0_40]
> at java.net.Socket.<init>(Socket.java:211) ~[na:1.8.0_40]
> at org.hudsonci.maven.eventspy.common.RemotingClient.open(RemotingClient.java:87) ~[maven3-eventspy-runtime.jar:na]
> at org.hudsonci.maven.eventspy_31.RemotingEventSpy.openChannel(RemotingEventSpy.java:90) ~[maven3-eventspy-3.1.jar:na]
> at org.hudsonci.maven.eventspy_31.RemotingEventSpy.init(RemotingEventSpy.java:118) ~[maven3-eventspy-3.1.jar:na]
> at org.hudsonci.maven.eventspy_31.DelegatingEventSpy.init(DelegatingEventSpy.java:127) ~[maven3-eventspy-3.1.jar:na]
> at org.apache.maven.eventspy.internal.EventSpyDispatcher.init(EventSpyDispatcher.java:85) [maven-core-3.3.1.jar:3.3.1]
> at org.apache.maven.cli.MavenCli.container(MavenCli.java:577) [maven-embedder-3.3.1.jar:3.3.1]
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:279) [maven-embedder-3.3.1.jar:3.3.1]
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:197) [maven-embedder-3.3.1.jar:3.3.1]
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[na:1.8.0_40]
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[na:1.8.0_40]
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:1.8.0_40]
> at java.lang.reflect.Method.invoke(Method.java:497) ~[na:1.8.0_40]
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289) [plexus-classworlds-2.5.2.jar:na]
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229) [plexus-classworlds-2.5.2.jar:na]
> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415) [plexus-classworlds-2.5.2.jar:na]
> at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356) [plexus-classworlds-2.5.2.jar:na]
> [ERROR] ABORTED
> [ERROR] Failed to initialize
> [ERROR] Caused by: Connection refused
> 
> The following mvn command is what I was trying to run
> /shared/common/apache-maven-latest/bin/mvn clean install -V -B -Dmaven.test.skip=true -Dmaven.test.error.ignore=true -Dmaven.test.failure.ignore=true -Dsurefire.timeout=1800 -DskipWithIssues=false -Dmaven.ext.class.path=/home/hudson/genie.webtools/.hudson/maven/slavebundle/resources:/home/hudson/genie.webtools/.hudson/maven/slavebundle/lib/maven3-eventspy-3.1.jar:/home/hudson/genie.webtools/.hudson/war/webapp/WEB-INF/lib/hudson-remoting-3.0.0.jar -Dhudson.eventspy.port=57990 -Dmaven.repo.local=/home/hudson/genie.webtools/.hudson/jobs/WTP-R3_7_x_Maintenance_test/workspace/.maven/repo -f webtools.webservices/pom.xml -P bree-libs -P eclipse-sign -ff
> 
> I wonder whether I take your suggestion a wrong way. 
> 
> Best Regards
> 
> Samuel Wu
> 
> "Sievers, Jan" ---07/03/2015 04:45:22 AM---yes probably toolchains-related. looks like https://bugs.eclipse.org/bugs/show_bug.cgi?id=466977#c13
> 
> From: "Sievers, Jan" <jan.sievers@xxxxxxx>
> To: Common-build Developers discussion <cbi-dev@xxxxxxxxxxx>
> Date: 07/03/2015 04:45 AM
> Subject: Re: [cbi-dev] WTP build failed to compile with latest Maven
> Sent by: cbi-dev-bounces@xxxxxxxxxxx
> ________________________________________
> 
> 
> 
> yes probably toolchains-related.
> looks like https://bugs.eclipse.org/bugs/show_bug.cgi?id=466977#c13 to me
> 
> the EventSpyProcessor looks suspiscious to me. Could be a bug in the maven hudson integration.
> To verify this, try directly executing mvn in a conosle build step instead of a maven build step.
> 
> 
> Jan
> 
> From: cbi-dev-bounces@xxxxxxxxxxx [mailto:cbi-dev-bounces@xxxxxxxxxxx] On Behalf Of Samuel Wu
> Sent: Freitag, 3. Juli 2015 05:33
> To: Common-build Developers discussion
> Subject: [cbi-dev] WTP build failed to compile with latest Maven
> 
> WTP build works well with Maven 3.2.5. After moving to Maven 3.3.1, it failed to compile the plugin org.eclipse.wst.wsdl with the following error.
> [ERROR] Failed to execute goal org.eclipse.tycho:tycho-compiler-plugin:0.20.0:compile (default-compile) on project org.eclipse.wst.wsdl: Compilation failure: Compilation failure:
> [ERROR] /jobs/genie.webtools/WTP-R3_7_x_Maintenance_test/workspace/webtools.webservices/bundles/org.eclipse.wst.wsdl/src-wsdl/org/eclipse/wst/wsdl/util/WSDLParser.java:[787]
> [ERROR] catch (IOException exception)
> [ERROR] ^^^^^^^^^^^
> [ERROR] Unreachable catch block for IOException. This exception is never thrown from the try statement body
> 
> It has been verified that the project can be compiled without a problem locally.
> The following warning messages were found in the Maven 3.3.1 build log. 
> [DEBUG] Connected to remote
> [WARN] o.h.m.e.EventSpyProcessor - Unhandled event: org.apache.maven.toolchain.building.DefaultToolchainsBuildingRequest@39aa45a1 (org.apache.maven.toolchain.building.DefaultToolchainsBuildingRequest)
> [WARN] o.h.m.e.EventSpyProcessor - Unhandled event: org.apache.maven.toolchain.building.DefaultToolchainsBuildingRequest@39aa45a1 (org.apache.maven.toolchain.building.DefaultToolchainsBuildingRequest)
> [INFO] o.h.m.e.h.MavenExecutionRequestHandler - Using tool-chains document ID: f1492191-c1d9-4caa-a6bf-44160486454d
> [INFO] Scanning for projects...
> 
> The following information was generated by Maven 3.2.5 build.
> [DEBUG] Connected to remote
> [INFO] o.h.m.e.h.MavenExecutionRequestHandler - Using tool-chains document ID: f1492191-c1d9-4caa-a6bf-44160486454d
> [INFO] Scanning for projects...
> 
> I wonder whether this has something to do with the toolchain. The BREE of the plugin is Bundle-RequiredExecutionEnvironment: J2SE-1.4 and the current toolchain is set up as the following.
> <toolchains>
>   <toolchain>
>     <type>jdk</type>
>     <provides>
>       <id>J2SE-1.4</id>
>     </provides>
>     <configuration>
>       <jdkHome>/shared/webtools/apps/IBMJava2-142-SR13FP10/jre</jdkHome>
>     </configuration>
>   </toolchain>
>   <toolchain>
>     <type>jdk</type>
>     <provides>
>       <id>J2SE-1.5</id>
>     </provides>
>     <configuration>
>       <jdkHome>/shared/common/jdk-1.5.0-22.x86_64/jre</jdkHome>
>     </configuration>
>   </toolchain>
>   <toolchain>
>     <type>jdk</type>
>     <provides>
>       <id>JavaSE-1.6</id>
>     </provides>
>     <configuration>
>       <jdkHome>/shared/common/jdk1.6.0_45/jre</jdkHome>
>     </configuration>
>   </toolchain>
>   <toolchain>
>     <type>jdk</type>
>     <provides>
>       <id>JavaSE-1.7</id>
>     </provides>
>     <configuration>
>       <jdkHome>/shared/common/jdk1.7.0_25/jre</jdkHome>
>     </configuration>
>   </toolchain>
> 
> </toolchains>
> 
> I appreciate if someone can shed some light.
> 
> Best Regards
> 
> Samuel Wu
> _______________________________________________
> cbi-dev mailing list
> cbi-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe from this list, visit
> https://dev.eclipse.org/mailman/listinfo/cbi-dev
> 
> _______________________________________________
> cbi-dev mailing list
> cbi-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe from this list, visit
> https://dev.eclipse.org/mailman/listinfo/cbi-dev
> 
> _______________________________________________
> cbi-dev mailing list
> cbi-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe from this list, visit
> https://dev.eclipse.org/mailman/listinfo/cbi-dev

_______________________________________________
cbi-dev mailing list
cbi-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/cbi-dev

_______________________________________________
cbi-dev mailing list
cbi-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/cbi-dev_______________________________________________
cbi-dev mailing list
cbi-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/cbi-dev