Here's a JIRA issue describing this problem - it provides a workaround: http://jira.codehaus.org/browse/MANTTASKS-103
After I apply the workaround (adding attribute 'id="localDisk"' to the <remoteRepository> tag in the "m2-deploy" macro definition in common-build.xml), 'ant clean generate-maven-artifacts' builds successfully using maven-ant-tasks 2.0.8. (I didn't make any changes in my M2 local repo.) I'm not sure, though, if this warrants changing in the trunk, since the problem will likely be fixed in the next release of maven-ant-tasks; also, I don't know how this change would affect non-local deployment. Steve On 01/18/2008 at 10:04 AM, Steven A Rowe wrote: > Hi Michael, > > On 01/17/2008 at 10:28 PM, Michael Busch wrote: > > it's a bit weird. I actually just had the same problem with > > 2.0.8. Then I switched back to 2.0.7 and > > 'ant generate-maven-artifacts' was successful. Then I tried > > 2.0.8 again, and then 'ant clean generate-maven-artifacts' > was successful too! > > Well, switching to maven-ant-tasks 2.0.7 made everything > work, but then switching back to 2.0.8 resulted in the same failure. > > > Try to make sure that your 'M2_HOME' env variable points to the > > correct directory. > > Yes, it does - I set that up when I installed M2. > > > You also might want to delete the maven metadata files in > > 'C:\Documents and Settings\sarowe\.m2\repository\org\apache\lucene'. > > That's what I just did and 'ant clean generate-maven-artifacts' > > finished successful with 2.0.8. > > I tried doing this, but it didn't seem to help at all. > > Guess I'll stick with 2.0.7 :). > > > On Linux I never saw this problem with 2.0.8 so far. > > Or maybe switch to building on Linux! > > Thanks for your help. > > Steve >
