I would like some clarification on jar file porting for
future arc cases.

findbugs plans to integrate the following project private
jar files.

163 f none usr/share/lib/java/findbugs/asm-analysis-3.1.jar
164 f none usr/share/lib/java/findbugs/asm-xml-3.1.jar
165 f none usr/share/lib/java/findbugs/asm-util-3.1.jar
169 f none usr/share/lib/java/findbugs/asm-tree-3.1.jar
170 f none usr/share/lib/java/findbugs/dom4j-1.6.1.jar
173 f none usr/share/lib/java/findbugs/asm-3.1.jar
174 f none usr/share/lib/java/findbugs/jaxen-1.1.1.jar
175 f none usr/share/lib/java/findbugs/asm-commons-3.1.jar
176 f none usr/share/lib/java/findbugs/bcel.jar

Which reduce down to these open source projects.
BTW. the versions seem to be current.

asm-*-3.1.jar   http://asm.objectweb.org/       (asm-3.1)
dom4j-1.6.1.jar http://www.dom4j.org/           (dom4j-1.6.1)
jaxen-1.1.1.jar http://jaxen.codehaus.org/      (jaxen-1.1.1)
bcel.jar        http://jakarta.apache.org/bcel/ (bcel-5.2?)

 From an arc perspective, wouldn't it be better to integrate
these jar files here, since they are all something other
applications can use (ie. they are not modified for findbugs).

/usr/share/lib/java/

BTW. all of these have multiple (6+) OSRs for delivery to multiple
products. It would be nice if we had just one copy of each like
was done for junit.

Cheers,
Jim

p.s. The SFW c-team requires that jar files be built from
source, which is also an issue for integration, but that's
not arc related.

Reply via email to