Hi Gary,

yes, it should work (at least the scp part). The maven-metadata.xml is only required for SNAPSHOT (not release). In your case, as it's your own feature, Maven should update the maven-metadata.xml itself.

What Karaf version do you use ?

Regards
JB

On 08/30/2015 10:43 PM, garyhodgson wrote:
Hi,

I'm having a little trouble following what should be a relatively
straightforward example.  I am trying to directly deploy an artifact into a
running karaf instance using the mvn deploy:deploy-file command, as given
under the "Apache Maven" section of here
https://karaf.apache.org/manual/latest/users-guide/remote.html, but maven
fails with an error:

   [ERROR] Failed to execute goal
org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy-file (default-cli)
on project features: Failed to retrieve remote metadata
com.example:features:1.0-SNAPSHOT/maven-metadata.xml: Could not transfer
metadata com.example:features:1.0-SNAPSHOT/maven-metadata.xml from/to
ssh-repository (scp://localhost:8104/system): Error occurred while
downloading 'com.example/features/1.0-SNAPSHOT/maven-metadata.xml' from the
remote repository:Repository[ssh-repository|scp://localhost:8104/system]:
Exit code: 2 - \system\com.example\features\1.0-SNAPSHOT\maven-metadata.xml:
no such file or directory -> [Help 1]

There appears to be no such maven-metadata.xml files in any of the system
sub-directories of the instance.

Is this functionality still expected to be working? has anyone had any
experience doing something similar?

Cheers
Gary



--
View this message in context: 
http://karaf.922171.n3.nabble.com/Maven-deploy-direct-to-Karaf-instance-tp4042149.html
Sent from the Karaf - User mailing list archive at Nabble.com.


--
Jean-Baptiste Onofré
[email protected]
http://blog.nanthrax.net
Talend - http://www.talend.com

Reply via email to