[ http://jira.codehaus.org/browse/MAVEN-1733?page=comments#action_64020 ]
Arnaud Heritier commented on MAVEN-1733: ---------------------------------------- It can be related to this note given in the javac ant task : Windows Note:When the modern compiler is used in unforked mode on Windows, it locks up the files present in the classpath of the <javac> task, and does not release them. The side effect of this is that you will not be able to delete or move those files later on in the build. The workaround is to fork when invoking the compiler. http://ant.apache.org/manual/CoreTasks/javac.html A workarround can be to set maven.compile.fork=true Since I applied it locally I didn't yet reproduce it. > Bootstrap failure: Unable to obtain goal [plugin:test], in maven:reactor > ------------------------------------------------------------------------ > > Key: MAVEN-1733 > URL: http://jira.codehaus.org/browse/MAVEN-1733 > Project: Maven > Type: Bug > Versions: 1.1-beta-3 > Environment: Win XP, svn Checked out revision 355781. > Reporter: Jeff Jensen > Assignee: Arnaud Heritier > Attachments: buildit.log > > > bootstrap consistently fails. Attached is log for my last run. > This is an interesting line from it: > [exec] Caused by: Unable to delete directory > C:\devroot\reference\maven\maven-1\plugins\trunk\genapp\src\plugin-test\nonStandardDirsTest\target > I completely deleted the svn dirs and got latest. The error above prior was > this: > [exec] Root cause > [exec] Unable to delete directory > C:\devroot\reference\maven\maven-1\plugins\trunk\genapp\src\plugin-test\mavenHomeLocalTemplateTest\target > And the run that failed before that one did not have an "unable to delete > dir". (I did about 6 or so bootstraps today, trying to get it to work) > They are on different plugins, such as Javadoc, Test Genapp. I have 3 of my > last logs, and a couple of them are the test genapp (not the middle run of > the 3). > I hope something helps here, and this isn't some silly chase. Thanks again > for looking into it. > I tried to determine some environment thing for me. > Oh, typing of environment, I am using JDK 1.5. Is that OK, or perhaps the > prob? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira