[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
RE: [p2-dev] Publisher vs. generator/director

Surfacing the publisher through the generator has been discussed for things like features and update site builds and should be fairly straightforward.
However when it comes to product, I don't think this will be possible because the publisher takes a really different approach to create metadata and now promotes a product file based approach that we are still polishing up but that was demonstrated by Andrew during the tutorial (see the org.eclipse.equinox.p2.examples.rcp.cloud.releng project).
HTH
PaScaL

Inactive hide details for "Haigermoser, Helmut" ---04/01/2009 04:00:27 AM---P2 could help and make the generator/director a sim"Haigermoser, Helmut" ---04/01/2009 04:00:27 AM---P2 could help and make the generator/director a simple bridge calling the publisher behind the scene


From:

"Haigermoser, Helmut" <Helmut.Haigermoser@xxxxxxxxxxxxx>

To:

"P2 developer discussions" <p2-dev@xxxxxxxxxxx>

Date:

04/01/2009 04:00 AM

Subject:

RE: [p2-dev] Publisher vs. generator/director




P2 could help and make the generator/director a simple bridge calling
the publisher behind the scenes,
that way everybody, willingly or not, would call the director ;) If this
bridge were verbose enough we could then see the right director calls
and replace our calls to avoid the (useless) bridging...

For RCPs I'm hoping we get a single IU that references all other IUs  so
that we can continue to install as easily as before... (re Ians
statement regarding this..)
HTH,
Ciao, hh

-----Original Message-----
From: p2-dev-bounces@xxxxxxxxxxx [
mailto:p2-dev-bounces@xxxxxxxxxxx] On
Behalf Of Ian Bull
Sent: Tuesday, March 31, 2009 8:31 PM
To: P2 developer discussions
Subject: Re: [p2-dev] Publisher vs. generator/director

You should transition to the publisher (it will be the tool moving
forward, and we could use the help with bug reports, etc...).  I like
the question "Are there docs I'm missing"?  I think the question should
be "Are the docs missing" and the answer is yes.  Docs are now on my
todo list. :)

You should be able to run the features and bundle publisher and point to
a director (-source) containing /features and /plugins. When you use the
director to install you use -installIU (not -root). I don't think we
create a single IU that holds all the IUs.

cheers,
ian


On Tue, Mar 31, 2009 at 10:30 AM, Andrew Overholt <overholt@xxxxxxxxxx>
wrote:


Hi,

In 3.4.x, we in Fedora used the EclipseGenerator app to generate
metadata and then used the director app to install it.

In 3.5, should we use FeaturesAndBundlesPublisher?

I tried using the publisher with the director it and although it
generates metadata seemingly fine, the director fails when given
the
same "-root".  What am I doing wrong?  Is there a publisher
equivalent
to the director app?  Are there docs I'm missing?

Thanks,

Andrew

_______________________________________________
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


GIF image

GIF image