Hi Mikael, The way UI dependencies are resolved in tooling is to build one bundle that depends on PDE/WB/UI which exposes services to be used in core and ui bundles.
Maybe this approach is preferred over adding a dependency to EGit? Where is org.eclipse.e4.ui ATM? I could not find a git repo for it. Cheers, Wim On Mon, Feb 23, 2015 at 7:36 AM, Mickael Istria <[email protected]> wrote: > On 02/23/2015 07:32 AM, Mickael Istria wrote: > > Hi all, > > The new import framework contributed to org.eclipse.e4.ui repository is > making good progress. I encourage the most curious of you to give it a try > (at http://download.eclipse.org/e4/snapshots/org.eclipse.e4.ui/ ). > > ... (continuing my mail) ... > A next step for this framework would be to link it more closely with team > providers, such as EGit. As the framework is still incubating, I don't > think it would be good to have EGit depending on it already, 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). > Is it acceptable to add such a dependency? > -- > 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
