[
https://issues.apache.org/jira/browse/CAMEL-12563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16671593#comment-16671593
]
Dmitry Volodin commented on CAMEL-12563:
----------------------------------------
[[email protected]], it would be nice to move your work to the forked
Apache Camel repo in separate branch.
After first look, you need to change package structure to common name, as well
as ASF license headers for all files.
If you would like to test against real Linux based system with Samba support,
you can use camel-testcontainers for it. Please see camel-nats or camel-consul
as example of using Docker containers for tests.
> Samba 2 Component
> -----------------
>
> Key: CAMEL-12563
> URL: https://issues.apache.org/jira/browse/CAMEL-12563
> Project: Camel
> Issue Type: Task
> Reporter: Juraj Borza
> Priority: Major
>
> Hi,
> I've developed a successor component *camel-smbj* to the current camel-jcifs
> as the former doesn't support Samba 2, and SMB1 is vulnerable and soon to be
> unsupported.
> The code currently lives here: [https://github.com/jborza/camel-smbj]
> It uses smbj [https://github.com/hierynomus/smbj] for the SMB2 support
> Would it make sense to polish this some more and turn it into an official
> Camel (extras?) component?
> Cheers,
> Juraj
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
