Hi.
mvn will not create a default m2 pom when it did not find a valid v4 pom
in the remote repository. This is done to make mvn to keep on checking
the remore repo for a valid v4 pom.
Anyway, the output you see is just a warning and if mvn does not see a
pom in its local repo, it will create one "in-memory".
^_^
Sasvata Chatterjee wrote:
When m2 downloads m1-built JARs from a legacy repo, and there is an
associated m1-POM, is m2 supposed to create a
<modelVersion>4.0.0</modelVersion> POM in the local m2 repo?
I have this repo definition:
<repositories>
<repository>
<id>apache - legacy</id>
<layout>legacy</layout>
<url>http://cvs.apache.org/repository/</url>
</repository>
<repository>
<id>dist.codehaus.org - legacy</id>
<url>http://dist.codehaus.org</url>
<layout>legacy</layout>
</repository>
</repositories>
and when m2 (2.0.2) downloaded (several other codehaus.org JARs do
this, but as an example), picocontainer-1.2-RC-2.jar, it downloaded
the m1-POM verbatim. The build later complains:
[WARNING] POM for 'picocontainer:picocontainer:pom:1.2-RC-2' is invalid. It will
be ignored for artifact resolution. Reason: Not a v4.0.0 POM.
Thanks,
Shash
---------------------------------------------------------------------
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]
