Re: [p2-dev] EclipseInstallAction and ProductAction

[Pascal Rapicault <Pascal_Rapicault@xxxxxxxxxx>]

Note that we are doing a product file based build for the SDK and the Platform since 3.4, however it was using some ad-hoc ways.
The product files are stored in the org.eclipse.releng.eclipsebuilder and we are in the process of changing them to have leverage this new product build.

Ian Bull ---03/07/2009 10:57:54 AM---Yep, I would love to have a proper product file and use it for actual eclipse builds. There are a l

From:	Ian Bull <irbull@xxxxxxxxxxxxxxxxx>
To:	P2 developer discussions <p2-dev@xxxxxxxxxxx>
Date:	03/07/2009 10:57 AM
Subject:	Re: [p2-dev] EclipseInstallAction and ProductAction

---

Yep, I would love to have a proper product file and use it for actual eclipse builds.  There are a lot of complexities in this, especially since we build all sorts of different products, but I have managed to get it working in some simple test cases.

cheers,
Ian

On Fri, Mar 6, 2009 at 11:41 PM, Thomas Hallgren <thomas@xxxxxxx> wrote:

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 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 process.

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:
Hi,
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

-- 
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