Here's the contents of settings.xml relevant to our repo manager:
<mirrors>
<mirror>
<id>our-repository</id>
<name>Maven Repository Manager running on
corp.com</name>
<url>http://repo.corp.com/artifactory/repo</url>
<mirrorOf>*</mirrorOf>
</mirror>
</mirrors>
Martijn
On Wed, Nov 10, 2010 at 2:33 PM, Stephen Connolly
<[email protected]> wrote:
> How have you defined your corp maven repo in your settings.xml
>
> I'm wondering if it's a bug in maven 2 pulling releases from the wrong repo
> and therefore you don't notice that the repo is defined incorrectly in
> settings.xml
>
> On 10 Nov 2010 08:39, "mjsell" <[email protected]> wrote:
>
>
> Yeah, this is definitely not a pom that exists in the project tree, so the
> parent-pom resolution changes mentioned in the compatibility notes do not
> apply. In my case it is a corporate pom that is separately released, and
> all of our project trees end up inheriting from a previously released
> version of it. Maven 2.2.1 successfully pulls it down from the remote
> repository, but Maven 3.0 does not. If it is in the local repository
> everything works fine, but if it needs to be retrieved from the remote
> repository then it just fails without trying. Interestingly, if I change it
> to a snapshot version of the corporate pom, then Maven 3 appears to
> correctly attempt to pull it from the remote repositories. This definitely
> sounds like a bug to me.
> --
> View this message in context:
> http://maven.40175.n5.nabble.com/M3-fails-to-download-parent-pom-tp3240199p3258005.html
>
> Sent from the Maven - Users mailing list archive at Nabble.com.
>
> -----------------------------------...
>
--
Become a Wicket expert, learn from the best: http://wicketinaction.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
