Hi Arnaud,
If you're using an internal repo, central should be over-ridden. But it
shows that you're still accessing the ibiblio repo because, as you
mentioned in your first email, maven is trying to download from this URL:
http://repo1.maven.org/maven2
You should over-ride the central repo by declaring your internal repo's
ID as central. E.g.
<repositories>
<repository>
<id>central</id>
<name>your custom repo</name>
<url>http://your.custom.repo.url.org</url>
</repository>
</repositories>
Also change your custom-built cobertura plugin's groupId and artifactId
so that maven won't confuse it with the version in ibiblio.
If that still doesn't work, other than trying another build with a
clean/empty local repo, I don't have any more suggestions on how to
resolve your problem.
SNAPSHOTS are used for artifacts currently in development. E.g. if you
want other teams using your project have their copies updated whenever
you have updates to your code.
If you'll look at the artifacts in the remote snapshot repository, they
have timestamps after the version number. Here's an example:
http://snapshots.maven.codehaus.org/maven2/org/apache/maven/surefire/surefire-booter/1.5.3-SNAPSHOT/
The metadata keeps track of the latest version (last deployed) of that
artifact and maven downloads that version when the snapshot artifact is
used in a project.
Regards,
John
Arnaud Bailly wrote:
Hi John,
Yes, I have the tags <repositories> and <pluginRepositories>
configured. Actually, the pom is downloaded.
And I made a custom plugin, deployed it to our internal
repo and everything works fine. I would greatly appreciate some
insight into the maven-metadata and maven-artifact stuff if it exists,
before I starting digging into the code :-).
Here is what I understood/grabbed from docs :
- the maven-metadata-xxxx.xml in a group directory contains
informations about plugins in that group : the prefix for the plugin
and the version to use. The xxxx matches repositories ids which
means that the information corresponds to that repository: if I use
the corresponding pluginrepo, then artifact will use that metadata ;
- the maven-metadata-xxxx.xml in an artifact's base directory contains
information about the versions of a plugin :
- the current (latest ?) version of the artifact ;
- the current <release> version and the current <latest> version
(??) ;
- the various versions available in the directory ;
- the timestamp this file was last updated (for updates management
policy ?).
- the maven-metadata-xxxx.xml in a versionned artifact's directory
also contains updates information for the version this directory
contains (??). I suspect this is only true for snapshots (??).
Questions :
- what is the scenario for snapshots ?
- is there something special about naming a verisons X.Y.Z-SNAPSHOT ?
I am puzzled.
regards,
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
