Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cross-project-issues-dev] Pre-M1 Aggregation Repository

BTW, as I work through my maven/tycho prototype for the aggregator, it doesn't seem that far fetched that would could have nightly aggregator builds. Not sure why we couldn't have that now mind you.

BTW2, I fear the Nexus. But that's probably just me and my lack of education on it. I know how to manage my p2 repos.


From: Matthias Sohn <matthias.sohn@xxxxxxxxx>
Reply-To: Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>
Date: Wednesday, 21 August, 2013 3:47 PM
To: Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>
Subject: Re: [cross-project-issues-dev] Pre-M1 Aggregation Repository

On Wed, Aug 21, 2013 at 7:45 PM, Igor Fedorenko <ifedorenko@xxxxxxxxxxxx> wrote:
Again, I am not arguing against building with individual dependency
repositories. All I am saying there is currently no convenient way to do
this and I don't have the time&resources to maintain such fine-grained
dependency configuration. I am particularly concerned about two problems.

First, I need to find location of proper dependency versions to build
for luna, kepler and juno (we have N-1 compatibility policy). Second, I
need a way to know if these dependency repositories go stale and need to
be updated.

One way to address these is to require each participating project
provide separate repository URL they recommend for use as build target
for each yearly release and make list of these URLs documented somewhere.

maybe it would help if we would ask all projects to deploy their
snapshots/milestones/releases into Nexus ( This would 
simplify finding all these p2 repositories in a central place.


Back to the top