Welcome to the new Gigaspaces XAP forum. To recover your account, please follow these instructions.

Ask Your Question

Maven xap-jms Not Found XAP 10.1.1

Hi, we are using XAP 10.1.1-12800-RELEASE and during maven install I get this error:

Could not resolve dependencies for project com.example.app:parent-app:pom:3.0.2-SNAPSHOT: The following artifacts could not be resolved: com.gigaspaces:xap-jms:jar:10.1.1-12800-RELEASE

and I can't find that file anywhere. Where did you guys publish the file?

Thank you

Got this error when running


[ERROR] Failed to execute goal on project maven-openspaces-plugin: Could not resolve dependencies for project org.apache.maven.plugins:maven-openspaces-plugin:maven-plugin:10.2.0-13819-RELEASE: The following artifacts could not be resolved: com.gigaspaces:xap-jms:jar:10.2.0-13819-RELEASE, org.aopalliance:com.springsource.org.aopalliance:jar:1.0.0: Could not find artifact com.gigaspaces:xap-jms:jar:10.2.0-13819-RELEASE in org.openspaces (http://maven-repository.openspaces.org)

asked 2015-05-11 17:42:30 -0500

Christian gravatar image

updated 2018-02-04 02:26:50 -0500

inbarc gravatar image
edit retag flag offensive close merge delete


got this error above when running gigaspaces-xap-premium-10.2.0-ga-b13819\gigaspaces-xap-premium-10.2.0-ga\tools\maven\installmavenrep.bat

judgegideon gravatar imagejudgegideon ( 2018-02-01 08:54:21 -0500 )edit

Please review the answer in this section, it is regarding the same issue. Please let us know if you manage to solve the problem. Thanks

inbarc gravatar imageinbarc ( 2018-02-04 02:28:57 -0500 )edit

6 Answers

Sort by » oldest newest most voted


  1. There is improvement request for not including SNAPSHOT releases (e.g: jbossws-api:jar:1.0.0-SNAPSHO) in our Repository.
  2. Regarding xap-jms-10.1.1-12800-RELEASE.jar - it is already fixed. You can run the following command" "wget http://maven-repository.openspaces.or... and verify that the jar is downloaded:

[yuvald@pc-lab88 ~]$ wget http://maven-repository.openspaces.or... --2015-06-09 10:17:35-- http://maven-repository.openspaces.or... Resolving maven-repository.openspaces.org...,,, ... Connecting to maven-repository.openspaces.org||:80... connected. HTTP request sent, awaiting response... 200 OK Length: 157326 (154K) [application/octet-stream] Saving to: âxap-jms-10.1.1-12800-RELEASE.jarâ

100%[===================================================================================================================================================================================================>] 157,326 180K/s in 0.9s

answered 2015-06-09 02:25:19 -0500

Yuval gravatar image
edit flag offensive delete link more


answered 2015-05-12 10:53:34 -0500

DeWayne gravatar image
edit flag offensive delete link more


So, isn't there a maven artifact?

Christian gravatar imageChristian ( 2015-06-01 13:34:32 -0500 )edit

After removing: .m2\repository\com\gigaspaces\xap-jms\10.1.1-12800-RELEASE\xap-jms-10.1.1-12800-RELEASE.jar And running: gigaspaces-xap-premium-10.1.1-ga\tools\maven\installmavenrep.bat This jar was installed again. Could be that the internet connection between GS repository and Nexus repository is not working?

Yuval gravatar imageYuval ( 2015-06-07 08:05:16 -0500 )edit

As a workaround you can try deploy gigaspaces-xap-premium-10.1.1-ga\lib\optional\jms\gs-jms.jar to Nexus. Example of deploy command: mvn deploy:deploy-file -Durl=http://nexus:8081/nexus/content/repositories/releases/ -DrepositoryId=releases -Dfile=<file.jar> -DgeneratePom=true -DgroupId=<group.id> -DartifactId=<artifact-id> -Dversion=<version> -Dpackaging=jar

Yuval gravatar imageYuval ( 2015-06-08 02:37:00 -0500 )edit

Thank you, that is how I worked around this. The problem is the missing jbossws-api jar is a very old, non-official final build from jboss (it is version 1.0.0-SNAPSHOT). We don't make it a practice to install SNAPSHOT builds for third party libraries into our Nexus repository - especially for a non-existing version. The closest official version is 1.0.1.FINAL. To work around this would be to download that version and deploy it to our repository with a 1.0.0-SNAPSHOT version to get around this indirect dependency for this jar from gs-openspaces.jar. Very bad workaround and bad practice.

rich gravatar imagerich ( 2015-06-08 06:41:43 -0500 )edit


I've opened a ticket with Engineering



answered 2015-06-04 10:57:06 -0500

jb gravatar image
edit flag offensive delete link more


Hi John,

I can see with 11.0 this is still a problem. You mentioned you entered an engineering ticket on this can you report on when this will be fixed?



rich gravatar imagerich ( 2016-06-27 11:37:09 -0500 )edit


Did you run tools/maven/installmavenrep.sh?

jb gravatar imagejb ( 2016-06-27 14:55:45 -0500 )edit

Hi John,

We use Nexus as our Maven repository so I start out with that script and change all the installs to deploys. The last step fails until I manually deploy xap-gs.jar to Nexus.


rich gravatar imagerich ( 2016-06-27 15:32:50 -0500 )edit

Along with the above installation error with the xap-jms jar, i also found that the aopalliance.jar has the wrong version number which causes issues when using maven. The official version is 1.0 but XAP 10.1.1 is looking for 1.0.0 which required me to manually insert this jar with that version number instead of being able to pull it down automatically.

The other issue with this plug in has an indirect dependency on a jboss SNAPSHOT (jbossws-api) jar. If I comment out the gs-openspaces jar dependency for this plugin this indirect dependency on the the jboss SNAPSHOT jar dependency goes away. That makes it almost impossible to run the maven install.

At this point unless I down load an official jar and insert it in my repository manually with an invalid version number this install script is useless

answered 2015-06-05 07:05:03 -0500

rchristy gravatar image
edit flag offensive delete link more

Did anyone answer this question? I am having the same issue



answered 2015-06-04 10:53:44 -0500

rich gravatar image
edit flag offensive delete link more


So i installed lib/optional/jms/gs-jms.jar into our repository and gave it maven artifact com.gigaspaces:xap-jms:jar:10.1.1-12800-RELEASE and that seemed to resolve that problem.

Now it appears that SNAPSHOT dependency has been compiled in

[INFO] ------------------------------------------------------------------------ [INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Total time: 20.432s [INFO] Finished at: Thu Jun 04 11:02:59 CDT 2015 [INFO] Final Memory: 7M/241M [INFO] ------------------------------------------------------------------------ [ERROR] Failed to execute goal on project maven-openspaces-plugin: Could not resolve dependencies for project org.apache.maven.plugins:maven-openspaces-plugin:maven-plugin:10.1.1-12800-RELEASE: Could not find artifact org.jboss.ws:jbossws-api:jar:1.0.0-SNAPSHOT

Any ideas what version this was supposed to be?

rich gravatar imagerich ( 2015-06-04 11:37:26 -0500 )edit

ok I dug into this further. If I comment out the gs-openspaces jar dependency this indirect dependency on the the jboss SNAPSHOT jar dependency shown about goes away. So whoever at Gigaspaces built this release version did so with an unofficial jboss jar

rich gravatar imagerich ( 2015-06-04 12:08:48 -0500 )edit

Gigaspaces doesn't have a public maven repository. Maybe the bat file knows how to rename and install the gs-jms.jar file properly but the unix sh script doesn't. The bigger problem is the SNAPSHOT dependency on jboss. There is a ticket open on this problem but I haven't heard any updates on it yet

answered 2015-06-07 12:17:55 -0500

rich gravatar image
edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Question Tools


Asked: 2015-05-11 17:42:30 -0500

Seen: 7,285 times

Last updated: Feb 04