Metabug for the hundreds of other bugs related to this.
Now if only someone would fix java-dep-check so it actually worked they could close 29 bugs.
what is this problem about? there are many bugs related to this issue it seems.
See my blog post. http://skaba.wordpress.com/2009/02/06/java-dep-check-0-3-and-weird-bugs-it-dis/ Some may be ignored some may be not.
I just closed one of the ant task bugs as WONTFIX but didn't realise there were a whole load more here. This isn't a problem for ant and we probably don't want to fix it in the usual way either but we should quash the warning somehow.
Looked into this some more. /usr/bin/ant gathers up the ANT_TASKS and gets the classpath with java-config. By the look of it, this is *not* supposed to include ant itself so that would explain why it has always been marked as a build-only dependency. In terms of quashing the warning, I figured the best thing to do would be to skip the check if the ant-tasks eclass has been inherited. I'll send a patch around soon.
That patch has been merged and some bugs have been closed. The remaining bugs are probably genuine problems that should be investigated.
*** Bug 298708 has been marked as a duplicate of this bug. ***
*** Bug 298722 has been marked as a duplicate of this bug. ***
(In reply to James Le Cuirot from comment #6) > That patch has been merged and some bugs have been closed. The remaining > bugs are probably genuine problems that should be investigated. What was patched? Would the removal of ant-tasks.eclass cause any trouble?
Do we still need this empty tracker?
