Mailing-List: contact dev-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
Subject: Re: [VOTE] Release Apache Camel 2.19.0 (Attempt #2)
To: dev@camel.apache.org
References: <CADL1oArpVsU0wBH6YT9QVVL-stzpd4s3Pmq8i3XU-CEWhH4S+w@mail.gmail.com>
 <06103e99-92a7-8621-268b-6b064ec8aec7@gmail.com>
 <CAGB5yN=cD94Vy32d=S7iVLg=MZOcVqzka3OqTmfOffoHh9k6qA@mail.gmail.com>
From: Marco Collovati <mcollovati@gmail.com>
Message-ID: <c6441829-4096-0562-5c54-b5ded5c86d22@gmail.com>
Date: Tue, 2 May 2017 20:48:54 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101
 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <CAGB5yN=cD94Vy32d=S7iVLg=MZOcVqzka3OqTmfOffoHh9k6qA@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
archived-at: Tue, 02 May 2017 18:49:01 -0000

Ok, sorry.

BTW, aside from my previous problem, I tested RC on some production 
project involving camel-jms, camel-cxf, camel-mail and 
camel-api-component-maven-plugin and all is working fine.


On 02/05/2017 20:39, Claus Ibsen wrote:
> Hi Marco
>
> You should likely post a new thread with more details what you are trying to do.
> Your use-case is not normal and therefore not considering a blocker.
> There are likely other places where such check in doStart is checking
> the field also.
>
> The RC testing is more focusing on existing applications being
> migrated or ported to this versions to find regressions etc.
>
>
> On Mon, May 1, 2017 at 7:38 AM, Marco Collovati <mcollovati@gmail.com> wrote:
>> -1
>>
>> Got an issue with DefaultComponent change on doStart method:
>> the check for camel context is done via getter
>> ```ObjectHelper.notNull(getCamelContext(), "camelContext");```
>> but the following logic access the `camelContext` field directly.
>>
>> This leads to NPE when extending DefaultComponent as a decorator for other
>> components.
>>
>> Maybe this is more an issue on my code but I think the camelContext check
>> should be consistent with the following code.
>>
>>
>>
>> On 30/04/2017 17:32, Gregor Zurowski wrote:
>>>
>>> Hi Everyone:
>>>
>>> This is the second vote to release Apache Camel 2.19.0, a new minor
>>> release with over 670 new features, improvements and bug fixes.  A
>>> summary of the changes is available in the Camel wiki [1].  The first
>>> vote was cancelled due to multiple issues found while testing the
>>> first release candidate [1].
>>>
>>> Release notes:
>>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12337871&projectId=12311211
>>>
>>> Staging repository:
>>> https://repository.apache.org/content/repositories/orgapachecamel-1075/
>>>
>>> Tarballs:
>>> https://repository.apache.org/content/repositories/orgapachecamel-1075/org/apache/camel/apache-camel/2.19.0/
>>>
>>> Tag:
>>> https://git-wip-us.apache.org/repos/asf?p=camel.git;a=tag;h=0ae39c5223d4e58e1f3063e7e5f071be0e258e97
>>>
>>> Please test this release candidate and cast your vote.
>>> [ ] +1 Release the binary as Apache Camel 2.19.0
>>> [ ] -1 Veto the release (provide specific comments)
>>>
>>> The vote is open for at least 72 hours.
>>>
>>> Due to the many changes introduced with this new release, it would be
>>> beneficial if we could get as many Camel riders involved in testing
>>> this release candidate as possible.
>>>
>>> Thanks,
>>> Gregor
>>>
>>> [1] https://cwiki.apache.org/confluence/display/CAMEL/Camel+2.19+Release
>>> [2]
>>> http://camel.465427.n5.nabble.com/VOTE-Release-Apache-Camel-2-19-0-td5798264.html
>>>
>>
>
>
>