Discussion:
Unexpected NPE
(too old to reply)
Krzysztof Daniel
2012-10-31 13:13:38 UTC
Permalink
I'm trying to build Eclipse on arm. While running it with Tycho 0.16 I
get:

[INFO] Resolving dependencies of MavenProject:
eclipse.pde.ui:org.eclipse.pde.api.tools.ee.javase17:1.0.100-SNAPSHOT
@ /builddir/build/BUILD/R4_platform-aggregator/eclipse.pde.ui/apitools/org.eclipse.pde.api.tools.ee.javase17/pom.xml
[INFO] Resolving class path of MavenProject:
eclipse.pde.ui:org.eclipse.pde.api.tools.ee.javase17:1.0.100-SNAPSHOT
@ /builddir/build/BUILD/R4_platform-aggregator/eclipse.pde.ui/apitools/org.eclipse.pde.api.tools.ee.javase17/pom.xml
[ERROR] Internal error: java.lang.NullPointerException: -> [Help 1]
org.apache.maven.InternalErrorException: Internal error:
java.lang.NullPointerException:
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:170)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
at
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
at
org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
Caused by: java.lang.NullPointerException:
at
org.eclipse.tycho.core.osgitools.EquinoxResolver.assertResolved(EquinoxResolver.java:275)
at
org.eclipse.tycho.core.osgitools.EquinoxResolver.newResolvedState(EquinoxResolver.java:71)
at
org.eclipse.tycho.core.osgitools.OsgiBundleProject.getResolverState(OsgiBundleProject.java:258)
at
org.eclipse.tycho.core.osgitools.OsgiBundleProject.resolveClassPath(OsgiBundleProject.java:158)
at
org.eclipse.tycho.core.resolver.DefaultTychoDependencyResolver.resolveProject(DefaultTychoDependencyResolver.java:111)
at
org.eclipse.tycho.core.maven.TychoMavenLifecycleParticipant.afterProjectsRead(TychoMavenLifecycleParticipant.java:80)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:276)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:158)
... 11 more

This is weird, because other platforms (ppc, x86) work fine. Also, other
bundles, similar in shape and requirements, as
eclipse.pde.ui:org.eclipse.pde.api.tools.ee.javase16, can be built
without problems.

Do you have any clue what may be the cause of this behavior?
--
Krzysztof Daniel <***@redhat.com>
Red Hat
Sievers, Jan
2012-10-31 16:10:26 UTC
Permalink
looking at the stacktrace, this may be caused by a different java.io.File behaviour on ARM wrt canonical paths.

we had a similar issue some time ago on linux which occurred if you used symbolic links on the path to the project [1].

is there anything special in terms of filesystem layout of the module that fails to build?

Jan

[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=340852

-----Original Message-----
From: tycho-user-***@eclipse.org [mailto:tycho-user-***@eclipse.org] On Behalf Of Krzysztof Daniel
Sent: Mittwoch, 31. Oktober 2012 14:14
To: tycho-***@eclipse.org
Subject: [tycho-user] Unexpected NPE

I'm trying to build Eclipse on arm. While running it with Tycho 0.16 I
get:

[INFO] Resolving dependencies of MavenProject:
eclipse.pde.ui:org.eclipse.pde.api.tools.ee.javase17:1.0.100-SNAPSHOT
@ /builddir/build/BUILD/R4_platform-aggregator/eclipse.pde.ui/apitools/org.eclipse.pde.api.tools.ee.javase17/pom.xml
[INFO] Resolving class path of MavenProject:
eclipse.pde.ui:org.eclipse.pde.api.tools.ee.javase17:1.0.100-SNAPSHOT
@ /builddir/build/BUILD/R4_platform-aggregator/eclipse.pde.ui/apitools/org.eclipse.pde.api.tools.ee.javase17/pom.xml
[ERROR] Internal error: java.lang.NullPointerException: -> [Help 1]
org.apache.maven.InternalErrorException: Internal error:
java.lang.NullPointerException:
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:170)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
at
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
at
org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
Caused by: java.lang.NullPointerException:
at
org.eclipse.tycho.core.osgitools.EquinoxResolver.assertResolved(EquinoxResolver.java:275)
at
org.eclipse.tycho.core.osgitools.EquinoxResolver.newResolvedState(EquinoxResolver.java:71)
at
org.eclipse.tycho.core.osgitools.OsgiBundleProject.getResolverState(OsgiBundleProject.java:258)
at
org.eclipse.tycho.core.osgitools.OsgiBundleProject.resolveClassPath(OsgiBundleProject.java:158)
at
org.eclipse.tycho.core.resolver.DefaultTychoDependencyResolver.resolveProject(DefaultTychoDependencyResolver.java:111)
at
org.eclipse.tycho.core.maven.TychoMavenLifecycleParticipant.afterProjectsRead(TychoMavenLifecycleParticipant.java:80)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:276)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:158)
... 11 more

This is weird, because other platforms (ppc, x86) work fine. Also, other
bundles, similar in shape and requirements, as
eclipse.pde.ui:org.eclipse.pde.api.tools.ee.javase16, can be built
without problems.

Do you have any clue what may be the cause of this behavior?
--
Krzysztof Daniel <***@redhat.com>
Red Hat
Krzysztof Daniel
2012-11-07 13:28:48 UTC
Permalink
I looked at the code, too, and it indeed looks like the
state.getBundleByLocation(getCanonicalPath(basedir)); call returns null.

But I don't think this is the explanation, because I'm building
http://git.eclipse.org/c/pde/eclipse.pde.ui.git/tree/apitools/org.eclipse.pde.api.tools.ee.javase17,
which differs only in version from previously resolved artifacts..
(javase16, j2se15 etc). Nothing specific... On the other hand, the build
is deterministic and fails always in javase17. Unless the name
matters :-(
Post by Sievers, Jan
looking at the stacktrace, this may be caused by a different java.io.File behaviour on ARM wrt canonical paths.
we had a similar issue some time ago on linux which occurred if you used symbolic links on the path to the project [1].
is there anything special in terms of filesystem layout of the module that fails to build?
Jan
[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=340852
-----Original Message-----
Sent: Mittwoch, 31. Oktober 2012 14:14
Subject: [tycho-user] Unexpected NPE
I'm trying to build Eclipse on arm. While running it with Tycho 0.16 I
eclipse.pde.ui:org.eclipse.pde.api.tools.ee.javase17:1.0.100-SNAPSHOT
@ /builddir/build/BUILD/R4_platform-aggregator/eclipse.pde.ui/apitools/org.eclipse.pde.api.tools.ee.javase17/pom.xml
eclipse.pde.ui:org.eclipse.pde.api.tools.ee.javase17:1.0.100-SNAPSHOT
@ /builddir/build/BUILD/R4_platform-aggregator/eclipse.pde.ui/apitools/org.eclipse.pde.api.tools.ee.javase17/pom.xml
[ERROR] Internal error: java.lang.NullPointerException: -> [Help 1]
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:170)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
at
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
at
org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
at
org.eclipse.tycho.core.osgitools.EquinoxResolver.assertResolved(EquinoxResolver.java:275)
at
org.eclipse.tycho.core.osgitools.EquinoxResolver.newResolvedState(EquinoxResolver.java:71)
at
org.eclipse.tycho.core.osgitools.OsgiBundleProject.getResolverState(OsgiBundleProject.java:258)
at
org.eclipse.tycho.core.osgitools.OsgiBundleProject.resolveClassPath(OsgiBundleProject.java:158)
at
org.eclipse.tycho.core.resolver.DefaultTychoDependencyResolver.resolveProject(DefaultTychoDependencyResolver.java:111)
at
org.eclipse.tycho.core.maven.TychoMavenLifecycleParticipant.afterProjectsRead(TychoMavenLifecycleParticipant.java:80)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:276)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:158)
... 11 more
This is weird, because other platforms (ppc, x86) work fine. Also, other
bundles, similar in shape and requirements, as
eclipse.pde.ui:org.eclipse.pde.api.tools.ee.javase16, can be built
without problems.
Do you have any clue what may be the cause of this behavior?
--
Krzysztof Daniel <***@redhat.com>
Red Hat
Sievers, Jan
2012-11-07 15:40:52 UTC
Permalink
please open a bug with full maven debug log (mvn -X -e -V) attached and steps to reproduce.

if it only happens on ARM, it will be hard to analyse for me to reproduce though.
I may be wrong but I doubt many people are using maven on ARM hardware.

Jan

-----Original Message-----
From: tycho-user-***@eclipse.org [mailto:tycho-user-***@eclipse.org] On Behalf Of Krzysztof Daniel
Sent: Mittwoch, 7. November 2012 14:29
To: Tycho user list
Subject: Re: [tycho-user] Unexpected NPE

I looked at the code, too, and it indeed looks like the
state.getBundleByLocation(getCanonicalPath(basedir)); call returns null.

But I don't think this is the explanation, because I'm building
http://git.eclipse.org/c/pde/eclipse.pde.ui.git/tree/apitools/org.eclipse.pde.api.tools.ee.javase17,
which differs only in version from previously resolved artifacts..
(javase16, j2se15 etc). Nothing specific... On the other hand, the build
is deterministic and fails always in javase17. Unless the name
matters :-(
Post by Sievers, Jan
looking at the stacktrace, this may be caused by a different java.io.File behaviour on ARM wrt canonical paths.
we had a similar issue some time ago on linux which occurred if you used symbolic links on the path to the project [1].
is there anything special in terms of filesystem layout of the module that fails to build?
Jan
[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=340852
-----Original Message-----
Sent: Mittwoch, 31. Oktober 2012 14:14
Subject: [tycho-user] Unexpected NPE
I'm trying to build Eclipse on arm. While running it with Tycho 0.16 I
eclipse.pde.ui:org.eclipse.pde.api.tools.ee.javase17:1.0.100-SNAPSHOT
@ /builddir/build/BUILD/R4_platform-aggregator/eclipse.pde.ui/apitools/org.eclipse.pde.api.tools.ee.javase17/pom.xml
eclipse.pde.ui:org.eclipse.pde.api.tools.ee.javase17:1.0.100-SNAPSHOT
@ /builddir/build/BUILD/R4_platform-aggregator/eclipse.pde.ui/apitools/org.eclipse.pde.api.tools.ee.javase17/pom.xml
[ERROR] Internal error: java.lang.NullPointerException: -> [Help 1]
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:170)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
at
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
at
org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
at
org.eclipse.tycho.core.osgitools.EquinoxResolver.assertResolved(EquinoxResolver.java:275)
at
org.eclipse.tycho.core.osgitools.EquinoxResolver.newResolvedState(EquinoxResolver.java:71)
at
org.eclipse.tycho.core.osgitools.OsgiBundleProject.getResolverState(OsgiBundleProject.java:258)
at
org.eclipse.tycho.core.osgitools.OsgiBundleProject.resolveClassPath(OsgiBundleProject.java:158)
at
org.eclipse.tycho.core.resolver.DefaultTychoDependencyResolver.resolveProject(DefaultTychoDependencyResolver.java:111)
at
org.eclipse.tycho.core.maven.TychoMavenLifecycleParticipant.afterProjectsRead(TychoMavenLifecycleParticipant.java:80)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:276)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:158)
... 11 more
This is weird, because other platforms (ppc, x86) work fine. Also, other
bundles, similar in shape and requirements, as
eclipse.pde.ui:org.eclipse.pde.api.tools.ee.javase16, can be built
without problems.
Do you have any clue what may be the cause of this behavior?
--
Krzysztof Daniel <***@redhat.com>
Red Hat
Krzysztof Daniel
2012-11-08 10:47:11 UTC
Permalink
Reproducing the issue requires nearly 20 hours and less than-trivial arm
emulator setup (to clarify - the issue is reproducible also on an arm
hardware). But I took the liberty to sysout the resolved state and run
the build with debug flags:

http://libra.cs.put.poznan.pl/kdaniel/.build-4.2.1-14.fc18.log

I think that the most important observation is that the resolved state
for org.eclipse.pde.api.tools.ee.javase17 is
Resolved state Resolved OSGi state
RESOLVED
org.eclipse.osgi_3.8.1.qualifier : /home/kdaniel/eclipse/R4_platform-aggregator/rt.equinox.framework/bundles/org.eclipse.osgi


while org.eclipse.pde.api.tools.ee.javase16 state contains much more
bundles.

Is there a way to get more info from the P2resolver about why it puts
only bundle into resolution?
Post by Sievers, Jan
please open a bug with full maven debug log (mvn -X -e -V) attached and steps to reproduce.
if it only happens on ARM, it will be hard to analyse for me to reproduce though.
I may be wrong but I doubt many people are using maven on ARM hardware.
Jan
--
Krzysztof Daniel <***@redhat.com>
Red Hat
Sievers, Jan
2012-11-08 13:37:39 UTC
Permalink
Post by Krzysztof Daniel
Is there a way to get more info from the P2resolver about why it puts
only bundle into resolution?
http://wiki.eclipse.org/Tycho/Target_Platform#Dependency_resolution_troubleshooting

-----Original Message-----
From: tycho-user-***@eclipse.org [mailto:tycho-user-***@eclipse.org] On Behalf Of Krzysztof Daniel
Sent: Donnerstag, 8. November 2012 11:47
To: Tycho user list
Subject: Re: [tycho-user] Unexpected NPE

Reproducing the issue requires nearly 20 hours and less than-trivial arm
emulator setup (to clarify - the issue is reproducible also on an arm
hardware). But I took the liberty to sysout the resolved state and run
the build with debug flags:

http://libra.cs.put.poznan.pl/kdaniel/.build-4.2.1-14.fc18.log

I think that the most important observation is that the resolved state
for org.eclipse.pde.api.tools.ee.javase17 is
Resolved state Resolved OSGi state
RESOLVED
org.eclipse.osgi_3.8.1.qualifier : /home/kdaniel/eclipse/R4_platform-aggregator/rt.equinox.framework/bundles/org.eclipse.osgi


while org.eclipse.pde.api.tools.ee.javase16 state contains much more
bundles.

Is there a way to get more info from the P2resolver about why it puts
only bundle into resolution?
Post by Krzysztof Daniel
please open a bug with full maven debug log (mvn -X -e -V) attached and steps to reproduce.
if it only happens on ARM, it will be hard to analyse for me to reproduce though.
I may be wrong but I doubt many people are using maven on ARM hardware.
Jan
--
Krzysztof Daniel <***@redhat.com>
Red Hat
Sievers, Jan
2012-11-08 13:40:10 UTC
Permalink
BTW not sure if related but it seems you are using outdated tycho 0.16.0-SNAPSHOT which may disappear any time sine 0.16.0 was released.

Jan

-----Original Message-----
From: tycho-user-***@eclipse.org [mailto:tycho-user-***@eclipse.org] On Behalf Of Krzysztof Daniel
Sent: Donnerstag, 8. November 2012 11:47
To: Tycho user list
Subject: Re: [tycho-user] Unexpected NPE

Reproducing the issue requires nearly 20 hours and less than-trivial arm
emulator setup (to clarify - the issue is reproducible also on an arm
hardware). But I took the liberty to sysout the resolved state and run
the build with debug flags:

http://libra.cs.put.poznan.pl/kdaniel/.build-4.2.1-14.fc18.log

I think that the most important observation is that the resolved state
for org.eclipse.pde.api.tools.ee.javase17 is
Resolved state Resolved OSGi state
RESOLVED
org.eclipse.osgi_3.8.1.qualifier : /home/kdaniel/eclipse/R4_platform-aggregator/rt.equinox.framework/bundles/org.eclipse.osgi


while org.eclipse.pde.api.tools.ee.javase16 state contains much more
bundles.

Is there a way to get more info from the P2resolver about why it puts
only bundle into resolution?
Post by Sievers, Jan
please open a bug with full maven debug log (mvn -X -e -V) attached and steps to reproduce.
if it only happens on ARM, it will be hard to analyse for me to reproduce though.
I may be wrong but I doubt many people are using maven on ARM hardware.
Jan
--
Krzysztof Daniel <***@redhat.com>
Red Hat
Sievers, Jan
2012-11-08 14:15:50 UTC
Permalink
there is a non-trivial amount of bash-scripting in log [1],
it seems you are using a custom-built maven version, outdated jdk 7 version on an emulated ARM platform.

sorry, but here you are really on your own.

Jan

---
[1] http://libra.cs.put.poznan.pl/kdaniel/.build-4.2.1-14.fc18.log

from the log:

Apache Maven 3.0.4 (rNON-CANONICAL_2012-10-24_09-27_mockbuild; 2012-10-24 05:27:51-0400)
Maven home: /usr/share/maven
Java version: 1.7.0_03-icedtea, vendor: Oracle Corporation
Java home: /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.9/jre
Default locale: en_US, platform encoding: ANSI_X3.4-1968
OS name: "linux", version: "3.6.3-3.fc18.armv7hl", arch: "arm", family: "unix"



-----Original Message-----
From: tycho-user-***@eclipse.org [mailto:tycho-user-***@eclipse.org] On Behalf Of Krzysztof Daniel
Sent: Donnerstag, 8. November 2012 11:47
To: Tycho user list
Subject: Re: [tycho-user] Unexpected NPE

Reproducing the issue requires nearly 20 hours and less than-trivial arm
emulator setup (to clarify - the issue is reproducible also on an arm
hardware). But I took the liberty to sysout the resolved state and run
the build with debug flags:

http://libra.cs.put.poznan.pl/kdaniel/.build-4.2.1-14.fc18.log

I think that the most important observation is that the resolved state
for org.eclipse.pde.api.tools.ee.javase17 is
Resolved state Resolved OSGi state
RESOLVED
org.eclipse.osgi_3.8.1.qualifier : /home/kdaniel/eclipse/R4_platform-aggregator/rt.equinox.framework/bundles/org.eclipse.osgi


while org.eclipse.pde.api.tools.ee.javase16 state contains much more
bundles.

Is there a way to get more info from the P2resolver about why it puts
only bundle into resolution?
Post by Sievers, Jan
please open a bug with full maven debug log (mvn -X -e -V) attached and steps to reproduce.
if it only happens on ARM, it will be hard to analyse for me to reproduce though.
I may be wrong but I doubt many people are using maven on ARM hardware.
Jan
--
Krzysztof Daniel <***@redhat.com>
Red Hat
Krzysztof Daniel
2012-11-26 12:58:21 UTC
Permalink
For the record - turned out to be a JIT issue. Fixed by adding
-XX:CompileCommand=exclude,org/eclipse/tycho/core/osgitools/EquinoxResolver,newState
to the build command.
Post by Sievers, Jan
there is a non-trivial amount of bash-scripting in log [1],
it seems you are using a custom-built maven version, outdated jdk 7 version on an emulated ARM platform.
sorry, but here you are really on your own.
Jan
---
[1] http://libra.cs.put.poznan.pl/kdaniel/.build-4.2.1-14.fc18.log
Apache Maven 3.0.4 (rNON-CANONICAL_2012-10-24_09-27_mockbuild; 2012-10-24 05:27:51-0400)
Maven home: /usr/share/maven
Java version: 1.7.0_03-icedtea, vendor: Oracle Corporation
Java home: /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.9/jre
Default locale: en_US, platform encoding: ANSI_X3.4-1968
OS name: "linux", version: "3.6.3-3.fc18.armv7hl", arch: "arm", family: "unix"
-----Original Message-----
Sent: Donnerstag, 8. November 2012 11:47
To: Tycho user list
Subject: Re: [tycho-user] Unexpected NPE
Reproducing the issue requires nearly 20 hours and less than-trivial arm
emulator setup (to clarify - the issue is reproducible also on an arm
hardware). But I took the liberty to sysout the resolved state and run
http://libra.cs.put.poznan.pl/kdaniel/.build-4.2.1-14.fc18.log
I think that the most important observation is that the resolved state
for org.eclipse.pde.api.tools.ee.javase17 is
Resolved state Resolved OSGi state
RESOLVED
org.eclipse.osgi_3.8.1.qualifier : /home/kdaniel/eclipse/R4_platform-aggregator/rt.equinox.framework/bundles/org.eclipse.osgi
while org.eclipse.pde.api.tools.ee.javase16 state contains much more
bundles.
Is there a way to get more info from the P2resolver about why it puts
only bundle into resolution?
Post by Sievers, Jan
please open a bug with full maven debug log (mvn -X -e -V) attached and steps to reproduce.
if it only happens on ARM, it will be hard to analyse for me to reproduce though.
I may be wrong but I doubt many people are using maven on ARM hardware.
Jan
--
Krzysztof Daniel <***@redhat.com>
Red Hat
Loading...