|
Re: [galileo] "Unsatisfied version constraint" error [message #480231 is a reply to message #480214] |
Fri, 14 August 2009 13:25 |
Eclipse User |
|
|
|
Originally posted by: richkulp.us.NO_SPAM.ibm.com
If I remember correctly, "unsatisfied version constraint" usually means
that you are trying to run code generated for a higher level of Java
then what you are running on.
Daniel Rampanelli wrote:
> Hi to all,
>
> I'm working on a RCP application and until now I was using Eclipse
> Ganymede (3.4). Since I wanted to take advantage of the new features
> provided by Galileo, I installed it but things are not so nice as I had
> expected. I'm getting a lot of "unsatisfied version constraint" errors.
> I have discovered that I can get rid of those errors by converting the
> "Require-Bundle" dependencies into "Import-Package" statements. But even
> after this change, I have REALLY strange errors (e.g. build path errors
> for SWT classes only on a single class o_O).
>
> Has somebody any clue what is going on here?
>
> Best regards,
> Daniel
>
--
Thanks,
Rich Kulp
|
|
|
|
Re: [galileo] "Unsatisfied version constraint" error [message #480597 is a reply to message #480231] |
Mon, 17 August 2009 19:19 |
|
Rich Kulp wrote:
> Daniel Rampanelli wrote:
>> I'm working on a RCP application and until now I was using Eclipse
>> Ganymede (3.4). Since I wanted to take advantage of the new features
>> provided by Galileo, I installed it but things are not so nice as I
>> had expected. I'm getting a lot of "unsatisfied version constraint"
>> errors. I have discovered that I can get rid of those errors by
>> converting the "Require-Bundle" dependencies into "Import-Package"
>> statements. But even after this change, I have REALLY strange errors
>> (e.g. build path errors for SWT classes only on a single class o_O).
>>
>> Has somebody any clue what is going on here?
> If I remember correctly, "unsatisfied version constraint" usually
means
> that you are trying to run code generated for a higher level of Java
> then what you are running on.
Actually, it's not reporting a problem with the version of the
bytecodes in the classes, it's literally saying that your manifest's
Require-Bundle versions ranges aren't satisfied any more. This can
happen if you had a tight upper bound specified and Galileo's
version numbers increased beyond what was specified.
--
---
Nitin Dahyabhai
Eclipse WTP Source Editing
IBM Rational
_
Nitin Dahyabhai
Eclipse Web Tools Platform
|
|
|
Powered by
FUDForum. Page generated in 0.02292 seconds