It's interesting that this is a snapshot problem.  We had a very similar 
problem with our Archiva installation which proved to be related to use of 
the <mirrors> setting in settings.xml.    We had two Archiva repositories 
set up - one for regular artifacts and one for snapshots.   We used the 
<mirrorOf>*</mirrorOf> setting for the regular repository, which turned 
out to have the "side effect" (if I read the documentation correctly) of 
blocking access to the snapshots repository (since maven thought the whole 
world was in the regular repository).   Removing the mirror settings 
solved a lot of problems.

Details of the Maven mirror settings are here 
http://maven.apache.org/guides/mini/guide-mirror-settings.html 


Looking forward to finding out what the resolution of this problem is!




From:   Shay Thompson <[email protected]>
To:     Maven Users List <[email protected]>
Date:   02/17/2011 08:04 AM
Subject:        RE: Repository Confusion



Error is below.  It looks like it's looking in the snapshots repository 
but the url doesn't.  Odd.  The dependency I'm using is below too.

<dependency>
                 <groupId>org.apache.sling</groupId>
                 <artifactId>org.apache.sling.junit.core</artifactId>
                 <version>0.1.1-SNAPSHOT</version>
<dependency>



Downloading: 
http://xxx:8080/archiva/repository/internal//org/apache/sling/org.apache.sling.junit.core/0.1.1-SNAPSHOT/org.apache.sling.junit.core-0.1.1-SNAPSHOT.pom


[INFO] Unable to find resource 
'org.apache.sling:org.apache.sling.junit.core:pom:0.1.1-SNAPSHOT' in 
repository apache.snapshots (http://repository.apache.org/snapshots)

Downloading: 
http://xxx:8080/archiva/repository/internal//org/apache/sling/org.apache.sling.junit.core/0.1.1-SNAPSHOT/org.apache.sling.junit.core-0.1.1-SNAPSHOT.jar


[INFO] Unable to find resource 
'org.apache.sling:org.apache.sling.junit.core:jar:0.1.1-SNAPSHOT' in 
repository apache.snapshots (http://repository.apache.org/snapshots)

[INFO] 
------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] 
------------------------------------------------------------------------
[INFO] Failed to resolve artifact.



-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of Deng 
Ching
Sent: Thursday, February 17, 2011 12:46 AM
To: Maven Users List
Subject: Re: Repository Confusion

What's the exact error you're getting in Maven for the 2 machines?

-Deng

On Thu, Feb 17, 2011 at 2:35 PM, Shay Thompson <[email protected]> wrote:
>
> Outlook likes to capitalize. My file has a lower-case s.
>
> -----Original Message-----
> From: Ben Caradoc-Davies [mailto:[email protected]]
> Sent: Wednesday, February 16, 2011 11:58 PM
> To: Maven Users List
> Cc: Shay Thompson
> Subject: Re: Repository Confusion
>
> You are asking about your Maven settings.xml?
>
> The file should be called settings.xml (note case!) not Settings.xml on
> platforms and filesystems that filename case-sensitive. For example,
> Settings.xml would work on Windows/NTFS but not on Unix or Linux, where
> only settings.xml (lowercase) would work.
>
> Kind regards,
> Ben.
>
> On 17/02/11 13:41, Shay Thompson wrote:
>> Settings.xml is exactly the same on all machines.
>
> --
> Ben Caradoc-Davies <[email protected]>
> Software Engineering Team Leader
> CSIRO Earth Science and Resource Engineering
> Australian Resources Research Centre
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]


--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean (mailgw2:E73FA1E6FC.A3195).




This communication and any attachments are confidential, protected by 
Communications Privacy Act 18 USCS ยง 2510, solely for the use of the 
intended recipient, and may contain legally privileged material. If you 
are not the intended recipient, please return or destroy it immediately. 
Thank you.

Reply via email to