Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Archived » Buckminster » NullPointerException when bundle depends on the system bundle
NullPointerException when bundle depends on the system bundle [message #494540] Sat, 31 October 2009 09:41 Go to next message
Peter Kullmann is currently offline Peter KullmannFriend
Messages: 240
Registered: July 2009
Senior Member
Hi

I have a problem resolving bundles that have a dependency on the system
bundle. To reproduce try to materialize "javax.xml" from orbit. Here's
the output:

....
org.eclipse.osgi:osgi.bundle: Found match
org.eclipse.osgi:osgi.bundle$3.5.1.R35x_v20090827
Provider
eclipse.import( http://download.eclipse.org/tools/orbit/downloads/drops/R200 90529135407/updateSite?importType=binary):
materializing to /Users/kup/eclipse/ws-target/plugins/javax.xml/
Project refresh on javax.xml failed: null
java.lang.NullPointerException
at
org.eclipse.osgi.internal.resolver.VersionConstraintImpl.get Name(VersionConstraintImpl.java:30)
at
org.eclipse.buckminster.pde.cspecgen.bundle.CSpecFromBinary. addImports(CSpecFromBinary.java:264)
at
org.eclipse.buckminster.pde.cspecgen.bundle.CSpecFromBinary. generate(CSpecFromBinary.java:106)
at
org.eclipse.buckminster.pde.cspecgen.bundle.BundleBuilder.pa rseFile(BundleBuilder.java:286)
at
org.eclipse.buckminster.pde.cspecgen.PDEBuilder.build(PDEBui lder.java:86)
at
org.eclipse.buckminster.core.ctype.AbstractComponentType.get Resolution(AbstractComponentType.java:343)
at
org.eclipse.buckminster.pde.internal.EclipseBundleType.getRe solution(EclipseBundleType.java:55)
at
org.eclipse.buckminster.core.ctype.AbstractComponentType.get Resolution(AbstractComponentType.java:207)
at
org.eclipse.buckminster.core.resolver.LocalResolver.fromPath (LocalResolver.java:187)
at
org.eclipse.buckminster.core.resolver.LocalResolver.fromPath (LocalResolver.java:111)
at
org.eclipse.buckminster.core.metadata.MetadataSynchronizer.r efreshProject(MetadataSynchronizer.java:365)
at
org.eclipse.buckminster.core.metadata.MetadataSynchronizer$M etadataRefreshJob.run(MetadataSynchronizer.java:140)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)


This is not so bad as buckminster manages to materialize the bundle. It
gets more of a problem if I try to resolve such a bundle from a cvs
repository.

I'm using this:
Buckminster - Core 1.1.350.r10811
org.eclipse.buckminster.core.feature.feature.group
Buckminster - CVS support 1.0.350.r10811
org.eclipse.buckminster.cvs.feature.feature.group
Buckminster - PDE support 1.1.350.r10837
org.eclipse.buckminster.pde.feature.feature.group


Cheers,
Peter
Re: NullPointerException when bundle depends on the system bundle [message #494559 is a reply to message #494540] Sat, 31 October 2009 12:21 Go to previous messageGo to next message
Thomas Hallgren is currently offline Thomas HallgrenFriend
Messages: 3240
Registered: July 2009
Senior Member
Hi Peter,
Can you please attach this information to a Bugzilla?

Thanks,
Thomas Hallgren

On 10/31/2009 10:41 AM, Peter Kullmann wrote:
> Hi
>
> I have a problem resolving bundles that have a dependency on the system
> bundle. To reproduce try to materialize "javax.xml" from orbit. Here's
> the output:
>
> ...
> org.eclipse.osgi:osgi.bundle: Found match
> org.eclipse.osgi:osgi.bundle$3.5.1.R35x_v20090827
> Provider
> eclipse.import( http://download.eclipse.org/tools/orbit/downloads/drops/R200 90529135407/updateSite?importType=binary):
> materializing to /Users/kup/eclipse/ws-target/plugins/javax.xml/
> Project refresh on javax.xml failed: null
> java.lang.NullPointerException
> at
> org.eclipse.osgi.internal.resolver.VersionConstraintImpl.get Name(VersionConstraintImpl.java:30)
>
> at
> org.eclipse.buckminster.pde.cspecgen.bundle.CSpecFromBinary. addImports(CSpecFromBinary.java:264)
>
> at
> org.eclipse.buckminster.pde.cspecgen.bundle.CSpecFromBinary. generate(CSpecFromBinary.java:106)
>
> at
> org.eclipse.buckminster.pde.cspecgen.bundle.BundleBuilder.pa rseFile(BundleBuilder.java:286)
>
> at
> org.eclipse.buckminster.pde.cspecgen.PDEBuilder.build(PDEBui lder.java:86)
> at
> org.eclipse.buckminster.core.ctype.AbstractComponentType.get Resolution(AbstractComponentType.java:343)
>
> at
> org.eclipse.buckminster.pde.internal.EclipseBundleType.getRe solution(EclipseBundleType.java:55)
>
> at
> org.eclipse.buckminster.core.ctype.AbstractComponentType.get Resolution(AbstractComponentType.java:207)
>
> at
> org.eclipse.buckminster.core.resolver.LocalResolver.fromPath (LocalResolver.java:187)
>
> at
> org.eclipse.buckminster.core.resolver.LocalResolver.fromPath (LocalResolver.java:111)
>
> at
> org.eclipse.buckminster.core.metadata.MetadataSynchronizer.r efreshProject(MetadataSynchronizer.java:365)
>
> at
> org.eclipse.buckminster.core.metadata.MetadataSynchronizer$M etadataRefreshJob.run(MetadataSynchronizer.java:140)
>
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
>
>
> This is not so bad as buckminster manages to materialize the bundle. It
> gets more of a problem if I try to resolve such a bundle from a cvs
> repository.
>
> I'm using this:
> Buckminster - Core 1.1.350.r10811
> org.eclipse.buckminster.core.feature.feature.group
> Buckminster - CVS support 1.0.350.r10811
> org.eclipse.buckminster.cvs.feature.feature.group
> Buckminster - PDE support 1.1.350.r10837
> org.eclipse.buckminster.pde.feature.feature.group
>
>
> Cheers,
> Peter
Re: NullPointerException when bundle depends on the system bundle [message #494562 is a reply to message #494559] Sat, 31 October 2009 13:20 Go to previous message
Peter Kullmann is currently offline Peter KullmannFriend
Messages: 240
Registered: July 2009
Senior Member
This is the bugzilla: https://bugs.eclipse.org/bugs/show_bug.cgi?id=293849
Previous Topic:Problem resolving JAXB compontents from maven repository
Next Topic:bundle build order is taken from feature
Goto Forum:
  


Current Time: Fri Mar 29 02:10:33 GMT 2024

Powered by FUDForum. Page generated in 0.02063 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top