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

[Pascal Rapicault <Pascal_Rapicault@xxxxxxxxxx>]

3.4 metadata will be readable by 3.5
Most of 3.5 metadata will be readable in 3.4.
That said we are currently not aiming at being able to update an SDK 3.4 to an SDK 3.5.

James D Miles ---03/31/2009 04:33:50 PM---It is also a question of if we are going to change anything in the metadata between now and the end

From:	James D Miles <jdmiles@xxxxxxxxxx>
To:	P2 developer discussions <p2-dev@xxxxxxxxxxx>
Date:	03/31/2009 04:33 PM
Subject:	Re: [p2-dev] Publisher vs. generator/director

---

It is also a question of if we are going to change anything in the metadata between now and the end of the 3.5 release cycle that would make old stuff not usable.

Ian Bull ---03/31/2009 02:52:58 PM---Ideally you would use the publisher ant tasks directly in your build. If you are building features and bundles then you should

From:	Ian Bull <irbull@xxxxxxxxxxxxxxxxx>
To:	P2 developer discussions <p2-dev@xxxxxxxxxxx>
Date:	03/31/2009 02:52 PM
Subject:	Re: [p2-dev] Publisher vs. generator/director

---

Ideally you would use the publisher ant tasks directly in your build.  If you are building features and bundles then you should use that particular ant task. In the end you will have the bits on disk + the repositories.

As for backwards compatible, this is not a publisher vs. generator question, this is a question of whether our metadata is compatible from 3.4 to 3.5.  Pascal, do you know?

cheers,
ian

2009/3/31 James D Miles <jdmiles@xxxxxxxxxx>

That is good news. I will use it as soon as it is documented. I am assuming that I can create a site to install from using this. Correct?
I guess that means I would do something like
- export feature and plugins to a directory
- run the publisher to create a site
- install into sdk using new site.

So the next question is if it is totally backward compatible with the metadata generator or do I have to regenerate all my test sites? The sites were all created using 3.5.


Ian Bull ---03/31/2009 01:31:15 PM---You should transition to the publisher (it will be the tool moving forward, and we could use the help with bug reports, etc...)

From:	Ian Bull <irbull@xxxxxxxxxxxxxxxxx>
To:	P2 developer discussions <p2-dev@xxxxxxxxxxx>
Date:	03/31/2009 01:31 PM
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



_______________________________________________
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