[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
[epp-dev] Re: repository discussion - epp+galileo or galileo-only
|
Markus Knauer wrote:
Hi Thomas,
1. - Should be easy to solve.
Is it OK if I provide a patch?
2. - Yes, there was a reason to do it that way... it was the only
working configuration.
One problem was always that the application that we are running is
(always) the same (org.eclipse.ui.ide.workbench), provided by the
org.eclipse.platform feature. This is the reason why it is *included*
in the product defining feature. But the product extension point
definition lives in its own plug-in.
The normal approach would be - and here you are correct - to add the
package content as a list of *included* features to the top-level
feature (or to the .product file as a feature dependency). But in this
case you cannot export the "definition only" to a p2 repository, you
need to have the complete Galileo content somewhere in your target or
in your workspace. This is something that I am trying to avoid, since
it is IMHO easier to create metadata and as less as possible
additional artifacts because we need this repo as an augmenting repo
for the p2 director call only.
Does that help to clarify it a bit? If someone tells me a way to
circumvent this - and this way is really working I am happy to change it.
It helps. But at the same time, I think the issue goes away if we put
everything in Galileo. That way, there will be no need for any
additional repositories. All you need is the installer.
Regards,
Thomas Hallgren
