Hi
I have made the switch. The NewFileComponent is now FileComponent and
default in Camel.
The old file component has been deleted.
Committed revision 744825.
Thanks a lot to Willem for help and taking care of the glitches on the
Windows platform.
On Fri, Feb 6, 2009 at 11:42 AM, Claus Ibsen
Hi
I enabled it on trunk right now:
New Revision: 741515
On Fri, Feb 6, 2009 at 9:39 AM, Claus Ibsen wrote:
> Hi
>
> I will change the code in trunk to use the NewFileComponent later this
> afternoon.
> Then we have the weekend for the team city servers to crunch on testing as
> well.
>
> Wil
Hi
I will change the code in trunk to use the NewFileComponent later this
afternoon.
Then we have the weekend for the team city servers to crunch on testing as well.
Willem fixes the last remaning issues on the windows box, and I think
I got the occasional failing ones on the HP/AIX boxes as well
On Thu, Feb 5, 2009 at 10:19 AM, Willem Jiang wrote:
> Hi Claus,
>
> I'm monitoring the tests in windows box for a while, now it looks good :)
>
> I just have th quick note for the NewFileComponent.
>
> If we plan to rename the newfile component to file component when all
> the file tests become s
Hi Claus,
I'm monitoring the tests in windows box for a while, now it looks good :)
I just have th quick note for the NewFileComponent.
If we plan to rename the newfile component to file component when all
the file tests become stable, we don't need to mark the FileComponent as
deprecated or we
Hi
In Camel 2.0 we have refactored the File component to leverage a VFS
within Camel itself (common code/interface is named GenericFileXXX)
As the file component is used extensivly within Camel itself and to
test all camel components it would be great if we could give it a test
drive on various O
