After commenting out the <pluginRepositories> section of
maven-osgi-plugin's pom.xml (see attached), I was able to successfully
build and rebuild, both with and without a populated ~/.m2/repository
directory.
I'm not sure if this is the proper fix. I do know that no live chickens
were required.
I apologize for the "maven-resource-plugin" vs.
"maven-resources-plugin". I must have botched trimming the error message.
Thanks for all of the insight and suggestions. I'll try it all over
again when Maven 2.0.5 is released tomorrow.
Tim
Carlos Sanchez wrote:
I'm not sure you even need it at all.
On 2/13/07, Steven E. Harris <[EMAIL PROTECTED]> wrote:
Tim Moloney <[EMAIL PROTECTED]> writes:
> from the specified remote repositories:
> apache.snapshots
(http://people.apache.org/repo/m2-snapshot-repository),
> snapshots (http://snapshots.maven.codehaus.org/maven2)
> central (http://repo1.maven.org/maven2)
Where did that middle codehaus.org entry come from? Oh, I see, maybe
here, according to grep:
tools/maven2/maven-osgi-plugin/pom.xml
It too needs qualification that it's only hosting snapshots, not
released versions.
--
Steven E. Harris
Index: tools/maven2/maven-osgi-plugin/pom.xml
===================================================================
--- tools/maven2/maven-osgi-plugin/pom.xml (revision 507328)
+++ tools/maven2/maven-osgi-plugin/pom.xml (working copy)
@@ -37,6 +37,7 @@
</repository>
</repositories>
+<!--
<pluginRepositories>
<pluginRepository>
<id>snapshots</id>
@@ -49,6 +50,7 @@
<url>http://people.apache.org/repo/m2-snapshot-repository</url>
</pluginRepository>
</pluginRepositories>
+-->
<distributionManagement>
<snapshotRepository>
