xml-commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Aleksander Slominski <as...@cs.indiana.edu>
Subject Re: [PROPOSAL]: Upgrade XML Commons External to JAXP 1.4
Date Sat, 01 Apr 2006 00:07:42 GMT
Radu Preotiuc-Pietro wrote:
> Could you point me specifically to the file you are talking about? The
> one I found by going to stax.codehaus.org and doing "SVN browse" doesn't
> seem to have the Apache License included.
>   

http://svn.stax.codehaus.org/trunk/dev/
see README-API.txt <http://svn.stax.codehaus.org/trunk/dev/README-API.txt>
and jsr173_1.0_src.jar
<http://svn.stax.codehaus.org/trunk/dev/jsr173_1.0_src.jar>

best,

alek
> -----Original Message-----
> From: Aleksander Slominski [mailto:aslom@cs.indiana.edu] 
> Sent: Friday, March 31, 2006 3:44 PM
> To: Radu Preotiuc-Pietro
> Cc: dev@xmlbeans.apache.org; Michael Glavassevich;
> commons-dev@xml.apache.org
> Subject: Re: [PROPOSAL]: Upgrade XML Commons External to JAXP 1.4
>
> Radu Preotiuc-Pietro wrote:
>   
>> Do you need to check them into your svn repository or a Maven 
>> dependency, say, would be better? I would think in the later case, you
>>     
>
>   
>> would just be using it the same way we do, which would be ok. But 
>> let's find out, if we can do it quickly, if the current format is 
>> legal-wise safe for your intended use.
>>   
>>     
> few months ago on request of Ron Benson (see below; it seems though he
> no longer works in BEA?) i have put the jar file (jsr173_1.0_src.jar)
> into StAX RI SVN repository at codehaus.
>
> is it official enough for Apache XML purposes?
>
> thanks,
>
> alek
>
>
> -------- Original Message --------
> Subject: 	API and RI bundles
> Date: 	Mon, 28 Nov 2005 17:25:23 -0800
> From: 	Ron Benson <rbenson@bea.com>
> To: 	Chris Fry <chris_l_fry@yahoo.com>, Aleksander Slominski
> <aslom@cs.indiana.edu>
> CC: 	Peter Dapkus <pdapkus@bea.com>, Jim Barnett <jimb@bea.com>
>
>
>
> Hi Chris and Alek,
> Here are the updated bundles including the new ASF 2.0 licensing.
>
> Would you mind posting the included bundles to codehaus as I'm having
> problems getting access to the site? Please send any comments to me if
> you would like anything in the bundles to change.
>
> Then feel free to open access to the site.
>
> Thanks,
> Ron
>
>
>
>
>   
>> -----Original Message-----
>> From: Michael Glavassevich [mailto:mrglavas@ca.ibm.com]
>> Sent: Friday, March 31, 2006 12:10 PM
>> To: commons-dev@xml.apache.org
>> Cc: dev@xmlbeans.apache.org
>> Subject: RE: [PROPOSAL]: Upgrade XML Commons External to JAXP 1.4
>>
>> Hi Radu,
>>
>> That is reassuring though I wonder if the source files in their 
>> current form can be included in an ASF project. As Jeremias mentioned,
>>     
>
>   
>> none of the source files have a license header on them.
>>
>> Thanks.
>>
>> Michael Glavassevich
>> XML Parser Development
>> IBM Toronto Lab
>> E-mail: mrglavas@ca.ibm.com
>> E-mail: mrglavas@apache.org
>>
>> "Radu Preotiuc-Pietro" <radup@bea.com> wrote on 03/30/2006 04:43:32
>>     
> PM:
>   
>>   
>>     
>>> Here's some info on this.
>>>
>>> The XmlBeans team (esp Lawrence, with his Apache hat on ;-) ) have 
>>> worked with BEA (represented by the BEA legal team) to clarify the 
>>> licensing status of jsr173 APIs. The jar that we have made available 
>>> at 
>>> http://www.apache.org/dist/java-repository/xmlbeans/jars/jsr173_1.0_a
>>> p i_ bundle.jar is totally legit, as provided by BEA, licensed under 
>>> the
>>>     
>>>       
>>   
>>     
>>> Apache License 2.0 and with no modifications on our part. It is NOT 
>>> something that we just downloaded, changed a few things and commited.
>>> It's also been oked by Cliff (with his legal affairs hat on), see 
>>> this
>>>     
>>>       
>>   
>>     
>>> thread for details:
>>> http://mail-archives.apache.org/mod_mbox/xmlbeans-dev/200510.mbox/%3c
>>> 1
>>> 13 0357486.13564.0.camel@knossos.elmet%3e
>>>
>>> There are two points that are worth mentioning:
>>> 1. Is this .jar available from anywhere else other than the Apache 
>>> address above? Answer: not that I know of; BEA has said that they are
>>>       
>
>   
>>> interested in making it available for download in a more "public"
>>> place, but this has not happened yet, I guess it's just a lack of 
>>> leadership on their part, but we'll keep pinging them 2. Why is 
>>> another .jar still available at dev.java.net with the same classes in
>>>       
>
>   
>>> it and different license? Answer: because of BEA's agreement with Sun
>>>       
>
>   
>>> on the JCP, they can't modify what's already there AFAIK. Cliff 
>>> probably knows exactly what are the rules regarding code that 
>>> companies decided to make available under Apache license which was 
>>> previously licensed under different terms.
>>>
>>> So obviously each project has to decide for itself what to use and 
>>> what not to use, but for XmlBeans we have taken the steps to ensure 
>>> that what we use is completely within the legal constraints of the
>>>     
>>>       
>> ASF.
>>   
>>     
>>> Hope this helps,
>>> Radu
>>>
>>> -----Original Message-----
>>> From: Michael Glavassevich [mailto:mrglavas@ca.ibm.com]
>>> Sent: Wednesday, March 29, 2006 10:30 AM
>>> To: commons-dev@xml.apache.org
>>> Cc: dev@xmlbeans.apache.org
>>> Subject: Re: [PROPOSAL]: Upgrade XML Commons External to JAXP 1.4
>>>
>>> Jeremias Maerki <dev@jeremias-maerki.ch> wrote on 03/29/2006 02:08:32
>>> AM:
>>>
>>>     
>>>       
>>>> (cc'ing dev@xmlbeans.apache.org)
>>>>
>>>> That's ok with me. The only thing bothering me is the XMLBeans' JAR 
>>>> file with the API sources. It does not contain any indication 
>>>> whether this is a clean-room reconstruction of the API sources based
>>>>       
>>>>         
>>   
>>     
>>>> on the specification or if they have been taken from the java.net 
>>>> site and modified. The files there seem to be distributed under the 
>>>> CDDL [1] which is a Category B license (binary only). The sources at
>>>>       
>>>>         
>>   
>>     
>>>> java.net [2] have Bea copyrights all over the place. Furthermore, I 
>>>> can't find the StAX API sources anywhere in XMLBeans' repository.
>>>> The individual files in the API JAR do not contain the Apache 
>>>> license header as would
>>>>       
>>>> be required by any source file published by the ASF (due to the 
>>>> current policy). The good thing on the other side is that Bea seems 
>>>> to
>>>>       
>>>> be the driving force behind XMLBeans and could officially donate the
>>>>       
>>>>         
>>   
>>     
>>>> API sources to the ASF for inclusion into XML Commons Externals. And
>>>>       
>>>>         
>>   
>>     
>>>> Cliff is XMLBeans' PMC chair. :-) So, before the API sources can be 
>>>> included in XML Commons Externals a clarification will be necessary
>>>>       
>>>>         
>>> IMO.
>>>
>>> I agree.
>>>
>>>     
>>>       
>>>> [1] https://jaxp-sources.dev.java.net/source/browse/jaxp-
>>>> sources/jaxp-api/src/javax/xml/license.txt?rev=1.
>>>> 1&view=auto&content-type=text/vnd.viewcvs-markup
>>>> [2] https://jaxp-sources.dev.java.net/source/browse/jaxp-
>>>> sources/jaxp-api/src/javax/xml/stream/StreamFilter.java?rev=1.
>>>> 1&view=auto&content-type=text/vnd.viewcvs-markup
>>>>
>>>> On 29.03.2006 00:45:11 Michael Glavassevich wrote:
>>>>       
>>>>         
>>>>> Hi everyone,
>>>>>
>>>>> The Xerces developers (myself included) have started planning for a
>>>>>           
>
>   
>>>>> Xerces-J release which will add support for JAXP 1.4 [1][2].
>>>>> JAXP
>>>>> 1.4
>>>>>         
>>>>>           
>>> is a
>>>     
>>>       
>>>>> minor update to JAXP 1.3; the largest technical change being the
>>>>>         
>>>>>           
>>> addition
>>>     
>>>       
>>>>> of StAX (JSR 173) [3] and new Source/Result classes (see the 
>>>>> javax.xml.transform.stax package) which can be used with 
>>>>> transformers
>>>>>         
>>>>>           
>>> and
>>>     
>>>       
>>>>> validators. I believe Apache Harmony will eventually require JAXP
>>>>> 1.4
>>>>>         
>>>>>           
>>> to
>>>     
>>>       
>>>>> complete an implementation of Java SE 6.0. Other Apache projects
>>>>>         
>>>>>           
>>> (Axis2,
>>>     
>>>       
>>>>> XMLBeans, etc...) are already using StAX.
>>>>>
>>>>> With the JAXP 1.4 specification nearing finalization I propose that
>>>>>         
>>>>>           
>>> the
>>>     
>>>       
>>>>> main trunk of XML Commons External be upgraded to JAXP 1.4 and a
>>>>>         
>>>>>           
>>> branch be
>>>     
>>>       
>>>>> created for maintenance of JAXP 1.3 (which is what is currently on
>>>>>         
>>>>>           
>>   
>>     
>>>>> the
>>>>>         
>>>>> main trunk).
>>>>>
>>>>> I noticed that a copy of the StAX API source is being distributed 
>>>>> with
>>>>>         
>>>>> XMLBeans here [4] (see jsr173_1.0_api_bundle.jar) and on Apache 
>>>>> mirror
>>>>>         
>>>>> sites. The source files contain Javadoc so it would be great if we
>>>>>         
>>>>>           
>>> could
>>>     
>>>       
>>>>> use them. The README contained in the jar states that the source 
>>>>> and
>>>>>         
>>>>> binary files are distributed under the Apache License 2.0, so it 
>>>>> would
>>>>>         
>>>>> appear to me that the source can be included [5] in XML Commons
>>>>>         
>>>>>           
>>> External. 
>>>     
>>>       
>>>>> What do folks think?
>>>>>
>>>>> Thanks.
>>>>>
>>>>> [1] https://jaxp-sources.dev.java.net/nonav/docs/spec/html/
>>>>> [2] https://jaxp-sources.dev.java.net/nonav/docs/api/
>>>>> [3] http://jcp.org/en/jsr/detail?id=173
>>>>> [4] http://www.apache.org/dist/java-repository/xmlbeans/jars/
>>>>> [5] http://people.apache.org/~cliffs/3party.html#category-a
>>>>>
>>>>> Michael Glavassevich
>>>>> XML Parser Development
>>>>> IBM Toronto Lab
>>>>> E-mail: mrglavas@ca.ibm.com
>>>>> E-mail: mrglavas@apache.org
>>>>>         
>>>>>           
>>>> Jeremias Maerki
>>>>       
>>>>         
>>> Michael Glavassevich
>>> XML Parser Development
>>> IBM Toronto Lab
>>> E-mail: mrglavas@ca.ibm.com
>>> E-mail: mrglavas@apache.org
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@xmlbeans.apache.org
>>> For additional commands, e-mail: dev-help@xmlbeans.apache.org
>>>
>>> _____________________________________________________________________
>>> _
>>> _
>>> Notice:  This email message, together with any attachments, may 
>>> contain information  of  BEA Systems,  Inc.,  its subsidiaries  and 
>>> affiliated entities,  that may be confidential,  proprietary, 
>>> copyrighted  and/or legally privileged, and is intended solely for 
>>> the
>>>     
>>>       
>>   
>>     
>>> use of the individual or entity named in this message. If you are not
>>>       
>
>   
>>> the intended recipient, and have received this message in error, 
>>> please immediately return this by email and then delete it.
>>>     
>>>       
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@xmlbeans.apache.org
>> For additional commands, e-mail: dev-help@xmlbeans.apache.org
>>
>> ______________________________________________________________________
>> _
>> Notice:  This email message, together with any attachments, may 
>> contain information  of  BEA Systems,  Inc.,  its subsidiaries  and  
>> affiliated entities,  that may be confidential,  proprietary,  
>> copyrighted  and/or legally privileged, and is intended solely for the
>>     
>
>   
>> use of the individual or entity named in this message. If you are not 
>> the intended recipient, and have received this message in error, 
>> please immediately return this by email and then delete it.
>>
>>   
>>     
>
>
> --
> The best way to predict the future is to invent it - Alan Kay
>
> _______________________________________________________________________
> Notice:  This email message, together with any attachments, may contain
> information  of  BEA Systems,  Inc.,  its subsidiaries  and  affiliated
> entities,  that may be confidential,  proprietary,  copyrighted  and/or
> legally privileged, and is intended solely for the use of the individual
> or entity named in this message. If you are not the intended recipient,
> and have received this message in error, please immediately return this
> by email and then delete it.
>
>   


-- 
The best way to predict the future is to invent it - Alan Kay


Mime
View raw message