Igor,
Attached is a project demonstrating the "no system.bundle" error. It
appears that if the bundle's manifest doesn't import org.osgi.framework,
this error appears.
Matt
On Tue, Feb 7, 2012 at 11:55 AM, Igor Fedorenko <
igor@xxxxxxxxxxxxxx
<mailto:
igor@xxxxxxxxxxxxxx>> wrote:
system.bundle is a standard OSGi alias od OSGi framework bundle. There
are some heuristics Tycho uses to either find or fabricate appropriate
system bundle and apparently this does not work for your project. I
don't know if this explains resolution errors you get or not. Please
provide a standalone example project and I will have a look.
--
Regards,
Igor
On 12-02-07 1:09 PM, Ben Abernathy wrote:
Igor,
Your example is very close to one I made that also works in 0.14.0.
Upon looking at our project a little closer, I am noticing the
following warning. I did a quick Google for "tycho
system.bundle", but
couldn't find anything specific aside from some emails on this list.
Is the system.bundle a tycho or equinox thing?
[WARNING] No sustem.bundle
Thank you,
Ben
On Mon, Feb 6, 2012 at 5:27 PM, Igor
I am unable to reproduce the problem (see attached example).
I will need
a standalone complete example project and steps to reproduce
the problem
to be able to help you troubleshoot it.
--
Regards,
Igor
On 12-02-06 5:54 PM, Ben Abernathy wrote:
The Bundle-__RequiredExecutionEnvironment is JavaSE-1.6
and that version
of the JRE does have those packages. Does OSGi/Equinox
treat javax
packages differently such that they are not
automatically provided by
the runtime? And if the default runtime does not expose
those
packages, even though it does contain them, then how
would I specify
them as a maven dependency?
Thanks,
Ben
On Mon, Feb 6, 2012 at 3:32 PM, Igor
Fedorenko<igor@xxxxxxxxxxxxxx <mailto:igor@xxxxxxxxxxxxxx>>
wrote:
Are these packages expected to come from the target
JVM defined by
Bundle-__RequiredExecutionEnvironment?
--
Regards,
Igor
On 12-02-06 4:55 PM, Ben Abernathy wrote:
I am building a project using tycho 0.14.o and
starting with the
9d71c422fb004896bbc8b81963393e__7ede88b5cc
commit (related to this
ticket:
https://bugs.eclipse.org/bugs/__show_bug.cgi?id=367701
<https://bugs.eclipse.org/bugs/show_bug.cgi?id=367701>),
I have
been having problems importing packages such as
javax.xml.bind.annotations.__adapters and
javax.xml.datatype. Upon using
the previous commit, everything builds fine. The
dependencies listed
are not optional and do not specify a version
match. Before I start
building a minimal example project, I thought
I'd shoot off this email
to see if there is an obvious solution. I've
included the stack trace
below for reference.
Thanks in advance,
Ben
--build error--
org.apache.maven.__InternalErrorException:
Internal error:
java.lang.RuntimeException:
org.osgi.framework.__BundleException: Bundle
com.example.core cannot be resolved
Resolution errors:
Bundle com.example.core - Missing
Constraint: Import-Package:
javax.xml.bind.annotation.__adapters;
version="0.0.0"
Bundle com.example.core - Missing
Constraint: Import-Package:
javax.xml.datatype; version="0.0.0"
at
org.apache.maven.DefaultMaven.__execute(DefaultMaven.java:168)
at
org.apache.maven.cli.MavenCli.__execute(MavenCli.java:534)
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:__39)
at
sun.reflect.__DelegatingMethodAccessorImpl.__invoke(__DelegatingMethodAccessorImpl.__java:25)
at
java.lang.reflect.Method.__invoke(Method.java:597)
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.RuntimeException:
com.example.core cannot be
resolved
Resolution errors:
Bundle com.example.core - Missing
Constraint: Import-Package:
javax.xml.bind.annotation.__adapters;
version="0.0.0"
Bundle com.example.core - Missing
Constraint: Import-Package:
javax.xml.datatype; version="0.0.0"
at
org.eclipse.tycho.core.__osgitools.OsgiBundleProject.__getResolverState(__OsgiBundleProject.java:252)
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:61)
at
org.apache.maven.DefaultMaven.__doExecute(DefaultMaven.java:__273)
at
org.apache.maven.DefaultMaven.__execute(DefaultMaven.java:156)
... 11 more
Caused by: org.osgi.framework.__BundleException:
Bundle com.example.core
cannot be resolved
Resolution errors:
Bundle com.example.core - Missing
Constraint: Import-Package:
javax.xml.bind.annotation.__adapters;
version="0.0.0"
Bundle com.example.core - Missing
Constraint: Import-Package:
javax.xml.datatype; version="0.0.0"
at
