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

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.


Inactive hide details for Ian Bull ---03/31/2009 01:31:15 PM---You should transition to the publisher (it will be the tool moviIan 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:


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