You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tuscany.apache.org by Simon Nash <na...@apache.org> on 2010/08/16 16:34:05 UTC
Doing a 1.6.1 release
It's been over six months since we released 1.6. Since then a number
of bugs have been found in 1.6 and fixed in the 1.x codebase.
Some of these problems (e.g., TUSCANY-3587 and TUSCANY-3588) are
quite serious from a user perspective and I'd like to propose that we
produce a 1.6.1 bug fix release based on the 1.6 release branch with
the existing JIRA fixes merged in. I'd be willing to volunteer as
release manager for this.
I searched JIRA for issues with an Affects Versions tag of Java-SCA-1.6
and a Fix For tag of Java-SCA-Next, and which are marked as fixed.
I found the following:
TUSCANY-3639 Wire interceptors not created until binding interceptors have executed in Service wire
TUSCANY-3625 Issue converting case on methodName for WSDL-derived operation used with binding.ejb reference
TUSCANY-3615 itest/implementation-osgi produces bundle cache errors
TUSCANY-3589 Domain manager produces "get - Error getting data" message when doing a search
TUSCANY-3588 NullPointerException when adding composite in Domain Manager GUI
TUSCANY-3587 Domain manager produces "post - Error getting data" message when adding a composite
TUSCANY-3561 Domain manager throws policy exception if definitions.xml file is read after .composite file
TUSCANY-3551 ClassCastException in SCA Store Tutorial Integration Test
TUSCANY-3540 Axis2SCAReferenceBindingProvider throws exception if servlet host not present
TUSCANY-3490 Tuscany SCA binary distribution doesn't include implementation.web support
As a starting point I would suggest that these are the only changes
that should be included in 1.6.1. This should allow the release to be
done quite quickly and easily as it avoids the possibility of problems
caused by adding new functionality.
Does anyone know of any JIRAs with bug fixes for 1.6 that don't appear
in the above list, or any commits with bug fixes for 1.6 that don't
have JIRAs?
Simon
Re: Doing a 1.6.1 release
Posted by Simon Nash <na...@apache.org>.
Simon Nash wrote:
> Simon Nash wrote:
>> Simon Nash wrote:
>>> Simon Laws wrote:
>>>> On Mon, Aug 16, 2010 at 3:48 PM, Mike Edwards
>>>> <mi...@gmail.com> wrote:
>>>>> Simon Nash wrote:
>>>>>> It's been over six months since we released 1.6. Since then a number
>>>>>> of bugs have been found in 1.6 and fixed in the 1.x codebase.
>>>>>>
>>>>>> Some of these problems (e.g., TUSCANY-3587 and TUSCANY-3588) are
>>>>>> quite serious from a user perspective and I'd like to propose that we
>>>>>> produce a 1.6.1 bug fix release based on the 1.6 release branch with
>>>>>> the existing JIRA fixes merged in. I'd be willing to volunteer as
>>>>>> release manager for this.
>>>>>>
>>>>>> I searched JIRA for issues with an Affects Versions tag of
>>>>>> Java-SCA-1.6
>>>>>> and a Fix For tag of Java-SCA-Next, and which are marked as fixed.
>>>>>> I found the following:
>>>>>> TUSCANY-3639 Wire interceptors not created until binding
>>>>>> interceptors have
>>>>>> executed in Service wire
>>>>>> TUSCANY-3625 Issue converting case on methodName for WSDL-derived
>>>>>> operation used with binding.ejb reference
>>>>>> TUSCANY-3615 itest/implementation-osgi produces bundle cache errors
>>>>>> TUSCANY-3589 Domain manager produces "get - Error getting data"
>>>>>> message
>>>>>> when doing a search
>>>>>> TUSCANY-3588 NullPointerException when adding composite in Domain
>>>>>> Manager
>>>>>> GUI
>>>>>> TUSCANY-3587 Domain manager produces "post - Error getting data"
>>>>>> message
>>>>>> when adding a composite
>>>>>> TUSCANY-3561 Domain manager throws policy exception if
>>>>>> definitions.xml
>>>>>> file is read after .composite file
>>>>>> TUSCANY-3551 ClassCastException in SCA Store Tutorial Integration
>>>>>> Test
>>>>>> TUSCANY-3540 Axis2SCAReferenceBindingProvider throws exception if
>>>>>> servlet
>>>>>> host not present
>>>>>> TUSCANY-3490 Tuscany SCA binary distribution doesn't include
>>>>>> implementation.web support
>>>>>>
>>>>>> As a starting point I would suggest that these are the only changes
>>>>>> that should be included in 1.6.1. This should allow the release
>>>>>> to be
>>>>>> done quite quickly and easily as it avoids the possibility of
>>>>>> problems
>>>>>> caused by adding new functionality.
>>>>>>
>>>>>> Does anyone know of any JIRAs with bug fixes for 1.6 that don't
>>>>>> appear
>>>>>> in the above list, or any commits with bug fixes for 1.6 that don't
>>>>>> have JIRAs?
>>>>>>
>>>>>> Simon
>>>>>>
>>>>>>
>>>>> +1 from me - and I don't have any other JIRAs to suggest.
>>>>>
>>>>>
>>>>> Yours, Mike.
>>>>>
>>>>
>>>> +1 from me for doing the release in the way you suggest. I'll have a
>>>> look to see if I have JIRA to contribute.
>>>>
>>>> Regards
>>>>
>>>> Simon
>>>>
>>> I have created a branch for 1.6.1 development in
>>> https://svn.apache.org/repos/asf/tuscany/sca-java-1.x/branches/sca-java-1.6.1
>>>
>>>
>>> The branch is currently just a copy of the 1.6 release. I am
>>> starting to
>>> merge in the above JIRA fixes and I'll send another note when I have
>>> something ready for others to look at.
>>>
>>> Simon
>>>
>> >
>> I found some more JIRA fixes and some other commits that look like they
>> should be included in 1.6.1. Here's the list:
>>
>> JIRA fixes:
>> TUSCANY-3634 JMS Session is not closed when replyDest is null, then
>> OutOfMemoroy
>> TUSCANY-3569 PolicyConfigurationException: The are unfulfilled intents
>> for binding in reference
>> TUSCANY-3550 Build failure in itest/osgi-implementation
>> DSInterfacesTestCase
>> TUSCANY-3549 Build failure in binding-jsonrpc-runtime
>> TUSCANY-3475 Travel sample launcher for payment-bpel hangs before
>> returning
>> TUSCANY-3466 Cannot stop component or its services and references if
>> one of them fails to start
>> TUSCANY-3193 Domain Manager GUI does not put <binding.sca> entries in
>> generated node confiig files
>> TUSCANY-242 SCDL loader should trim the whitespaces when the element
>> text is parsed
>>
>> Other commits:
>> r959912: Add java.net2 repository (needed for mimepull-1.2.jar)
>> r959536: Add build-dependency.xml to svn:ignore list
>> r959529: Fix incorrect name for tutorial-assets.jar
>> r942469: Exclude junit 3.8 dependency brought in by wss4j and use
>> junit 4.5 instead
>> r921260: add ignores
>> r915259: Correct the composite name
>>
>> If any of these aren't appropriate, please let me know.
>>
>> Simon
>>
>>
>>
> I omitted one of these:
> TUSCANY-3549 Build failure in binding-jsonrpc-runtime
> because it was fixing a problem introduced by other changes that
> aren't in the 1.6.1 branch.
>
> I have merged all the others and I'm trying a full build now.
>
> Simon
>
>
>
Success first time!
[INFO] ------------------------------------------------------------------------
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESSFUL
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 45 minutes 53 seconds
[INFO] Finished at: Tue Aug 24 22:35:12 BST 2010
[INFO] Final Memory: 500M/909M
[INFO] ------------------------------------------------------------------------
Now to run some samples...
Simon
Re: Doing a 1.6.1 release
Posted by Simon Nash <na...@apache.org>.
Simon Nash wrote:
> Simon Nash wrote:
>> Simon Laws wrote:
>>> On Mon, Aug 16, 2010 at 3:48 PM, Mike Edwards
>>> <mi...@gmail.com> wrote:
>>>> Simon Nash wrote:
>>>>> It's been over six months since we released 1.6. Since then a number
>>>>> of bugs have been found in 1.6 and fixed in the 1.x codebase.
>>>>>
>>>>> Some of these problems (e.g., TUSCANY-3587 and TUSCANY-3588) are
>>>>> quite serious from a user perspective and I'd like to propose that we
>>>>> produce a 1.6.1 bug fix release based on the 1.6 release branch with
>>>>> the existing JIRA fixes merged in. I'd be willing to volunteer as
>>>>> release manager for this.
>>>>>
>>>>> I searched JIRA for issues with an Affects Versions tag of
>>>>> Java-SCA-1.6
>>>>> and a Fix For tag of Java-SCA-Next, and which are marked as fixed.
>>>>> I found the following:
>>>>> TUSCANY-3639 Wire interceptors not created until binding
>>>>> interceptors have
>>>>> executed in Service wire
>>>>> TUSCANY-3625 Issue converting case on methodName for WSDL-derived
>>>>> operation used with binding.ejb reference
>>>>> TUSCANY-3615 itest/implementation-osgi produces bundle cache errors
>>>>> TUSCANY-3589 Domain manager produces "get - Error getting data"
>>>>> message
>>>>> when doing a search
>>>>> TUSCANY-3588 NullPointerException when adding composite in Domain
>>>>> Manager
>>>>> GUI
>>>>> TUSCANY-3587 Domain manager produces "post - Error getting data"
>>>>> message
>>>>> when adding a composite
>>>>> TUSCANY-3561 Domain manager throws policy exception if definitions.xml
>>>>> file is read after .composite file
>>>>> TUSCANY-3551 ClassCastException in SCA Store Tutorial Integration Test
>>>>> TUSCANY-3540 Axis2SCAReferenceBindingProvider throws exception if
>>>>> servlet
>>>>> host not present
>>>>> TUSCANY-3490 Tuscany SCA binary distribution doesn't include
>>>>> implementation.web support
>>>>>
>>>>> As a starting point I would suggest that these are the only changes
>>>>> that should be included in 1.6.1. This should allow the release to be
>>>>> done quite quickly and easily as it avoids the possibility of problems
>>>>> caused by adding new functionality.
>>>>>
>>>>> Does anyone know of any JIRAs with bug fixes for 1.6 that don't appear
>>>>> in the above list, or any commits with bug fixes for 1.6 that don't
>>>>> have JIRAs?
>>>>>
>>>>> Simon
>>>>>
>>>>>
>>>> +1 from me - and I don't have any other JIRAs to suggest.
>>>>
>>>>
>>>> Yours, Mike.
>>>>
>>>
>>> +1 from me for doing the release in the way you suggest. I'll have a
>>> look to see if I have JIRA to contribute.
>>>
>>> Regards
>>>
>>> Simon
>>>
>> I have created a branch for 1.6.1 development in
>> https://svn.apache.org/repos/asf/tuscany/sca-java-1.x/branches/sca-java-1.6.1
>>
>>
>> The branch is currently just a copy of the 1.6 release. I am starting to
>> merge in the above JIRA fixes and I'll send another note when I have
>> something ready for others to look at.
>>
>> Simon
>>
> >
> I found some more JIRA fixes and some other commits that look like they
> should be included in 1.6.1. Here's the list:
>
> JIRA fixes:
> TUSCANY-3634 JMS Session is not closed when replyDest is null, then
> OutOfMemoroy
> TUSCANY-3569 PolicyConfigurationException: The are unfulfilled intents
> for binding in reference
> TUSCANY-3550 Build failure in itest/osgi-implementation
> DSInterfacesTestCase
> TUSCANY-3549 Build failure in binding-jsonrpc-runtime
> TUSCANY-3475 Travel sample launcher for payment-bpel hangs before returning
> TUSCANY-3466 Cannot stop component or its services and references if one
> of them fails to start
> TUSCANY-3193 Domain Manager GUI does not put <binding.sca> entries in
> generated node confiig files
> TUSCANY-242 SCDL loader should trim the whitespaces when the element
> text is parsed
>
> Other commits:
> r959912: Add java.net2 repository (needed for mimepull-1.2.jar)
> r959536: Add build-dependency.xml to svn:ignore list
> r959529: Fix incorrect name for tutorial-assets.jar
> r942469: Exclude junit 3.8 dependency brought in by wss4j and use junit
> 4.5 instead
> r921260: add ignores
> r915259: Correct the composite name
>
> If any of these aren't appropriate, please let me know.
>
> Simon
>
>
>
I omitted one of these:
TUSCANY-3549 Build failure in binding-jsonrpc-runtime
because it was fixing a problem introduced by other changes that
aren't in the 1.6.1 branch.
I have merged all the others and I'm trying a full build now.
Simon
Re: Doing a 1.6.1 release
Posted by Simon Nash <na...@apache.org>.
Simon Nash wrote:
> Simon Laws wrote:
>> On Mon, Aug 16, 2010 at 3:48 PM, Mike Edwards
>> <mi...@gmail.com> wrote:
>>> Simon Nash wrote:
>>>> It's been over six months since we released 1.6. Since then a number
>>>> of bugs have been found in 1.6 and fixed in the 1.x codebase.
>>>>
>>>> Some of these problems (e.g., TUSCANY-3587 and TUSCANY-3588) are
>>>> quite serious from a user perspective and I'd like to propose that we
>>>> produce a 1.6.1 bug fix release based on the 1.6 release branch with
>>>> the existing JIRA fixes merged in. I'd be willing to volunteer as
>>>> release manager for this.
>>>>
>>>> I searched JIRA for issues with an Affects Versions tag of Java-SCA-1.6
>>>> and a Fix For tag of Java-SCA-Next, and which are marked as fixed.
>>>> I found the following:
>>>> TUSCANY-3639 Wire interceptors not created until binding
>>>> interceptors have
>>>> executed in Service wire
>>>> TUSCANY-3625 Issue converting case on methodName for WSDL-derived
>>>> operation used with binding.ejb reference
>>>> TUSCANY-3615 itest/implementation-osgi produces bundle cache errors
>>>> TUSCANY-3589 Domain manager produces "get - Error getting data" message
>>>> when doing a search
>>>> TUSCANY-3588 NullPointerException when adding composite in Domain
>>>> Manager
>>>> GUI
>>>> TUSCANY-3587 Domain manager produces "post - Error getting data"
>>>> message
>>>> when adding a composite
>>>> TUSCANY-3561 Domain manager throws policy exception if definitions.xml
>>>> file is read after .composite file
>>>> TUSCANY-3551 ClassCastException in SCA Store Tutorial Integration Test
>>>> TUSCANY-3540 Axis2SCAReferenceBindingProvider throws exception if
>>>> servlet
>>>> host not present
>>>> TUSCANY-3490 Tuscany SCA binary distribution doesn't include
>>>> implementation.web support
>>>>
>>>> As a starting point I would suggest that these are the only changes
>>>> that should be included in 1.6.1. This should allow the release to be
>>>> done quite quickly and easily as it avoids the possibility of problems
>>>> caused by adding new functionality.
>>>>
>>>> Does anyone know of any JIRAs with bug fixes for 1.6 that don't appear
>>>> in the above list, or any commits with bug fixes for 1.6 that don't
>>>> have JIRAs?
>>>>
>>>> Simon
>>>>
>>>>
>>> +1 from me - and I don't have any other JIRAs to suggest.
>>>
>>>
>>> Yours, Mike.
>>>
>>
>> +1 from me for doing the release in the way you suggest. I'll have a
>> look to see if I have JIRA to contribute.
>>
>> Regards
>>
>> Simon
>>
> I have created a branch for 1.6.1 development in
> https://svn.apache.org/repos/asf/tuscany/sca-java-1.x/branches/sca-java-1.6.1
>
>
> The branch is currently just a copy of the 1.6 release. I am starting to
> merge in the above JIRA fixes and I'll send another note when I have
> something ready for others to look at.
>
> Simon
>
>
I found some more JIRA fixes and some other commits that look like they
should be included in 1.6.1. Here's the list:
JIRA fixes:
TUSCANY-3634 JMS Session is not closed when replyDest is null, then OutOfMemoroy
TUSCANY-3569 PolicyConfigurationException: The are unfulfilled intents for binding in reference
TUSCANY-3550 Build failure in itest/osgi-implementation DSInterfacesTestCase
TUSCANY-3549 Build failure in binding-jsonrpc-runtime
TUSCANY-3475 Travel sample launcher for payment-bpel hangs before returning
TUSCANY-3466 Cannot stop component or its services and references if one of them fails to start
TUSCANY-3193 Domain Manager GUI does not put <binding.sca> entries in generated node confiig files
TUSCANY-242 SCDL loader should trim the whitespaces when the element text is parsed
Other commits:
r959912: Add java.net2 repository (needed for mimepull-1.2.jar)
r959536: Add build-dependency.xml to svn:ignore list
r959529: Fix incorrect name for tutorial-assets.jar
r942469: Exclude junit 3.8 dependency brought in by wss4j and use junit 4.5 instead
r921260: add ignores
r915259: Correct the composite name
If any of these aren't appropriate, please let me know.
Simon
Re: Doing a 1.6.1 release
Posted by Simon Nash <na...@apache.org>.
Simon Laws wrote:
> On Mon, Aug 16, 2010 at 3:48 PM, Mike Edwards
> <mi...@gmail.com> wrote:
>> Simon Nash wrote:
>>> It's been over six months since we released 1.6. Since then a number
>>> of bugs have been found in 1.6 and fixed in the 1.x codebase.
>>>
>>> Some of these problems (e.g., TUSCANY-3587 and TUSCANY-3588) are
>>> quite serious from a user perspective and I'd like to propose that we
>>> produce a 1.6.1 bug fix release based on the 1.6 release branch with
>>> the existing JIRA fixes merged in. I'd be willing to volunteer as
>>> release manager for this.
>>>
>>> I searched JIRA for issues with an Affects Versions tag of Java-SCA-1.6
>>> and a Fix For tag of Java-SCA-Next, and which are marked as fixed.
>>> I found the following:
>>> TUSCANY-3639 Wire interceptors not created until binding interceptors have
>>> executed in Service wire
>>> TUSCANY-3625 Issue converting case on methodName for WSDL-derived
>>> operation used with binding.ejb reference
>>> TUSCANY-3615 itest/implementation-osgi produces bundle cache errors
>>> TUSCANY-3589 Domain manager produces "get - Error getting data" message
>>> when doing a search
>>> TUSCANY-3588 NullPointerException when adding composite in Domain Manager
>>> GUI
>>> TUSCANY-3587 Domain manager produces "post - Error getting data" message
>>> when adding a composite
>>> TUSCANY-3561 Domain manager throws policy exception if definitions.xml
>>> file is read after .composite file
>>> TUSCANY-3551 ClassCastException in SCA Store Tutorial Integration Test
>>> TUSCANY-3540 Axis2SCAReferenceBindingProvider throws exception if servlet
>>> host not present
>>> TUSCANY-3490 Tuscany SCA binary distribution doesn't include
>>> implementation.web support
>>>
>>> As a starting point I would suggest that these are the only changes
>>> that should be included in 1.6.1. This should allow the release to be
>>> done quite quickly and easily as it avoids the possibility of problems
>>> caused by adding new functionality.
>>>
>>> Does anyone know of any JIRAs with bug fixes for 1.6 that don't appear
>>> in the above list, or any commits with bug fixes for 1.6 that don't
>>> have JIRAs?
>>>
>>> Simon
>>>
>>>
>> +1 from me - and I don't have any other JIRAs to suggest.
>>
>>
>> Yours, Mike.
>>
>
> +1 from me for doing the release in the way you suggest. I'll have a
> look to see if I have JIRA to contribute.
>
> Regards
>
> Simon
>
I have created a branch for 1.6.1 development in
https://svn.apache.org/repos/asf/tuscany/sca-java-1.x/branches/sca-java-1.6.1
The branch is currently just a copy of the 1.6 release. I am starting to
merge in the above JIRA fixes and I'll send another note when I have
something ready for others to look at.
Simon
Re: Doing a 1.6.1 release
Posted by Simon Laws <si...@googlemail.com>.
On Mon, Aug 16, 2010 at 3:48 PM, Mike Edwards
<mi...@gmail.com> wrote:
> Simon Nash wrote:
>>
>> It's been over six months since we released 1.6. Since then a number
>> of bugs have been found in 1.6 and fixed in the 1.x codebase.
>>
>> Some of these problems (e.g., TUSCANY-3587 and TUSCANY-3588) are
>> quite serious from a user perspective and I'd like to propose that we
>> produce a 1.6.1 bug fix release based on the 1.6 release branch with
>> the existing JIRA fixes merged in. I'd be willing to volunteer as
>> release manager for this.
>>
>> I searched JIRA for issues with an Affects Versions tag of Java-SCA-1.6
>> and a Fix For tag of Java-SCA-Next, and which are marked as fixed.
>> I found the following:
>> TUSCANY-3639 Wire interceptors not created until binding interceptors have
>> executed in Service wire
>> TUSCANY-3625 Issue converting case on methodName for WSDL-derived
>> operation used with binding.ejb reference
>> TUSCANY-3615 itest/implementation-osgi produces bundle cache errors
>> TUSCANY-3589 Domain manager produces "get - Error getting data" message
>> when doing a search
>> TUSCANY-3588 NullPointerException when adding composite in Domain Manager
>> GUI
>> TUSCANY-3587 Domain manager produces "post - Error getting data" message
>> when adding a composite
>> TUSCANY-3561 Domain manager throws policy exception if definitions.xml
>> file is read after .composite file
>> TUSCANY-3551 ClassCastException in SCA Store Tutorial Integration Test
>> TUSCANY-3540 Axis2SCAReferenceBindingProvider throws exception if servlet
>> host not present
>> TUSCANY-3490 Tuscany SCA binary distribution doesn't include
>> implementation.web support
>>
>> As a starting point I would suggest that these are the only changes
>> that should be included in 1.6.1. This should allow the release to be
>> done quite quickly and easily as it avoids the possibility of problems
>> caused by adding new functionality.
>>
>> Does anyone know of any JIRAs with bug fixes for 1.6 that don't appear
>> in the above list, or any commits with bug fixes for 1.6 that don't
>> have JIRAs?
>>
>> Simon
>>
>>
>
> +1 from me - and I don't have any other JIRAs to suggest.
>
>
> Yours, Mike.
>
+1 from me for doing the release in the way you suggest. I'll have a
look to see if I have JIRA to contribute.
Regards
Simon
--
Apache Tuscany committer: tuscany.apache.org
Co-author of a book about Tuscany and SCA: tuscanyinaction.com
Re: Doing a 1.6.1 release
Posted by Mike Edwards <mi...@gmail.com>.
Simon Nash wrote:
> It's been over six months since we released 1.6. Since then a number
> of bugs have been found in 1.6 and fixed in the 1.x codebase.
>
> Some of these problems (e.g., TUSCANY-3587 and TUSCANY-3588) are
> quite serious from a user perspective and I'd like to propose that we
> produce a 1.6.1 bug fix release based on the 1.6 release branch with
> the existing JIRA fixes merged in. I'd be willing to volunteer as
> release manager for this.
>
> I searched JIRA for issues with an Affects Versions tag of Java-SCA-1.6
> and a Fix For tag of Java-SCA-Next, and which are marked as fixed.
> I found the following:
> TUSCANY-3639 Wire interceptors not created until binding interceptors
> have executed in Service wire
> TUSCANY-3625 Issue converting case on methodName for WSDL-derived
> operation used with binding.ejb reference
> TUSCANY-3615 itest/implementation-osgi produces bundle cache errors
> TUSCANY-3589 Domain manager produces "get - Error getting data" message
> when doing a search
> TUSCANY-3588 NullPointerException when adding composite in Domain
> Manager GUI
> TUSCANY-3587 Domain manager produces "post - Error getting data" message
> when adding a composite
> TUSCANY-3561 Domain manager throws policy exception if definitions.xml
> file is read after .composite file
> TUSCANY-3551 ClassCastException in SCA Store Tutorial Integration Test
> TUSCANY-3540 Axis2SCAReferenceBindingProvider throws exception if
> servlet host not present
> TUSCANY-3490 Tuscany SCA binary distribution doesn't include
> implementation.web support
>
> As a starting point I would suggest that these are the only changes
> that should be included in 1.6.1. This should allow the release to be
> done quite quickly and easily as it avoids the possibility of problems
> caused by adding new functionality.
>
> Does anyone know of any JIRAs with bug fixes for 1.6 that don't appear
> in the above list, or any commits with bug fixes for 1.6 that don't
> have JIRAs?
>
> Simon
>
>
+1 from me - and I don't have any other JIRAs to suggest.
Yours, Mike.