[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [epp-dev] Simplifying the EPP packages
|
I will have a close look later today, but it looks promising.
The product definitions that we have today are only a 'workaround' and this proposal seems to solve many problems caused by this approach. One of the reasons for having a 'product' of its own is to specify parameters, such as JVM parameters, initial perspective, eclipse.ini
Thanks,
Markus
2009/5/15 Thomas Hallgren
<thomas@xxxxxxx>
Hi,
I was chatting with Pascal and Andrew N. yesterday. They suggested a simplified approach for creating the packages. Instead of as today, base each package on a product of its own, we could extend the already existing org.eclipse.platform.ide product:
http://wiki.eclipse.org/Equinox/p2/Reusing_Platform_Metadata
Essentially, this means that we would no longer need any product definitions. Only one single feature per package. That feature extends the already existing org.eclipse.platform.ide product. The only thing needed to make it work is that we add a p2.inf file in the root of the feature where we express the dependency to the platform.ide product. The dependency must be defined that way since a feature cannot be dependent on a product.
It would be easy for me to change the automated build to accommodate this.
What do you think?
Regards,
Thomas Hallgren
_______________________________________________
epp-dev mailing list
epp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/epp-dev
--
Markus Knauer
EclipseSource
### phone: +49 721 664 733 0 (GMT +2)
### fax: +49 721 664 733 29
### web:
www.eclipsesource.com
Innoopract Informationssysteme GmbH
Stephanienstrasse 20, 76133 Karlsruhe Germany
General Manager: Jochen Krause
Registered Office: Karlsruhe, Commercial Register Mannheim HRB 107883
