Re: [e4-dev] Eclipse org.eclipse.e4.rcp feature project question

[Lars Vogel <lars.vogel@xxxxxxxxx>]

Hi Paul, John,

thanks for the answer. If I get it correctly, the current setup is
based on the build setup. As platform does not build the EMF
components we don't want to include them into our feature but rather
express a dependencies.

Makes sense, thanks for answering.

Best regards, Lars

2013/2/11 John Arthorne <John_Arthorne@xxxxxxxxxx>:
> Here's the bug that talks about doing the inverse change...
>
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=356644
>
> John
>
>
>
> From:        Lars Vogel <lars.vogel@xxxxxxxxx>
> To:        E4 Project developer mailing list <e4-dev@xxxxxxxxxxx>,
> Date:        02/11/2013 01:18 PM
> Subject:        [e4-dev] Eclipse org.eclipse.e4.rcp feature project question
> Sent by:        e4-dev-bounces@xxxxxxxxxxx
> ________________________________
>
>
>
> Hi,
>
> I forgot why we decided that the org.eclipse.e4.rcp feature should not
> include the EMF plug-ins. Currently org.eclipse.e4.rcp adds
> org.eclipse.emf.ecore and org.eclipse.emf.common as dependencies.
>
> My personal preference would be to change the org.eclipse.e4.rcp
> feature and put org.eclipse.emf.ecore and org.eclipse.emf.common into
> the "Included features" part.
>
> This would make setting up Eclipse 4 application easier for new
> starters, they only have to add their features and one framework
> feature.
>
> Are there objections against this change? If not I will open a bug
> report with a patch.
>
> Best regards, Lars
> _______________________________________________
> e4-dev mailing list
> e4-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/e4-dev
>
>
>
> _______________________________________________
> e4-dev mailing list
> e4-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/e4-dev
>