The jboss-cache-1.3.0.3 from the migrated-java-experimental-overlay fails because it uses or overrides deprecated API see attatchment for emerge output
Created attachment 98863 [details] emerge output
After nichoj pointed out that there was a "no such file" error in the output, I did some testing, and came to the result that the ebuild fails due to the output folder "classes" isn't being created (and the deprecation was a warning after all). When I created the folder manually after emerge unpacked the source, the output was the following (note that the "cp resources/*" fails too since there is no "resources" folder, only "src"): >>> Unpacking source... >>> Unpacking jboss-cache-srcOnly-1.3.0.SP3.zip to /var/tmp/portage/jboss-cache-1.3.0.3/work >>> Source unpacked. >>> Compiling source in /var/tmp/portage/jboss-cache-1.3.0.3/work/JBossCache-1.3.0.SP3 ... Note: Some input files use or override a deprecated API. Note: Recompile with -Xlint:deprecation for details. cp: cannot stat `resources/*': No such file or directory >>> Source compiled. >>> Test phase [not enabled]: dev-java/jboss-cache-1.3.0.3 >>> Install jboss-cache-1.3.0.3 into /var/tmp/portage/jboss-cache-1.3.0.3/image/ category dev-java >>> Completed installing jboss-cache-1.3.0.3 into /var/tmp/portage/jboss-cache-1.3.0.3/image/
Fixed in 1.3.0.3-r1. Thanks for reporting.
