Re: [eclipse-dev] Making platform bundles more reuseable - A Mars target

[Tom Schindl <tom.schindl@xxxxxxxxxxxxxxx>]

Hi,

I'm not a fan of split-packages myself BUT this would mean we'd have to
create parallel API and maintain 2 forks which is a no go with the given
resources we all have.

I know that import-package is much better than require-bundle but as
long as the packages are not versioned I don't see a point in using
import-package over require-bundle.

Tom

On 19.05.14 07:15, Mickael Istria wrote:
> On 05/17/2014 02:21 PM, Tom Schindl wrote:
>> Are we fine with split-packages?
> Split package can cause troubles to p2 or even OSGi (when using
> Import-Package instead of Require-Bundle). On one side, there are people
> wanting better OSGi practices in Eclipse such as using Require-Bundle,
> and one the other side, you now want split-packages. Both are not
> compatible.
> As an "integrator" of Eclipse, I would definitely like to avoid
> split-packages which make things more complex to assemble things.
> 
> Cheers
> -- 
> Mickael Istria
> Eclipse developer at JBoss, by Red Hat <http://www.jboss.org/tools>
> My blog <http://mickaelistria.wordpress.com> - My Tweets
> <http://twitter.com/mickaelistria>
> 
> 
> _______________________________________________
> eclipse-dev mailing list
> eclipse-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe from this list, visit
> https://dev.eclipse.org/mailman/listinfo/eclipse-dev
>