Ignacio's thing is basically what I did, created a local module with the jclouds JARs. I guess the questions are 1. Was he using CDI in his app? 2. Was he using JClouds 1.6 or 1.7?
Since he was talking about Guava 15.0 in the thread I'm guessing 1.7.
I'm kind of tied closely w/ CDI as my IoC runtime. I would also hope libraries would not be IoC oriented, letting the app pick up whatever appropriate wiring is needed.. sometimes it's a pipe dream. :-)
I can understand how you feel. jclouds' wiring should be self-contained and be able to coexist with whatever you and the container would like to choose. Unfortunately, some of the CDI and JSR 250 JARs can indeed conflict, although you can always try to see what happens if you override the versions jclouds uses with potential newer versions your app and container need.
I've used jclouds in Spring- and Weld-wired projects (not in JBoss 7, I should add) without problems. But the kind of classloader isolation needed here is not exactly Java's strong point, unfortunately :-(
If you figure out a way to get it to work, it'd be great to hear more about that!
Regards ap
