| Re: [p2-dev] EclipseInstallAction and ProductAction |
|
This is one of the goal for 3.5 to prove that the publisher story is working.
Thanks Ian. This was very helpful. Would it be correct to assume that you aim to publish the IDE itself as a product some time going forward? Regards, Thomas Hallgren Ian Bull wrote:
The EclipseInstallAction, as the name implies, publishes an Eclipse Install. It grovels around on disk, looking in known places for known things and tries to publish them. This is extremely brittle and not really useful in a build process. So in summary, the EclipseInstallAction was created because we had to start from somewhere, but going forward, the publisher action is what you should likely be using. cheers, ian On Fri, Mar 6, 2009 at 5:36 AM, Thomas Hallgren <thomas@xxxxxxx> wrote:
I'm trying to understand the difference between the EclipseInstallAction and the ProductAction. From where I stand, the Eclipse IDE is a product and to have two actions should be redundant. Can someone please shed some light on the current design? I'm trying to learn how to leverage the publisher the best way possible. Regards, Thomas Hallgren _______________________________________________ p2-dev mailing list p2-dev@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/p2-dev -- R. Ian Bull | EclipseSource Victoria | +1 250 477 7484 http://eclipsesource.com | http://twitter.com/eclipsesource _______________________________________________ p2-dev mailing list p2-dev@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/p2-dev p2-dev mailing list p2-dev@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/p2-dev |
