ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dominique Devienne" <>
Subject Why fail on a missing dependency of an unused task?
Date Thu, 20 Jan 2005 22:30:21 GMT
When I setup the performance testing environment for sync,
I dropped my custom Antlib jar into a freshly made Ant CVS
HEAD distrib. I ran my build file, which referenced my old
lsync task using the antlib: magic XML namespace, and I was
surprised to get an error about a task I wasn't even using!

I always thought that tasks whose dependents cannot be found
are simply ignored, with just a warning at verbose level.
Otherwise I'd get such errors left and right for the many
optional tasks I don't have the JARs for.

So what's different in this case? BTW, I checked, and also
got an error if I used <taskdef resource=""> instead of an
XML NS, and I checked it's the same for CVS HEAD and 1.6.2.

Can someone please explain what's going on? Thanks, --DD

P:\com_lgc\cycle9>P:\oss\org_apache\ant\apache-ant-1.7alpha\bin\ant -f
Buildfile: sync.xml

    [mkdir] Created dir: P:\com_lgc\cycle9\build\sb-sync
     [sync] Copying 5 files to P:\com_lgc\cycle9\build\sb-sync

    [mkdir] Created dir: P:\com_lgc\cycle9\build\dd-sync

P:\com_lgc\cycle9\sync.xml:19: The following error occurred while
executing this line:
l:5: taskdef A class needed by class com.lgc.buildmagic.JUnitx cannot be
found: junit/framework/Test

Total time: 1 second

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message