[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [tycho-dev] Working on a software artifact repository

Hi,

Yes I do know that. And I don't have the intention of replicating Maven
Central!

What I want to achieve is to have a tool for a local development
workflow, with the possibility to capture the P2 output of Maven Tycho
and render it as either a Maven or P2 repository. With the main use case
of using P2. So that you can have a continuous integration build,
feeding a repository, with a cleanup option. Once the output looks good,
the repository channel get frozen and the next iteration can begin. We
would need the same for ".deb" and ".rpm".

I am not sure in which way Tycho should be extended? At the moment it
can create P2 metadata, which can be deployed a repository. The
repository just has to be smart enough to extract and process this
information.

In addition we do have bundles which do not have a Tycho generated P2
metadata. For this we would need to extract it using a different way.

So instead of downloading an artifact manually from maven central,
processing P2 meta data manually, uploading it to some http location, so
that the compile process can consume it and manually track the state of
that, I would just like to create a repository channel with a mirrored
artifact from maven central, or just drop the "jar" in the repository.

So again, the idea is not to replicate maven central. But to provide a
tool which helps with the local build and deploy process.

But in which way could Tycho and the Unzip plugin be extended?

Best regards

Jens

On 12/02/2014 06:02 PM, Oberlies, Tobias wrote:
>> 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.
>
> Regards
> Tobias
>
> _______________________________________________
> tycho-dev mailing list
> tycho-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe from this list, visit
> https://dev.eclipse.org/mailman/listinfo/tycho-dev