« Java Plugin and Java Web Start for x86_64 usersApplications failing with Turkish locale »

java-dep-check-0.3 and weird bugs it discovered

01/30/09

Permalink 08:32:47 pm, by Serkan KABA Email , 359 words   English (US) latin1
Categories: Gentoo, Java

java-dep-check-0.3 and weird bugs it discovered

The tool Betelgeuse wrote was scanning Java packages for unneeded dependencies. It was scanning the registered jar's for any referenced classes and generated a list of classes in dependent packages/jars to see if any of them are redundant. Back on December I came up with an idea to use that information to dig out for an opposite fact. Packages that reference classes which are not provided by it's dependencies not itself. It was bug #252249 which inspired me. The initial ebuild was definitely missing a dev-java/sun-jai-bin .dependency which I wanted to verify. The intention was to discover missing dependencies. of binary Java packages.

After I got it working without (hopefully) false positives it was then time to see the results. I first ran it in over the packages installed on my system. Thanks to Diego who kindly ran it in his tinderbox which had most of the Java packages in portage installed and posted the output. I was surprised about the outcome. There were many source based packages that it reported to depend on missing classes. Roughly examining the list I saw that some packages installing ant tasks were missing an ant core dependency and fixed a few. Another set of packages seem to package its unit tests (see java-wakeonlan for example) Digging out others I figured out a third kind of problem. Packages missing already generated jars or classes in the final package.env entry. Those (openoffice,xulrunner,java-access-bridge) reported missing classes that was already provided by themselves. They either didn't install the jar at all or installed but not registered them (we have java-pkg_regjar provided by java-utils-2 eclass which registers an already installed jar). But java-access-bridge had an interesting bug which was there for ages. The generated jar misses already compiled classes due to wildcards not being expanded recursively during make and reported the bug to upstream. Mindterm exibits a similar bug. Classes were missed out in jars because they weren't in the hardcoded list of classes to package.

As a final word, I'll be taking next days investigating output generated in Diego's tinderbox, and fixing the packages.

Addition: Add note about net-misc/mindterm bug.

1 comment

Comment from: nfl jerseys [Visitor] · http://dearjerseys.com
thumps up for your article, great post...
09/10/10 @ 05:03

Leave a comment


Your email address will not be revealed on this site.

Your URL will be displayed.
(Line breaks become <br />)
(Name, email & website)
(Allow users to contact you through a message form (your email will not be revealed.)
September 2010
Sun Mon Tue Wed Thu Fri Sat
 << <   > >>
      1 2 3 4
5 6 7 8 9 10 11
12 13 14 15 16 17 18
19 20 21 22 23 24 25
26 27 28 29 30    

Search

XML Feeds

powered by b2evolution free blog software