According to gentoo guidelines, 30 days have to pass for an ebuild to become stable. The ebuild for dev-java/xml-commons-resolver-1.2 has been in the trunk since nov 23 2006 I've been using this app for some time with no problems at all. Thus, I'm requesting the stabilization.. Thanks! Reproducible: Always
00:11 <Betelgeuse> !rdep xml-commons-resolver 00:11 <jeeves> dev-java/xml-commons-resolver <- dev-java/ant-apache-resolver dev-java/jax-ws dev-java/jax-ws-tools dev-java/jaxb dev-java/jaxb-tools dev-java/msv dev-java/xerces Fine by me as long as reverse deps still emerge (testing for arch teams)
amd64 done
ia64 stable
* Using all available ANT_TASKS !!! ERROR: Dependency package xml-commons-resolver was not found! !!! ERROR: Dependency package xml-commons-resolver was not found! Buildfile: resolver.xml
(In reply to comment #4) > * Using all available ANT_TASKS > !!! ERROR: Dependency package xml-commons-resolver was not found! > !!! ERROR: Dependency package xml-commons-resolver was not found! > Buildfile: resolver.xml Looks like you unmerged the old xml-commons-resolver version but left ant-apache-resolver (which depends on it) around.
(In reply to comment #5) > (In reply to comment #4) > > * Using all available ANT_TASKS > > !!! ERROR: Dependency package xml-commons-resolver was not found! > > !!! ERROR: Dependency package xml-commons-resolver was not found! > > Buildfile: resolver.xml > > Looks like you unmerged the old xml-commons-resolver version but left > ant-apache-resolver (which depends on it) around. I unmerge ant-apache-resolver and the message is still there for xml-commons-resolver.
(In reply to comment #6) > I unmerge ant-apache-resolver and the message is still there for > xml-commons-resolver. xerces pulls it, and xerces is used by xalan which is used by ant-trax, and there might be other traces too :). So you would have to start from scratch if you want to test it doesn't need itself to compile :) It needs just ant-core to compile, but we let ant use all tasks unless you have JAVA_PKG_STRICT set... which won't be default until somebody tests everything stable to build with it... Anyway I think it continues even after the errors? And if it doesn't fail, it means it really doesn't need itself, the code depending on it is never called.
I think I stop stabling Java...you guys just confuse me. :) x86 stable
ppc64 stable
ppc stable. Closing since we are the last arch.