Re: [equinox-dev] List of installable units or log - using p2 director t

[misha680 <misha680@xxxxxxxxx>]

Ah, I see, thank you very much.

I did not find a good reference for the provisional API - perhaps you could
suggest one?

I could probably work backwards from 
http://wiki.eclipse.org/Equinox/p2/Helios_Migration_Guide

but if you have any other hints/references much appreciated.

Thank you
Misha

p.s. This is quite minor but I noticed that in:
http://dev.eclipse.org/viewsvn/index.cgi/org.eclipse.platform.doc.isv/guide/p2_api_overview.htm?view=co

I believe there should be a semicolon after agent.close() in this line:
        public void done(IJobChangeEvent event) {agent.close()}});
so that it reads:
        public void done(IJobChangeEvent event) {agent.close();}});

Another great reference I did _not_ previously mention where you do _not_
have this typo is:
http://www.slideshare.net/PascalRapicault/discovering-the-p2-api

Thank you
Misha


Pascal Rapicault-3 wrote:
> 
> 	p2 has been around since 3.4 and it had a provisional API in 3.4 and 3.5.
> It is only since 3.6 that p2 has an official API.  I definitely recommend
> staying out of update manager API and use the p2 provisional API instead.
> Though in different packages, the final APIs are really close to the
> provisional one and once you will have figured out how to make your
> installer work on 3.6, making it work in only a few package and method
> renames away.
> 	The other important point is that the metadata is compatible so you would
> not have to generate two sets of information.
> _______________________________________________
> equinox-dev mailing list
> equinox-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/equinox-dev
> 
> 

-- 
View this message in context: http://old.nabble.com/List-of-installable-units-or-log---using-p2-director-to-automate-Subclipse%2C-M2eclipse%2C-and-M2eclipse-Extra-for-OpenMRS-developers-tp29693317p29749801.html
Sent from the Equinox - Dev mailing list archive at Nabble.com.