savannah-hackers
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Savannah-hackers] submission of japitools - savannah.nongnu.org


From: Alaska Subedi
Subject: Re: [Savannah-hackers] submission of japitools - savannah.nongnu.org
Date: Sun, 10 Oct 2004 01:22:42 -0400

Hi,

I'm evaluating the project you submitted for approval in Savannah.

address@hidden writes:
 > A package was submitted to savannah.nongnu.org
 > This mail was sent to address@hidden, address@hidden
 > 
 > 
 > Stuart Ballard <address@hidden> described the package as follows:
 > License: gpl
 > Other License: 
 > Package: japitools
 > System name: japitools
 > Type: non-GNU
 > 
 > Description:
 > japitools is a tool for comparing Java APIs for compatibility with each 
 > other. It tests for binary backward compatibility as defined by Sun, plus a 
 > few additional tests.
 > 
 > In order to compare APIs using Japitools, first a Java program called Japize 
 > must be run against both APIs to be compared. This produces output in the 
 > form of a file with the .japi.gz file extension. Secondly, a Perl program 
 > called japicompat must be run against the two japi.gz files to be compared. 
 > japicompat can produce output in text or HTML format.
 > 
 > japitools is primarily useful for people implementing a Free version of a 
 > proprietary API, such as the Java platform itself and the proprietary 
 > "standard extensions" that Sun provides.
 > 
 > The homepage, including downloadable source and binaries, can be found at 
 > http://www.kaffe.org/~stuart/japi/
 > 
 > Other Software Required:
 > Japize requires an implementation of Java but works perfectly well with at 
 > least gcj and probably most other Classpath-based VMs.
 > 
 > japicompat requires perl and gzip/gunzip, but of course that's pretty 
 > standard on most Free operating systems.
 > 
 > In order to actually test an API, a japi.gz file for the API you are 
 > comparing against is required. This must be produced by running Japize 
 > against the binary libraries implementing that API. This means that in 
 > common use, *someone* must have obtained the proprietary software, installed 
 > it, and run Japize against its libraries (note that Japize does not need to 
 > *link* against these libraries, just to read and parse the "jar" files). I 
 > provide japi.gz files for all of Sun's JDK releases up to 1.4.
 > 
 > Other Comments:
 > 


I don't think we can publish the .japi files generated from Sun's JDK
API. If you think it is leagal to publish, please tell us the reason
and you may put it.

Also, you cannot use 2000-2002 in copyright notice. Please check
http://www.gnu.org/prep/maintain/html_node/Copyright-Notices.html for
more information on this.

Please address this issue and I will approve your project for
inclusion in Savannah.

Regards,

Alaska Subedi





reply via email to

[Prev in Thread] Current Thread [Next in Thread]