Andrew, thanks for the quick reply. I think you are right, but I'm not
sure how to perform this rebuild since the feature.xml file does not
exist in the jclouds-cli source package. It seems that file gets pulled
in via the jclouds-karaf dependency. If I modify the feature.xml file
(that was downloaded during the first time through the build) and then
rebuild with "mvn package", the file just gets re-downloaded and my
edits are lost.
Also, there does seem to be a "branding" module whose intent seems to be
to customize the welcome screen, but is not working for some reason.
On 03/30/2015 05:46 PM, Andrew Phillips wrote:
> Hi Mike
>
> Hm, it looks like something is going on with the dependency packaging
> for the jsch-agent-proxy. Without diving straight into too much
> technical detail, it seems as though the dependency on usocket-nc [1]
> is not sufficient in your scenario, for some reason.
>
> I'm not able to test this right now, but could you see if adding the
> following line to the feature.xml file after [1] and rebuilding makes
> any difference?
>
> <bundle
> dependency='true'>mvn:com.jcraft/jsch.agentproxy.usocket-jna/${jsch.agentproxy.version}</bundle>
>
> As regards the "karaf>" prompt: that's expected, from what I know,
> since jclouds-cli is a bundled version of Apache Karaf.
>
> Regards
>
> ap
>
> [1]
> https://github.com/jclouds/jclouds-karaf/blob/master/feature/src/main/resources/feature.xml#L393
