antlr runtime [LSARC/2009/075 FastTrack timeout 02/18/2009]]

[Mark Martin]

Vivek Titarmare wrote:
> Hi John,
>
> All the Exported Interfaces listed are in the package JAR file which would
> be compiled with sfw. Do I need to add a jar file with every fasttrack?
> Pl. let me know.
>
>   

The idea here is that we're delivering these common projects (jars) for 
public consumption, instead of just lumping (possibly) duplicated copies 
them into project private and moving on.   I would expect to see at 
least 1 jar file for each of these fast tracks that collectively 
constitute "Drools", the aggregate project.

I'll raise my concern to other reviewers one final time, or otherwise 
move on from it.  I'm concerned about the naming conventions for these 
jars.  I presume  there is a big rule (rather than a best practice) 
about standard library naming conventions.  Version taxonomy and all 
that.  Are the rules relaxed for these jars?  I know that 
conventionally, in the upstream FOSS community from whence these jars 
are coming, jar naming is a simplified mixed bag.  Sadly, I doubt that 
the metadata (i.e. the manifest) is used or reliable, and if so, I 
suspect only translates to SONAME in machine native libraries if it were 
even of any value.   I'm imagining a burgeoning population of 
/usr/share/lib/java in the times to come, particularly as efforts to 
ramp up FOSS integration continue.

To my mind, the jars should be named, even if different than 
as-distributed from upstream, according to version major/minor rules -- 
similar to "regular" libraries.  I'm also wondering if the manifest 
constitutes an "interface".

I'll defer the question about whether they should be built from scratch 
from source to Jim Walker or others as I'm not sure that is an 
architectural issue.  The notion that these jars could/should be signed 
may also be worth pondering, but that's also really more of a 
distribution issue (signed by whom?).

> Thanks,
> ~Vivek R. Titarmare
>
> -----Original Message-----
> From: John.Fischer at Sun.COM [mailto:John.Fischer at Sun.COM] 
> Sent: Tuesday, February 10, 2009 1:12 AM
> To: Rick Matthews
> Cc: LSARC-ext at sun.com; drools_team at sun.com
> Subject: Re: antlr runtime [LSARC/2009/075 FastTrack timeout 02/18/2009]]
>
> Vivek,
>
> The FOSS check list states that there are libraries being delivered
> with this project.  However, the libraries are not included in the
> Exported Interface tables.  Is this information incorrect in the
> FOSS check list or is there missing information within the interface
> table?
>
> Thanks,
>
> John
>
>
> Rick Matthews wrote:
>   
>> I am sponsoring the attached fast-track for Vivek Titarmare. The
>> timeout is set at Feb 18. The case directory contains the supplied
>> materials, which I am attaching in a zip file for reference.
>>
>> This fast-track is a portion of the Drools case LSARC 2008/748, which
>> is a dependency of ADM - PSARC 2007/210.
>>
>>
>> ------------------------------------------------------------------------
>>
>> Subject:
>> antlr runtime [LSARC/2009/075 FastTrack timeout 02/18/2009]
>> From:
>> Richard Jr Matthews <rm129958 at sac.sfbay.sun.com>
>> Date:
>> Mon, 09 Feb 2009 11:03:20 -0800 (PST)
>> To:
>> LSARC-ext at Sun.COM
>>
>> To:
>> LSARC-ext at Sun.COM
>> CC:
>> drools_team.sun.com at sac.sfbay.sun.com
>>
>>
>> Template Version: @(#)sac_nextcase %I% %G% SMI
>> This information is Copyright 2009 Sun Microsystems
>> 1. Introduction
>>     1.1. Project/Component Working Name:
>> 	 antlr runtime
>>     1.2. Name of Document Author/Supplier:
>> 	 Author:  Vivek Titarmare
>>     1.3  Date of This Document:
>> 	09 February, 2009
>> 4. Technical Description
>> Template Version: @(#)sac_nextcase %I% %G% SMI This information is
>>     
> Copyright 2009 Sun Microsystems 1. Introduction
>   
>>     1.1. Project/Component Working Name:
>> 	 antlr-runtime
>>     1.2. Name of Document Author/Supplier:
>> 	 Author:  Vivek R. Titarmare
>>     1.3  Date of This Document:
>> 	 22 January, 2009
>>
>> 2. Project Summary
>>    2.1 Project Description
>>
>> 	ANTLR, (AN)other (T)ool for (L)anguage (R)ecognition - formerly
>>     
> known as PCCTS - is a language tool that provides a framework
> forconstructing recognizers, compilers, and translators from grammatical
> descriptions containing actions in the following languages: Java, C++, C# or
> Python
>   
>> 4. Technical Description:
>>
>> 	ANTLR, (AN)other (T)ool for (L)anguage (R)ecognition - formerly
>>     
> known as PCCTS - is a language tool that provides a framework
> forconstructing recognizers, compilers, and translators from grammatical
> descriptions containing actions in the following languages: Java, C++, C# or
> Python
>   
>> 5. Interfaces 
>>
>>    Exported interface                   Classification
>>     
> Interface type
>   
>>    =============================        ==============
>>     
> ==============
>   
>>    org.antlr.runtime
>> 	* CharStream			Uncommitted    		Interface
>> 	* IntStream			Uncommitted    		Interface
>> 	* Token				Uncommitted    		Interface
>> 	* TokenSource			Uncommitted    		Interface
>> 	* TokenStream			Uncommitted    		Interface
>>
>>    org.antlr.runtime.debug
>> 	* DebugEventListener		Uncommitted    		Interface
>>
>>    org.antlr.runtime.tree 
>> 	* Tree				Uncommitted    		Interface
>> 	* TreeAdaptor			Uncommitted    		Interface
>> 	* TreeNodeStream		Uncommitted    		Interface
>> 	
>>
>>    The Jar file would go in "usr/share/lib/java"
>>
>>    Imported interface        Classification   Comments
>>    =======================   ==============
>>     
> =================================== 
>   
>> 	None
>>
>>
>> 6. Resources and Schedule
>>     6.4. Steering Committee requested information
>>    	6.4.1. Consolidation C-team Name:
>> 		SFW
>>     6.5. ARC review type: FastTrack
>>     6.6. ARC Exposure: open
>>
>> 6. Resources and Schedule
>>     6.4. Steering Committee requested information
>>    	6.4.1. Consolidation C-team Name:
>> 		SFW
>>     6.5. ARC review type: FastTrack
>>     6.6. ARC Exposure: open
>>     
>
> _______________________________________________
> opensolaris-arc mailing list
> opensolaris-arc at opensolaris.org
>