This started out as "can't find junit task" and has evolved into
something truly strange. I can offer a test scenario that fails
consistently with the current CVS head.
The short of it is that $MAVEN_HOME/plugins/plugins.cache makes it
impossible for me to create a taskdef using JUnitTask in my maven.xml
export MAVEN_HOME=~/tools/maven/current
rm -rf $MAVEN_HOME
mkdir -p $MAVEN_HOME
cd ~/jakarta
rm -rf jakarta-turbine-maven
cvs -d [EMAIL PROTECTED]:/home/cvs checkout jakarta-turbine-maven
cd jakarta-turbine-maven/
ant -f build-bootstrap.xml
mkdir ~/tmp/funk
cd ~/tmp/funk
jar xvf $MAVEN_HOME/plugins/maven-test-plugin-1.2-SNAPSHOT.jar project.xml
cat > maven.xml <<EOF
<?xml version="1.0"?>
<project default="funk">
<goal name="funk">
<taskdef name="junit"
classname="org.apache.tools.ant.taskdefs.optional.junit.JUnitTask"
/>
</goal>
</project>
EOF
# This will succeed
maven
# This will fail with 'taskdef ...JUnitTask cannot be found'
maven
# This will succeed
rm -f $MAVEN_HOME/plugins/plugins.cache
maven
# Any subsequent invocations will also succeed.
# Note that plugins.cache is essentially empty at this point.
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
- Re: Bizarre taskdef and plugins.cache interaction James CE Johnson
- Re: Bizarre taskdef and plugins.cache interaction James CE Johnson
