[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [orbit-dev] Problems with dependencies when using Orbit p2 repository as part of a target platform (stream, mail
|
ok, thanks Tom!
On Jul 23, 2013, at 12:10 PM, Tom Schindl <tom.schindl@xxxxxxxxxxxxxxx> wrote:
> On 23.07.13 21:00, Cohen, Tamar (ARC-TI)[Stinger Ghaffarian Technologies
> Inc. (SGT Inc.)] wrote:
>> Hi Orbit --
>>
>> I'm in the process of overhauling NASA's Eclipse plugin infrastructure and part of that will be using Orbit. I am working to define target platforms as well as Maven poms that will refer to Orbit.
>>
>> I have found some issues with dependencies; if I select all Orbit plugins and leave the "include required software" checked when I am defining a target platform, there are a number of issues that cannot be resolved.
>>
>> In particular, the ones that have bitten me include:
>> xstream (com.thoughtworks.xstream) - missing requirement - requires package javax.security.auth 0.0.0 (I see something called javax.security.auth.message in orbit, but not javax.security.auth)
>>
>> javax.mail from Glassfish - this requires javax.activation, and when I include that it says it requires org.eclispe.osgi 0.0.0 but it could not be found. Obviously I'm running Eclipse and I have my full Eclipse install as part of the target platform so I don't see why it should not find that plugin, unless it's trying to do an exact match on 0.0.0.
>>
>
> This is a bug in PDE-Target-Platform Wizard because it does not pass a
> EE to p2, those bundles can not be resolved from the java-Version.
>
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=284465 and
> http://dev.eclipse.org/mhonarc/lists/equinox-dev/msg07437.html
>
> Tom
> _______________________________________________
> orbit-dev mailing list
> orbit-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/orbit-dev
