Thanks for the reply.
Unfortunately, I do not believe this is the problem. I cleaned out my local
repository, then ran mvn clean on my project. The same error appeared:
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] The plugin 'org.apache.maven.plugins:maven-clean-plugin' does not exist
or no valid version could be found
The only pluginRepository listed in my pom was the development server. Nothing
downloaded before the error appeared, so my central repository was definitely
not overridden.
Is there some additional configuration that I'm not aware of that plugin
repositories require? For example, do I need to specify some sort of metadata
in the repo somewhere?
>>>[EMAIL PROTECTED] 04/18/06 12:39 pm >>>
From Wayne Fay:
I think the problem is that some of these Maven poms are defining new
Repos which are added to the Repos list when they are added as
dependencies.
maven-help-plugin-2.0 has none defined
but it specifies maven-plugin-parent-2.0 as a dependency which specifies
<repositories>
<repository>
<id>snapshots</id>
<name>Maven Central Development Repository</name>
<url>http://snapshots.maven.codehaus.org/maven2</url>
<releases>
<enabled>false</enabled>
</releases>
</repository>
</repositories>
<pluginRepositories>
<pluginRepository>
<id>snapshots</id>
<name>Maven Central Plugins Development Repository</name>
<url>http://snapshots.maven.codehaus.org/maven2</url>
<releases>
<enabled>false</enabled>
</releases>
</pluginRepository>
</pluginRepositories>
See here:
http://www.ibiblio.org/maven2/org/apache/maven/plugins/maven-plugin-parent/2.0/maven-plugin-parent-2.0.pom
And then it has a bunch of other dependencies, which all have their
own poms and dependencies etc... So in all likelihood, somewhere in
that chain, I'm guessing that you are getting several new Repos and
PluginRepos added to your list.
This is certainly a bug in those poms. We've seen this before and I
believe it was agreed that it was not proper for hosted poms to
add/change Repos on the user out of the blue. It would be great if
there was an easy code solution to this problem, but I haven't looked
into it, and at the time the fix was to simply repair that one
specific pom.
So if we can find all the poms like this on Central and open a bunch
of MEV Jira bugs, Carlos will love us (not), but it should get rid of
your problems, EJ.
Wayne
-----Original Message-----
From: Mark Misurak [mailto:[EMAIL PROTECTED]
Sent: Tuesday, April 18, 2006 11:40 AM
To: users@maven.apache.org
Subject: Plugin repository issue
Hello. I'm having an issue with setting up a plugin repository on a
development server (I'm setting up this repository so that our
organization's developers will use the development server's repository
instead of Ibiblio). In my pom.xml for my project saved locally, I have
the following:
<project>
...
<repositories>
<repository>
<id>central</id>
<url>http://myorg.ca/maven2</url>
</repository>
</repositories>
<pluginRepositories>
<pluginRepository>
<id>central</id>
<url>http://myorg.ca/maven2</url>
</pluginRepository>
</pluginRepositories>
...
</project>
When I run mvn clean on the project, I see the following error:
[INFO] The plugin 'org.apache.maven.plugins:maven-clean-plugin' does not
exist or no valid version could be found
When I set the plugin repository back to Ibiblio, clean works fine.
Essentially, the dev server's repository works fine (ordinary jars
download just fine), but the server's plugin repository does not. How do
I set up my plugin repository correctly?
This email and/or any documents in this transmission is intended for the
addressee(s) only and may contain legally privileged or confidential
information. Any unauthorized use, disclosure, distribution, copying or
dissemination is strictly prohibited. If you receive this transmission in
error, please notify the sender immediately and return the original.
Ce courriel et tout document dans cette transmission est destiné à la personne
ou aux personnes à qui il est adressé. Il peut contenir des informations
privilégiées ou confidentielles. Toute utilisation, divulgation, distribution,
copie, ou diffusion non autorisée est strictement défendue. Si vous n'êtes pas
le destinataire de ce message, veuillez en informer l'expéditeur immédiatement
et lui remettre l'original.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
This email and/or any documents in this transmission is intended for the
addressee(s) only and may contain legally privileged or confidential
information. Any unauthorized use, disclosure, distribution, copying or
dissemination is strictly prohibited. If you receive this transmission in
error, please notify the sender immediately and return the original.
Ce courriel et tout document dans cette transmission est destiné à la personne
ou aux personnes à qui il est adressé. Il peut contenir des informations
privilégiées ou confidentielles. Toute utilisation, divulgation, distribution,
copie, ou diffusion non autorisée est strictement défendue. Si vous n'êtes pas
le destinataire de ce message, veuillez en informer l'expéditeur immédiatement
et lui remettre l'original.
