Subject: Re: [prov] Participation opportunity - msg#00068
List: ide.eclipse.equinox.devel
Hi Pascal,
this sounds very exciting. The more I understand about P2, the more I
realize how similar it is to what we (Cloudsmith) are planning to do. We
are very interested in participating and with a somewhat aggressive
schedule that involves several committers. The work with the mirroring
application is probably the most important area for us but we are also
interested in the action based touchpoints.
Our current headless framework contains a command line application and
an installer (currently based on the Update Manager) that we plan make
P2 aware. Perhaps that could serve as the "director application"?
Regards,
Thomas Hallgren
Pascal Rapicault wrote:
I'm calling out for participation from the community on the following item:
- Director application. This consists in improving the "interface" of our
command line client and ensure that it replaces the equivalent
functionality available in update manager.
- Repository mirroring application. This consists in improving the
mirroring application, which is key to selectively publish content from one
repository to another.
- Action based contribution to touchpoints. This consists in revisiting the
way actions are contributed to touchpoints by allowing them to be shared
across touchpoints.
If you are interested in any of these areas, please let us know.
Thank you,
PaScaL
_______________________________________________
equinox-dev mailing list
equinox-dev-j9T/66MeVpFAfugRpC6u6w@xxxxxxxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/equinox-dev
Was this page helpful?
Thread at a glance:
Previous Message by Date:
click to view message preview
Re: [p2] Categories in Profiles / Group layers
> One minor thing about todays HEAD:
> org.eclipse.equinox.internal.provisional.p2.engine.phases.Messages has
> an incorrect BUNDLE_NAME, this one is missing a "provisional"...
Thanks. Fixed in HEAD.
Next Message by Date:
click to view message preview
New test project created
We have been working to get the p2 tests integrated with the build so they
are run as part of the automated test framework. Unfortuanatly we have some
tests which are testing (and therefore referencing) bundles which aren't
included in the SDK so there were failures. We have pulled these tests into
a separate project (org.eclipse.equinox.p2.tests.optimizers) and updated
the team project set files.
Please load the new project and add it to the list of tests you run before
releasing code to ensure that things are not broken.
Thanks.
Previous Message by Thread:
click to view message preview
[prov] Participation opportunity
I'm calling out for participation from the community on the following item:
- Director application. This consists in improving the "interface" of our
command line client and ensure that it replaces the equivalent
functionality available in update manager.
- Repository mirroring application. This consists in improving the
mirroring application, which is key to selectively publish content from one
repository to another.
- Action based contribution to touchpoints. This consists in revisiting the
way actions are contributed to touchpoints by allowing them to be shared
across touchpoints.
If you are interested in any of these areas, please let us know.
Thank you,
PaScaL
Next Message by Thread:
click to view message preview
Re: [prov] Participation opportunity
Thomas,
This is really great news! I'm really happy to see your involvement.
Please post on the mailing list or in bug reports for more specific details
on what you can / want to do.
Thx,
PaScaL
equinox-dev-bounces-j9T/66MeVpFAfugRpC6u6w@xxxxxxxxxxxxxxxx wrote on 04/08/2008
10:34:13 AM:
> Hi Pascal,
> this sounds very exciting. The more I understand about P2, the more I
> realize how similar it is to what we (Cloudsmith) are planning to do. We
> are very interested in participating and with a somewhat aggressive
> schedule that involves several committers. The work with the mirroring
> application is probably the most important area for us but we are also
> interested in the action based touchpoints.
>
> Our current headless framework contains a command line application and
> an installer (currently based on the Update Manager) that we plan make
> P2 aware. Perhaps that could serve as the "director application"?
>
> Regards,
> Thomas Hallgren
>
>
> Pascal Rapicault wrote:
> > I'm calling out for participation from the community on the following
item:
> > - Director application. This consists in improving the "interface" of
our
> > command line client and ensure that it replaces the equivalent
> > functionality available in update manager.
> > - Repository mirroring application. This consists in improving the
> > mirroring application, which is key to selectively publish content from
one
> > repository to another.
> > - Action based contribution to touchpoints. This consists in revisiting
the
> > way actions are contributed to touchpoints by allowing them to be
shared
> > across touchpoints.
> >
> > If you are interested in any of these areas, please let us know.
> >
> > Thank you,
> >
> > PaScaL
> >
> > _______________________________________________
> > equinox-dev mailing list
> > equinox-dev-j9T/66MeVpFAfugRpC6u6w@xxxxxxxxxxxxxxxx
> > https://dev.eclipse.org/mailman/listinfo/equinox-dev
> >
>
> _______________________________________________
> equinox-dev mailing list
> equinox-dev-j9T/66MeVpFAfugRpC6u6w@xxxxxxxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/equinox-dev