|
|
Re: eclipse plugin deployment troubleshooting [message #1125 is a reply to message #1098] |
Wed, 16 April 2008 09:48 |
Jean-Marc Vanel Messages: 23 Registered: July 2009 |
Junior Member |
|
|
Thanks a lot!
Under the console, "diag" didn't show the problem, but "start" did:
Missing Constraint: Bundle-RequiredExecutionEnvironment: JavaSE-1.6
The problem was that I compiled in a Java 6 environment, but deployed on
Debian with only Java 5, and I didn't pay attention to this in the
"Overview" tag of my plug-in in PDE:
"specifiy the minimum execution environments required to run this plug-in"
I changed this from J2SE-1.5 to JavaSE-1.6, which entailed this change
in MANIFEST.MF: from
Bundle-RequiredExecutionEnvironment: J2SE-1.5
to:
Bundle-RequiredExecutionEnvironment: JavaSE-1.6
I redeployed, and IT WORKED !!!!!
Note that the message :
Missing Constraint: Bundle-RequiredExecutionEnvironment: JavaSE-1.6
was hard to obtain, and even then, it is not very explicit.
A message like this would be better:
Violated Constraint: bundle XXX declares:
Bundle-RequiredExecutionEnvironment: JavaSE-1.6
but Execution Environment is: J2SE-1.5 (incompatible with JavaSE-1.6)
Todd Williams wrote:
> Jean-Marc,
>
> I haven't tried this in the 3.4 milestones but in 3.3 you could do the
> following:
>
> 1) Start Eclipse like the following: eclipse.exe -console
> 2) Type "ss" in the console to get the 'short status' of all the bundles
> starting up
> 3) Find your plugin in the list and note its bundle number
> 4) Type "diag <bundle-number>" in the console to see what prerequisites (if
> any) are preventing your plugin from starting up.
> 5) If any plugins are listed that are already in the install, use "diag" to
> find out what's preventing them from starting up.
>
> HTH,
> Todd
>
>
> "Jean-Marc Vanel" <jeanmarc.vanel@gmail.com> wrote in message
> news:fu2j9g$l2$1@build.eclipse.org...
>
>>Hi
>>
>>I have a plugin that works from the PDE environment, but when I export it
>>and deploy it elsewhere, it doesn't work (it has an editor with a
>>configured extension; it also contributes to the preference page).
>>
>>I use eclipse 3.4M5 .
>>
>>Is there a systematic way of debugging this case ?
>>
>
>
>
|
|
|
|
|
Re: eclipse plugin deployment troubleshooting [message #565665 is a reply to message #1098] |
Wed, 16 April 2008 09:48 |
Jean-Marc Vanel Messages: 23 Registered: July 2009 |
Junior Member |
|
|
Thanks a lot!
Under the console, "diag" didn't show the problem, but "start" did:
Missing Constraint: Bundle-RequiredExecutionEnvironment: JavaSE-1.6
The problem was that I compiled in a Java 6 environment, but deployed on
Debian with only Java 5, and I didn't pay attention to this in the
"Overview" tag of my plug-in in PDE:
"specifiy the minimum execution environments required to run this plug-in"
I changed this from J2SE-1.5 to JavaSE-1.6, which entailed this change
in MANIFEST.MF: from
Bundle-RequiredExecutionEnvironment: J2SE-1.5
to:
Bundle-RequiredExecutionEnvironment: JavaSE-1.6
I redeployed, and IT WORKED !!!!!
Note that the message :
Missing Constraint: Bundle-RequiredExecutionEnvironment: JavaSE-1.6
was hard to obtain, and even then, it is not very explicit.
A message like this would be better:
Violated Constraint: bundle XXX declares:
Bundle-RequiredExecutionEnvironment: JavaSE-1.6
but Execution Environment is: J2SE-1.5 (incompatible with JavaSE-1.6)
Todd Williams wrote:
> Jean-Marc,
>
> I haven't tried this in the 3.4 milestones but in 3.3 you could do the
> following:
>
> 1) Start Eclipse like the following: eclipse.exe -console
> 2) Type "ss" in the console to get the 'short status' of all the bundles
> starting up
> 3) Find your plugin in the list and note its bundle number
> 4) Type "diag <bundle-number>" in the console to see what prerequisites (if
> any) are preventing your plugin from starting up.
> 5) If any plugins are listed that are already in the install, use "diag" to
> find out what's preventing them from starting up.
>
> HTH,
> Todd
>
>
> "Jean-Marc Vanel" <jeanmarc.vanel@gmail.com> wrote in message
> news:fu2j9g$l2$1@build.eclipse.org...
>
>>Hi
>>
>>I have a plugin that works from the PDE environment, but when I export it
>>and deploy it elsewhere, it doesn't work (it has an editor with a
>>configured extension; it also contributes to the preference page).
>>
>>I use eclipse 3.4M5 .
>>
>>Is there a systematic way of debugging this case ?
>>
>
>
>
|
|
|
|
Powered by
FUDForum. Page generated in 0.02881 seconds