On May 30, 2012, at 12:31 AM, Romain Manni-Bucau wrote:

> new links:
> https://repository.apache.org/content/repositories/orgapacheopenejb-155/
> http://people.apache.org/~rmannibucau/orgapacheopenejb-155/archives.html

I think we got it!  Let's put that up for a vote!

Great work, Romain!


-David

> 2012/5/30 David Blevins <[email protected]>
> 
>> 
>> On May 29, 2012, at 2:45 PM, Romain Manni-Bucau wrote:
>> 
>>> new repo:
>>> http://people.apache.org/~rmannibucau/orgapacheopenejb-154/archives.html
>>> tag: http://svn.apache.org/repos/asf/openejb/tags/javaee-api-6.0-4/
>> 
>> Zip looks great with regards to the LICENSE file.  The NOTICE file still
>> needs to have the text I mention in the previous email.
>> 
>> For javaee-api-6.0-4.jar, javaee-api-6.0-4-sources.jar,
>> javaee-api-6.0-4-tomcat.jar and javaee-api-6.0-4-tomcat-sources.jar well
>> want to filter out the extra LICENSE and NOTICE files so that there is just
>> one of each.  Only the ones immediately in META-INF/ should be there, the
>> others shouldn't be in the jar.
>> 
>> 
>> -David
>> 
>>> 2012/5/29 David Blevins <[email protected]>
>>> 
>>>> 
>>>> On May 29, 2012, at 11:05 AM, David Blevins wrote:
>>>> 
>>>>> 
>>>>> On May 29, 2012, at 8:54 AM, Romain Manni-Bucau wrote:
>>>>> 
>>>>>> generated:
>>>>>> 
>>>> 
>> http://people.apache.org/~rmannibucau/orgapacheopenejb-147/archives.html
>>>>> 
>>>>> Excellent!  Still looking it over, but see that we need to add the WC3
>>>> license to our LICENSE file:
>>>>> 
>>>>> 
>>>> 
>> http://people.apache.org/~rmannibucau/orgapacheopenejb-147/org.apache.openejb.javaee-api.6.0-4.javaee-api-6.0-4.zip.licenses.html
>>>>> 
>>>>> The servlet API jar contains code under that license and so the zip
>> that
>>>> contains that jar must have that license.  We'll also need to make sure
>> the
>>>> all-in-one spec jar that contains the servlet api classes has that
>> license
>>>> and the "-tomcat" one does not.
>>>> 
>>>> We'll need the same consideration in our NOTICE files.  Some text like
>>>> this in the servlet API containing jars and zips:
>>>> 
>>>> This product includes software developed by
>>>> The W3C Consortium (http://www.w3.org/).
>>>> 
>>>> Copyright (c) 1994-2002 World Wide Web Consortium,
>>>> (Massachusetts Institute of Technology, Institut National
>>>> de Recherche en Informatique et en Automatique, Keio
>>>> University). All Rights Reserved.
>>>> http://www.w3.org/Consortium/Legal/
>>>> 
>>>> -David
>>>> 
>>>>> 
>>>>>> 2012/5/29 Jean-Louis MONTEIRO <[email protected]>
>>>>>> 
>>>>>>> Hey,
>>>>>>> 
>>>>>>> Gonna have a look with Romain.
>>>>>>> Would be great if more people can perform a release.
>>>>>>> 
>>>>>>> Jean-Louis
>>>>>>> 
>>>>>>> 2012/5/29 David Blevins <[email protected]>
>>>>>>> 
>>>>>>>> 
>>>>>>>> On May 28, 2012, at 5:46 PM, David Blevins wrote:
>>>>>>>> 
>>>>>>>>> 
>>>>>>>>> On May 28, 2012, at 5:36 PM, Romain Manni-Bucau wrote:
>>>>>>>>> 
>>>>>>>>>> created a staging repo
>>>>>>>>>> 
>>>>>>>> 
>>>> 
>> https://repository.apache.org/content/repositories/orgapacheopenejb-147/
>>>>>>>>> 
>>>>>>>>> Excellent!  We're making great progress!
>>>>>>>>> 
>>>>>>>>> Now we need to get the LICENSE and NOTICE files updated.  Looks
>> like
>>>>>>>> there are some entries we missed.
>>>>>>>>> 
>>>>>>>>> Next step would be to run a Tentacles report and see what we can
>>>> find.
>>>>>>>>> 
>>>>>>>>> I'll upload some snapshots of that tool so you can download it and
>>>> use
>>>>>>>> it.
>>>>>>>> 
>>>>>>>> Uploaded the tool here:
>>>>>>>> 
>>>>>>> 
>>>> 
>> http://people.apache.org/~dblevins/apache-creadur-tentacles-0.1-SNAPSHOT.jar
>>>>>>>> 
>>>>>>>> You'll want to log into your people.a.o account, go to public_html/
>>>> then
>>>>>>>> run this command:
>>>>>>>> 
>>>>>>>> java -ea -jar apache-creadur-tentacles-0.1-SNAPSHOT.jar
>>>>>>>> 
>>>> https://repository.apache.org/content/repositories/orgapacheopenejb-147
>>>>>>>> 
>>>>>>>> That will generate the legal report and we can see what LICENSE and
>>>>>>> NOTICE
>>>>>>>> files might be missing from the zips.
>>>>>>>> 
>>>>>>>> 
>>>>>>>> -David
>>>>>>>> 
>>>>>>>> 
>>>>>>> 
>>>>> 
>>>> 
>>>> 
>> 
>> 

Reply via email to