On Sat, Jul 7, 2012 at 12:24 PM, Sebastian Bauer
<mail_at_sebastianbauer.info>wrote:
> Hi!
>
> On Sat, 07 Jul 2012 20:10:41 +0200, Sebastian Bauer wrote:
> > if I install Subclipse on a plain Eclipse platform installation
> > (Platform Runtime Binary), which previously didn't offer the Java
> > perspective, then, after installing the main Subclipse plugin, the
> > Java
> > perspective is offered. I would not have expected that. Is this a
> > known
> > issue of Subclipse or may another component be the reason? In one of
> > my
> > installations, I like to use Subclipse, but I don't need JDT.
>
> I dug in the source. The Subclipse UI module optionally depends on
> org.eclipse.jdt.ui and org.eclipse.jdt.core, but as there is no control
> whether optional components are used nor not, it is installed. See
> http://wiki.eclipse.org/Equinox/p2/Publisher about this. Especially the
> Note section. Basically, it is recommended to move the features that
> optionally depend on something into an own feature. This makes sense to
> me.
>
>
I wonder if it would make a difference if we removed the dependencies and
instead used "Import-Package" in our manifest? Does anyone know how that
will change the P2 metadata that is generated?
--
Thanks
Mark Phippard
http://markphip.blogspot.com/
------------------------------------------------------
http://subclipse.tigris.org/ds/viewMessage.do?dsForumId=1047&dsMessageId=2984820
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subclipse.tigris.org].
Received on 2012-07-12 16:18:47 CEST