we had same problem with 2.0.5 - it seems for me the problem is:
1. you tried to get some artifacts
2. getting was failed
3. information about it was placed into local repository
4. next time maven did not tried to get them
Try to remove local repository - or part related to this group/artifact -
maybe it will help
2007/4/2, Stefan Hübner <[EMAIL PROTECTED]>:
Hi all,
keen to migrate to 2.0.6 this morning I've ran right into a problem
concerning the wagon-webdav extension and the way I declared it (using
a version range) in our company wide Super POM.
Up to maven 2.0.5 the following declaration worked fine:
<extension>
<groupId>org.apache.maven.wagon</groupId>
<artifactId>wagon-webdav</artifactId>
<version>[1.0-beta-1,)</version>
</extension>
With maven 2.0.6 I get the following exception:
[INFO]
------------------------------------------------------------------------
[ERROR] FATAL ERROR
[INFO]
------------------------------------------------------------------------
[INFO] An invalid artifact was detected.
This artifact might be in your project's POM, or it might have been
included transitively during the resolution process. Here is the in
formation we do have for this artifact:
o GroupID: org.apache.maven.wagon
o ArtifactID: wagon-webdav
o Version: <<< MISSING >>>
o Type: pom
[INFO]
------------------------------------------------------------------------
[INFO] Trace
org.apache.maven.artifact.InvalidArtifactRTException: For artifact
{org.apache.maven.wagon:wagon-webdav:null:pom}: The version cannot b
e empty.
What's the deal here? Is this a side effect of some refactoring or a
certain decision concerning extension handling?
Any hints much appreciated,
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
With Best Regards,
Alexey Kakunin, EmDev Limited
Professional Software Development:
http://www.emdev.ru
