Description of problem: Gefasoft customer has the installation of JBoss BPM Suite on a remote machine and developer has problem to use kjar (maven dependency) from the BPMS 6 maven repository and uses it in threir application locally. locally they set up the maven repo like this: <repository> <id>guvnor-m2-repo</id> <name>Guvnor M2 Repo</name> <url>http://rms-bpm:8080/business-central/maven2:8080/business-central/maven2/</url> </repository> Actual results: and after the build of their client maven application, they got this message: [INFO] ------------------------------------------------------------------------ Downloading: http://rms-bpm:8080/business-central/maven2/de/gefasoft/bpms/showcases/demoproject1/2/demoproject1-2.pom Mrz 07, 2014 6:12:19 PM org.apache.maven.wagon.providers.http.httpclient.impl.client.DefaultRequestDirector handleResponse Warnung: Authentication error: Unable to respond to any of these challenges: {} [INFO] ------------------------------------------------------------------------ [INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ Expected results: kjar module artifact needs to be downloaded from intern JBoss BPM Suite 6 Maven repository.
In the ~/.m2/settings.xml, the guvnor repo username / passwords needs to be configured, as the url you are trying to access requires authentication. For example: <servers> <server> <id>guvnor-m2-repo</id> <username>admin</username> <password>admin</password> </server> </servers> <profiles> <profile> <id>profile-default</id> <repositories> <repository> <id>guvnor-m2-repo</id> <name>jBPM Console Guvnor Repository</name> <url>http://localhost:8080/jbpm-console/maven2/</url> </repository> </repositories> <activation> <activeByDefault>true</activeByDefault> </activation> </profile> </profiles> This adds the guvnor-m2-repo as one of the default repos (note that the user could instead also add the repository to his pom, make sure to use the same id though) and configures username / password. Does this help?
Thanks Chris, I will test it and than give here feedback. But I would suggest that this information need to be documented in the Product document. then many customer s will ask the question. Cheers, Serge
See the referenced BZ for more details.
Closing the bug as duplicate of BZ1059584, because no fix was done. I have filed a new documentation Bugzilla to track documenting of this issue. https://bugzilla.redhat.com/show_bug.cgi?id=1090010 *** This bug has been marked as a duplicate of bug 1059584 ***