Summary: | dev-java/javahelp-bin uses packed jars | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Thomas Matthijs (RETIRED) <axxo> |
Component: | New packages | Assignee: | Java team <java> |
Status: | RESOLVED FIXED | ||
Severity: | enhancement | CC: | eddymul |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | All | ||
URL: | https://javahelp.dev.java.net/ | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | 168991, 176971 | ||
Bug Blocks: | 69972, 63304 |
Description
Thomas Matthijs (RETIRED)
![]() I'm trying to make an ebuild for javahelp-2.0.02. I'm having trouble compiling from source. Some source files are missing (not included?) in javahelp-2_0_02.zip/jh2.0/src.jar. I looked at an older version's javahelp-1.1.3.zip/jh1.1.3/src.jar, but they're not there either. Apparently, the classes are present in bytecode in javahelp-2_0_02.zip/jh2.0/javahelp/lib/jhall.jar. Some of the offending classes are in package com.sun.java.help.impl: XmlReader, ParserListener, Parser, ParserEvent, Tag, TagProperties, LangElement. Any suggestions on where I should go with the ebuild? (methinks that I can extract jhall.jar, and use the offending binary-only classes, but that would defeat the whole "anti-trojan" thing as mentioned in http://gentoo-wiki.com/Why_Build_Java_Code_From_Source). Is this an upstream bug? I haven't looked at the specifics, but anything that relies on com.sun.* which is not Sun's own stuff should be eyed with some suspicion. It may be worthwhile to report this as a bug upstream, but I fear you wont get much sympathy. Now it should be possible. javahelp-bin is package.masked and going away. |