Ok, I found out the problem by looking at debug-level logging on Karaf when trying to install the feature.
Karaf seems to be trying to fetch the dependencies from /home/.m2/... folder. So NOT from inside the KAR-file where the jars are stored. I was under the impression that the whole point of the KAR-file was to be able to deploy a group of dependencies that would be resolved FROM the KAR itself. Or from the repository-folder inside the KAR. However, on my windows-environment the deployment worked because the windows-computer had access to the maven repository that I use, or rather, the .m2 folder inside my dev computer. The linux-computer had no access to external maven repository nor did it have the .m2-folder. So what's the deal here, should the dependencies inside the KAR-file be used or not? For example, inside the KAR-file there is: /repository/joda-time/joda-time/2.0/joda-time-2.0.jar And in the features.xml I have <feature...> <bundle start="auto">mvn:joda-time/joda-time/2.0</bundle> </feature> So I'd expect the bundle inside the KAR to be used. But now, according to the debug loggin it tries to find the joda-time-2.0.jar first from my home/.m2, then it tries to access several other maven repos from the internet which aren't visible to the linux computer where I run Karaf. So what's up here? -- View this message in context: http://karaf.922171.n3.nabble.com/Difference-in-KAR-deployment-between-Windows-and-Linux-tp4027093p4027111.html Sent from the Karaf - User mailing list archive at Nabble.com.
