[jbosstools-issues] [JBoss JIRA] (JBIDE-10840) Consumption of sun.misc.Signal makes Tycho 0.14 fails because of non-OSGi conformance
[
https://issues.jboss.org/browse/JBIDE-10840?page=com.atlassian.jira.plugi...
]
Mickael Istria commented on JBIDE-10840:
----------------------------------------
btw. koen if this doesn't need to be a tycho module then change
the packaging type to jar and you should be ok I guess .. need to get the jar included in
as a raw jar in another plugin then.
Same would apply to forge.runtime. Having a runtime/ module under forge with both runtime
projects would be clearer IMHO. But I imagine it would introduce some more work on the way
they are consumed at runtime. I'd prefer avoiding this path for now.
...Ctrl+C...
Ok, then there may be a SignalHandler somewhere else in forge code that handles the INT
signal differently than usual. That explains sending a SIGINT here has a different
behaviour compared to a System.exit().
I think that the current most efficient way to go ahead with this issue without risk to
change current behavior is to use reflection.
Consumption of sun.misc.Signal makes Tycho 0.14 fails because of
non-OSGi conformance
-------------------------------------------------------------------------------------
Key: JBIDE-10840
URL: https://issues.jboss.org/browse/JBIDE-10840
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: forge
Environment: any
Reporter: Mickael Istria
Assignee: Koen Aers
Priority: Blocker
When building with Tycho, I get:
[ERROR] Failed to execute goal
org.eclipse.tycho:tycho-compiler-plugin:0.14.0-SNAPSHOT:compile (default-compile) on
project org.jboss.tools.forge.runtime.ext: Compilation failure: Compilation failure:
[ERROR]
/home/mistria/workspaceJBossTools/trunk/forge/plugins/org.jboss.tools.forge.runtime.ext/src/org/jboss/tools/forge/runtime/ext/CtrlCAction.java:[8,0]
[ERROR] import sun.misc.Signal;
[ERROR] ^^^^^^^^^^^^^^^
[ERROR] Access restriction: The type Signal is not accessible due to restriction on
classpath entry /usr/lib/jvm/java-6-openjdk/jre/lib/rt.jar
To be clear with OSGi, the forge component has to provide a "framework extension
bundle" to re-export these libs: see
http://blog.meschberger.ch/2008/10/osgi-bundles-require-classes-from.html
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira