'
*Reply To: *Cross project issues
*Subject: *Re: [cross-project-issues-dev] Pre-M1 Aggregation Repository
That sounds identical in effect to building against simrel repo, with
all the same issues.
*From:*cross-project-issues-dev-boun...@eclipse.org
[mailto:cross-project-issues-dev-boun
-project-issues-dev] Pre-M1 Aggregation Repository
Sent by:cross-project-issues-dev-boun...@eclipse.org
Hi,
I noticed that an empty Luna repository had been created some time after
the release of Kepler. An empty repository is
not really useful as a source for build dependencies and I
@eclipse.org
mailto:cross-project-issues-dev@eclipse.org,
Date: 08/21/2013 03:49 AM
Subject: [cross-project-issues-dev] Pre-M1 Aggregation Repository
Sent by: cross-project-issues-dev-boun...@eclipse.org
mailto:cross-project-issues-dev-boun...@eclipse.org
: [cross-project-issues-dev] Pre-M1 Aggregation Repository
Sent by: cross-project-issues-dev-boun...@eclipse.org
mailto:cross-project-issues-dev-boun...@eclipse.org
Hi,
I noticed that an empty Luna repository had been created
/2013 03:49 AM
Subject: [cross-project-issues-dev] Pre-M1 Aggregation Repository
Sent by: cross-project-issues-dev-boun...@eclipse.org
mailto:cross-project-issues-dev-boun...@eclipse.org
Hi,
I noticed that an empty Luna
@eclipse.org
Subject: Re: [cross-project-issues-dev] Pre-M1 Aggregation Repository
Theoretically, yes, it does open possibility for bad things to happen.
In practice, however, this worked for us for last three releases. If there
was an easy way to consume current simrel dependencies from the build
, 2013 8:36 AM
To: cross-project-issues-dev@eclipse.org
Subject: Re: [cross-project-issues-dev] Pre-M1 Aggregation Repository
Theoretically, yes, it does open possibility for bad things to happen.
In practice, however, this worked for us for last three releases. If
there was an easy way
On Wed, Aug 21, 2013 at 7:45 PM, Igor Fedorenko ifedore...@sonatype.comwrote:
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 timeresources to maintain such fine-grained
-issues-dev@eclipse.orgmailto:cross-project-issues-dev@eclipse.org
Subject: Re: [cross-project-issues-dev] Pre-M1 Aggregation Repository
On Wed, Aug 21, 2013 at 7:45 PM, Igor Fedorenko
ifedore...@sonatype.commailto:ifedore...@sonatype.com wrote:
Again, I am not arguing against building
Nexus does not support mutable p2 repositories similar to maven, so we
will have to deploy separate p2 repository per build per project. I am
not sure what advantages this will have compared to existing download
area, and we will still have no easy way to tell what repositories
should be used for
...@eclipse.org
[mailto:cross-project-issues-dev-boun...@eclipse.org] On Behalf Of Igor
Fedorenko
Sent: Wednesday, August 21, 2013 12:55 PM
To: cross-project-issues-dev@eclipse.org
Subject: Re: [cross-project-issues-dev] Pre-M1 Aggregation Repository
Nexus does not support mutable p2 repositories similar
To: 'Cross project issues'
Subject: RE: [cross-project-issues-dev] Pre-M1 Aggregation Repository
A single repo that has everyone's builds, milestones and releases would make
the situation worse rather than better. Whether you use an uber p2 repo with
links or Maven. The issue is how do you control
[mailto:konstantin.komissarc...@oracle.com]
Sent: Wednesday, August 21, 2013 1:04 PM
To: 'Cross project issues'
Subject: RE: [cross-project-issues-dev] Pre-M1 Aggregation Repository
A single repo that has everyone's builds, milestones and releases would make
the situation worse rather than better. Whether you
: Wednesday, August 21, 2013 1:26 PM
To: cross-project-issues-dev@eclipse.org
Subject: Re: [cross-project-issues-dev] Pre-M1 Aggregation Repository
Is this really better than using single simrel repo as build target
platform? I mean, all these repositories get aggregated into simrel repo on
regular
@eclipse.org; 'Cross project issues'
Subject: Re: [cross-project-issues-dev] Pre-M1 Aggregation Repository
Another option would be to create a top level pom that has all the dependent
repos that feed into the aggregate and you can use that for your builds.
Sent from my BlackBerry 10 smartphone
15 matches
Mail list logo
