[JBoss JIRA] (JBIDE-19463) Cannot connect to remote server in JMX Navigator
by Jeff Bride (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19463?page=com.atlassian.jira.plugi... ]
Jeff Bride commented on JBIDE-19463:
------------------------------------
Martin's option #1 would be of value.
> Cannot connect to remote server in JMX Navigator
> ------------------------------------------------
>
> Key: JBIDE-19463
> URL: https://issues.jboss.org/browse/JBIDE-19463
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jmx
> Affects Versions: 4.2.3.CR1, 4.3.0.Alpha1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.3.0.Beta1
>
>
> When you start a remote EAP 6.3 server with management enabled and set up and then want to connect in JMX Navigator, it does not work - double clicking the connection will not do anything and when you right-click, there is no Connect item.
> For local servers this works fine - there is a Connect item when you right-click the server in JMX Navigator.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBDS-3018) Install screen moves to bottom left corner of the screen
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBDS-3018?page=com.atlassian.jira.plugin.... ]
Martin Malina commented on JBDS-3018:
-------------------------------------
Funny thing, it turns out that this was fixed by some changes in JDK updates - I just tried to run the installer (JBDS 8.1) with Oracle JDK 1.8.0_05 and the issue is there (installer window moves), but with more recent jdk updates it disappeared (e.g. this does not happen with Oracle JDK 1.8.0_45).
> Install screen moves to bottom left corner of the screen
> --------------------------------------------------------
>
> Key: JBDS-3018
> URL: https://issues.jboss.org/browse/JBDS-3018
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: installer, upstream
> Affects Versions: 7.1.1.GA
> Environment: java version "1.8.0"
> Java(TM) SE Runtime Environment (build 1.8.0-b132)
> Java HotSpot(TM) 64-Bit Server VM (build 25.0-b70, mixed mode)
> OSX 10.9.2
> One monitor
> No additional software for windows management
> Reporter: Arun Gupta
> Assignee: Denis Golovin
> Priority: Minor
> Fix For: 8.x, 9.0.x
>
> Attachments: Screen Shot 2014-04-21 at 9.07.53 PM.png
>
>
> I started the install as
> java -jar ~/Downloads/jbdevstudio-product-eap-universal-7.1.1.GA-v20140314-2145-B688.jar
> Install screen (step 1 of 9) popped up in the middle and then right away went in the bottom left corner of the screen as shown in attachment.
> This does not seem right.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-19808) Teiid Designer would like to depend on org.apache.directory.studio plugins
by Paul Richardson (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19808?page=com.atlassian.jira.plugi... ]
Paul Richardson updated JBIDE-19808:
------------------------------------
Description:
*Reason:*
Teiid Designer currently employs a UI for interrogating and importing metadata from an LDAP server. This UI (2 wizards) is limited and prone to issues, eg. [TEIIDDES-2478|https://issues.jboss.org/browse/TEIIDDES-2478].
The project [directory.apache.org|https://directory.apache.org] provides a more sophisticated LDAP browser View UI but has componentized into smaller reusable widgets. The BrowserWidget provides the main tree view and querying ability. Teiid would like to reuse this widget in its UI. Originally, an attempt was made to copy the widget yet porting in this fashion required the porting of 100+ classes hence a dependency makes far more sense.
The current working implementation of Teiid with this widget can be found here:
https://github.com/phantomjinx/teiid-designer/tree/ldap-studio
The current release of the apache.directory project is 2 years old. However, speaking to one of the developers on #apache-directory, the project is being actively maintained and a release is being considered with the next couple of months. In addition, the [svn repository|https://svn.apache.org/repos/asf/directory/studio/trunk] is receiving commits.
*Project page/sources:*
* [directory.apache.org|https://directory.apache.org]
* [svn repository|https://svn.apache.org/repos/asf/directory/studio/trunk]
* [udpate site | http://directory.apache.org/studio/update/2.x/]
*Version:* 2.0.0
*License and owner:* Apache licence and Foundation
*Original p2 repo:* http://directory.apache.org/studio/update/2.x/
*JBoss mirror:*
*Include Sources:* Not available from existing update site but may well be in the next release.
*Affected projects:* Teiid Designer
*Include in JBDS:* Yes
*Type of dependency:* distribution
*List of bundles added/removed:*
* org.apache.directory.api.ldap.model
* org.apache.directory.studio.common.core
* org.apache.directory.studio.common.ui
* org.apache.directory.studio.connection.core
* org.apache.directory.studio.connection.ui
* org.apache.directory.studio.ldapbrowser.common
* org.apache.directory.studio.ldapbrowser.core
* -org.apache.directory.studio.ldapbrowser.ui- Eliminated the dependency
{code}
<!-- Needed by Teiid Designer for support with ldap browsing UI -->
<location includeAllPlatforms="false" includeMode="slicer" includeSource="true" type="InstallableUnit">
<repository location="http://directory.apache.org/studio/update/2.x/"/>
<unit id="org.apache.directory.studio.ldapbrowser.feature.feature.group" version="2.0.0.v20130628"/>
</location>
{code}
was:
*Reason:*
Teiid Designer currently employs a UI for interrogating and importing metadata from an LDAP server. This UI (2 wizards) is limited and prone to issues, eg. [TEIIDDES-2478|https://issues.jboss.org/browse/TEIIDDES-2478].
The project [directory.apache.org|https://directory.apache.org] provides a more sophisticated LDAP browser View UI but has componentized into smaller reusable widgets. The BrowserWidget provides the main tree view and querying ability. Teiid would like to reuse this widget in its UI. Originally, an attempt was made to copy the widget yet porting in this fashion required the porting of 100+ classes hence a dependency makes far more sense.
The current working implementation of Teiid with this widget can be found here:
https://github.com/phantomjinx/teiid-designer/tree/ldap-studio
The current release of the apache.directory project is 2 years old. However, speaking to one of the developers on #apache-directory, the project is being actively maintained and a release is being considered with the next couple of months. In addition, the [svn repository|https://svn.apache.org/repos/asf/directory/studio/trunk] is receiving commits.
*Project page/sources:*
* [directory.apache.org|https://directory.apache.org]
* [svn repository|https://svn.apache.org/repos/asf/directory/studio/trunk]
* [udpate site | http://directory.apache.org/studio/update/2.x/]
*Version:* 2.0.0
*License and owner:* Apache licence and Foundation
*Original p2 repo:* http://directory.apache.org/studio/update/2.x/
*JBoss mirror:*
*Include Sources:* Not available from existing update site but may well be in the next release.
*Affected projects:* Teiid Designer
*Include in JBDS:* Yes
*Type of dependency:* distribution
*List of bundles added/removed:*
* org.apache.directory.api.ldap.model
* org.apache.directory.studio.common.core
* org.apache.directory.studio.common.ui
* org.apache.directory.studio.connection.core
* org.apache.directory.studio.connection.ui
* org.apache.directory.studio.ldapbrowser.common
* org.apache.directory.studio.ldapbrowser.core
-* org.apache.directory.studio.ldapbrowser.ui- Eliminated the dependency
{code}
<!-- Needed by Teiid Designer for support with ldap browsing UI -->
<location includeAllPlatforms="false" includeMode="slicer" includeSource="true" type="InstallableUnit">
<repository location="http://directory.apache.org/studio/update/2.x/"/>
<unit id="org.apache.directory.studio.ldapbrowser.feature.feature.group" version="2.0.0.v20130628"/>
</location>
{code}
> Teiid Designer would like to depend on org.apache.directory.studio plugins
> --------------------------------------------------------------------------
>
> Key: JBIDE-19808
> URL: https://issues.jboss.org/browse/JBIDE-19808
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: target-platform, teiid
> Affects Versions: 4.2.3.Final
> Reporter: Paul Richardson
> Assignee: Barry LaFond
> Attachments: p2.diff
>
>
> *Reason:*
> Teiid Designer currently employs a UI for interrogating and importing metadata from an LDAP server. This UI (2 wizards) is limited and prone to issues, eg. [TEIIDDES-2478|https://issues.jboss.org/browse/TEIIDDES-2478].
> The project [directory.apache.org|https://directory.apache.org] provides a more sophisticated LDAP browser View UI but has componentized into smaller reusable widgets. The BrowserWidget provides the main tree view and querying ability. Teiid would like to reuse this widget in its UI. Originally, an attempt was made to copy the widget yet porting in this fashion required the porting of 100+ classes hence a dependency makes far more sense.
> The current working implementation of Teiid with this widget can be found here:
> https://github.com/phantomjinx/teiid-designer/tree/ldap-studio
> The current release of the apache.directory project is 2 years old. However, speaking to one of the developers on #apache-directory, the project is being actively maintained and a release is being considered with the next couple of months. In addition, the [svn repository|https://svn.apache.org/repos/asf/directory/studio/trunk] is receiving commits.
> *Project page/sources:*
> * [directory.apache.org|https://directory.apache.org]
> * [svn repository|https://svn.apache.org/repos/asf/directory/studio/trunk]
> * [udpate site | http://directory.apache.org/studio/update/2.x/]
> *Version:* 2.0.0
> *License and owner:* Apache licence and Foundation
> *Original p2 repo:* http://directory.apache.org/studio/update/2.x/
> *JBoss mirror:*
> *Include Sources:* Not available from existing update site but may well be in the next release.
> *Affected projects:* Teiid Designer
> *Include in JBDS:* Yes
> *Type of dependency:* distribution
> *List of bundles added/removed:*
> * org.apache.directory.api.ldap.model
> * org.apache.directory.studio.common.core
> * org.apache.directory.studio.common.ui
> * org.apache.directory.studio.connection.core
> * org.apache.directory.studio.connection.ui
> * org.apache.directory.studio.ldapbrowser.common
> * org.apache.directory.studio.ldapbrowser.core
> * -org.apache.directory.studio.ldapbrowser.ui- Eliminated the dependency
> {code}
> <!-- Needed by Teiid Designer for support with ldap browsing UI -->
> <location includeAllPlatforms="false" includeMode="slicer" includeSource="true" type="InstallableUnit">
> <repository location="http://directory.apache.org/studio/update/2.x/"/>
> <unit id="org.apache.directory.studio.ldapbrowser.feature.feature.group" version="2.0.0.v20130628"/>
> </location>
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-19808) Teiid Designer would like to depend on org.apache.directory.studio plugins
by Paul Richardson (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19808?page=com.atlassian.jira.plugi... ]
Paul Richardson updated JBIDE-19808:
------------------------------------
Description:
*Reason:*
Teiid Designer currently employs a UI for interrogating and importing metadata from an LDAP server. This UI (2 wizards) is limited and prone to issues, eg. [TEIIDDES-2478|https://issues.jboss.org/browse/TEIIDDES-2478].
The project [directory.apache.org|https://directory.apache.org] provides a more sophisticated LDAP browser View UI but has componentized into smaller reusable widgets. The BrowserWidget provides the main tree view and querying ability. Teiid would like to reuse this widget in its UI. Originally, an attempt was made to copy the widget yet porting in this fashion required the porting of 100+ classes hence a dependency makes far more sense.
The current working implementation of Teiid with this widget can be found here:
https://github.com/phantomjinx/teiid-designer/tree/ldap-studio
The current release of the apache.directory project is 2 years old. However, speaking to one of the developers on #apache-directory, the project is being actively maintained and a release is being considered with the next couple of months. In addition, the [svn repository|https://svn.apache.org/repos/asf/directory/studio/trunk] is receiving commits.
*Project page/sources:*
* [directory.apache.org|https://directory.apache.org]
* [svn repository|https://svn.apache.org/repos/asf/directory/studio/trunk]
* [udpate site | http://directory.apache.org/studio/update/2.x/]
*Version:* 2.0.0
*License and owner:* Apache licence and Foundation
*Original p2 repo:* http://directory.apache.org/studio/update/2.x/
*JBoss mirror:*
*Include Sources:* Not available from existing update site but may well be in the next release.
*Affected projects:* Teiid Designer
*Include in JBDS:* Yes
*Type of dependency:* distribution
*List of bundles added/removed:*
* org.apache.directory.api.ldap.model
* org.apache.directory.studio.common.core
* org.apache.directory.studio.common.ui
* org.apache.directory.studio.connection.core
* org.apache.directory.studio.connection.ui
* org.apache.directory.studio.ldapbrowser.common
* org.apache.directory.studio.ldapbrowser.core
-* org.apache.directory.studio.ldapbrowser.ui- Eliminated the dependency
{code}
<!-- Needed by Teiid Designer for support with ldap browsing UI -->
<location includeAllPlatforms="false" includeMode="slicer" includeSource="true" type="InstallableUnit">
<repository location="http://directory.apache.org/studio/update/2.x/"/>
<unit id="org.apache.directory.studio.ldapbrowser.feature.feature.group" version="2.0.0.v20130628"/>
</location>
{code}
was:
*Reason:*
Teiid Designer currently employs a UI for interrogating and importing metadata from an LDAP server. This UI (2 wizards) is limited and prone to issues, eg. [TEIIDDES-2478|https://issues.jboss.org/browse/TEIIDDES-2478].
The project [directory.apache.org|https://directory.apache.org] provides a more sophisticated LDAP browser View UI but has componentized into smaller reusable widgets. The BrowserWidget provides the main tree view and querying ability. Teiid would like to reuse this widget in its UI. Originally, an attempt was made to copy the widget yet porting in this fashion required the porting of 100+ classes hence a dependency makes far more sense.
The current working implementation of Teiid with this widget can be found here:
https://github.com/phantomjinx/teiid-designer/tree/ldap-studio
The current release of the apache.directory project is 2 years old. However, speaking to one of the developers on #apache-directory, the project is being actively maintained and a release is being considered with the next couple of months. In addition, the [svn repository|https://svn.apache.org/repos/asf/directory/studio/trunk] is receiving commits.
*Project page/sources:*
* [directory.apache.org|https://directory.apache.org]
* [svn repository|https://svn.apache.org/repos/asf/directory/studio/trunk]
* [udpate site | http://directory.apache.org/studio/update/2.x/]
*Version:* 2.0.0
*License and owner:* Apache licence and Foundation
*Original p2 repo:* http://directory.apache.org/studio/update/2.x/
*JBoss mirror:*
*Include Sources:* Not available from existing update site but may well be in the next release.
*Affected projects:* Teiid Designer
*Include in JBDS:* Yes
*Type of dependency:* distribution
*List of bundles added/removed:*
* org.apache.directory.api.ldap.model
* org.apache.directory.studio.common.core
* org.apache.directory.studio.common.ui
* org.apache.directory.studio.connection.core
* org.apache.directory.studio.connection.ui
* org.apache.directory.studio.ldapbrowser.common
* org.apache.directory.studio.ldapbrowser.core
* org.apache.directory.studio.ldapbrowser.ui
{code}
<!-- Needed by Teiid Designer for support with ldap browsing UI -->
<location includeAllPlatforms="false" includeMode="slicer" includeSource="true" type="InstallableUnit">
<repository location="http://directory.apache.org/studio/update/2.x/"/>
<unit id="org.apache.directory.studio.ldapbrowser.feature.feature.group" version="2.0.0.v20130628"/>
</location>
{code}
> Teiid Designer would like to depend on org.apache.directory.studio plugins
> --------------------------------------------------------------------------
>
> Key: JBIDE-19808
> URL: https://issues.jboss.org/browse/JBIDE-19808
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: target-platform, teiid
> Affects Versions: 4.2.3.Final
> Reporter: Paul Richardson
> Assignee: Barry LaFond
> Attachments: p2.diff
>
>
> *Reason:*
> Teiid Designer currently employs a UI for interrogating and importing metadata from an LDAP server. This UI (2 wizards) is limited and prone to issues, eg. [TEIIDDES-2478|https://issues.jboss.org/browse/TEIIDDES-2478].
> The project [directory.apache.org|https://directory.apache.org] provides a more sophisticated LDAP browser View UI but has componentized into smaller reusable widgets. The BrowserWidget provides the main tree view and querying ability. Teiid would like to reuse this widget in its UI. Originally, an attempt was made to copy the widget yet porting in this fashion required the porting of 100+ classes hence a dependency makes far more sense.
> The current working implementation of Teiid with this widget can be found here:
> https://github.com/phantomjinx/teiid-designer/tree/ldap-studio
> The current release of the apache.directory project is 2 years old. However, speaking to one of the developers on #apache-directory, the project is being actively maintained and a release is being considered with the next couple of months. In addition, the [svn repository|https://svn.apache.org/repos/asf/directory/studio/trunk] is receiving commits.
> *Project page/sources:*
> * [directory.apache.org|https://directory.apache.org]
> * [svn repository|https://svn.apache.org/repos/asf/directory/studio/trunk]
> * [udpate site | http://directory.apache.org/studio/update/2.x/]
> *Version:* 2.0.0
> *License and owner:* Apache licence and Foundation
> *Original p2 repo:* http://directory.apache.org/studio/update/2.x/
> *JBoss mirror:*
> *Include Sources:* Not available from existing update site but may well be in the next release.
> *Affected projects:* Teiid Designer
> *Include in JBDS:* Yes
> *Type of dependency:* distribution
> *List of bundles added/removed:*
> * org.apache.directory.api.ldap.model
> * org.apache.directory.studio.common.core
> * org.apache.directory.studio.common.ui
> * org.apache.directory.studio.connection.core
> * org.apache.directory.studio.connection.ui
> * org.apache.directory.studio.ldapbrowser.common
> * org.apache.directory.studio.ldapbrowser.core
> -* org.apache.directory.studio.ldapbrowser.ui- Eliminated the dependency
> {code}
> <!-- Needed by Teiid Designer for support with ldap browsing UI -->
> <location includeAllPlatforms="false" includeMode="slicer" includeSource="true" type="InstallableUnit">
> <repository location="http://directory.apache.org/studio/update/2.x/"/>
> <unit id="org.apache.directory.studio.ldapbrowser.feature.feature.group" version="2.0.0.v20130628"/>
> </location>
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-19881) Servertools local build failing with very strange errors
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19881?page=com.atlassian.jira.plugi... ]
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)
10 years, 10 months
[JBoss JIRA] (JBIDE-19881) Servertools local build failing with very strange errors
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19881?page=com.atlassian.jira.plugi... ]
Mickael Istria updated JBIDE-19881:
-----------------------------------
Priority: Blocker (was: Major)
> 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
> 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)
10 years, 10 months