[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[p2-dev] P2 self provisioning

Hi guys,

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
installation.
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
opinions.

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.

-- 
Alin Dreghiciu
Software Developer
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
Participation Software.
http://www.qi4j.org - New Energy for Java - Domain Driven Development.