Hi Claus ,
Hi
Welcome to the community.
Thanks ;-).. quite lively in here !
I am afraid not as skipping dot files is hardcoded into the component,
as its supposed to skip hidden files.
We could of course add some option to the component, but we should
also avoid "adding to many features" into the product.
So maybe you can tell a bit more about your use case for processing those files?
I understand completly the "safety first" rule of adding to many
features ;-).
The fact that Camel moves processed files (moved or so) into a .camel file
requires that dotted file to be ignored... otherwise this could lead up to
reprocessing the file..... a nice endless loop.
My test case was indeed to re-process Eclipse .project files (generated
either
by the eclipse and the m2eclipse plugins of Maven), as it does not take into
account web app overlays (ie : a web application that depends on another
webapp).
My goal was to use Camel, in a Maven plugin to "reprocess" properly the
generated
Eclipse info files... (quite ambitious I agree... but hey, got to try it ;-)
Is it be possible for me to extend the existing File class into another
one where I could
"overide" the filename match method ?
Thanks for the reply
*Pierre-yves*
