, KARR, DAVID <dk0...@att.com> wrote:
>> -Original Message-
>> From: Mark H. Wood [mailto:mw...@iupui.edu]
>> Sent: Wednesday, October 19, 2016 5:55 AM
>> To: users@maven.apache.org
>> Subject: Re: Comparing specifying repositories in pom vs. settings.xml
> -Original Message-
> From: Mark H. Wood [mailto:mw...@iupui.edu]
> Sent: Wednesday, October 19, 2016 5:55 AM
> To: users@maven.apache.org
> Subject: Re: Comparing specifying repositories in pom vs. settings.xml?
>
> OK, I'm going to learn a lot from this thread
OK, I'm going to learn a lot from this thread.
On Tue, Oct 18, 2016 at 06:57:42AM -0700, Robert Patrick wrote:
> But in a large corporate environment, the centralized repository manager can
> house hundreds/thousands of repositories so unless you want to virtualize the
> entire set of
On 17 Okt 2016, Manfred Moser wrote:
> If you really feel you need to control the source of where you download
> components from within the source control system
> I would still NOT use the repositories definition in the POM since that is
> them transferred to the target repo on deployment
the repositories to search, right?
-Original Message-
From: Curtis Rueden [mailto:ctrue...@wisc.edu]
Sent: Tuesday, October 18, 2016 8:14 AM
To: Maven Users List
Subject: Re: Comparing specifying repositories in pom vs. settings.xml?
> I'm trying, without success, to imagine why you do not sim
-Reyes [mailto:st...@apache.org]
Sent: Tuesday, October 18, 2016 8:00 AM
To: Maven Users List
Subject: Re: Comparing specifying repositories in pom vs. settings.xml?
Yes, some years ago we did exactly this; most academic open source projects
then didn't bother with Maven Central and we relied on 8
Yes, some years ago we did exactly this; most academic open source projects
then didn't bother with Maven Central and we relied on 8 different open
repositories around the world, often with dubious hostnames like
rpc268.cs.example.edu:8080 -- this meant that although the build was
reproducible for
?
-Original Message-
From: Curtis Rueden [mailto:ctrue...@wisc.edu]
Sent: Tuesday, October 18, 2016 8:14 AM
To: Maven Users List
Subject: Re: Comparing specifying repositories in pom vs. settings.xml?
> I'm trying, without success, to imagine why you do not simply
> accumulate el
> I'm trying, without success, to imagine why you do not simply
> accumulate elements as required.
Wouldn't that cause Maven to ping every server sequentially for every
needed artifact?
Better to set up a Maven repository manager (Nexus, Artifactory, etc.) and
proxy all the needed sources, no?
On Mon, Oct 17, 2016 at 08:03:03PM +, KARR, DAVID wrote:
> One thing I run into when jumping between different projects is different
> expectations for what maven repos I need to be using. In the past, I had to
> have multiple copies of "~/.m2/settings.xml" lying around, and I would hack
>
rred to the target repo on deployment (unless you use
> flatten).
> >>
> >> Instead I would check in a specific settings.xml as part of the
> project...
> >> or even multiple ones for different build scenarios..
> >>
> >> Manfred
> >
d scenarios..
>>
>> Manfred
>>
>> KARR, DAVID wrote on 2016-10-17 14:42:
>>
>> >> -Original Message-
>> >> From: Manfred Moser [mailto:manf...@simpligility.com]
>> >> Sent: Monday, October 17, 2016 1:35 PM
>> >> To: users@maven
Manfred Moser [mailto:manf...@simpligility.com]
> >> Sent: Monday, October 17, 2016 1:35 PM
> >> To: users@maven.apache.org
> >> Subject: Re: Comparing specifying repositories in pom vs. settings.xml?
> >>
> >> http://blog.sonatype.com/2009/02/why-
35 PM
>> To: users@maven.apache.org
>> Subject: Re: Comparing specifying repositories in pom vs. settings.xml?
>>
>> http://blog.sonatype.com/2009/02/why-putting-repositories-in-your-poms-
>> is-a-bad-idea/
>
> The point about open-source projects is well
> -Original Message-
> From: Manfred Moser [mailto:manf...@simpligility.com]
> Sent: Monday, October 17, 2016 1:35 PM
> To: users@maven.apache.org
> Subject: Re: Comparing specifying repositories in pom vs. settings.xml?
>
> http://blog.sonatype.com/2009/02/why
http://blog.sonatype.com/2009/02/why-putting-repositories-in-your-poms-is-a-bad-idea/
KARR, DAVID wrote on 2016-10-17 13:03:
> One thing I run into when jumping between different projects is different
> expectations for what maven repos I need to be using. In the past, I had to
> have multiple
My team always favors defining repos in the top-level (parent) POM. If we
require special project-specific settings that must be in settings.xml, we put
settings.xml in the top-level of the project source tree and check it in...
For publishing projects to our binary repo for consumption by
17 matches
Mail list logo
