[ https://issues.jboss.org/browse/JBWS-4091?page=com.atlassian.jira.plugin.... ] R Searls edited comment on JBWS-4091 at 2/1/18 1:51 PM: -------------------------------------------------------- jbossws-cxf:5.2.1-SNAPSHOT had dependencies on several archives that only reside in repository, https://repository.jboss.org/nexus/content/groups/developer/. com.sun.xml.messaging.saaj:saaj-impl:jar:1.3.16-jbossorg-1 org.apache.activemq:artemis-commons:jar:1.1.0.wildfly-011 Travis CI does not appear to be able to get access to this repository. Travis CI appears to have access only to maven central. saaj-impl:jar:1.3.16-jbossorg-1 can be resolved by moving to saaj-impl:jar:1.3.18 because that version resides in maven central. It does not appear artemis-commons:jar:1.1.0.wildfly-011 can be resolved because no "wildfly-0*" releases resides in maven central. In the project I have provided a custom maven settings.xml file that enables access to https://repository.jboss.org/nexus/content/groups/developer/. I tested the customer file in my local builds; it works there. This settings file does not work in Travis CI Travis.yml is as follows, line 2 directs maven to use the custom settings.xml file {code:java} install: - mvn -s tarvis-settings.xml clean install script: - mvn -B -fae -P$SERVER_VERSION integration-test language: java jdk: - oraclejdk8 - oraclejdk9 env: - SERVER_VERSION=wildfly1010 # - SERVER_VERSION=wildfly1000 # - SERVER_VERSION=wildfly1100 # - SERVER_VERSION=wildfly1110 matrix: exclude: - jdk: oraclejdk9 env: SERVER_VERSION=wildfly1010 - jdk: oraclejdk9 env: SERVER_VERSION=wildfly1000 - jdk: oraclejdk9 env: SERVER_VERSION=wildfly1100 - jdk: oraclejdk9 env: SERVER_VERSION=wildfly1110 cache: directories: - $HOME/.m2 addons: apt: packages: - oracle-java8-installer before_install: - "if [ -d \"$JAVA_HOME/jre\" ]; then SEC_LIB=$JAVA_HOME/jre; else SEC_LIB=$JAVA_HOME; fi; sudo unzip -j -o travis-libs/jce_policy-8.zip *.jar -d $SEC_LIB/lib/security;" {code} was (Author: rsearls): jbossws-cxf:5.2.1-SNAPSHOT had dependencies on several archives that only reside in repository, https://repository.jboss.org/nexus/content/groups/developer/. com.sun.xml.messaging.saaj:saaj-impl:jar:1.3.16-jbossorg-1 org.apache.activemq:artemis-commons:jar:1.1.0.wildfly-011 Travis CI does not appear to be able to get access to this repository. Travis CI appears to have access only to maven central. saaj-impl:jar:1.3.16-jbossorg-1 can be resolved by moving to saaj-impl:jar:1.3.18. It does not appear artemis-commons:jar:1.1.0.wildfly-011 can be resolved because no "wildfly-0*" releases resides in maven central. In the project I have provided a custom maven settings.xml file that enables access to https://repository.jboss.org/nexus/content/groups/developer/. I tested the customer file in my local builds; it works there. This settings file does not work in Travis CI Travis.yml is as follows, line 2 directs maven to use the custom settings.xml file {code:java} install: - mvn -s tarvis-settings.xml clean install script: - mvn -B -fae -P$SERVER_VERSION integration-test language: java jdk: - oraclejdk8 - oraclejdk9 env: - SERVER_VERSION=wildfly1010 # - SERVER_VERSION=wildfly1000 # - SERVER_VERSION=wildfly1100 # - SERVER_VERSION=wildfly1110 matrix: exclude: - jdk: oraclejdk9 env: SERVER_VERSION=wildfly1010 - jdk: oraclejdk9 env: SERVER_VERSION=wildfly1000 - jdk: oraclejdk9 env: SERVER_VERSION=wildfly1100 - jdk: oraclejdk9 env: SERVER_VERSION=wildfly1110 cache: directories: - $HOME/.m2 addons: apt: packages: - oracle-java8-installer before_install: - "if [ -d \"$JAVA_HOME/jre\" ]; then SEC_LIB=$JAVA_HOME/jre; else SEC_LIB=$JAVA_HOME; fi; sudo unzip -j -o travis-libs/jce_policy-8.zip *.jar -d $SEC_LIB/lib/security;" {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)