[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[p2-dev] P2 self provisioning
- From: Alin Dreghiciu <adreghiciu@xxxxxxxxx>
- Date: Thu, 1 Apr 2010 09:00:37 +0300
- Delivered-to: email@example.com
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=U4wzrgRDz9QFhomNjUMC+dq2zpB1NsMEnj08iS6UysqnOwsu1pK3sIOdhN8zgD0Szi MrjQyQzhh88oDMdosUwXq4eqJYYl+H9mw/3D5fMG/3iaI5wVIBa9VG6bM1o9i7to5kab MgCOk4QAD1kZHhaCQ6LEQG4i18HOXjnYktBdw=
My use case is that I need P2 to use custom repository types, without
having the agent to already be aware of this new repo types prior
I filed a bug (https://bugs.eclipse.org/bugs/show_bug.cgi?id=307274)
about this but I guess a post here will have bigger audience, so
My idea is simple and similar to current meta requirements: p2 is
first looking in the repositories to be used for meta
metadata/artifacts. If present, P2 will first provision itself with
the root iu's found in this meta repository and then proceed to the
normal provisioning process (the current one).
Basically I ask here an additional optional provisioning of P2 itself
before doing teh actual provisioning. This beside solving my use case
with custom repositories types it actually allow any extensions to be
added to P2 (touchpoint types/actions) before the actual provisioning.
This meta repositories are suppose to be usable with a standard p2
install (standard repositories types) or other types if you know that
the agent already knows them.
If we agree that this will be useful I would go and create a patch.
My profile: http://www.linkedin.com/in/alindreghiciu
My blog: http://adreghiciu.wordpress.com
http://sonatype.com - Sonatype - The Maven Company
http://www.ops4j.org - New Energy for OSS Communities - Open
http://www.qi4j.org - New Energy for Java - Domain Driven Development.