You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@cxf.apache.org by Bozhong Lin <bl...@iona.com> on 2006/11/28 07:26:23 UTC

cutting a new release build (was: Re: WS-I license issues, MTOM sample from JAXWS-RI)

I will go ahead and cut another release build with all the changes. The 
release process will start in the next hour or so. Please let me know if 
you are going to commit any code during the next two hours.

Thanks,
Bo

Bozhong Lin wrote:
> With Tom's fix and my commit for fixing license header issues, what 
> should we do next? Shall we cut a new build out of mainline, or shall 
> we migrate those fixes to M1 tag and build new kit from M1 tag? I am 
> ok to cut a new build from mainline, since it includes several fixes 
> for Eclipse tooling in the last week and also includes some servlet 
> transport improvement/fixes.
>
> Any thoughts?
>
> Cheers,
> Bo
>
> Li, Tao (Tom) wrote:
>> Hi Dan.D,
>>
>> Sorry for the issues brought by mtom module.
>> I've commited a fix for mtom, now it only has systest & demo for xop, 
>> the swa case has been discarded.
>>
>> If we using import from the location set to network, the demo can 
>> also support the swa feature without involve license issues.
>>
>> But previousely we have already made efforts to let the build &
>> demo working in offline mode.
>>
>> It's better that not break the offline support. So I discard the swa
>> cases even our system support it.
>>
>> Please help to review and give your comments.
>>
>> Thanks.
>> Tom
>>
>>
>>  
>>> -----Original Message-----
>>> From: Dan Diephouse [mailto:dan@envoisolutions.com]
>>> Sent: 2006?11?23? 17:48
>>> To: cxf-dev@incubator.apache.org
>>> Subject: WS-I license issues, MTOM sample from JAXWS-RI
>>>
>>>
>>> I've removed all copies of the wsi-swa.xsd under the WS-I license 
>>> per the
>>> request from Robert on general@incubator as it is not legal for us 
>>> to have
>>> them in SVN. If anyone knows of other files please speak up. We 
>>> should go
>>> through and double check that all the files which use licenses from
>>> standards organizations are OK. Yes, this breaks the build, but 
>>> immediate
>>> action needed to be taken.
>>>
>>> ALSO, the MTOM sample and the MTOM WSDL/XSD in testutils appears to be
>>> directly copied from the JAX-WS RI. It may have ultimately 
>>> originated from
>>> somewhere else, but I can't figure out where. If this it did come 
>>> from the
>>> JAX-WS RI, it is VERY not cool. CDDL sources can not be included in 
>>> Apache
>>> SVN. If there are any other things that people have copied, speak up 
>>> now and
>>> get them removed ASAP.
>>>
>>> - Dan
>>>
>>> -- 
>>> Dan Diephouse
>>> Envoi Solutions
>>> http://envoisolutions.com | http://netzooid.com/blog
>>>
>>>

Re: cutting a new release build

Posted by Daniel Kulp <da...@iona.com>.

Jim,

I updated the javadoc stuff to change the headers/footers from:

-                   <bottom>-</bottom>
-                   <header>CXF API</header>
-                   <footer>CXF API</footer>

To:

+                    <bottom>Apache CXF is an effort undergoing incubation at 
the Apache Software Foundation(ASF) and sponsored by the Apache Incubator 
PMC.</bottom>
+                    <header>Apache CXF API</header>
+                    <footer>Apache CXF API</footer>


Is that adequate for the javadocs?   That put's the "Apache CXF API" (instead 
of just CXF API) at the top and bottom of every page.   It also puts the 
incubator disclaimer thing at the bottom of every page.   There really isn't 
a way to put it at the top without completely screwing up the formatting.


I'll leave the release notes to Bo.

Are there other files that may need changing?

Thanks!
-- 
J. Daniel Kulp
Principal Engineer
IONA
P: 781-902-8727    C: 508-380-7194
daniel.kulp@iona.com

Re: cutting a new release build

Posted by Jim Jagielski <ji...@jaguNET.com>.

Just a different directory and tar/zip name.
Just so people can tell for sure which
version they have and are testing (in case
they grabbed an earlier version).

On Dec 1, 2006, at 11:25 AM, Daniel Kulp wrote:

>
>
> On Friday 01 December 2006 08:15, Jim Jagielski wrote:
>> It might be best to have some sort of renaming
>> (like M1-v1, etc) to allow for better tracking...
>
> Would we need to rename everything (jars, etc...) or would it just  
> be OK to
> use a different directory?   Example, instead of:
>
> http://people.apache.org/~blin/
>
> use:
>
> http://people.apache.org/~blin/M1-v1
> http://people.apache.org/~blin/M1-v2
> ....
>
>
> Dan
>
>
>> On Nov 28, 2006, at 6:13 AM, Bozhong Lin wrote:
>>> DONE. It has been uploaded to the same location here [1].
>>>
>>> Cheers,
>>> Bo
>>> [1] http://people.apache.org/~blin/
>>>
>>> Bozhong Lin wrote:
>>>> I will go ahead and cut another release build with all the
>>>> changes. The release process will start in the next hour or so.
>>>> Please let me know if you are going to commit any code during the
>>>> next two hours.
>>>>
>>>> Thanks,
>>>> Bo
>
> -- 
> J. Daniel Kulp
> Principal Engineer
> IONA
> P: 781-902-8727    C: 508-380-7194
> daniel.kulp@iona.com
>

Re: cutting a new release build

Posted by Daniel Kulp <da...@iona.com>.


On Friday 01 December 2006 08:15, Jim Jagielski wrote:
> It might be best to have some sort of renaming
> (like M1-v1, etc) to allow for better tracking...

Would we need to rename everything (jars, etc...) or would it just be OK to 
use a different directory?   Example, instead of:

http://people.apache.org/~blin/

use:

http://people.apache.org/~blin/M1-v1
http://people.apache.org/~blin/M1-v2
....


Dan


> On Nov 28, 2006, at 6:13 AM, Bozhong Lin wrote:
> > DONE. It has been uploaded to the same location here [1].
> >
> > Cheers,
> > Bo
> > [1] http://people.apache.org/~blin/
> >
> > Bozhong Lin wrote:
> >> I will go ahead and cut another release build with all the
> >> changes. The release process will start in the next hour or so.
> >> Please let me know if you are going to commit any code during the
> >> next two hours.
> >>
> >> Thanks,
> >> Bo

-- 
J. Daniel Kulp
Principal Engineer
IONA
P: 781-902-8727    C: 508-380-7194
daniel.kulp@iona.com

RE: cutting a new release build

Posted by "Lin, Bozhong" <Bo...@iona.com>.

Sounds good, Jim. I will make sure we keep track of this when cutting/building another release. Do you have other feedbacks besides the release_note thing? We can fix all together.

Cheers,
Bo

-----Original Message-----
From: Jim Jagielski [mailto:jim@jaguNET.com]
Sent: Fri 12/1/2006 8:15 AM
To: cxf-dev@incubator.apache.org
Subject: Re: cutting a new release build

It might be best to have some sort of renaming
(like M1-v1, etc) to allow for better tracking...

On Nov 28, 2006, at 6:13 AM, Bozhong Lin wrote:

> DONE. It has been uploaded to the same location here [1].
>
> Cheers,
> Bo
> [1] http://people.apache.org/~blin/
>
> Bozhong Lin wrote:
>> I will go ahead and cut another release build with all the  
>> changes. The release process will start in the next hour or so.  
>> Please let me know if you are going to commit any code during the  
>> next two hours.
>>
>> Thanks,
>> Bo
>>
>>
>

Re: cutting a new release build

Posted by Jim Jagielski <ji...@jaguNET.com>.

It might be best to have some sort of renaming
(like M1-v1, etc) to allow for better tracking...

On Nov 28, 2006, at 6:13 AM, Bozhong Lin wrote:

> DONE. It has been uploaded to the same location here [1].
>
> Cheers,
> Bo
> [1] http://people.apache.org/~blin/
>
> Bozhong Lin wrote:
>> I will go ahead and cut another release build with all the  
>> changes. The release process will start in the next hour or so.  
>> Please let me know if you are going to commit any code during the  
>> next two hours.
>>
>> Thanks,
>> Bo
>>
>>
>

Re: cutting a new release build

Posted by Bozhong Lin <bl...@iona.com>.

Andrea,

I have done with release before the build failure started, so you are 
free to commit any code at any time now.

Cheers,
Bo

Andrea Smyth wrote:
> Yes I will commit a workaround that allows to re-enable the 
> testTwoWayMessageLoss test shortly.
> Andrea.
>
> Bozhong Lin wrote:
>
>> DONE. It has been uploaded to the same location here [1].
>>
>> Cheers,
>> Bo
>> [1] http://people.apache.org/~blin/
>>
>> Bozhong Lin wrote:
>>
>>> I will go ahead and cut another release build with all the changes. 
>>> The release process will start in the next hour or so. Please let me 
>>> know if you are going to commit any code during the next two hours.
>>>
>>> Thanks,
>>> Bo
>>>
>>>
>

Re: cutting a new release build

Posted by Andrea Smyth <an...@iona.com>.

Yes I will commit a workaround that allows to re-enable the 
testTwoWayMessageLoss test shortly.
Andrea.

Bozhong Lin wrote:

> DONE. It has been uploaded to the same location here [1].
>
> Cheers,
> Bo
> [1] http://people.apache.org/~blin/
>
> Bozhong Lin wrote:
>
>> I will go ahead and cut another release build with all the changes. 
>> The release process will start in the next hour or so. Please let me 
>> know if you are going to commit any code during the next two hours.
>>
>> Thanks,
>> Bo
>>
>>

Re: cutting a new release build

Posted by Bozhong Lin <bl...@iona.com>.

DONE. It has been uploaded to the same location here [1].

Cheers,
Bo
[1] http://people.apache.org/~blin/

Bozhong Lin wrote:
> I will go ahead and cut another release build with all the changes. 
> The release process will start in the next hour or so. Please let me 
> know if you are going to commit any code during the next two hours.
>
> Thanks,
> Bo
>
>