Hi Mickael,

I begin to think I understood you incorrectly.

you said:

so I'm thinking about contributing the EGit integration into
> org.eclipse.e4.ui, so that org.eclipse.e4.ui would now have a dependency on
> EGit (to be reversed when the import framework can be considered as mature).
>

>From this I figured that you wanted to add this dependency to a bundle
called "org.eclipse.e4.ui". This name looks very "core" to e4 so that is
why I suggested to not add a direct dependency. (Apparently there is no
bundle with this name. I looked for it but could not find it.)

I have no authority to say something about adding the EGit dependency to
org.eclipse.e4.ui.import. AFAICT it is perfectly fine to do so.

Cheers,

Wim

On Mon, Feb 23, 2015 at 6:09 PM, Mickael Istria <[email protected]> wrote:

>  On 02/23/2015 04:44 PM, Wim Jongman wrote:
>
>  Yes. I think the main question is: Can e4.ui be used in pure e4
> applications without dragging in e3. You have to look at the pulled in
> dependencies and make a educated decision.
>
> To be honest, this work is in e4.ui more like a platform.ui incubator.
> Whether it drags e3 or not is totally out my scope, and is not relevant for
> this change.
>
>    Funny, I don;t see org.eclipse.e4.ui in this
>
>    Not sure what you're looking for, but the import framework in in that
> repository, under bundles/org.eclipse.e4.ui.impor
> --
> 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>
>
> _______________________________________________
> e4-dev mailing list
> [email protected]
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit
> https://dev.eclipse.org/mailman/listinfo/e4-dev
>
_______________________________________________
e4-dev mailing list
[email protected]
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/e4-dev

Reply via email to