The product action simply publishes a .product file (and I
think it does the executables). Nothing More! If you want to publish a
product you will likely publish your plugins, features, (categories
maybe) and the .product file. This will likely be part of your build
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.
On Fri, Mar 6, 2009 at 5:36 AM, Thomas
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.
p2-dev mailing list
R. Ian Bull | EclipseSource Victoria | +1 250 477 7484