On Wed, Aug 21, 2013 at 7:45 PM, Igor Fedorenko <ifedore...@sonatype.com>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 (repo.eclipse.org). This would
simplify finding all these p2 repositories in a central place.

--
Matthias
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Reply via email to