[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [tycho-dev] Working on a software artifact repository
- From: "Oberlies, Tobias" <tobias.oberlies@xxxxxxx>
- Date: Tue, 2 Dec 2014 17:02:30 +0000
- Accept-language: en-US
- Delivered-to: email@example.com
- Thread-index: AQHQDf97cgHd4uZfCU2bSyceJ64z6px8hL3w
- Thread-topic: [tycho-dev] Working on a software artifact repository
> I just wanted to check if there is interest in an open source (EPL),
> software artifact repository. The idea is not new, but we wanted to have
> some piece of software which can receive OSGi bundles and Eclipse
> features from a Maven Tycho build and push it into some sort of
> repository, consuming it later on as a P2 repository.
You know that p2 repositories don't scale to sizes far beyond what is used today, i.e. one Eclipse release train. Creating a "Maven central" for p2 has been tried by a team of Maven and p2 experts, and the approach failed. You seem to be trying to do something similar.
This is why we came up with the solution of having the repository manager only serve fixed sets artifacts as p2 repositories. This is done with Nexus OSS (i.e. the open-source Nexus) and the (open-source) Tycho unzip plugin. The "groups of artifacts" are produced by Tycho's eclipse-repository packaging type. At the moment, the implementation is pretty dumb. Currently, it deploys artifacts redundantly, but this could be fixed.
So in summary, we would only be interested if you are planning to extend Tycho and the Tycho Unzip Plugin.