]
Paul Leacu commented on JBTIS-1015:
-----------------------------------
Took another quick look at this. I'm really at a loss on how to proceed. EMF Ecore
needs crypto but that will always be a local development system package defined by the
local $JDK_HOME/jre/lib/jce.jar (Java Cryptography Extension). Since we're building a
target platform that by definition is built statically on a server then expanded locally -
the only solution would be for the local project to define where jce.jar is -
unfortunately - the TP definition wants to be complete. If there's another solution
that can work for a local TP ref I guess I'd go with that. The Integration Stack TP
is correct - it just can't cover this situation where the needed plugin is always
defined locally...
Latest JBDSIS Target Platform cannot be used locally
----------------------------------------------------
Key: JBTIS-1015
URL:
https://issues.jboss.org/browse/JBTIS-1015
Project: JBoss Tools Integration Stack
Issue Type: Bug
Components: target-platform
Affects Versions: 4.4.1.CR2-TP
Reporter: Aurélien Pupier
Assignee: Paul Leacu
Attachments: a1.png, a2.png, a3.png, a4.png, a5.png, b1.png, b2.png, commons.io
available in folder.png, commons.io not visible in update site.png
Current state of understanding:
There are 2 different bugs:
* when using local "Directory": the jars which should be exploded in folder
stay in jars
** wondering if org.jboss.tools.tycho-plugins:target-platform-utils should be
responsible to explode them or if it should be the task for P2 itself?
** the implication is that we can't start a CDK server with such a TP
* when using local "Software site": the JVM packages are not recognized
(javax.crypto for instance)
** looks like a p2 bugs
** the implication is that the TP doesn't resolve at all
If one of these two bugs can be fixed, we will have a way to consume a local Target
Platform.
see [JBTIS-1008] for original discussions