Re: Can anyone confirm the behavior of updatePolicy never for repositories?

That was great advice, Bernd. I never was aware of that goal before, mostly using the 'analzye' and 'tree' goals. I also see that it is possible not use includes and excludes, i.e. to just purge what annoys you and not a whole 60 GB or so local repo. For reference:

Re: Can anyone confirm the behavior of updatePolicy never for repositories?

-- http://bernd.eckenfels.net Von: Shipp, Scott Gesendet: Friday, March 25, 2022 5:03:03 PM An: users@maven.apache.org Betreff: Can anyone confirm the behavior of updatePolicy never for repositories? Hi fellow Maven users, I have used Maven for 10 years or more

Can anyone confirm the behavior of updatePolicy never for repositories?

Hi fellow Maven users, I have used Maven for 10 years or more and I’m writing with a first. I have a project which was set up in Jenkins with a settings.xml that has updatePolicy set to “never” for a certain repository. I have experienced that when Maven 3.3.9 fails to resolve an artifact for

Re: Unable to clone the maven repositories

Hi Sandeep, yesterday almost everyone had problems getting artifacts from maven central, it should be resolved by now. My guess is that a lot of developers pushed their updated artifacts b/c of the log4j2 issue. If you have a in internal build server and cannot accept downtimes, you can install

Unable to clone the maven repositories

Hi Team , Could you please help me for the below issues -bash-4.2$ mvn package [INFO] Scanning for projects... [INFO] [INFO] --< oracle.km.provision:km-provision >-- [INFO] Building km-provision 1.0.0-master-SNAPSHOT [INFO] [ jar

Re: Scratching my head over repositories ...

Oh damn it! I should have figured that out! It now works. Thanks Anders! /Tommy   Från: Anders Hammar Svara: Maven Users List Datum: 24 april 2021 at 19:43:58 Till: Maven Users List Ämne:  Re: Scratching my head over repositories ... Ok, the problem is that you've declared a repository

Re: Scratching my head over repositories ...

tusoft/tools/codelicmgr/CodeLicenseManager/2.2.2/CodeLicenseManager-2.2.2.pom.sha1 > > And yes, the rest of the artifacts are there too. > > /Tommy > > > Från: Tommy Svensson > Svara: Maven Users List > Datum: 24 april 2021 at 15:21:03 > Till: Maven Users List > Ä

Re: Scratching my head over repositories ...

too. /Tommy Från: Tommy Svensson Svara: Maven Users List Datum: 24 april 2021 at 15:21:03 Till: Maven Users List Ämne:  Re: Scratching my head over repositories ... I am using latest IDEA which supplies maven 3.6.3. No version ranges. My interpretation of  https://maven.apache.org/gui

Re: Scratching my head over repositories ...

april 2021 at 20:37:20 Till: Maven Users List Ämne:  Re: Scratching my head over repositories ... But it should work. At least as long as you specify the version. This is what we do when we create patched versions of external libraries. We publish them to our internal repo but with the "co

CVE-2021-26291: Apache Maven: block repositories using http by default

Apache Maven may follow repositories that are defined in a dependency’s Project Object Model (pom) which may be surprising to some users, resulting in potential risk if a malicious actor takes over that repository or is able to insert themselves into a position to pretend to be that repository

Re: Scratching my head over repositories ...

On 2021-04-22T18:38:24 +0200 Tamás Cservenák wrote: > > So, IMO, bite the bullet, and continue publishing to Central. Yes, is a > process, is slow and has many problems, but is still the best way to go. At > least for your users. Publish your PGP key. Then, add this:

Re: Scratching my head over repositories ...

But it should work. At least as long as you specify the version. This is what we do when we create patched versions of external libraries. We publish them to our internal repo but with the "correct" groupId and artifactId, but a version that identifies it as patched (1.2-ISSUE123 e.g.). I admit

Re: Scratching my head over repositories ...

Howdy Tommy, I think you are on a thin ice with this setup: if your artifacts are in Central, why not publish them in future as well? Having your "own" repo, while it seems cool at first glance, is usually NOT what you want, unless you can guarantee reliability, availability and speed of that of

Re: Scratching my head over repositories ...

I think you should be able to define your repo to take precedence over Maven Central. >From documentation Remote repository URLs are queried in the following order for artifacts until one returns a valid

Scratching my head over repositories ...

Hello fellow maven fans, A very long time ago I released a package to maven central. That was such a pain that when Bintray came I  switched to Bintray (the best and simplest service I've ever used! Really sad to see it gone). Now that Bintray is no more I realized that I can publish my

Re: How maven repositories are resolved?

Thanks John for such a detailed explanation. Few doubts For release version assuming empty local repo. > - Build order this time alpha, bravo, charlie > - Alpha needs A, and Aa is downloaded as it's in central repo and that > was 1st repo in the order list When you say central repo is the first

Re: How maven repositories are resolved?

The answer depends on the following; 1) is it a release version or snapshot version. As if the release version is in local repo then no remote repo's are checked. 2) order your pom's are executed I've simplified your profiles with central repo and company repo, and Aa, Ab and Ac are the same GAV

How maven repositories are resolved?

Cross-posting from stackoverflow <https://stackoverflow.com/questions/63071141/how-maven-repositories-are-resolved> Let's say my settings.xml is defined like below http://maven.apache.org/SETTINGS/1.1.0 http://maven.apache.org/xsd/settings-1.1.0.xsd; xmlns="http://maven.apache.org/SET

Doc page on Maven repositories at Apache

Hi, all: I am in the process of moving some pages from one location to another on the Apache websites. We have a page that was marked as a "draft" in its original location. I have moved it to https://infra.apache.org/repository-faq.html , and would love any suggestions you might have about how to

Maven Artifact Resolver Ant Tasks - Remote Repositories

Does "Maven Artifact Resolver Ant Tasks" respect remote repositories defined in the specified POM when resolving? What about remote repositories the specified POM's parent?

Re: Default update policy for plugin repositories is never?

, Laird On Mon, Oct 2, 2017 at 12:19 PM Tom Golden <tgol...@andplus.com> wrote: > Wondering if someone can link me to some explicit documentation around the > update policy for plugin repositories. > > I ran into an issue today with our CI server where one build would use a

Default update policy for plugin repositories is never?

Wondering if someone can link me to some explicit documentation around the update policy for plugin repositories. I ran into an issue today with our CI server where one build would use a particularly old version of the sonar-maven-plugin. I eventually realized after some digging that it was due

Re: Order of maven repositories in settings.xml

IIRC they are checked in the reverse order compared to how they are defined. That's probably undocumented though and could change between Maven versions. /Anders On Sun, Oct 23, 2016 at 12:07 PM, Debraj Manna wrote: > I have a settings.xml which looks like below:- > >

Order of maven repositories in settings.xml

I have a settings.xml which looks like below:- http://maven.apache.org/SETTINGS/1.0.0; xmlns:xsi=" http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=" http://maven.apache.org/SETTINGS/1.0.0 http://maven.apache.org/xsd/settings-1.0.0.xsd;> nexusReleases

Re: Comparing specifying repositories in pom vs. settings.xml?

, 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

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

Re: Comparing specifying repositories in pom vs. settings.xml?

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 > e

Re: Comparing specifying repositories in pom vs. settings.xml?

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 o

Re: Comparing specifying repositories in pom vs. settings.xml?

with different repositories is also the local repository cache. While it does remeber where an artifact has come from, it does not cleanly isolate repos So when you build something which should not use a specific repo it might still discover the artifacts. So when you set up different settings

RE: Comparing specifying repositories in pom vs. settings.xml?

-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

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 different open repositories around the world, often with dubious hostnames like rpc268.cs.example.edu:8080 -- this meant that although the build was reproducible

RE: Comparing specifying repositories in pom vs. settings.xml?

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 repositories (which tends to make the repository manager slower), you still need to specify the repositories to search, right

Re: Comparing specifying repositories in pom vs. settings.xml?

ources, no? Then your settings.xml is always constant, pointing at your master Nexus, which groups all your needed repositories. Your build is reproducible and remains resilient to otherwise disruptive remote repository changes -- as long as your master Nexus does not change. On Tue, Oct 18, 2016 at 8

Re: Comparing specifying repositories in pom vs. settings.xml?

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 >

AW: Comparing specifying repositories in pom vs. settings.xml?

Re: Comparing specifying repositories in pom vs. settings.xml? "The best way is to sync your stuff to the Central Repository" -- true, but again, there are cases where this is _not possible_. What then? I feel we keep repeating this mantra, but leaving out some cornerstones... On Tue,

Re: Comparing specifying repositories in pom vs. settings.xml?

ty.com> wrote: > The best way is to sync your stuff to the Central Repository imho. > > Otherwise you are probably best off with using repositories in the POM or > a checked in settings file and build.sh reference command build like mvn -s > ... > > manfred > > Curtis

Re: Comparing specifying repositories in pom vs. settings.xml?

The best way is to sync your stuff to the Central Repository imho. Otherwise you are probably best off with using repositories in the POM or a checked in settings file and build.sh reference command build like mvn -s ... manfred Curtis Rueden wrote on 2016-10-17 15:00: > Hi everyone, >

Re: Comparing specifying repositories in pom vs. settings.xml?

...@simpligility.com> 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 (un

Re: Comparing specifying repositories in pom vs. settings.xml?

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 (unless you use flatten). Instead I would check

RE: Comparing specifying repositories in pom vs. settings.xml?

> -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

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/ 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

RE: Comparing specifying repositories in pom vs. settings.xml?

repositories in pom vs. settings.xml? 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 the specified repos whe

Comparing specifying repositories in pom vs. settings.xml?

situation where the required repositories were simply defined in the top-level pom for the project. If this is done consistently, there's no longer any need to hack the settings.xml file. I seem to remember seeing some advice that specifying repositories in the POM is a bad practice. If I'm r

RE: [EXTERNAL] re: re-using server credentials for repositories

[EXTERNAL] re: re-using server credentials for repositories > > Hi, > > Looking at the code, there is really a one-to-one implicit mapping between the > repository id and the server id used to look-up authentication information. > > Maven adds to a DefaultAuthenticationSe

re: re-using server credentials for repositories

7 > De : "Justin Georgeson" > A : "Maven Users List" > Copie à : > Objet : re-using server credentials for repositories > > I’m curious why there doesn’t seem to be a way to reuse server credentials across multiple repositories (at least without a warning

re-using server credentials for repositories

I'm curious why there doesn't seem to be a way to reuse server credentials across multiple repositories (at least without a warning for those fortunate few on stack-overflow who claim success). For reference I mean as exemplified in [1], I have to define in my settings.xml a unique

Re: Multiple local repositories

/other/repository Kind regards Karl Heinz Marbaise Thank you Am 07.05.2016 um 22:57 schrieb Karl Heinz Marbaise: Hi, On 5/7/16 9:49 PM, Karagkiaouris Diamantis wrote: Hello, I would like to ask if it is possible to have multiple local maven repositories and if it can be set as a parameter

Re: Multiple local repositories

multiple local maven repositories and if it can be set as a parameter in a maven profile. Can you explain what you exactly mean. Do you mean having a different local caches for different purposes ? Runinng one build with cache at $HOME/.m2/repository and running a second build with cache

Re: Multiple local repositories

Hello, you can configure local repositories with file: URLs configured in profiles. https://maven.apache.org/guides/mini/guide-multiple-repositories.html It is not possible to have the local repository cache in a profile, but you can use different settings.xml files with the -s option. https

Re: Multiple local repositories

Hi, On 5/7/16 9:49 PM, Karagkiaouris Diamantis wrote: Hello, I would like to ask if it is possible to have multiple local maven repositories and if it can be set as a parameter in a maven profile. Can you explain what you exactly mean. Do you mean having a different local caches

Multiple local repositories

Hello, I would like to ask if it is possible to have multiple local maven repositories and if it can be set as a parameter in a maven profile. Thank you -- Karagkiaouris G. Diamantis, Junior Java EE Software Engineer, www.eurodyn.com

RE: Setting Up Internal Repositories

...@gmail.com] On Behalf Of Anders Hammar Sent: Friday, October 16, 2015 1:39 PM To: Maven Users List Subject: Re: Setting Up Internal Repositories You could also check the signature against expected release managers or similar. /Anders (mobile) Den 16 okt 2015 18:56 skrev "Ron Wheeler&qu

Re: Setting Up Internal Repositories

ganization. Wayne On Fri, Oct 16, 2015 at 9:33 AM, <michael.ctr.taru...@faa.gov> wrote: > The Maven Introduction to Repositories documentation contains a section that > describes setting up an internal repository. > > In that section is described an option to manually download and

Re: Setting Up Internal Repositories

essage- > From: Ron Wheeler [mailto:rwhee...@artifact-software.com] > Sent: Friday, October 16, 2015 12:56 PM > To: users@maven.apache.org > Subject: Re: Setting Up Internal Repositories > > Hard to say but checking the checksums from the author's site would be one > way to vet a rel

RE: Setting Up Internal Repositories

Repositories Hard to say but checking the checksums from the author's site would be one way to vet a release from a third party. Opening the download and looking inside to see that the artifacts are the ones that you were expecting is less secure but could be part of vetting. Ron On 16/10/2015

Re: Setting Up Internal Repositories

ase from a third party. > Opening the download and looking inside to see that the artifacts are the > ones that you were expecting is less secure but could be part of vetting. > > Ron > > On 16/10/2015 12:33 PM, michael.ctr.taru...@faa.gov wrote: > >> The Maven Introduction

Re: Setting Up Internal Repositories

, michael.ctr.taru...@faa.gov wrote: The Maven Introduction to Repositories documentation contains a section that describes setting up an internal repository. In that section is described an option to manually download and vet releases, apparently of a remote repo. What is meant by "vet&q

Setting Up Internal Repositories

The Maven Introduction to Repositories documentation contains a section that describes setting up an internal repository. In that section is described an option to manually download and vet releases, apparently of a remote repo. What is meant by "vet"? Can you provide an example of

Re: Use of Multiple Local Repositories

Hi Mehdi, it could be great if we can use multiple local reposiry for a build That has been discussed before on the list [1]. It was an interesting discussion but ultimately Maven does not support such a feature. I think it would be useful if a motivated party pursued it, though. Regards,

Re: Use of Multiple Local Repositories

Thank u for your answer. @Jeff, if we declare local repo 1 as a remote Maven repo, During the build, Maven will copy dependencies from local repo 1 to local repo 2, and one of the reasons of trying to set up two local repos at the same time is to avoid dependencies duplication between projects

Use of Multiple Local Repositories

Hello, I'm actually working on a continuous integration platform, and most of the projects are using Maven as a build tool. We've found that there is a list of dependencies and plugins most of the projects have to download in addition of there specific dependencies. Therefore, I though it could

Re: Use of Multiple Local Repositories

Then declare local repo 1 as a remove Maven repo accessed from the file: URL prefix Jeff On Thu, Jun 4, 2015 at 11:41 AM, Curtis Rueden ctrue...@wisc.edu wrote: Hi Mehdi, it could be great if we can use multiple local reposiry for a build That has been discussed before on the list [1]. It

Re: Use of Multiple Local Repositories

You can take a look at https://github.com/takari/tesla-split-localrepo I remember seeing a demo of this, but I don't know if it is working with recent versions of Maven / Aether HTH On 06/04/2015 04:30 AM, Mehdi Hayani wrote: Hello, I'm actually working on a continuous integration

Re: Cleaning source code repositories

-based projects. However discovering these modules in source repositories were always highlighting: - lack of knowledge if a certain module in repository is needed or even used in multiple products; - duplications of modules with similar purposes - sometimes a conscious decision

Cleaning source code repositories

results, I was able to trace down every module, which is needed to build the master CD. It was especially easy for Maven-based projects. However discovering these modules in source repositories were always highlighting: - lack of knowledge if a certain module in repository is needed or even used

Re: Cleaning source code repositories

projects. However discovering these modules in source repositories were always highlighting: - lack of knowledge if a certain module in repository is needed or even used in multiple products; - duplications of modules with similar purposes - sometimes a conscious decision to copy

Re: Cleaning source code repositories

these modules in source repositories were always highlighting: - lack of knowledge if a certain module in repository is needed or even used in multiple products; - duplications of modules with similar purposes - sometimes a conscious decision to copy in order to avoid breaking backward

Maven Repositories settings best practice

I do believe using maven mirror under setting.xml is best practice rather define them in pom.xml. However I am not able to locate some blogs I used to read before. Do you have any reference to this best practice? Very much appreciated -D

Re: Maven Repositories settings best practice

I found this http://blog.sonatype.com/2009/02/why-putting-repositories-in-your-poms-is-a-bad-idea/#.VIpCmTHF_AQ sorry about the noise -D On Thu, Dec 11, 2014 at 3:42 PM, Dan Tran dant...@gmail.com wrote: I do believe using maven mirror under setting.xml is best practice rather define them

Re: Maven Repositories settings best practice

On 12 December 2014 at 11:53, Dan Tran dant...@gmail.com wrote: I found this http://blog.sonatype.com/2009/02/why-putting-repositories-in-your-poms-is-a-bad-idea/#.VIpCmTHF_AQ sorry about the noise If you can't find it in the official docs, then feel free to hack up some enhancements.

Re: Maven Repositories settings best practice

Where is in the official doc, this should land? Thanks -D On Thu, Dec 11, 2014 at 6:52 PM, Barrie Treloar baerr...@gmail.com wrote: On 12 December 2014 at 11:53, Dan Tran dant...@gmail.com wrote: I found this http://blog.sonatype.com/2009/02/why-putting-repositories-in-your-poms

Re: Maven Repositories settings best practice

, but I would expect this advice to land in there. Or perhaps the Run Maven Configuring Maven ( http://maven.apache.org/guides/mini/guide-configuring-maven.html) has a section on Mirrors that links to http://maven.apache.org/guides/mini/guide-mirror-settings.html. The first sentence says Repositories

maven-release-plugin: multi module project with multiple git repositories

Hi,   i wonder if it's possible to use the maven-release-plugin for a project where each child project is served by a different git repository:   root - pom.xml [stored in git1] child1 - pom.xml [stored in git2] child2 - pom.xml [stored in git3] I searched the web for hours because there

Re: maven-release-plugin: multi module project with multiple git repositories

Short answer: no, that's not possible. The plugin assumes that every svn-folder or git-repository is a complete project with its own release-cycle. thanks, Robert Op Wed, 06 Aug 2014 18:24:42 +0200 schreef Henning Moll newssc...@gmx.de: Hi, i wonder if it's possible to use the

Remote repositories protocols

Hi, I read in the documentation ( https://maven.apache.org/guides/introduction/introduction-to-repositories.html) that maven repositories can be accessed by a variety of protocols such as file:// and http://; By curiosity I'm wondering what are the other protocols supported by maven

Re: Remote repositories protocols

Cornely ericcorn...@gmail.com wrote: Hi, I read in the documentation ( https://maven.apache.org/guides/introduction/introduction-to-repositories.html ) that maven repositories can be accessed by a variety of protocols such as file:// and http://; By curiosity I'm wondering what are the other

Re: Remote repositories protocols

/introduction/introduction-to-repositories.html ) that maven repositories can be accessed by a variety of protocols such as file:// and http://; By curiosity I'm wondering what are the other protocols supported by maven. Is there a list of them or a way I could make it ? by listing existing wagon

Re: Remote repositories protocols

Ok cool ! Thanks a lot I tried copying a part of a repository and pointed to it with an sftp url and it works perfectly. Here below is what it looks like : project... repositories repository idsftp/id urlsftp://maven.server.com/path/to/repository//url

RE: [nexus-user] Why are alternate repositories so hard to configure

] profiles profile idnexus/id activation activeByDefaulttrue/activeByDefault /activation repositories repository idcentral/id urlhttp://central/url releasesenabledtrue/enabled/releases

Re: [nexus-user] Why are alternate repositories so hard to configure

configuration. Maybe try something like the following: -[snip] profiles profile idnexus/id activation activeByDefaulttrue/activeByDefault /activation repositories repository idcentral/id urlhttp://central/url releasesenabledtrue/enabled

Re: [nexus-user] Why are alternate repositories so hard to configure

Hello back :-) On 4/15/2014 6:50 AM, Peter Lynch wrote: Hello, On Tue, Apr 15, 2014 at 12:14 AM, Eric Kolotyluk eric.koloty...@gmail.com mailto:eric.koloty...@gmail.com wrote: I have the following repositories repository idsonatype/id nameSonatype Maven OSS Repository

Re: [nexus-user] Why are alternate repositories so hard to configure

Hello, On Tue, Apr 15, 2014 at 12:14 AM, Eric Kolotyluk eric.koloty...@gmail.comwrote: I have the following repositories repository idsonatype/id nameSonatype Maven OSS Repository/name releases enabledtrue/enabled

Why are alternate repositories so hard to configure

I have the following repositories repository idsonatype/id nameSonatype Maven OSS Repository/name releases enabledtrue/enabled /releases snapshots enabledtrue/enabled /snapshots urlhttps://oss.sonatype.org/content/groups/public/url /repository /repositories But when I run maven I get [ERROR

updatePolicy for release repositories

I can't seem to find a detailed description of how updatePolicy affects release repository behavior. Can someone explain or point me to a document that does? I'm also interested in understanding how, if at all, updatePolicy affects release-version range resolution with regard to how often

Preventing Maven from downloading certain versions from external repositories

Hi, In a current project, by convention, we use 1.0-LOCAL-SNAPSHOT as the default version for local builds, producing official builds only through our CI server. This works well but during local builds, Maven will needlessly look for these versions in external repositories, slowing the build down

Re: Preventing Maven from downloading certain versions from external repositories

as the default version for local builds, producing official builds only through our CI server. This works well but during local builds, Maven will needlessly look for these versions in external repositories, slowing the build down. Is there a way to configure Maven never to look for specific versions

Re: Preventing Maven from downloading certain versions from external repositories

for local builds, producing official builds only through our CI server. This works well but during local builds, Maven will needlessly look for these versions in external repositories, slowing the build down. Is there a way to configure Maven never to look for specific versions outside

Re: Preventing Maven from downloading certain versions from external repositories

for these versions in external repositories, slowing the build down. Is there a way to configure Maven never to look for specific versions outside the local .m2 cache to avoid this slowdown? Regards, Kristian - Come read my webnovel, Take a Lemon http://www.takealemon.com, and listen

Re: Preventing Maven from downloading certain versions from external repositories

in external repositories, slowing the build down. Is there a way to configure Maven never to look for specific versions outside the local .m2 cache to avoid this slowdown? Regards, Kristian -- Andreas Dolk Zurmainerstraße 33 D-54292 Trier Phone「+49 651 4362884」 Mobile「+49 177 4970815」 EMail

Re: Preventing Maven from downloading certain versions from external repositories

Hi Kristian, In a current project, by convention, we use 1.0-LOCAL-SNAPSHOT as the default version for local builds, producing official builds only through our CI server. This works well but during local builds, Maven will needlessly look for these versions in external repositories, slowing

Re: Preventing Maven from downloading certain versions from external repositories

...@gmail.com Hi, In a current project, by convention, we use 1.0-LOCAL-SNAPSHOT as the default version for local builds, producing official builds only through our CI server. This works well but during local builds, Maven will needlessly look for these versions in external repositories

Mojo Developer Cook Book: For accessing artifacts and repositories

I have tried to resolve artifact as described in mojo dev cook bookhttp://docs.codehaus.org/display/MAVENUSER/Mojo+Developer+Cookbook#MojoDeveloperCookbook-Creatingandresolvinganartifact. org.apache.maven.artifact.resolver.ArtifactResolver class is missing in the latest maven-artifact plug-in.

Re: Mojo Developer Cook Book: For accessing artifacts and repositories

Since Maven3 this class is available in the maven-compat component: http://search.maven.org/#search%7Cga%7C1%7Cg%3A%22org.apache.maven%22%20AND%20a%3A%22maven-compat%22 Note that plugins compiled against the old maven-artifact component should still work with Maven3 (it gets translated

I need to run 2 profiles to deploy to 2 seperate Nexus repositories

. -- View this message in context: http://maven.40175.n5.nabble.com/I-need-to-run-2-profiles-to-deploy-to-2-seperate-Nexus-repositories-tp5751508.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe

Re: I need to run 2 profiles to deploy to 2 seperate Nexus repositories

How can I get Maven to run 2 separate Profiles to deploy the build artifacts to 2 separate Nexus repos? I have tried the following but only the second profile deploys to its Nexus repo. Instead of this approach, I suggest asking how to achieve your end goal on the Nexus lists. Surely there

Re: I need to run 2 profiles to deploy to 2 seperate Nexus repositories

A kind of dummy idea, Why not copy the deployed artifacts using wagon plugin from repository one to repository two ? Not sure if wagon plugin works for nexus, but it might. Hope it helps somehow tonio On Fri, Mar 22, 2013 at 11:25 AM, Wayne Fay wayne...@gmail.com wrote: How can I get

How to play with 2 repositories ?

settings files so that when I switch the config I keep my entire local repository useable, independantly of the place from where I downloaded it. - Gilles Scokart -- View this message in context: http://maven.40175.n5.nabble.com/How-to-play-with-2-repositories-tp5748541.html Sent from

Re: How to play with 2 repositories ?

I configure my settings files so that when I switch the config I keep my entire local repository useable, independantly of the place from where I downloaded it. - Gilles Scokart -- View this message in context: http://maven.40175.n5.nabble.com/How-to-play-with-2-repositories

Re: How to play with 2 repositories ?

it. - Gilles Scokart -- View this message in context: http://maven.40175.n5.nabble.com/How-to-play-with-2-repositories-tp5748541.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail

Re: How to play with 2 repositories ?

files so that when I switch the config I keep my entire local repository useable, independantly of the place from where I downloaded it. - Gilles Scokart -- View this message in context: http://maven.40175.n5.nabble.com/How-to-play-with-2-repositories-tp5748541.html Sent from the Maven

  1   2   3   4   5   6   7   8   9   10   >