[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
RE: [p2-dev] Backporting p2 to Eclipse 3.4

> I managed to successfully backport the Galileo p2 functionality to
> Ganymede. I tried a simple update example and it works; I also tried
> an example using

> a Policy defined by myself and it works. But of course that I ran
> into some problems:

>  
> 1) - the update site generated with Eclipse 3.4 is not compatible
> with the Galileo p2 provisioning (the one generated with Eclipse 3.5
> works fine); I guess I kind of saw that coming and that it has
> something to do with the org.eclipse.pde.p2.ui you mentioned. Is it
> there where the update site project functionality is implemented?

I'm rather surprised as the metadata format has not changed between 3.4 and 3.5. I think you are probably better using 3.5 generation anyway, but if you wanted to open a bug about the specific problems you are encountering that could be useful for further migration.

>  
> 2) - the About dialog functionality you mentioned. I found some
> classes in the org.eclipse.ui.workbench that implement the
> functionality (InstallationPage, InstalledSoftwarePage,
> ProductInfoPage, AboutPluginsPage, aboutSystemPage). Are these the
> only ones or are there any other related to p2?

See Susan's answer in a previous email.

> 3) - I cannot find a consistent example on how to properly generate
> and configure an update site that would update my specific features/
> plugins, my Eclipse

> platform plugins and also some other stuff I have in my product
> (like folders with executables, libraries and configuration files).
> Dou you know of any such examples?

The only publicly available example that I know of is the eclipse SDK. We basically build it like an RCP product and each new build produces a new version of the IU that represents the porduct. Having one such root allows for easy addition and removal of functionality as new versions of your product become available.
However this example does not deliver a file outside of the eclipse/ directory. That said if you search through the history of this forum you may find a few good data point, and with detailed questions you may get a quick answer here as well.

Also you may want to look at http://www.slideshare.net/PascalRapicault/understanding-and-extending-p2-for-fun-and-profit or take a look at Ian's recent webcast http://live.eclipse.org/node/789


>  
> Thanks
> Marius Cetateanu
> DevTech  - Software Engineer
> Freescale Semiconductor Romania SRL
> 45, Tudor Vladimirescu Street
> Tati Business Center
> Bucharest 050881, Romania
> www.freescale.com
> Phone:    +040 213052078
> Mobile:    +040 742191809
> Fax:        +040 213052000
> email:  Marius.Cetateanu@xxxxxxxxxxxxx

>  
>
> From: p2-dev-bounces@xxxxxxxxxxx [mailto:p2-dev-bounces@xxxxxxxxxxx]
> On Behalf Of Pascal Rapicault
> Sent: Thursday, October 01, 2009 4:46 PM
> To: P2 developer discussions
> Cc: p2-dev@xxxxxxxxxxx; p2-dev-bounces@xxxxxxxxxxx
> Subject: Re: [p2-dev] Backporting p2 to Eclipse 3.4

> Hi Marius,
>
> This is not something that we actively support nor that we have tried.
> However I think it should be doable given that in 3.4 the
> dependencies on p2 from the other plug-ins was rather minimal. In
> fact, running the API usage tool [1], the only reference I got back
> was org.eclipse.pde.p2.ui, which I believe you could simply punt if
> it turned out to be incompatible.
>
> However this will not get you the new about dialog behavior which
> provides a way for users to uninstall or revert since this relies on
> new functionality being introduced in UI plug-in in 3.5. That said
> this could probably easily be backported to 3.4 as well as this is
> rather self contained.
>
> HTH
>
> PaScaL
>
> [1] http://download.eclipse.org/eclipse/downloads/drops/S-3.
> 6M2-200909170100/eclipse-news-M2.html#PDE
>
> [image removed] "Cetateanu Marius-B01107" ---10/01/2009 02:51:35 AM---Hi,

>
> [image removed]
> From:

>
> [image removed]
> "Cetateanu Marius-B01107" <Marius.Cetateanu@xxxxxxxxxxxxx>

>
> [image removed]
> To:

>
> [image removed]
> <p2-dev@xxxxxxxxxxx>

>
> [image removed]
> Date:

>
> [image removed]
> 10/01/2009 02:51 AM

>
> [image removed]
> Subject:

>
> [image removed]
> [p2-dev] Backporting p2 to Eclipse 3.4

>
>
>
>
>
> Hi,
>
> I would like to know if it's possible and feasible to backport the whole
> p2 updater feature
> to Eclipse 3.4. We're working on an Eclipse based IDE and we cannot
> update for the time being
> to Eclipse 3.5 but we would benefit from having the p2 updater feature
> from 3.5 in our product.
> If it's possible (we have about 3 weeks to do the backporting) could
> anyone point me to
> the documentation I should read to start the process?
>
> Thanks  
>
> Marius Cetateanu  
> DevTech  - Software Engineer
> Freescale Semiconductor Romania SRL
> 45, Tudor Vladimirescu Street
> Tati Business Center
> Bucharest 050881, Romania
> www.freescale.com
> Phone:    +040 213052078
> Mobile:    +040 742191809
> Fax:        +040 213052000
> email:  Marius.Cetateanu@xxxxxxxxxxxxx
>
> _______________________________________________
> 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