[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [cross-project-issues-dev] Migrating your automated tests to use p2's /dropins/ folder
|
John,
This is really helpful! The information about the dropins directory
structure has been well-fleshed out and it looks like such nice flexible
mechanism. The instructions don't say anything about needing to take
explicit action to actually install the plugins that you've dropped into
the dropins folder. Such an explicit step is required, right?
I've been trying to bootstrap EMF following the steps in
http://wiki.eclipse.org/EMF/Getting_Source but have so far been
unsuccessful (using the 0324 build). I get a lot of messages of the form
when I try to install the plugins that I've brought to the installer's
attention:
Unsatisfied dependency: [org.eclipse.emf.ecore.sdo.feature.group
2.4.0.qualifier] requiredCapability:
org.eclipse.equinox.p2.iu/org.eclipse.emf.commonj.sdo/[0.0.0,0.0.0]
Unsatisfied dependency: [org.eclipse.emf.ecore.sdo.sdk.feature.group
2.4.0.qualifier] requiredCapability:
org.eclipse.equinox.p2.iu/org.eclipse.emf.commonj.sdo/[0.0.0,0.0.0]
Unsatisfied dependency: [org.eclipse.emf.codegen.ecore.ui.feature.group
2.4.0.qualifier] requiredCapability:
org.eclipse.equinox.p2.iu/org.eclipse.emf.codegen.ecore.ui/[0.0.0,0.0.0]
But I don't know what these "*.group" things are? If I can't bootstrap a
development using M6, then I'm completely hosed from a development point of
view, even if Nick manages to pull off a build for it. I'm not sure how
best to pursue arriving at a workable solution. You should interpret this
as an desperate cry for help (and one that's likely to become shrill as
Friday's M6 deadline approaches without a solution)...
Ed Merks/Toronto/IBM@IBMCA
mailto: merks@xxxxxxxxxx
905-413-3265 (t/l 313)
John
Arthorne/Ottawa/I
BM@IBMCA To
Sent by: Cross project issues
cross-project-iss <cross-project-issues-dev@eclipse.o
ues-dev-bounces@e rg>
clipse.org cc
Subject
03/26/2008 01:05 Re: [cross-project-issues-dev]
PM Migrating your automated tests to
use p2's /dropins/ folder
Please respond to
Cross project
issues
<cross-project-is
sues-dev@eclipse.
org>
Hey Nick,
Sorry, as usual our documentation is continually lagging behind the
implementation (between code and doc, code usually wins). Based on some
questions that came up this week I have been updating the getting started
guide. This is really the main document of interest for most consumers:
http://wiki.eclipse.org/Equinox_p2_Getting_Started
For buildmeisters and release engineers, there are more migration details
that we are currently working out. We'll set up a separate getting started
wiki page for this audience as soon as possible. Mileage may vary, but for
more p2 documentation than you can shake a stick at, see:
http://wiki.eclipse.org/Category:Equinox_p2
Thanks for pestering about documentation - we rely on the community to let
us know where information is lacking so please speak up if more details are
needed on any particular topic. There's tons of p2 information out there,
but often it's buried in bugzilla reports, the wiki, meeting minutes, the
equinox mailing list, etc. It's sometimes hard to gauge the appropriate
amount of communication needed in the various channels.
Also of interest, we have an initial M6 candidate available this morning
(I20080325-2233). We have been kicking the tires on it, installing WTP,
TPTP, and various other wads into the dropins folder and it's looking good
so far. Everyone is encouraged to pick up the builds this week and report
problems as soon as possible.
John
Nick
Boldt/Toronto/IBM@IBMCA
Sent by: To
cross-project-issues-dev-bo "Cross project issues"
unces@xxxxxxxxxxx <cross-project-issues-dev@xxxxxxxxxx
g>
cc
03/26/2008 09:42 AM
Subject
Re: [cross-project-issues-dev]
Please respond to Migrating your automated tests to
Cross project issues use p2's /dropins/ folder
<cross-project-issues-dev@
eclipse.org>
Everyone:
Apologies, the link should have been:
http://www.eclipse.org/modeling/emf/searchcvs.php?q=223977&fullpath=Y
Phillipe:
When exactly is soon? I've been asking for better p2 adopter/developer
docs since December [1], and very little has improved (or at least
very little has been advertised on this list).
[1]
http://dev.eclipse.org/blogs/releng/2007/12/01/equinox-p2-first-impressions/
Nick
On Wed, Mar 26, 2008 at 7:52 AM, Philippe P Mulet
<philippe_mulet@xxxxxxxxxx> wrote:
>
> The p2 team will soon post some documentation on p2 adoption. We are
hoping
> to have a good build shortly to point at.
> Given the late availability for p2 technology, we are considering
providing
> our M6 deliveries in 2 forms: one form with p2 enabled, one form with p2
> disabled.
> This would be a M6-only story to ease adoption and reduce the stress
level
> in our community.
> More details from the p2 team shortly.
>
> Apologies to all; and thanks for your endurance.
>
>
>
>
> "Nick Boldt" <codeslave@xxxxxxxxxx>
> Sent by: cross-project-issues-dev-bounces@xxxxxxxxxxx
>
> 03/26/2008 06:15 AM
>
> Please respond to
> Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>
>
>
> To "Cross project issues" <cross-project-issues-dev@xxxxxxxxxxx>
>
> cc
>
> Subject [cross-project-issues-dev] Migrating your automated tests to use
> p2's /dropins/ folder
>
>
>
>
>
>
> Everyone:
>
> I plan to turn this into a more digestable FAQ in the EclipseWiki, but
> for those who urgently need to get a build out using p2, here's a list
> of the files I had to change, and what I changed. (I'm still sniff
> testing the build to ensure that everything is in place and works as
> it did in last week's pre-p2 build, so consider this advice still in
> draft.)
>
> It's basically 4+ files:
>
> * o.e.foo.test.*/test.xml (one test.xml for each of your test plugins)
> * o.e.foo.releng/builder/tests/scripts/test.xml
> * o.e.foo.releng/builder/tests/customTargets.xml
> * org.eclipse.foo.releng/maps/foo.map (to update to the latest
> o.e.test tag, which may not have been required)
>
> Full details & links from here:
>
> http://www.eclipse.org/modeling/emf/searchcvs.php?q=223977fullpath=Y
>
> Nick
> _______________________________________________
> cross-project-issues-dev mailing list
> cross-project-issues-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
>
>
>
> Sauf indication contraire ci-dessus:/ Unless stated otherwise above:
> Compagnie IBM France
> Siège Social : Tour Descartes, 2, avenue Gambetta, La Défense 5, 92400
> Courbevoie
> RCS Nanterre 552 118 465
> Forme Sociale : S.A.S.
> Capital Social : 542.737.118 ?
> SIREN/SIRET : 552 118 465 02430
>
>
> _______________________________________________
> cross-project-issues-dev mailing list
> cross-project-issues-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
>
>
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
