Home » Eclipse Projects » Plugin Development Environment (PDE) » Unwanted plugin/bundle getting deployed (jetty 1.1.0 ticked, jetty 2.0.0 NOT, both deployed)
| Unwanted plugin/bundle getting deployed (jetty 1.1.0 ticked, jetty 2.0.0 NOT, both deployed) [message #18723] |
Sat, 30 August 2008 16:45  |
 Neale Upstone
Messages: 50
Registered: July 2009 |
Member |
|
|
Hi,
Has anyone else come across this situation.
My Prefs->PDE->Target Platform specifically has one version of a plugin
specified, but it seems that both are getting deployed when I run an
OSGi launch.
The relevant settings are:
[ ] Build based on targets installed plugins (i.e. unticked)
[ticked] org.eclipse.equinox.http.jetty (1.1.0 v20080425)
[ ] org.eclipse.equinox.http.jetty (2.0.0 v20080425)
My launch config naturally just specifies
org.eclipse.equinox.http.jetty@default:default
And within my bundles, I don't refer to any jetty packages, as I'm using
the OSGi HttpService.
In my view, when I launch my configuration, I should only get the
[ticked] bundle. Instead, what happens is:
- I get a dialog box warning that the jetty package has unresolved
dependencies (due to the fact that the required bundles for 2.0.0 are
not included).
- When launched, all runs okay, as only the 1.1.0 bundle succeeds in
launching. A 'diag' on the 2.0.0 bundle shows that it didn't start.
The question is: why is eclipse deploying it at all.
Seems to me that PDE is failing to honour what's specified in the target
platform.
Any clues?
|
|
|
| Re: Unwanted plugin/bundle getting deployed (jetty 1.1.0 ticked, jetty 2.0.0 NOT, both deployed) [message #18746 is a reply to message #18723] |
Sun, 31 August 2008 01:02  |
Eclipse User |
|
|
|
Originally posted by: zx.code9.com
Neale wrote:
> Hi,
>
> Has anyone else come across this situation.
>
> My Prefs->PDE->Target Platform specifically has one version of a plugin
> specified, but it seems that both are getting deployed when I run an
> OSGi launch.
>
> The relevant settings are:
> [ ] Build based on targets installed plugins (i.e. unticked)
> [ticked] org.eclipse.equinox.http.jetty (1.1.0 v20080425)
> [ ] org.eclipse.equinox.http.jetty (2.0.0 v20080425)
>
> My launch config naturally just specifies
> org.eclipse.equinox.http.jetty@default:default
>
> And within my bundles, I don't refer to any jetty packages, as I'm using
> the OSGi HttpService.
>
> In my view, when I launch my configuration, I should only get the
> [ticked] bundle. Instead, what happens is:
> - I get a dialog box warning that the jetty package has unresolved
> dependencies (due to the fact that the required bundles for 2.0.0 are
> not included).
> - When launched, all runs okay, as only the 1.1.0 bundle succeeds in
> launching. A 'diag' on the 2.0.0 bundle shows that it didn't start.
>
> The question is: why is eclipse deploying it at all.
>
> Seems to me that PDE is failing to honour what's specified in the target
> platform.
>
> Any clues?
It sounds like a possible bug, can you file a bug with a small
reproducible test case?
Sorry for the trouble!
Cheers,
~ Chris
|
|
|
| Re: Unwanted plugin/bundle getting deployed (jetty 1.1.0 ticked, jetty 2.0.0 NOT, both deployed) [message #577946 is a reply to message #18723] |
Sun, 31 August 2008 01:02 |
Chris Aniszczyk
Messages: 674
Registered: July 2009 |
Senior Member |
|
|
Neale wrote:
> Hi,
>
> Has anyone else come across this situation.
>
> My Prefs->PDE->Target Platform specifically has one version of a plugin
> specified, but it seems that both are getting deployed when I run an
> OSGi launch.
>
> The relevant settings are:
> [ ] Build based on targets installed plugins (i.e. unticked)
> [ticked] org.eclipse.equinox.http.jetty (1.1.0 v20080425)
> [ ] org.eclipse.equinox.http.jetty (2.0.0 v20080425)
>
> My launch config naturally just specifies
> org.eclipse.equinox.http.jetty@default:default
>
> And within my bundles, I don't refer to any jetty packages, as I'm using
> the OSGi HttpService.
>
> In my view, when I launch my configuration, I should only get the
> [ticked] bundle. Instead, what happens is:
> - I get a dialog box warning that the jetty package has unresolved
> dependencies (due to the fact that the required bundles for 2.0.0 are
> not included).
> - When launched, all runs okay, as only the 1.1.0 bundle succeeds in
> launching. A 'diag' on the 2.0.0 bundle shows that it didn't start.
>
> The question is: why is eclipse deploying it at all.
>
> Seems to me that PDE is failing to honour what's specified in the target
> platform.
>
> Any clues?
It sounds like a possible bug, can you file a bug with a small
reproducible test case?
Sorry for the trouble!
Cheers,
~ Chris
|
|
|
Goto Forum:
Current Time: Thu Dec 26 17:11:26 GMT 2024
Powered by FUDForum. Page generated in 0.03406 seconds |
] 
Search
Help
Register
Login
Home
