[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [tycho-user] Eclipse-ExtensibleAPI an Fragment to Fragment dependency

Tycho follows runtime classpath resolution rules and fragments are
expected to be able to add additional packages regardless of

Try forcing Fragment A as a dependency of Fragment B, either using
explicit Import-Package or using something like the following in B's pom.xml

                <id>Fragment A symbolic name</id>

If this does not work, please submit a bugreport in eclipse bugzilla and
provide small standalone example that demonstrates the problem.

Most likely I will not have time to look at this any time soon, so
consider providing a patch. Relevant code can be found in
org.eclipse.tycho.core.osgitools.DependencyComputer . Wiki [1] explains
how to setup tycho dev env, among other things.

[1] http://wiki.eclipse.org/Tycho/Contributor_Guide


On 12-09-09 9:24 AM, Björn Kasteleiner wrote:

I'm trying to build a Eclipse RCP Application containing a Plugin, which is the host for two fragments.
Currently I'm building the app with the PDE ant build, this is working fine. But I want to switch to tycho.

In the plugin Manifest the Eclipse-ExtensibleAPI option is set to true.
So fare so good. But the there are dependencies from Fragment B to Fragment A. So that Fragment B needs to be aware of Fragment A.

This issue seems to be documented already as https://issues.sonatype.org/browse/TYCHO-60

I've already tried to set the jars.extra.classpath property in the build.properties of the Fragment B project, without any success.
Is there any solution available?

I'm using tycho version 0.15.0 with Eclipse 3.5.1 as target platform.

Best regards


tycho-user mailing list