You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by Hadrian Zbarcea <hz...@gmail.com> on 2009/08/18 23:39:31 UTC
[VOTE] Release Apache Camel 2.0.0
The first release candidate of apache-camel-2.0.0 is out with 61 new
features, improvements and bug fixes. This concludes more than one
year of efforts to bring a new and improved Apache Camel. Many thanks
to everybody in the community who contributed to this release.
Please find the staging repo here:
https://repository.apache.org/content/groups/staging/org/apache/camel/
The tarballs are here
https://repository.apache.org/content/groups/staging/org/apache/camel/apache-camel/2.0.0/
Please vote to approve this release binary
[ ] +1 Release the binary as Apache Camel 2.0-M3
[ ] -1 Veto the release (provide specific comments)
Vote is open for 72 hours.
The Camel Riders
Re: [VOTE] Release Apache Camel 2.0.0
Posted by Jon Anstey <ja...@gmail.com>.
Awesome work Hadrian! Kit looks good to me.
+1 to release
On Tue, Aug 18, 2009 at 7:09 PM, Hadrian Zbarcea <hz...@gmail.com> wrote:
> The first release candidate of apache-camel-2.0.0 is out with 61 new
> features, improvements and bug fixes. This concludes more than one year of
> efforts to bring a new and improved Apache Camel. Many thanks to everybody
> in the community who contributed to this release.
>
> Please find the staging repo here:
> https://repository.apache.org/content/groups/staging/org/apache/camel/
>
> The tarballs are here
>
> https://repository.apache.org/content/groups/staging/org/apache/camel/apache-camel/2.0.0/
>
> Please vote to approve this release binary
>
> [ ] +1 Release the binary as Apache Camel 2.0-M3
> [ ] -1 Veto the release (provide specific comments)
> Vote is open for 72 hours.
>
>
> The Camel Riders
--
Cheers,
Jon
http://janstey.blogspot.com/
Re: [VOTE] Release Apache Camel 2.0.0
Posted by Rob Davies <ra...@gmail.com>.
+1
On 18 Aug 2009, at 22:39, Hadrian Zbarcea wrote:
> The first release candidate of apache-camel-2.0.0 is out with 61 new
> features, improvements and bug fixes. This concludes more than one
> year of efforts to bring a new and improved Apache Camel. Many
> thanks to everybody in the community who contributed to this release.
>
> Please find the staging repo here:
> https://repository.apache.org/content/groups/staging/org/apache/camel/
>
> The tarballs are here
> https://repository.apache.org/content/groups/staging/org/apache/camel/apache-camel/2.0.0/
>
> Please vote to approve this release binary
>
> [ ] +1 Release the binary as Apache Camel 2.0-M3
> [ ] -1 Veto the release (provide specific comments)
> Vote is open for 72 hours.
>
>
> The Camel Riders
Rob Davies
I work here: http://fusesource.com
My Blog: http://rajdavies.blogspot.com/
I'm writing this: http://www.manning.com/snyder/
Re: Finalizing the Camel release (was: [RESULT][VOTE] Release Apache Camel 2.0.0)
Posted by Hadrian Zbarcea <hz...@gmail.com>.
Hi William,
Yes, you can go ahead with your commits. The rest of the release
process is not affected by changes on trunk.
Cheers,
Hadrian
On Aug 23, 2009, at 7:22 PM, William Tam wrote:
> Hi Hadrian,
>
> I just submitted a patch to trunk for 2.1 (I saw the POM version
> updates and thought the trunk has been cleared). Let me know if it is
> a problem.
>
> Thanks,
> William
>
> On Sun, Aug 23, 2009 at 7:13 PM, Hadrian Zbarcea<hz...@gmail.com>
> wrote:
>> At this time the minotaur is still down. Hopefully it will be back
>> up
>> tomorrow so I can finalize the release.
>>
>> Hadrian
>>
>>
>> On Aug 22, 2009, at 6:39 PM, Hadrian Zbarcea wrote:
>>
>>> The vote passes with:
>>> [7] +1 binding votes [janstey, rajdavies, jstrachan, wtam,
>>> ningjiang,
>>> cibsen, hadrian]
>>> [1] +1 non-binding votes [cmoulliard]
>>> [0] -1 votes
>>>
>>> Many thanks to all who took the time to test this release and to the
>>> community in general who made this release possible.
>>>
>>> During the next days I will finalize the release process. The
>>> minotaur
>>> server seems down at the moment.
>>>
>>> Hadrian
>>>
>>>
>>> On Aug 18, 2009, at 5:39 PM, Hadrian Zbarcea wrote:
>>>
>>>> The first release candidate of apache-camel-2.0.0 is out with 61
>>>> new
>>>> features, improvements and bug fixes. This concludes more than
>>>> one year of
>>>> efforts to bring a new and improved Apache Camel. Many thanks to
>>>> everybody
>>>> in the community who contributed to this release.
>>>>
>>>> Please find the staging repo here:
>>>> https://repository.apache.org/content/groups/staging/org/apache/camel/
>>>>
>>>> The tarballs are here
>>>>
>>>> https://repository.apache.org/content/groups/staging/org/apache/camel/apache-camel/2.0.0/
>>>>
>>>> Please vote to approve this release binary
>>>>
>>>> [ ] +1 Release the binary as Apache Camel 2.0-M3
>>>> [ ] -1 Veto the release (provide specific comments)
>>>> Vote is open for 72 hours.
>>>>
>>>>
>>>> The Camel Riders
>>>
>>
>>
Re: Finalizing the Camel release (was: [RESULT][VOTE] Release Apache
Camel 2.0.0)
Posted by William Tam <em...@gmail.com>.
Hi Hadrian,
I just submitted a patch to trunk for 2.1 (I saw the POM version
updates and thought the trunk has been cleared). Let me know if it is
a problem.
Thanks,
William
On Sun, Aug 23, 2009 at 7:13 PM, Hadrian Zbarcea<hz...@gmail.com> wrote:
> At this time the minotaur is still down. Hopefully it will be back up
> tomorrow so I can finalize the release.
>
> Hadrian
>
>
> On Aug 22, 2009, at 6:39 PM, Hadrian Zbarcea wrote:
>
>> The vote passes with:
>> [7] +1 binding votes [janstey, rajdavies, jstrachan, wtam, ningjiang,
>> cibsen, hadrian]
>> [1] +1 non-binding votes [cmoulliard]
>> [0] -1 votes
>>
>> Many thanks to all who took the time to test this release and to the
>> community in general who made this release possible.
>>
>> During the next days I will finalize the release process. The minotaur
>> server seems down at the moment.
>>
>> Hadrian
>>
>>
>> On Aug 18, 2009, at 5:39 PM, Hadrian Zbarcea wrote:
>>
>>> The first release candidate of apache-camel-2.0.0 is out with 61 new
>>> features, improvements and bug fixes. This concludes more than one year of
>>> efforts to bring a new and improved Apache Camel. Many thanks to everybody
>>> in the community who contributed to this release.
>>>
>>> Please find the staging repo here:
>>> https://repository.apache.org/content/groups/staging/org/apache/camel/
>>>
>>> The tarballs are here
>>>
>>> https://repository.apache.org/content/groups/staging/org/apache/camel/apache-camel/2.0.0/
>>>
>>> Please vote to approve this release binary
>>>
>>> [ ] +1 Release the binary as Apache Camel 2.0-M3
>>> [ ] -1 Veto the release (provide specific comments)
>>> Vote is open for 72 hours.
>>>
>>>
>>> The Camel Riders
>>
>
>
Finalizing the Camel release (was: [RESULT][VOTE] Release Apache Camel 2.0.0)
Posted by Hadrian Zbarcea <hz...@gmail.com>.
At this time the minotaur is still down. Hopefully it will be back up
tomorrow so I can finalize the release.
Hadrian
On Aug 22, 2009, at 6:39 PM, Hadrian Zbarcea wrote:
> The vote passes with:
> [7] +1 binding votes [janstey, rajdavies, jstrachan, wtam,
> ningjiang, cibsen, hadrian]
> [1] +1 non-binding votes [cmoulliard]
> [0] -1 votes
>
> Many thanks to all who took the time to test this release and to the
> community in general who made this release possible.
>
> During the next days I will finalize the release process. The
> minotaur server seems down at the moment.
>
> Hadrian
>
>
> On Aug 18, 2009, at 5:39 PM, Hadrian Zbarcea wrote:
>
>> The first release candidate of apache-camel-2.0.0 is out with 61
>> new features, improvements and bug fixes. This concludes more than
>> one year of efforts to bring a new and improved Apache Camel. Many
>> thanks to everybody in the community who contributed to this release.
>>
>> Please find the staging repo here:
>> https://repository.apache.org/content/groups/staging/org/apache/
>> camel/
>>
>> The tarballs are here
>> https://repository.apache.org/content/groups/staging/org/apache/camel/apache-camel/2.0.0/
>>
>> Please vote to approve this release binary
>>
>> [ ] +1 Release the binary as Apache Camel 2.0-M3
>> [ ] -1 Veto the release (provide specific comments)
>> Vote is open for 72 hours.
>>
>>
>> The Camel Riders
>
[RESULT][VOTE] Release Apache Camel 2.0.0
Posted by Hadrian Zbarcea <hz...@gmail.com>.
The vote passes with:
[7] +1 binding votes [janstey, rajdavies, jstrachan, wtam, ningjiang,
cibsen, hadrian]
[1] +1 non-binding votes [cmoulliard]
[0] -1 votes
Many thanks to all who took the time to test this release and to the
community in general who made this release possible.
During the next days I will finalize the release process. The
minotaur server seems down at the moment.
Hadrian
On Aug 18, 2009, at 5:39 PM, Hadrian Zbarcea wrote:
> The first release candidate of apache-camel-2.0.0 is out with 61 new
> features, improvements and bug fixes. This concludes more than one
> year of efforts to bring a new and improved Apache Camel. Many
> thanks to everybody in the community who contributed to this release.
>
> Please find the staging repo here:
> https://repository.apache.org/content/groups/staging/org/apache/camel/
>
> The tarballs are here
> https://repository.apache.org/content/groups/staging/org/apache/camel/apache-camel/2.0.0/
>
> Please vote to approve this release binary
>
> [ ] +1 Release the binary as Apache Camel 2.0-M3
> [ ] -1 Veto the release (provide specific comments)
> Vote is open for 72 hours.
>
>
> The Camel Riders
Re: [VOTE] Release Apache Camel 2.0.0
Posted by Claus Ibsen <cl...@gmail.com>.
+1
On Tue, Aug 18, 2009 at 11:39 PM, Hadrian Zbarcea<hz...@gmail.com> wrote:
> The first release candidate of apache-camel-2.0.0 is out with 61 new
> features, improvements and bug fixes. This concludes more than one year of
> efforts to bring a new and improved Apache Camel. Many thanks to everybody
> in the community who contributed to this release.
>
> Please find the staging repo here:
> https://repository.apache.org/content/groups/staging/org/apache/camel/
>
> The tarballs are here
> https://repository.apache.org/content/groups/staging/org/apache/camel/apache-camel/2.0.0/
>
> Please vote to approve this release binary
>
> [ ] +1 Release the binary as Apache Camel 2.0-M3
> [ ] -1 Veto the release (provide specific comments)
> Vote is open for 72 hours.
>
>
> The Camel Riders
--
Claus Ibsen
Apache Camel Committer
Open Source Integration: http://fusesource.com
Blog: http://davsclaus.blogspot.com/
Twitter: http://twitter.com/davsclaus
Re: [VOTE] Release Apache Camel 2.0.0
Posted by Willem Jiang <wi...@gmail.com>.
+1
Willem
Hadrian Zbarcea wrote:
> The first release candidate of apache-camel-2.0.0 is out with 61 new
> features, improvements and bug fixes. This concludes more than one year
> of efforts to bring a new and improved Apache Camel. Many thanks to
> everybody in the community who contributed to this release.
>
> Please find the staging repo here:
> https://repository.apache.org/content/groups/staging/org/apache/camel/
>
> The tarballs are here
> https://repository.apache.org/content/groups/staging/org/apache/camel/apache-camel/2.0.0/
>
>
> Please vote to approve this release binary
>
> [ ] +1 Release the binary as Apache Camel 2.0-M3
> [ ] -1 Veto the release (provide specific comments)
> Vote is open for 72 hours.
>
>
> The Camel Riders
Re: [VOTE] Release Apache Camel 2.0.0
Posted by Christian Schneider <ch...@die-schneider.net>.
Claus Ibsen schrieb:
>
>> I will report back when I found the problem in the other cases. In any case
>> it would be a good idea to have a windows system that does continouus
>> integration for camel beside the existing linux and mac systems.
>>
>>
>
> Apache does not have such we only got Hudson.
>
> However at fusesource we got a full range of servers and
> infrastructure. So we catch these when we do a FUSE release based on
> Camel 2.0
>
>
I think it would be better to catch these problems earlier. Could
FuseSource set up a server that builds the head on each checkin like
hudson does?
Perhaps apache could also create a windows system for hudson.
Greetings
Christian
Re: [VOTE] Release Apache Camel 2.0.0
Posted by Claus Ibsen <cl...@gmail.com>.
On Thu, Aug 20, 2009 at 9:00 AM, Christian
Schneider<ch...@die-schneider.net> wrote:
> Hi Hadrian,
>
> I have found the problem in the first test that failed:
> GenericFileDeleteProcessStrategyTest.testCannotDeleteFile
>
> In the method exists file the test checks if the file name equals
> "target/foo/boom.txt" but on windows the file name is "target\foo\boom.txt".
> So the method says the file does not exist. The test then thinks it has
> successfully deleted the file and does not throw the expected exception.
>
Good use the FileUtil.normalizePath to ensure the path can be tested
using equals.
There are other unit tests that does this as well.
> I will report back when I found the problem in the other cases. In any case
> it would be a good idea to have a windows system that does continouus
> integration for camel beside the existing linux and mac systems.
>
Apache does not have such we only got Hudson.
However at fusesource we got a full range of servers and
infrastructure. So we catch these when we do a FUSE release based on
Camel 2.0
> Greetings
>
> Christian
>
> Hadrian Zbarcea schrieb:
>>
>> Hi Christian,
>>
>> Thanks for doing the tests. No, it is not ok, but all the tests are
>> passing consistently for a few weeks on mac and linux. That code is not
>> quite platform specific (well, except for the Windows fs). Could you
>> *please* take a look a bit more and maybe figure out what the issue is? Is
>> it a fluke, a timing issue, a more serious problem, does it work from an IDE
>> like Eclipse?
>>
>> Imho this is not a blocker for this release (yet), but it's good to know.
>>
>> Many thanks again,
>> Hadrian
>>
>>
>> On Aug 19, 2009, at 7:26 AM, Christian Schneider wrote:
>>
>>> I just checked out the head (hope this is still the release 2.0.0 state)
>>> and did a full build. I got three test failures in camel-core. Is this ok?
>>>
>>> I built on Windows Vista, JDK 1.6.0_14 and maven 2.2.0.
>>>
>>> Greetings
>>>
>>> Christian
>>> Failure Details
>>>
>>> <icon_warning_sml.gif> testCannotDeleteFile
>>>
>>> junit.framework.AssertionFailedError: Should have thrown an exception
>>>
>>>
>>> org.apache.camel.component.file.strategy.GenericFileDeleteProcessStrategyTest:125
>>> <icon_warning_sml.gif> testCacheStreamToFileAndNotCloseStream
>>>
>>> junit.framework.AssertionFailedError: we should have no temp file
>>> expected:<1> but was:<0>
>>>
>>> org.apache.camel.converter.stream.CachedOutputStreamTest:117
>>> <icon_warning_sml.gif> testRouteIsCorrectAtRuntime
>>>
>>> junit.framework.AssertionFailedError: expected:<4> but was:<1>
>>>
>>> org.apache.camel.processor.ChoiceWithEndTest:39
>>>
>>>
>>> Hadrian Zbarcea schrieb:
>>>>
>>>> The first release candidate of apache-camel-2.0.0 is out with 61 new
>>>> features, improvements and bug fixes. This concludes more than one year of
>>>> efforts to bring a new and improved Apache Camel. Many thanks to everybody
>>>> in the community who contributed to this release.
>>>>
>>>> Please find the staging repo here:
>>>> https://repository.apache.org/content/groups/staging/org/apache/camel/
>>>>
>>>> The tarballs are here
>>>>
>>>> https://repository.apache.org/content/groups/staging/org/apache/camel/apache-camel/2.0.0/
>>>>
>>>> Please vote to approve this release binary
>>>>
>>>> [ ] +1 Release the binary as Apache Camel 2.0-M3
>>>> [ ] -1 Veto the release (provide specific comments)
>>>> Vote is open for 72 hours.
>>>>
>>>>
>>>> The Camel Riders
>>>
>>
>>
>
>
--
Claus Ibsen
Apache Camel Committer
Open Source Integration: http://fusesource.com
Blog: http://davsclaus.blogspot.com/
Twitter: http://twitter.com/davsclaus
Re: [VOTE] Release Apache Camel 2.0.0
Posted by Christian Schneider <ch...@die-schneider.net>.
Hi Hadrian,
I have found the problem in the first test that failed:
GenericFileDeleteProcessStrategyTest.testCannotDeleteFile
In the method exists file the test checks if the file name equals
"target/foo/boom.txt" but on windows the file name is
"target\foo\boom.txt". So the method says the file does not exist. The
test then thinks it has successfully deleted the file and does not throw
the expected exception.
I will report back when I found the problem in the other cases. In any
case it would be a good idea to have a windows system that does
continouus integration for camel beside the existing linux and mac systems.
Greetings
Christian
Hadrian Zbarcea schrieb:
> Hi Christian,
>
> Thanks for doing the tests. No, it is not ok, but all the tests are
> passing consistently for a few weeks on mac and linux. That code is
> not quite platform specific (well, except for the Windows fs). Could
> you *please* take a look a bit more and maybe figure out what the
> issue is? Is it a fluke, a timing issue, a more serious problem, does
> it work from an IDE like Eclipse?
>
> Imho this is not a blocker for this release (yet), but it's good to know.
>
> Many thanks again,
> Hadrian
>
>
> On Aug 19, 2009, at 7:26 AM, Christian Schneider wrote:
>
>> I just checked out the head (hope this is still the release 2.0.0
>> state) and did a full build. I got three test failures in camel-core.
>> Is this ok?
>>
>> I built on Windows Vista, JDK 1.6.0_14 and maven 2.2.0.
>>
>> Greetings
>>
>> Christian
>> Failure Details
>>
>> <icon_warning_sml.gif> testCannotDeleteFile
>>
>> junit.framework.AssertionFailedError: Should have thrown an exception
>>
>> org.apache.camel.component.file.strategy.GenericFileDeleteProcessStrategyTest:125
>>
>> <icon_warning_sml.gif> testCacheStreamToFileAndNotCloseStream
>>
>> junit.framework.AssertionFailedError: we should have no temp file
>> expected:<1> but was:<0>
>>
>> org.apache.camel.converter.stream.CachedOutputStreamTest:117
>> <icon_warning_sml.gif> testRouteIsCorrectAtRuntime
>>
>> junit.framework.AssertionFailedError: expected:<4> but was:<1>
>>
>> org.apache.camel.processor.ChoiceWithEndTest:39
>>
>>
>> Hadrian Zbarcea schrieb:
>>>
>>> The first release candidate of apache-camel-2.0.0 is out with 61 new
>>> features, improvements and bug fixes. This concludes more than one
>>> year of efforts to bring a new and improved Apache Camel. Many
>>> thanks to everybody in the community who contributed to this release.
>>>
>>> Please find the staging repo here:
>>> https://repository.apache.org/content/groups/staging/org/apache/camel/
>>>
>>> The tarballs are here
>>> https://repository.apache.org/content/groups/staging/org/apache/camel/apache-camel/2.0.0/
>>>
>>>
>>> Please vote to approve this release binary
>>>
>>> [ ] +1 Release the binary as Apache Camel 2.0-M3
>>> [ ] -1 Veto the release (provide specific comments)
>>> Vote is open for 72 hours.
>>>
>>>
>>> The Camel Riders
>>
>
>
Re: [VOTE] Release Apache Camel 2.0.0
Posted by Christian Schneider <ch...@die-schneider.net>.
Hi Hadrian,
I have digged into the next failure.
CachedOutputStreamTest.testCacheStreamToFileAndNotCloseStream
At the end of the test the temporary file is expected to be deleted. But
honestly I do not understand how this could work.
The test first calls exchange.getUnitOfWork().done(exchange);. This will
try to delete the file but the delete will fail as the stream is still open.
Then it calls ((InputStream)cache).close(); which will close the stream.
The problem is that now the file will not be deleted again.
I have swapped the two commands and the test works but I think this is
wrong as the test seems to explicitly test the fact that close is not
called before done.
Can anyone clarify what this test tries to do?
Btw. I think this test works on unix as the delete on the file will also
work when the file is opened. On windows this does not work.
Greetings
Christian
Hadrian Zbarcea schrieb:
> Hi Christian,
>
> Thanks for doing the tests. No, it is not ok, but all the tests are
> passing consistently for a few weeks on mac and linux. That code is
> not quite platform specific (well, except for the Windows fs). Could
> you *please* take a look a bit more and maybe figure out what the
> issue is? Is it a fluke, a timing issue, a more serious problem, does
> it work from an IDE like Eclipse?
>
> Imho this is not a blocker for this release (yet), but it's good to know.
>
> Many thanks again,
> Hadrian
>
>
> On Aug 19, 2009, at 7:26 AM, Christian Schneider wrote:
>
>> I just checked out the head (hope this is still the release 2.0.0
>> state) and did a full build. I got three test failures in camel-core.
>> Is this ok?
>>
>> I built on Windows Vista, JDK 1.6.0_14 and maven 2.2.0.
>>
>> Greetings
>>
>> Christian
>> Failure Details
>>
>> <icon_warning_sml.gif> testCannotDeleteFile
>>
>> junit.framework.AssertionFailedError: Should have thrown an exception
>>
>> org.apache.camel.component.file.strategy.GenericFileDeleteProcessStrategyTest:125
>>
>> <icon_warning_sml.gif> testCacheStreamToFileAndNotCloseStream
>>
>> junit.framework.AssertionFailedError: we should have no temp file
>> expected:<1> but was:<0>
>>
>> org.apache.camel.converter.stream.CachedOutputStreamTest:117
>> <icon_warning_sml.gif> testRouteIsCorrectAtRuntime
>>
>> junit.framework.AssertionFailedError: expected:<4> but was:<1>
>>
>> org.apache.camel.processor.ChoiceWithEndTest:39
>>
>>
>> Hadrian Zbarcea schrieb:
>>>
>>> The first release candidate of apache-camel-2.0.0 is out with 61 new
>>> features, improvements and bug fixes. This concludes more than one
>>> year of efforts to bring a new and improved Apache Camel. Many
>>> thanks to everybody in the community who contributed to this release.
>>>
>>> Please find the staging repo here:
>>> https://repository.apache.org/content/groups/staging/org/apache/camel/
>>>
>>> The tarballs are here
>>> https://repository.apache.org/content/groups/staging/org/apache/camel/apache-camel/2.0.0/
>>>
>>>
>>> Please vote to approve this release binary
>>>
>>> [ ] +1 Release the binary as Apache Camel 2.0-M3
>>> [ ] -1 Veto the release (provide specific comments)
>>> Vote is open for 72 hours.
>>>
>>>
>>> The Camel Riders
>>
>
>
Re: [VOTE] Release Apache Camel 2.0.0
Posted by Claus Ibsen <cl...@gmail.com>.
On Thu, Aug 20, 2009 at 3:43 PM, Christian
Schneider<ch...@die-schneider.net> wrote:
> Hi Hadrian and Claus,
>
> I have created a ticket https://issues.apache.org/activemq/browse/CAMEL-1924
> and attached all necessary mails from this thread.
>
Thanks a lot I guess most of these is easy to fix. If you have time
patches is also much welcome as you got the windows system.
Otherwise we gotta wait for the CI servers to do a run and test on the
windows boxes :)
> btw: You guys did some great work with the new camel release. We are already
> using the 2.0.0-M3 in production and looking forward to the final 2.0.0.
>
Glad to know its already in production. You are not the first on a Mx
in production but glad it works for you.
> Greetings
>
> Christian
>
>
> Hadrian Zbarcea schrieb:
>>
>> Awesome work Christian, thank you for the extra effort. As Claus said,
>> we'll get this fixed as soon as 2.0 is out the door.
>>
>> Cheers,
>> Hadrian
>>
>> On Aug 20, 2009, at 8:25 AM, Claus Ibsen wrote:
>>
>>> On Thu, Aug 20, 2009 at 2:22 PM, Christian
>>> Schneider<ch...@die-schneider.net> wrote:
>>>>
>>>> Hi Hadrian,
>>>>
>>>> I have just debugged the last failure:
>>>>
>>>> org.apache.camel.processor.ChoiceWithEndTest.testRouteIsCorrectAtRuntime
>>>>
>>>> It checks for 4 nodes but only gets one.
>>>>
>>>> The reason is that it checks the wrong route. When I change the line
>>>> Navigate<Processor> nav = context.getRoutes().get(0).navigate();
>>>> to
>>>> Navigate<Processor> nav = context.getRoutes().get(1).navigate();
>>>> then it works. So it seems the sequence of the routes is not the same
>>>> for
>>>> all systems. Perhaps it would be better to use another way of getting
>>>> the
>>>> route from the camel context.
>>>>
>>>> So after I have checked all the failures I would also say there is no
>>>> blocker.
>>>> Should I create jira tickets for the three problems?
>>>
>>> Just create one ticket as the issue are minor. We will get it fixed
>>> post 2.0 release.
>>>
>>>
>>>>
>>>> Greetings
>>>>
>>>> Christian
>>>>
>>>> Hadrian Zbarcea schrieb:
>>>>>
>>>>> Hi Christian,
>>>>>
>>>>> Thanks for doing the tests. No, it is not ok, but all the tests are
>>>>> passing consistently for a few weeks on mac and linux. That code is
>>>>> not
>>>>> quite platform specific (well, except for the Windows fs). Could you
>>>>> *please* take a look a bit more and maybe figure out what the issue is?
>>>>> Is
>>>>> it a fluke, a timing issue, a more serious problem, does it work from
>>>>> an IDE
>>>>> like Eclipse?
>>>>>
>>>>> Imho this is not a blocker for this release (yet), but it's good to
>>>>> know.
>>>>>
>>>>> Many thanks again,
>>>>> Hadrian
>>>>>
>>>>>
>>>>> On Aug 19, 2009, at 7:26 AM, Christian Schneider wrote:
>>>>>
>>>>>> I just checked out the head (hope this is still the release 2.0.0
>>>>>> state)
>>>>>> and did a full build. I got three test failures in camel-core. Is this
>>>>>> ok?
>>>>>>
>>>>>> I built on Windows Vista, JDK 1.6.0_14 and maven 2.2.0.
>>>>>>
>>>>>> Greetings
>>>>>>
>>>>>> Christian
>>>>>> Failure Details
>>>>>>
>>>>>> <icon_warning_sml.gif> testCannotDeleteFile
>>>>>>
>>>>>> junit.framework.AssertionFailedError: Should have thrown an exception
>>>>>>
>>>>>>
>>>>>>
>>>>>> org.apache.camel.component.file.strategy.GenericFileDeleteProcessStrategyTest:125
>>>>>> <icon_warning_sml.gif> testCacheStreamToFileAndNotCloseStream
>>>>>>
>>>>>> junit.framework.AssertionFailedError: we should have no temp file
>>>>>> expected:<1> but was:<0>
>>>>>>
>>>>>> org.apache.camel.converter.stream.CachedOutputStreamTest:117
>>>>>> <icon_warning_sml.gif> testRouteIsCorrectAtRuntime
>>>>>>
>>>>>> junit.framework.AssertionFailedError: expected:<4> but was:<1>
>>>>>>
>>>>>> org.apache.camel.processor.ChoiceWithEndTest:39
>>>>>>
>>>>>>
>>>>>> Hadrian Zbarcea schrieb:
>>>>>>>
>>>>>>> The first release candidate of apache-camel-2.0.0 is out with 61 new
>>>>>>> features, improvements and bug fixes. This concludes more than one
>>>>>>> year of
>>>>>>> efforts to bring a new and improved Apache Camel. Many thanks to
>>>>>>> everybody
>>>>>>> in the community who contributed to this release.
>>>>>>>
>>>>>>> Please find the staging repo here:
>>>>>>>
>>>>>>> https://repository.apache.org/content/groups/staging/org/apache/camel/
>>>>>>>
>>>>>>> The tarballs are here
>>>>>>>
>>>>>>>
>>>>>>> https://repository.apache.org/content/groups/staging/org/apache/camel/apache-camel/2.0.0/
>>>>>>>
>>>>>>> Please vote to approve this release binary
>>>>>>>
>>>>>>> [ ] +1 Release the binary as Apache Camel 2.0-M3
>>>>>>> [ ] -1 Veto the release (provide specific comments)
>>>>>>> Vote is open for 72 hours.
>>>>>>>
>>>>>>>
>>>>>>> The Camel Riders
>>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>
>>>
>>>
>>> --
>>> Claus Ibsen
>>> Apache Camel Committer
>>>
>>> Open Source Integration: http://fusesource.com
>>> Blog: http://davsclaus.blogspot.com/
>>> Twitter: http://twitter.com/davsclaus
>>
>>
>
>
--
Claus Ibsen
Apache Camel Committer
Open Source Integration: http://fusesource.com
Blog: http://davsclaus.blogspot.com/
Twitter: http://twitter.com/davsclaus
Re: [VOTE] Release Apache Camel 2.0.0
Posted by Christian Schneider <ch...@die-schneider.net>.
Hi Hadrian and Claus,
I have created a ticket
https://issues.apache.org/activemq/browse/CAMEL-1924 and attached all
necessary mails from this thread.
btw: You guys did some great work with the new camel release. We are
already using the 2.0.0-M3 in production and looking forward to the
final 2.0.0.
Greetings
Christian
Hadrian Zbarcea schrieb:
> Awesome work Christian, thank you for the extra effort. As Claus
> said, we'll get this fixed as soon as 2.0 is out the door.
>
> Cheers,
> Hadrian
>
> On Aug 20, 2009, at 8:25 AM, Claus Ibsen wrote:
>
>> On Thu, Aug 20, 2009 at 2:22 PM, Christian
>> Schneider<ch...@die-schneider.net> wrote:
>>> Hi Hadrian,
>>>
>>> I have just debugged the last failure:
>>>
>>> org.apache.camel.processor.ChoiceWithEndTest.testRouteIsCorrectAtRuntime
>>>
>>>
>>> It checks for 4 nodes but only gets one.
>>>
>>> The reason is that it checks the wrong route. When I change the line
>>> Navigate<Processor> nav = context.getRoutes().get(0).navigate();
>>> to
>>> Navigate<Processor> nav = context.getRoutes().get(1).navigate();
>>> then it works. So it seems the sequence of the routes is not the
>>> same for
>>> all systems. Perhaps it would be better to use another way of
>>> getting the
>>> route from the camel context.
>>>
>>> So after I have checked all the failures I would also say there is no
>>> blocker.
>>> Should I create jira tickets for the three problems?
>>
>> Just create one ticket as the issue are minor. We will get it fixed
>> post 2.0 release.
>>
>>
>>>
>>> Greetings
>>>
>>> Christian
>>>
>>> Hadrian Zbarcea schrieb:
>>>>
>>>> Hi Christian,
>>>>
>>>> Thanks for doing the tests. No, it is not ok, but all the tests are
>>>> passing consistently for a few weeks on mac and linux. That code
>>>> is not
>>>> quite platform specific (well, except for the Windows fs). Could you
>>>> *please* take a look a bit more and maybe figure out what the issue
>>>> is? Is
>>>> it a fluke, a timing issue, a more serious problem, does it work
>>>> from an IDE
>>>> like Eclipse?
>>>>
>>>> Imho this is not a blocker for this release (yet), but it's good to
>>>> know.
>>>>
>>>> Many thanks again,
>>>> Hadrian
>>>>
>>>>
>>>> On Aug 19, 2009, at 7:26 AM, Christian Schneider wrote:
>>>>
>>>>> I just checked out the head (hope this is still the release 2.0.0
>>>>> state)
>>>>> and did a full build. I got three test failures in camel-core. Is
>>>>> this ok?
>>>>>
>>>>> I built on Windows Vista, JDK 1.6.0_14 and maven 2.2.0.
>>>>>
>>>>> Greetings
>>>>>
>>>>> Christian
>>>>> Failure Details
>>>>>
>>>>> <icon_warning_sml.gif> testCannotDeleteFile
>>>>>
>>>>> junit.framework.AssertionFailedError: Should have thrown an exception
>>>>>
>>>>>
>>>>> org.apache.camel.component.file.strategy.GenericFileDeleteProcessStrategyTest:125
>>>>>
>>>>> <icon_warning_sml.gif> testCacheStreamToFileAndNotCloseStream
>>>>>
>>>>> junit.framework.AssertionFailedError: we should have no temp file
>>>>> expected:<1> but was:<0>
>>>>>
>>>>> org.apache.camel.converter.stream.CachedOutputStreamTest:117
>>>>> <icon_warning_sml.gif> testRouteIsCorrectAtRuntime
>>>>>
>>>>> junit.framework.AssertionFailedError: expected:<4> but was:<1>
>>>>>
>>>>> org.apache.camel.processor.ChoiceWithEndTest:39
>>>>>
>>>>>
>>>>> Hadrian Zbarcea schrieb:
>>>>>>
>>>>>> The first release candidate of apache-camel-2.0.0 is out with 61 new
>>>>>> features, improvements and bug fixes. This concludes more than
>>>>>> one year of
>>>>>> efforts to bring a new and improved Apache Camel. Many thanks to
>>>>>> everybody
>>>>>> in the community who contributed to this release.
>>>>>>
>>>>>> Please find the staging repo here:
>>>>>> https://repository.apache.org/content/groups/staging/org/apache/camel/
>>>>>>
>>>>>>
>>>>>> The tarballs are here
>>>>>>
>>>>>> https://repository.apache.org/content/groups/staging/org/apache/camel/apache-camel/2.0.0/
>>>>>>
>>>>>>
>>>>>> Please vote to approve this release binary
>>>>>>
>>>>>> [ ] +1 Release the binary as Apache Camel 2.0-M3
>>>>>> [ ] -1 Veto the release (provide specific comments)
>>>>>> Vote is open for 72 hours.
>>>>>>
>>>>>>
>>>>>> The Camel Riders
>>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>>
>> --
>> Claus Ibsen
>> Apache Camel Committer
>>
>> Open Source Integration: http://fusesource.com
>> Blog: http://davsclaus.blogspot.com/
>> Twitter: http://twitter.com/davsclaus
>
>
Re: [VOTE] Release Apache Camel 2.0.0
Posted by Hadrian Zbarcea <hz...@gmail.com>.
Awesome work Christian, thank you for the extra effort. As Claus
said, we'll get this fixed as soon as 2.0 is out the door.
Cheers,
Hadrian
On Aug 20, 2009, at 8:25 AM, Claus Ibsen wrote:
> On Thu, Aug 20, 2009 at 2:22 PM, Christian
> Schneider<ch...@die-schneider.net> wrote:
>> Hi Hadrian,
>>
>> I have just debugged the last failure:
>>
>> org
>> .apache.camel.processor.ChoiceWithEndTest.testRouteIsCorrectAtRuntime
>>
>> It checks for 4 nodes but only gets one.
>>
>> The reason is that it checks the wrong route. When I change the line
>> Navigate<Processor> nav =
>> context.getRoutes().get(0).navigate();
>> to
>> Navigate<Processor> nav =
>> context.getRoutes().get(1).navigate();
>> then it works. So it seems the sequence of the routes is not the
>> same for
>> all systems. Perhaps it would be better to use another way of
>> getting the
>> route from the camel context.
>>
>> So after I have checked all the failures I would also say there is no
>> blocker.
>> Should I create jira tickets for the three problems?
>
> Just create one ticket as the issue are minor. We will get it fixed
> post 2.0 release.
>
>
>>
>> Greetings
>>
>> Christian
>>
>> Hadrian Zbarcea schrieb:
>>>
>>> Hi Christian,
>>>
>>> Thanks for doing the tests. No, it is not ok, but all the tests are
>>> passing consistently for a few weeks on mac and linux. That code
>>> is not
>>> quite platform specific (well, except for the Windows fs). Could
>>> you
>>> *please* take a look a bit more and maybe figure out what the
>>> issue is? Is
>>> it a fluke, a timing issue, a more serious problem, does it work
>>> from an IDE
>>> like Eclipse?
>>>
>>> Imho this is not a blocker for this release (yet), but it's good
>>> to know.
>>>
>>> Many thanks again,
>>> Hadrian
>>>
>>>
>>> On Aug 19, 2009, at 7:26 AM, Christian Schneider wrote:
>>>
>>>> I just checked out the head (hope this is still the release 2.0.0
>>>> state)
>>>> and did a full build. I got three test failures in camel-core. Is
>>>> this ok?
>>>>
>>>> I built on Windows Vista, JDK 1.6.0_14 and maven 2.2.0.
>>>>
>>>> Greetings
>>>>
>>>> Christian
>>>> Failure Details
>>>>
>>>> <icon_warning_sml.gif> testCannotDeleteFile
>>>>
>>>> junit.framework.AssertionFailedError: Should have thrown an
>>>> exception
>>>>
>>>>
>>>> org
>>>> .apache
>>>> .camel
>>>> .component.file.strategy.GenericFileDeleteProcessStrategyTest:125
>>>> <icon_warning_sml.gif> testCacheStreamToFileAndNotCloseStream
>>>>
>>>> junit.framework.AssertionFailedError: we should have no temp file
>>>> expected:<1> but was:<0>
>>>>
>>>> org.apache.camel.converter.stream.CachedOutputStreamTest:117
>>>> <icon_warning_sml.gif> testRouteIsCorrectAtRuntime
>>>>
>>>> junit.framework.AssertionFailedError: expected:<4> but was:<1>
>>>>
>>>> org.apache.camel.processor.ChoiceWithEndTest:39
>>>>
>>>>
>>>> Hadrian Zbarcea schrieb:
>>>>>
>>>>> The first release candidate of apache-camel-2.0.0 is out with 61
>>>>> new
>>>>> features, improvements and bug fixes. This concludes more than
>>>>> one year of
>>>>> efforts to bring a new and improved Apache Camel. Many thanks
>>>>> to everybody
>>>>> in the community who contributed to this release.
>>>>>
>>>>> Please find the staging repo here:
>>>>> https://repository.apache.org/content/groups/staging/org/apache/camel/
>>>>>
>>>>> The tarballs are here
>>>>>
>>>>> https://repository.apache.org/content/groups/staging/org/apache/camel/apache-camel/2.0.0/
>>>>>
>>>>> Please vote to approve this release binary
>>>>>
>>>>> [ ] +1 Release the binary as Apache Camel 2.0-M3
>>>>> [ ] -1 Veto the release (provide specific comments)
>>>>> Vote is open for 72 hours.
>>>>>
>>>>>
>>>>> The Camel Riders
>>>>
>>>
>>>
>>
>>
>
>
>
> --
> Claus Ibsen
> Apache Camel Committer
>
> Open Source Integration: http://fusesource.com
> Blog: http://davsclaus.blogspot.com/
> Twitter: http://twitter.com/davsclaus
Re: [VOTE] Release Apache Camel 2.0.0
Posted by Claus Ibsen <cl...@gmail.com>.
On Thu, Aug 20, 2009 at 2:22 PM, Christian
Schneider<ch...@die-schneider.net> wrote:
> Hi Hadrian,
>
> I have just debugged the last failure:
>
> org.apache.camel.processor.ChoiceWithEndTest.testRouteIsCorrectAtRuntime
>
> It checks for 4 nodes but only gets one.
>
> The reason is that it checks the wrong route. When I change the line
> Navigate<Processor> nav = context.getRoutes().get(0).navigate();
> to
> Navigate<Processor> nav = context.getRoutes().get(1).navigate();
> then it works. So it seems the sequence of the routes is not the same for
> all systems. Perhaps it would be better to use another way of getting the
> route from the camel context.
>
> So after I have checked all the failures I would also say there is no
> blocker.
> Should I create jira tickets for the three problems?
Just create one ticket as the issue are minor. We will get it fixed
post 2.0 release.
>
> Greetings
>
> Christian
>
> Hadrian Zbarcea schrieb:
>>
>> Hi Christian,
>>
>> Thanks for doing the tests. No, it is not ok, but all the tests are
>> passing consistently for a few weeks on mac and linux. That code is not
>> quite platform specific (well, except for the Windows fs). Could you
>> *please* take a look a bit more and maybe figure out what the issue is? Is
>> it a fluke, a timing issue, a more serious problem, does it work from an IDE
>> like Eclipse?
>>
>> Imho this is not a blocker for this release (yet), but it's good to know.
>>
>> Many thanks again,
>> Hadrian
>>
>>
>> On Aug 19, 2009, at 7:26 AM, Christian Schneider wrote:
>>
>>> I just checked out the head (hope this is still the release 2.0.0 state)
>>> and did a full build. I got three test failures in camel-core. Is this ok?
>>>
>>> I built on Windows Vista, JDK 1.6.0_14 and maven 2.2.0.
>>>
>>> Greetings
>>>
>>> Christian
>>> Failure Details
>>>
>>> <icon_warning_sml.gif> testCannotDeleteFile
>>>
>>> junit.framework.AssertionFailedError: Should have thrown an exception
>>>
>>>
>>> org.apache.camel.component.file.strategy.GenericFileDeleteProcessStrategyTest:125
>>> <icon_warning_sml.gif> testCacheStreamToFileAndNotCloseStream
>>>
>>> junit.framework.AssertionFailedError: we should have no temp file
>>> expected:<1> but was:<0>
>>>
>>> org.apache.camel.converter.stream.CachedOutputStreamTest:117
>>> <icon_warning_sml.gif> testRouteIsCorrectAtRuntime
>>>
>>> junit.framework.AssertionFailedError: expected:<4> but was:<1>
>>>
>>> org.apache.camel.processor.ChoiceWithEndTest:39
>>>
>>>
>>> Hadrian Zbarcea schrieb:
>>>>
>>>> The first release candidate of apache-camel-2.0.0 is out with 61 new
>>>> features, improvements and bug fixes. This concludes more than one year of
>>>> efforts to bring a new and improved Apache Camel. Many thanks to everybody
>>>> in the community who contributed to this release.
>>>>
>>>> Please find the staging repo here:
>>>> https://repository.apache.org/content/groups/staging/org/apache/camel/
>>>>
>>>> The tarballs are here
>>>>
>>>> https://repository.apache.org/content/groups/staging/org/apache/camel/apache-camel/2.0.0/
>>>>
>>>> Please vote to approve this release binary
>>>>
>>>> [ ] +1 Release the binary as Apache Camel 2.0-M3
>>>> [ ] -1 Veto the release (provide specific comments)
>>>> Vote is open for 72 hours.
>>>>
>>>>
>>>> The Camel Riders
>>>
>>
>>
>
>
--
Claus Ibsen
Apache Camel Committer
Open Source Integration: http://fusesource.com
Blog: http://davsclaus.blogspot.com/
Twitter: http://twitter.com/davsclaus
Re: [VOTE] Release Apache Camel 2.0.0
Posted by Christian Schneider <ch...@die-schneider.net>.
Hi Hadrian,
I have just debugged the last failure:
org.apache.camel.processor.ChoiceWithEndTest.testRouteIsCorrectAtRuntime
It checks for 4 nodes but only gets one.
The reason is that it checks the wrong route. When I change the line
Navigate<Processor> nav = context.getRoutes().get(0).navigate();
to
Navigate<Processor> nav = context.getRoutes().get(1).navigate();
then it works. So it seems the sequence of the routes is not the same
for all systems. Perhaps it would be better to use another way of
getting the route from the camel context.
So after I have checked all the failures I would also say there is no
blocker.
Should I create jira tickets for the three problems?
Greetings
Christian
Hadrian Zbarcea schrieb:
> Hi Christian,
>
> Thanks for doing the tests. No, it is not ok, but all the tests are
> passing consistently for a few weeks on mac and linux. That code is
> not quite platform specific (well, except for the Windows fs). Could
> you *please* take a look a bit more and maybe figure out what the
> issue is? Is it a fluke, a timing issue, a more serious problem, does
> it work from an IDE like Eclipse?
>
> Imho this is not a blocker for this release (yet), but it's good to know.
>
> Many thanks again,
> Hadrian
>
>
> On Aug 19, 2009, at 7:26 AM, Christian Schneider wrote:
>
>> I just checked out the head (hope this is still the release 2.0.0
>> state) and did a full build. I got three test failures in camel-core.
>> Is this ok?
>>
>> I built on Windows Vista, JDK 1.6.0_14 and maven 2.2.0.
>>
>> Greetings
>>
>> Christian
>> Failure Details
>>
>> <icon_warning_sml.gif> testCannotDeleteFile
>>
>> junit.framework.AssertionFailedError: Should have thrown an exception
>>
>> org.apache.camel.component.file.strategy.GenericFileDeleteProcessStrategyTest:125
>>
>> <icon_warning_sml.gif> testCacheStreamToFileAndNotCloseStream
>>
>> junit.framework.AssertionFailedError: we should have no temp file
>> expected:<1> but was:<0>
>>
>> org.apache.camel.converter.stream.CachedOutputStreamTest:117
>> <icon_warning_sml.gif> testRouteIsCorrectAtRuntime
>>
>> junit.framework.AssertionFailedError: expected:<4> but was:<1>
>>
>> org.apache.camel.processor.ChoiceWithEndTest:39
>>
>>
>> Hadrian Zbarcea schrieb:
>>>
>>> The first release candidate of apache-camel-2.0.0 is out with 61 new
>>> features, improvements and bug fixes. This concludes more than one
>>> year of efforts to bring a new and improved Apache Camel. Many
>>> thanks to everybody in the community who contributed to this release.
>>>
>>> Please find the staging repo here:
>>> https://repository.apache.org/content/groups/staging/org/apache/camel/
>>>
>>> The tarballs are here
>>> https://repository.apache.org/content/groups/staging/org/apache/camel/apache-camel/2.0.0/
>>>
>>>
>>> Please vote to approve this release binary
>>>
>>> [ ] +1 Release the binary as Apache Camel 2.0-M3
>>> [ ] -1 Veto the release (provide specific comments)
>>> Vote is open for 72 hours.
>>>
>>>
>>> The Camel Riders
>>
>
>
Re: [VOTE] Release Apache Camel 2.0.0
Posted by Hadrian Zbarcea <hz...@gmail.com>.
Hi Christian,
Thanks for doing the tests. No, it is not ok, but all the tests are
passing consistently for a few weeks on mac and linux. That code is
not quite platform specific (well, except for the Windows fs). Could
you *please* take a look a bit more and maybe figure out what the
issue is? Is it a fluke, a timing issue, a more serious problem, does
it work from an IDE like Eclipse?
Imho this is not a blocker for this release (yet), but it's good to
know.
Many thanks again,
Hadrian
On Aug 19, 2009, at 7:26 AM, Christian Schneider wrote:
> I just checked out the head (hope this is still the release 2.0.0
> state) and did a full build. I got three test failures in camel-
> core. Is this ok?
>
> I built on Windows Vista, JDK 1.6.0_14 and maven 2.2.0.
>
> Greetings
>
> Christian
> Failure Details
>
> <icon_warning_sml.gif> testCannotDeleteFile
>
> junit.framework.AssertionFailedError: Should have thrown an exception
>
> org
> .apache
> .camel.component.file.strategy.GenericFileDeleteProcessStrategyTest:
> 125
> <icon_warning_sml.gif> testCacheStreamToFileAndNotCloseStream
>
> junit.framework.AssertionFailedError: we should have no temp file
> expected:<1> but was:<0>
>
> org.apache.camel.converter.stream.CachedOutputStreamTest:117
> <icon_warning_sml.gif> testRouteIsCorrectAtRuntime
>
> junit.framework.AssertionFailedError: expected:<4> but was:<1>
>
> org.apache.camel.processor.ChoiceWithEndTest:39
>
>
> Hadrian Zbarcea schrieb:
>>
>> The first release candidate of apache-camel-2.0.0 is out with 61
>> new features, improvements and bug fixes. This concludes more than
>> one year of efforts to bring a new and improved Apache Camel. Many
>> thanks to everybody in the community who contributed to this release.
>>
>> Please find the staging repo here:
>> https://repository.apache.org/content/groups/staging/org/apache/
>> camel/
>>
>> The tarballs are here
>> https://repository.apache.org/content/groups/staging/org/apache/camel/apache-camel/2.0.0/
>>
>> Please vote to approve this release binary
>>
>> [ ] +1 Release the binary as Apache Camel 2.0-M3
>> [ ] -1 Veto the release (provide specific comments)
>> Vote is open for 72 hours.
>>
>>
>> The Camel Riders
>
Re: [VOTE] Release Apache Camel 2.0.0
Posted by Christian Schneider <ch...@die-schneider.net>.
I just checked out the head (hope this is still the release 2.0.0 state)
and did a full build. I got three test failures in camel-core. Is this ok?
I built on Windows Vista, JDK 1.6.0_14 and maven 2.2.0.
Greetings
Christian
Failure Details
testCannotDeleteFile
junit.framework.AssertionFailedError: Should have thrown an exception
org.apache.camel.component.file.strategy.GenericFileDeleteProcessStrategyTest:125
testCacheStreamToFileAndNotCloseStream
junit.framework.AssertionFailedError: we should have no temp file
expected:<1> but was:<0>
org.apache.camel.converter.stream.CachedOutputStreamTest:117
testRouteIsCorrectAtRuntime
junit.framework.AssertionFailedError: expected:<4> but was:<1>
org.apache.camel.processor.ChoiceWithEndTest:39
Hadrian Zbarcea schrieb:
> The first release candidate of apache-camel-2.0.0 is out with 61 new
> features, improvements and bug fixes. This concludes more than one
> year of efforts to bring a new and improved Apache Camel. Many thanks
> to everybody in the community who contributed to this release.
>
> Please find the staging repo here:
> https://repository.apache.org/content/groups/staging/org/apache/camel/
>
> The tarballs are here
> https://repository.apache.org/content/groups/staging/org/apache/camel/apache-camel/2.0.0/
>
>
> Please vote to approve this release binary
>
> [ ] +1 Release the binary as Apache Camel 2.0-M3
> [ ] -1 Veto the release (provide specific comments)
> Vote is open for 72 hours.
>
>
> The Camel Riders
Re: [VOTE] Release Apache Camel 2.0.0
Posted by Charles Moulliard <cm...@gmail.com>.
+1
Charles Moulliard
Senior Enterprise Architect
Apache Camel Committer
*****************************
blog : http://cmoulliard.blogspot.com
On Tue, Aug 18, 2009 at 11:39 PM, Hadrian Zbarcea <hz...@gmail.com>wrote:
> The first release candidate of apache-camel-2.0.0 is out with 61 new
> features, improvements and bug fixes. This concludes more than one year of
> efforts to bring a new and improved Apache Camel. Many thanks to everybody
> in the community who contributed to this release.
>
> Please find the staging repo here:
> https://repository.apache.org/content/groups/staging/org/apache/camel/
>
> The tarballs are here
>
> https://repository.apache.org/content/groups/staging/org/apache/camel/apache-camel/2.0.0/
>
> Please vote to approve this release binary
>
> [ ] +1 Release the binary as Apache Camel 2.0-M3
> [ ] -1 Veto the release (provide specific comments)
> Vote is open for 72 hours.
>
>
> The Camel Riders
Re: [VOTE] Release Apache Camel 2.0.0
Posted by Hadrian Zbarcea <hz...@gmail.com>.
James,
Yes, my bad, that was cut 'n' paste. The release is 2.0.0.
And yes, the release note will include all the diffs from the 1.x line.
Hadrian
On Aug 19, 2009, at 9:11 AM, James Strachan wrote:
> +1
>
> More below...
>
>
>
> 2009/8/18 Hadrian Zbarcea <hz...@gmail.com>:
>> The first release candidate of apache-camel-2.0.0 is out with 61 new
>> features, improvements and bug fixes.
>
> When the release notes are completed for 2.0.0
> http://camel.apache.org/camel-200-release.html
>
> I'm assuming we're going to add up all the issues resolved from M1,
> M2, M3 right (368, 222, 109) so that the release goes out with a big
> bang (rather than just focussing on the 61 issues resolved since M3).
>
>
>> Please vote to approve this release binary
>>
>> [ ] +1 Release the binary as Apache Camel 2.0-M3
>
> BTW this is a cut and paste right; this vote is for the actual 2.0.0
> release, not 2.0-M3 which went out last month :)
>
> --
> James
> -------
> http://macstrac.blogspot.com/
>
> Open Source Integration
> http://fusesource.com/
Re: [VOTE] Release Apache Camel 2.0.0
Posted by William Tam <em...@gmail.com>.
+1
On Wed, Aug 19, 2009 at 9:11 AM, James Strachan<ja...@gmail.com> wrote:
> +1
>
> More below...
>
>
>
> 2009/8/18 Hadrian Zbarcea <hz...@gmail.com>:
>> The first release candidate of apache-camel-2.0.0 is out with 61 new
>> features, improvements and bug fixes.
>
> When the release notes are completed for 2.0.0
> http://camel.apache.org/camel-200-release.html
>
> I'm assuming we're going to add up all the issues resolved from M1,
> M2, M3 right (368, 222, 109) so that the release goes out with a big
> bang (rather than just focussing on the 61 issues resolved since M3).
>
>
>> Please vote to approve this release binary
>>
>> [ ] +1 Release the binary as Apache Camel 2.0-M3
>
> BTW this is a cut and paste right; this vote is for the actual 2.0.0
> release, not 2.0-M3 which went out last month :)
>
> --
> James
> -------
> http://macstrac.blogspot.com/
>
> Open Source Integration
> http://fusesource.com/
>
Re: [VOTE] Release Apache Camel 2.0.0
Posted by James Strachan <ja...@gmail.com>.
+1
More below...
2009/8/18 Hadrian Zbarcea <hz...@gmail.com>:
> The first release candidate of apache-camel-2.0.0 is out with 61 new
> features, improvements and bug fixes.
When the release notes are completed for 2.0.0
http://camel.apache.org/camel-200-release.html
I'm assuming we're going to add up all the issues resolved from M1,
M2, M3 right (368, 222, 109) so that the release goes out with a big
bang (rather than just focussing on the 61 issues resolved since M3).
> Please vote to approve this release binary
>
> [ ] +1 Release the binary as Apache Camel 2.0-M3
BTW this is a cut and paste right; this vote is for the actual 2.0.0
release, not 2.0-M3 which went out last month :)
--
James
-------
http://macstrac.blogspot.com/
Open Source Integration
http://fusesource.com/