Bugzilla Bug 110337

Following http://www.gentoo.org/proj/en/java/java-devel.xml we should only
depend on dev-java/ant-core when possible. I opened this bug for tracking
various issues related to this transition and for people to report packages that
only need ant-core or have missing dependencies because /usr/bin/ant puts
packages to CLASSPATH which can result as missing dependencies. Nichoj has
created a list to experimental which can act as a starting point:
http://gentooexperimental.org/svn/java/gentoo-java-experimental/ant-deps-nichoj

I also noticed by removing LOCALCLASSPATH from /usr/bin/ant that the following
packages have missing xerces dependency:
dev-java/xmldb
dev-java/aspectj

I will be updating this bug as I find new packages with missing dependencies or
fix packages to depend only on dev-java/ant-core.

Created an attachment (id=71337) [details]
patch for java-devel.xml

Here is a proposed patch against
http://gentooexperimental.org/svn/java/axxo-overlay/README/docs/java-devel.xml
to improve the documentation.

I fixed dev-java/xmldb and dev-java/aspectj is bogus. It is dev-java/adaptx
that
failed.

commons-httpclient-3.0_rc4 fixed

Last night nichoj fixed dev-java/saxpath and earlier dev-java/commons-dbcp

We have to be careful about ant dependencies... I just fixed xdoclet, where it
only had ant-core, but needed ant-tasks for normal compilation.

(In reply to comment #5)
> We have to be careful about ant dependencies... I just fixed xdoclet, where it
> only had ant-core, but needed ant-tasks for normal compilation.

That is why I always turn off LOCALCLASSPATH in /usr/bin/ant and start with no
packages installed before changing to just ant-core.

Fixed dev-java/picocontainer

Is there an easy way to check that a package only needs dev-java/ant-core
without removing everything that comes with dev-java/ant before testing?

(In reply to comment #8)
> Is there an easy way to check that a package only needs dev-java/ant-core
> without removing everything that comes with dev-java/ant before testing?
> 

Add JAVA_PKG_STRICT=1 to make.conf

Well JAVA_PKG_STRICT=1 makes sure there are not unsatisfied deps. One way to do
it is to remove the ant-tasks package and it to package.provided. This should
make packages that need full ant fail.  

(In reply to comment #8)
> Is there an easy way to check that a package only needs dev-java/ant-core
> without removing everything that comes with dev-java/ant before testing?
> 

It will be possible with the split-ant packaging I'm working on.
JAVA_PKG_STRICT=1 will disable optional tasks if there's only ant-core in
DEPEND. And you will be able to override it with envvar to test without
modifying the ebuild.

dev-java/lucene modified

This bug was solved ages ago, any new cases of this would be exceptional and
need not be meta-tracked.