Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [tycho-user] Unexpected NPE

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-bounces@xxxxxxxxxxx [mailto:tycho-user-bounces@xxxxxxxxxxx] On Behalf Of Krzysztof Daniel
Sent: Mittwoch, 31. Oktober 2012 14:14
To: tycho-user@xxxxxxxxxxx
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 <kdaniel@xxxxxxxxxx>
Red Hat

_______________________________________________
tycho-user mailing list
tycho-user@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/tycho-user


Back to the top