Created attachment 488370 [details] build.log using python-3.4 The lastest version dev-java/javatoolkit-0.5.0 breaks ant-core during rewriting of the build.xml file. It is broken with both python-2.7 and python-3.4 due to changes in the xml-rewrite-2.py file.
Created attachment 488372 [details] emerge --info
Created attachment 488374 [details] build.log using python-2.7
At this time all versions > javatoolkit-0.3.0-r9 are broken, including 0.4.0 and 0.5.0. They need to be masked till fixed. Please revert back to javatoolkit-0.3.0-r9 in the mean time to bypass this issue. The only changes to javatoolkit are updating for newer python. Thus javatoolkit-0.3.0-r9 is fine to use till the newer stuff is working.
is it possible to mask them in profile? It make no sense that everyone start a debug session, then came on bugzilla to see it's a known bug.
tomcat is affected aswell.
commit 2cf57b9a15326906f6d79dcaa56c1a4cb5965db5 (HEAD -> master, origin/master, origin/HEAD) Author: Patrice Clement <monsieurp@gentoo.org> AuthorDate: Thu Aug 10 11:45:51 2017 +0200 Commit: Patrice Clement <monsieurp@gentoo.org> CommitDate: Thu Aug 10 11:46:54 2017 +0200 profiles/package.mask: mask dev-java/toolkit-0.{4,5}.0. profiles/package.mask | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) I have masked both versions for the time being. @Manuel: sorry.
Are there any updates on this?
javatoolkit versions >=0.6.1 are also broken for me.
there's nobody maintaining javatoolkit afaik so it's "a bit" problem... unless somebody steps up and takes care of it, it would be best to get rid of all of the build.xml rewrite and go the kava-pkg-simple.eclass way... these days most of the packages use maven pom.xml anyway so it makes more sense than few years back... anyway, that's a lot of work too to migrate packages to java-pkg-simple.eclass... you can mask >dev-java/javatoolkit-0.3.0-r9 locally to avoid the issue.
