p2-dev

Re: [p2-dev] Build from the branch available

aniefer@xxxxxxx (Andrew Niefer) — Fri, 27 Nov 2009 13:30:31 GMT

A new build from the api branch is available here:
https://build.eclipse.org/hudson/job/equinox_R3_6_api_cleanup/18/artifact/builds/transfer/files/testUpdates-I/I20091126-1807

-Andrew

From:	Pascal Rapicault/Ottawa/IBM@IBMCA
To:	p2-dev@xxxxxxxxxxx
Date:	11/23/2009 01:05 PM
Subject:	[p2-dev] Build from the branch available
Sent by:	p2-dev-bounces@xxxxxxxxxxx

We now have our first build from the R3_6_api_cleanup branch!
It is made of last week I build plus our p2 work (and dependee) from the branch.

You can update from last week build using the following repo:
https://build.eclipse.org/hudson/job/equinox_R3_6_api_cleanup/15/artifact/builds/transfer/files/testUpdates-I/I20091121-1523/

To run builds: https://build.eclipse.org/hudson/job/equinox_R3_6_api_cleanup/

PaScaL_______________________________________________ p2-dev mailing list p2-dev@xxxxxxxxxxxhttps://dev.eclipse.org/mailman/listinfo/p2-dev

Re: [p2-dev] ui changes in the branch - repo management and error reporting

Pascal_Rapicault@xxxxxxx (Pascal Rapicault) — Thu, 26 Nov 2009 18:31:29 GMT

I'm running a build today with all these changes. Given that the CVS checkout is very slow the build should be available tomorrow (CVS slowness has been reported to the webmaster).

PaScaL

[p2-dev] ui changes in the branch - repo management and error reporting

[p2-dev] ui changes in the branch - repo management and error reporting

Susan Franklin McCourt

to:

P2 developer discussions

11/25/2009 07:57 PM

Sent by:

p2-dev-bounces@xxxxxxxxxxx

Please respond to P2 developer discussions

I just released some code to the api branch to finalize a batching strategy during repo loads.
AFAIK, I think I've finally beat down the "combo keeps resetting," "combo keeps flashing," "composite child repos are showing up," etc. kinds of problems. [1]

I know that Pascal was kicking off a build earlier today (before these changes were released).

So...if you are seeing these flashes and oddities in the build, don't panic. Try a self-hosted workbench based on the branch (or spin another build?)
I only mention this because I'll be offline for the next day or two on Thanksgiving holiday, and didn't want anyone to panic if the build didn't seem to match what I'm saying in bug reports about things that should be working....

susan

[1]
https://bugs.eclipse.org/bugs/show_bug.cgi?id=234489
https://bugs.eclipse.org/bugs/show_bug.cgi?id=282176
https://bugs.eclipse.org/bugs/show_bug.cgi?id=276884_______________________________________________ p2-dev mailing list p2-dev@xxxxxxxxxxxhttps://dev.eclipse.org/mailman/listinfo/p2-dev

Re: [p2-dev] Export feature, p2 metadata and drop ins.

Pascal_Rapicault@xxxxxxx (Pascal Rapicault) — Thu, 26 Nov 2009 15:05:00 GMT

> http://help.eclipse.org/galileo/index.jsp?topic=/org.eclipse.pde. > doc.user/guide/tools/export_wizards/export_features.htm > motivates how p2 metadata is needed for the 'install into your > running host' option.
The metadata generated is needed in order to fix the feature dependencies on the plug-in being replaced. This also allows to easily get back to the previous state if you newly installed plug-in is not good. Behind the scene pde has logic to generate a feature patch.

> It appears to me that the advanced options (categorize, package as > individual JAR archives) can be used to create a p2 equivalent of an > old style update site, or not?
Correct.
> When using the output for a drop in install, it is not clear how the > p2 metadata is used. > I would assume that the reconciler would generate p2 metadata for > the affected profile for features and plugins found in the dropin folder. > > Does the reconciler use the p2 metadata in drop-in folder? If so in which way?
Yes it uses the metadata (as well as the artifacts.xml). When metadata is found no on-the-fly metadata generation is being done.

[p2-dev] ui changes in the branch - repo management and error reporting

susan_franklin@xxxxxxx (Susan Franklin McCourt) — Thu, 26 Nov 2009 00:56:47 GMT

[p2-dev] Export feature, p2 metadata and drop ins.

henrich.kraemer@xxxxxxx (Henrich Kraemer) — Wed, 25 Nov 2009 23:44:39 GMT

http://help.eclipse.org/galileo/index.jsp?topic=/org.eclipse.pde.doc.user/guide/tools/export_wizards/export_features.htm
motivates how p2 metadata is needed for the 'install into your running host' option.

It appears to me that the advanced options (categorize, package as individual JAR archives) can be used to create a p2 equivalent of an old style update site, or not?

When using the output for a drop in install, it is not clear how the p2 metadata is used.
I would assume that the reconciler would generate p2 metadata for the affected profile for features and plugins found in the dropin folder.

Does the reconciler use the p2 metadata in drop-in folder? If so in which way?

Thanks,

Henrich

Re: [p2-dev] Build from the branch available

susan_franklin@xxxxxxx (Susan Franklin McCourt) — Tue, 24 Nov 2009 00:53:37 GMT

It is very cool to have this build!

When I went to run the p2 UI tests in this build, I had some odd failures regarding my launch config. That happens to me quite frequently, but in trying to track it down, I noticed that there is no longer the checkbox for supporting install (pde target p2 provisioning) in the launch config page.

Is that checkbox gone because we've broken pde/p2 self hosting in our branch build?

susan

Pascal Rapicault ---11/23/2009 10:05:43 AM---We now have our first build from the R3_6_api_cleanup branch!

Pascal Rapicault

Sent by: p2-dev-bounces@xxxxxxxxxxx

11/23/2009 10:04 AM
Please respond to P2 developer discussions

To: p2-dev@xxxxxxxxxxx
cc:
Subject: [p2-dev] Build from the branch available

[p2-dev] Build from the branch available

Pascal_Rapicault@xxxxxxx (Pascal Rapicault) — Mon, 23 Nov 2009 18:04:37 GMT

Re: [p2-dev] p2 UI API

susan_franklin@xxxxxxx (Susan Franklin McCourt) — Mon, 23 Nov 2009 17:34:30 GMT

Thanks, John.
Yes, I had this same heretical thought a couple weeks ago on a p2 call. But I agree completely that we should not expand the operations API to cover harder cases. I've really adopted "keep the simple things simple" as the mantra for this API, and the challenge is drawing the line. If operations become too complex, then we haven't really won anything.

At what point does a client enter the den of the lower level API? I think that as we release the p2 API, we should really encourage folks doing simple things to move to operations and see if we can find that line (ie, are there simple changes that would let more folks use operations?).

I'll use the bugs to respond to the other issues, thanks for the thorough review...

susan

John Arthorne ---11/23/2009 08:17:08 AM---Hi Susan,

John Arthorne

Sent by: p2-dev-bounces@xxxxxxxxxxx

11/23/2009 08:16 AM
Please respond to P2 developer discussions

To: P2 developer discussions
cc:
Subject: Re: [p2-dev] p2 UI API

Hi Susan,

I reviewed the operation API this morning and it looks great! In particular I really like the install/uninstall/update operations, since as you noted this vastly simplifies client code for these simple use cases. It even gave me the heretical thought that we could defer turning the complicated IPlanner/IEngine stuff into real API in this release, but I'm not sure this is possible because there are several clients doing some more complicated things. Rather than expanding the operation API to cover all these fringe cases, it's probably best to keep this operation API simple and leave the complex stuff to the lower level API.

I have released some minor fixes directly in the branch, and opened bugs for a couple of other issues, but overall I really like it. I just wanted to send some positive feedback here because if you see the bug reports you only get the negative feedback...

John

Susan Franklin McCourt
Sent by: p2-dev-bounces@xxxxxxxxxxx

11/19/2009 06:46 PM

Please respond to
P2 developer discussions

To	P2 developer discussions
cc
Subject	[p2-dev] p2 UI API

I've finished the javadoc for the API coming out of the p2 UI.
It is released to the R3_6_api_cleanup branch.

The relevant bundles are

org.eclipse.equinox.p2.common (which may or may not continue to live as a separate bundle)
org.eclipse.equinox.p2.operations
org.eclipse.equinox.p2.ui

I'm reasonably happy with the shape of the API, but I've been working with it for a few weeks straight so I've lost all objectivity.
What's interesting to me about the shape is:

- the SDK UI is now a "good citizen" as far as using only API. I wasn't sure we could get there.
- it is still expected that clients will have to use internals if they want to reuse more fine-grained pieces of the UI (ie, the admin UI, PDE reusing some composites, etc.)
- the examples have been able to survive some significant class movement in core. For the most part, examples only need to know now about metadata and core. This is really good news.
- simple stuff is now simple. For example, checking for updates to the currently running profile is done like this:

UpdateOperation op = new UpdateOperation(provisioningSession);
IStatus result = op.resolveModal(monitor);
if (result.isOK()) {
op.getProvisioningJob(monitor).schedule;
}

Contrast that to the code here [1].

I invite anyone interested to review the code in the branch and open a bug with comments (or correct any errors you see...thanks John for spotting some already).

susan

[1] http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.equinox/p2/examples/org.eclipse.equinox.p2.examples.rcp.prestartupdate/src/org/eclipse/equinox/p2/examples/rcp/prestartupdate/P2Util.java?root=RT_Project&view=markup_______________________________________________ p2-dev mailing list p2-dev@xxxxxxxxxxxhttps://dev.eclipse.org/mailman/listinfo/p2-dev
_______________________________________________ p2-dev mailing list p2-dev@xxxxxxxxxxxhttps://dev.eclipse.org/mailman/listinfo/p2-dev

[p2-dev] AUTO: David Klein/Austin/IBM is out of the office. (returning 11/30/2009)

kleind@xxxxxxx (David Klein) — Mon, 23 Nov 2009 17:03:27 GMT

I am out of the office until 11/30/2009.

I will respond to your message when I return.

Note: This is an automated response to your message Re: [p2-dev] p2 UI API sent on 11/23/09 9:16:22.
This is the only notification you will receive while this person is away.

Re: [p2-dev] p2 UI API

John_Arthorne@xxxxxxx (John Arthorne) — Mon, 23 Nov 2009 16:16:40 GMT

Susan Franklin McCourt
Sent by: p2-dev-bounces@xxxxxxxxxxx

11/19/2009 06:46 PM

Please respond to
P2 developer discussions

To	P2 developer discussions
cc
Subject	[p2-dev] p2 UI API