I'm back.
First, thank you for your answers.
Sorry to say this but the more I try it, the more I find it strange (under
linux) ... and I can't start using a tool with such questions haunting me.
Question 1 :
I work under Linux (this could be important because I never succeeded in
using the automatic update under linux but it worked as soon as I tried
under Windows, even with a proxy configuration).
So I used the automatic update with a windows machine, and then transferred
the local repository to my linux secured network. I want this copy to become
my remote repository.
I tried the solution of a "single mirror" entry with mirrorOf set to central
in the settings.xml and it works ONLY IF I rename all the
maven-metadata-central.xml files to maven-metadata.xml. When I use "mvn -c
archetype:create ...", after the "download" to my $HOME/.m2/repository,
these files have been automatically renamed again to
maven-metadata-central.xml. Is it a normal behaviour ? (not intuitive
anyway)
Question 2 :
Now, I would like to use the <repositories> way, instead of mirror.
What I can say is that whatever the id of the repository ("central" or not),
it always failed BUT with the following settings :
<profiles>
<profile>
<repositories>
<repository>
<releases>
<enabled>true</enabled>
<updatePolicy/>
<checksumPolicy/>
</releases>
<snapshots>
<enabled>true</enabled>
<updatePolicy/>
<checksumPolicy/>
</snapshots>
<id>_REPO_1</id>
<name>My repo1</name>
<url>file:///mypath/ibiblio/maven2</url>
<layout/>
</repository>
</repositories>
<pluginRepositories>
<pluginRepository>
<releases>
<enabled>true</enabled>
<updatePolicy/>
<checksumPolicy/>
</releases>
<snapshots>
<enabled>true</enabled>
<updatePolicy/>
<checksumPolicy/>
</snapshots>
<id>_REPO_2_</id>
<name>My repo2</name>
<layout/>
<url>file:///mypath/ibiblio/maven2</url>
</pluginRepository>
</pluginRepositories>
<id>MyProfile</id>
</profile>
<activeProfiles>
<activeProfile>MyProfile</activeProfile>
</activeProfiles>
IT HAS BEEN WORKING ... FOR AN HOUR ...
Among the output, I could see the proof that my repository was taken into
account (with an id not equal to central) :
...
[INFO] org.apache.maven.plugins: checking for updates from _REPO_2_
[INFO] org.apache.maven.plugins: checking for updates from central
...
I have to say that I don't know very well the usefulness of <enabled>,
<updatePolicy>, <checksumPolicy> and <layout> but as it was working, I made
preciously a copy of settings.xml in a safe place.
It was the only time I succeeded using repositories. The day after, no way.
It worked no more. It's a mystery.
So : have you heard of an intermittent problem with mvn and/or Linux and/or
the file:/// protocol ?
Anybody having the same problem ?
Thank you.
_________________________________________________________________
Apprenez à lutter contre le spam !
http://go.msn.fr/10-channel/80-security/spam/default.asp
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
