wagon

I have a closed-source project that I would like to build using Maven. It has a dependency on two java libraries which are not available in any public repository that I've been able to find (libGoogleAnalytics.jar and FlurryAgent.jar in this case, but the question applies to any closed-source dependency). I would like anyone in my organization to be able to build the application using the exact same versions of the dependencies that I use to build the application. This includes my colleagues and our build-server. How do I manage closed-source dependencies that maven doesn't know how to resolve

I try to upload an ear created by maven to an application server using scp. When I tried to run mvn wagon:upload-single But I get the following error: [ERROR] Failed to execute goal org.codehaus.mojo:wagon-maven-plugin:1.0-beta-3:upload-single (default-cli) on project de.volkswagen.dps.ear: Unable to create a Wagon instance for null: url can not be null -> [Help 1] org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.codehaus.mojo:wagon-maven-plugin:1.0-beta-3:upload-single (default-cli) on project de.volkswagen.dps.ear: Unable to create a Wagon instance for null

I am trying to copy resources to another location. I am using maven wagon-ssh plugin to do this. It works fine locally, I am having issues when using Hudson/Jenkins. My settings.xml file looks like this: <servers> <server> <id>iq</id> <configuration> <knownHostsProvider implementation="org.apache.maven.wagon.providers.ssh.knownhost.NullKnownHostProvider"> <hostKeyChecking>no</hostKeyChecking> </knownHostsProvider> </configuration> <username>user</username> <password>pass</password> </server> </servers> I tried this answer to skipping checking as I was getting: Are you sure you want to continue