[
https://issues.apache.org/jira/browse/KARAF-3760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14570808#comment-14570808
]
ASF GitHub Bot commented on KARAF-3760:
---------------------------------------
GitHub user lars-n opened a pull request:
https://github.com/apache/karaf/pull/63
Moved karaf scripts away from filtered-resources to avoid filtering.
KARAF-3760 When I create a Karaf distribution using the karaf-maven-plugin
the bin/karaf and bin/karaf.bat script get filtered by the maven-resources
plugin. In my case JAVA_HOME gets replaced when creating a karaf-assembly.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/lars-n/karaf master
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/karaf/pull/63.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #63
----
commit d50b32a6f0af4cee6803ad2dce724548cba3a4b1
Author: Lars Neumann <[email protected]>
Date: 2015-06-03T12:36:53Z
Moved karaf scripts away from filtered-resources to avoid filtering.
JAVA_HOME otherwise gets replaced.
----
> Can't ssh to Karaf when using the karaf-maven-plugin
> ----------------------------------------------------
>
> Key: KARAF-3760
> URL: https://issues.apache.org/jira/browse/KARAF-3760
> Project: Karaf
> Issue Type: Bug
> Affects Versions: 4.0.0.M2
> Environment: Ubuntu 14.04, Java 7 and 8
> Reporter: Lars Neumann
>
> Seems like KARAF-3087 got lost on master.
> When I create a Karaf distribution using the karaf-maven-plugin the bin/karaf
> and bin/karaf.bat script get filtered by the maven-resources plugin. In my
> case JAVA_HOME gets replaced when creating a karaf-assembly.
> When I try to ssh to karaf using ssh -p 8101 karaf@localhost I get the same
> error as in KARAF-3087.
> {code}
> no matching cipher found: client
> aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,[email protected]
> server
> {code}
> Restoring the original karaf start script resolves the problem.
> Can this be fixed before the final 4.0.0 release?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
