Olivier,
Ah, I have proximity
(https://is-micro.myip.hu/projects/ismicro-commons/proximity/) setup
as a mirror of central.
Will try setting up the settings.xml as you have, and then get ontp
the proximity guys.
Thanks
Ben
On 6/5/06, Olivier Lamy <[EMAIL PROTECTED]> wrote:
Strange,
Because for me it works well.
How your company repositories are declared ?
In my case, we have two company repo declared in developpers
settings.xml :
Release one :
<repository>
<releases>
<updatePolicy>never</updatePolicy>
</releases>
<snapshots>
<updatePolicy>never</updatePolicy>
</snapshots>
<id>id</id>
<name>id-maven2</name>
<url>http://ip/maven2</url>
</repository>
Snapshot one :
<repository>
<releases>
<updatePolicy>never</updatePolicy>
<enabled>false</enabled>
</releases>
<snapshots>
<updatePolicy>interval:30</updatePolicy>
</snapshots>
<id>id-snapshots</id>
<name>id-maven2-snapshots</name>
<url>http://ip/snapshots</url>
</repository>
This works like a charm.
I have just tryed with a rm -rf $HOME/.m2/repository/com
And all artifacts downloaded without trouble.
--
Olivier
-----Message d'origine-----
De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] De la part de
ben short
Envoyé : lundi 5 juin 2006 12:29
À : Maven Users List
Objet : Re: RE : [M2] Snapshots deployed to server not being found
Oliver,
I have tried the -U. But i dont have any version of the artifact in my
local repo. So i would of assumed that it would download it.
Ben
On 6/5/06, Olivier Lamy <[EMAIL PROTECTED]> wrote:
> Hi,
> Try -U (sometimes saved troubles)
> You can change updatePolicy in your settings for this repo (during a
> furious dev phase you set always ;-) or interval:xxx in minutes)
>
> --
> Olivier
>
> -----Message d'origine-----
> De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] De la part
> de ben short Envoyé : lundi 5 juin 2006 12:13
> À : Maven Users List
> Objet : [M2] Snapshots deployed to server not being found
>
>
> Hi,
>
> I am trying to include a snapshot that has been deployed to our
> internal repository. When I do mvn compile, maven complains that it
> couldn't resolve the dependency.
>
> Is this a bug with maven 2.0.4?
>
> Ben
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
> This e-mail, any attachments and the information contained therein
> ("this message") are confidential and intended solely for the use of
the addressee(s). If you have received this message in error please send
it back to the sender and delete it. Unauthorized publication, use,
dissemination or disclosure of this message, either in whole or in part
is strictly prohibited.
>
------------------------------------------------------------------------
--------------------------------------
> Ce message électronique et tous les fichiers joints ainsi que les
informations contenues dans ce message ( ci après "le message" ), sont
confidentiels et destinés exclusivement à l'usage de la personne à
laquelle ils sont adressés. Si vous avez reçu ce message par erreur,
merci de le renvoyer à son émetteur et de le détruire. Toutes
diffusion, publication, totale ou partielle ou divulgation sous quelque
forme que se soit non expressément autorisées de ce message, sont
interdites.
>
------------------------------------------------------------------------
-------------------------------------
>
>
> ---------------------------------------------------------------------
> 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]
---------------------------------------------------------------------
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]
