[
https://issues.apache.org/jira/browse/CAMEL-4321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13410464#comment-13410464
]
Henryk Konsek commented on CAMEL-4321:
--------------------------------------
Hi Pontus,
First of all I'd start with changing package name to the
org.apachextras.camel.component.jcifs .
The same with Maven artifacts (org.apache-extras.camel-extra:camel-cifs) naming
and parent POM inheritance (org.apache-extras.camel-extra:components).
Also build of the module fails (mvn install) due to the reference to some
config file in user home directory:
File configFile = new
File(System.getProperty("user.home")+File.separator+"camelsmb.prp");
We should be able to build module issuing just 'mvn install' so all resources
needed to run standard set of tests should be available for Maven (probably in
'resource' directory). You need probably to mock Samba resources access for
unit testing.
This is a good point to start from :) I'll take a closer look at the component
itself after my holidays.
> Create camel-jcifs component
> ----------------------------
>
> Key: CAMEL-4321
> URL: https://issues.apache.org/jira/browse/CAMEL-4321
> Project: Camel
> Issue Type: New Feature
> Reporter: Jean-Baptiste Onofré
> Assignee: Henryk Konsek
> Fix For: Future
>
>
> Currently, we don't have any component to use a CIFS/Samba share.
> Using jcifs, users will be able to use CIFS shares.
> This component is an extension of the file one (more or less like camel-ftp).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
