Hi Margot, Thanks, I will add both in the interface list in the future.
~VRT -----Original Message----- From: Margot Miller [mailto:margot.mil...@sun.com] Sent: Tuesday, February 24, 2009 11:06 PM To: Vivek Titarmare Cc: 'Richard Jr Matthews'; LSARC-ext at sun.com; Drools_team at sun.com Subject: Re: JDOM [LSARC/2009/127 FastTrack timeout 03/03/2009] Hey Vikek, I would do that. In the future, you might have such one interface table and all the materials point to that. That way if you have to update it, you only update it once. The jar file is an interface and should go in the interface table. Also, the SVR4 package is an interface and goes in the table. Ex.: --------------- -------------- ----------------------- SUNWlibproxy Uncommitted Package name of base library SUNWlibproxy-devel Uncommitted Package name of library for development /usr/lib/libproxy.so.0 Volatile C library /usr/lib/amd64/libproxy.so.0 Volatile 64-bit library Thanks Margot Vivek Titarmare wrote: > Hi Margot, > > The FOSS check list has the name of the jar file. Do I need to add the same > in the fast-track also. Let me know. > > Thanks, > ~Vivek R. T. > > -----Original Message----- > From: Margot Miller [mailto:Margot.Miller at Sun.COM] > Sent: Monday, February 23, 2009 11:41 PM > To: Richard Jr Matthews > Cc: LSARC-ext at sun.com; Drools_team at sun.com > Subject: Re: JDOM [LSARC/2009/127 FastTrack timeout 03/03/2009] > > What is the name of the jar file? Is this jar file in its own > SVR4 package? And, java docs are delivered with this? > > Thanks > Margot > > > Richard Jr Matthews wrote: > >> I am sponsoring this fast-track for Vivek Titarmare. The >> timeout is set at March 3. The case directory contains the supplied >> materials. >> >> This fast-track is a portion of the Drools case LSARC 2008/748, which >> is a dependency of ADM - PSARC 2007/210. >> >> Template Version: @(#)sac_nextcase %I% %G% SMI This information is >> > Copyright 2009 Sun Microsystems 1. Introduction > >> 1.1. Project/Component Working Name: >> JDOM >> 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 >> >> JDOM is an open source, tree-based, pure Java API for parsing, >> > creating, manipulating, and serializing XML documents > >> 4. Technical Description: >> >> JDOM is an open source, tree-based, pure Java API for parsing, >> > creating, manipulating, and serializing XML documents > >> 5. Interfaces >> >> Exported interface Classification >> > Interface type > >> ============================= ============== >> > ============== > >> org.jdom >> * JDOMFactory Uncommitted Interface >> * Parent Uncommitted Interface >> >> org.jdom.adapters >> * DOMAdapter Uncommitted Interface >> >> org.jdom.filter >> * Filter Uncommitted Interface >> >> org.jdom.output >> * EscapeStrategyr Uncommitted Interface >> >> >> The Jar file would go in "usr/share/lib/java" >> >> Imported interface Classification Comments >> ======================= ============== >> > =================================== > >> >> Interfaces are imported from "jaxen-core_1.1.1.jar" >> >> 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 >> >> >> > > >
