[jbosstools-issues] [JBoss JIRA] (JBIDE-19881) Servertools local build failing with very strange errors
Rob Stryker (JIRA)
issues at jboss.org
Thu May 28 06:04:02 EDT 2015
[ https://issues.jboss.org/browse/JBIDE-19881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13071870#comment-13071870 ]
Rob Stryker commented on JBIDE-19881:
-------------------------------------
Fixed as per comments on PR
> Servertools local build failing with very strange errors
> --------------------------------------------------------
>
> Key: JBIDE-19881
> URL: https://issues.jboss.org/browse/JBIDE-19881
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, server
> Reporter: Rob Stryker
> Assignee: Mickael Istria
> Priority: Blocker
> Fix For: 4.3.0.Beta1
>
>
> So I tried to run my servertools build while making a patch for https://issues.jboss.org/browse/JBIDE-19801
> And I started getting very very weird errors:
> http://fpaste.org/226368/32788687/
> Nick instructed me to check if my build was using Java8, and it wasn't. Somehow it was still using java7.
> So next, I export JAVA_HOME to a java8 installation, and I get a newer weirder error:
> {code}
> Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m; support was removed in 8.0
> Exception in thread "main" java.lang.reflect.InvocationTargetException
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:483)
> at sun.instrument.InstrumentationImpl.loadClassAndStartAgent(InstrumentationImpl.java:386)
> at sun.instrument.InstrumentationImpl.loadClassAndCallPremain(InstrumentationImpl.java:401)
> Caused by: java.lang.RuntimeException: Class java/util/UUID could not be instrumented.
> at org.jacoco.agent.rt_6l8m50.core.runtime.ModifiedSystemClassRuntime.createFor(ModifiedSystemClassRuntime.java:138)
> at org.jacoco.agent.rt_6l8m50.core.runtime.ModifiedSystemClassRuntime.createFor(ModifiedSystemClassRuntime.java:99)
> at org.jacoco.agent.rt_6l8m50.JacocoAgent.createRuntime(JacocoAgent.java:128)
> at org.jacoco.agent.rt_6l8m50.JacocoAgent.init(JacocoAgent.java:74)
> at org.jacoco.agent.rt_6l8m50.JacocoAgent.premain(JacocoAgent.java:165)
> ... 6 more
> Caused by: java.lang.NoSuchFieldException: $jacocoAccess
> at java.lang.Class.getField(Class.java:1690)
> at org.jacoco.agent.rt_6l8m50.core.runtime.ModifiedSystemClassRuntime.createFor(ModifiedSystemClassRuntime.java:136)
> ... 10 more
> FATAL ERROR in native method: processing of -javaagent failed
> {code}
> I come to find out that the jacoco we're using is org.jacoco.agent/0.6.1.201212231917. This was released, obviously by timestamp, in 2012. I find https://github.com/jacoco/jacoco/issues/74 which was a bug fixed in 2013, after our current jacoco. So if we must now run with java8, then clearly we need a newer jacoco.
> Either way, it seems that either my machine is very messed up, or there's a lot of weird stuff changing on build side that's not matching each other.
> No idea how to fix either bug ;)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
More information about the jbosstools-issues
mailing list