if adding the import-package doesn't work, you can create a bundle
fragment to the org.eclipse.osgi bundle...
this was what I have to do to access xjc and some other internal
packages. take a look at the manifest:
Manifest-Version: 1.0
Bundle-ManifestVersion: 2
Bundle-Name: %pluginName
Bundle-SymbolicName: com.c4biz.osgiutils.jdk.deps
Bundle-Version: 0.0.1.qualifier
Bundle-Vendor: %providerName
Fragment-Host: org.eclipse.osgi;extension:=framework
Export-Package: com.sun.codemodel,
com.sun.msv.datatype,
com.sun.msv.datatype.xsd,
com.sun.tools.xjc,
com.sun.tools.xjc.model,
com.sun.tools.xjc.outline,
org.relaxng.datatype,
sun.misc,
sun.reflect
Bundle-RequiredExecutionEnvironment: JavaSE-1.6
cheers
Cristiano
On 04/01/12 13:11, Tom Brus wrote:
no it does not... would that help?
it is com.sun.xml.internal.bind.marshaller.NamespacePrefixMapper
by the way...
but it works under manual eclipse and under Tycho
0.12.0... can you elaborate?
but I will try anyhow :-)
-Tom
On Wed, Jan 4, 2012 at 16:48, Cristiano Gavião <cvgaviao@xxxxxxxxx>
wrote:
One question:
the bundle that is accessing this api has a Import-Package
to where NamespacePrefixMapper
is located ?
On 04/01/12 12:30, Tom Brus wrote:
Hi
list,
I am trying to
move from Tycho 0.12.0 to 0.14.0-SNAPSHOT (I
need some feature fixed in 14).
My project
builds just fine under 0.12.0.
When I
use 0.14.0-SNAPSHOT I get the following error
from the java compiler:
Access
restriction: The type NamespacePrefixMapper
is not accessible due to restriction on
classpath entry
/usr/lib/jvm/java-6-openjdk/jre/lib/rt.jar
Indeed, my source
uses NamespacePrefixMapper and indeed that
should not be done.
But why does
that suddenly break the build? Or maybe I should
ask: why did it not break under 0.12.0?
To fix that
I tried to put the following in my pom:
<build>
<plugins>
<plugin>
<groupId>org.eclipse.tycho</groupId>
<artifactId>tycho-compiler-plugin</artifactId>
<version>0.14.0-SNAPSHOT</version>
<configuration>
<compilerArgument>-XDignore.symbol.file=true</compilerArgument>
</configuration>
</plugin>
</plugins>
</build>
but this does not
fix it. I verified that the option is passed to
the plugin, the logging shows:
...
[DEBUG] (f)
compileSourceRoots = [.....]
[DEBUG] (f)
compilerArgument =
-XDignore.symbol.file=true
[DEBUG] (f)
compilerId = jdt
...
Furthermore I see
the following line in the log, which was not there
in 0.12.0, does that give a clue:
[DEBUG] (f)
useJDK = SYSTEM
Any ideas?
Thanks,
Tom
_______________________________________________
tycho-user mailing list
tycho-user@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/tycho-user
_______________________________________________
tycho-user mailing list
tycho-user@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/tycho-user
_______________________________________________
tycho-user mailing list
tycho-user@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/tycho-user
|
