spring-modules-cache dependencies

[nivancevic]

After I included spring-modules-cache dependency in my project's pom,

<dependency>
<groupId>org.springmodules</groupId>
<artifactId>spring-modules-cache</artifactId>
<version>0.6</version>
</dependency>

maven is unable to resolve following dependencies:

1) gigaspaces:gigaspaces-ce:jar:5.1-1603-000
2) jini:webster:jar:20060125
3) jboss:jboss-jmx:jar:4.0.3
4) xpp3:xpp3_min:jar:1.1.3.4.I
5) jini:start:jar:2.1
6) jboss:jboss-minimal:jar:4.0.3
7) jini:reggie:jar:2.1
8) jboss:jboss-cache:jar:1.2.4
9) jcs:jcs:jar:1.2.6.5
10) jboss:jboss-system:jar:4.0.3
11) jini:jsk-platform:jar:2.1
12) jboss:jboss-common:jar:4.0.3
13) jini:mahalo:jar:2.1
14) jini:jsk-lib:jar:2.1
15) jini:boot:jar:20060125

I'm not sure if I am supposed to use some other maven2 repository (apart central)?
Or I have to provide all these dependencies manually?

[Costin Leau]

Most (if not all) of the dependencies you listen can't be found on ibiblio. Spring Modules provides them in the -with-dependencies distribution. There is also an ivy.xml file which contains URLs for downloading the jars (note that most of the URLs are not maven repositories).

[ncdc]

In the pom, would it be possible to mark the non-essential dependencies as <optional>true</optional>? For example, if my project only needs EhCache, I don't necessarily want to pull in JBossCache support (or vice versa). What are your thoughts?

Thanks,
Andy

[qwerty777]

Hi,

First of all, like what this original post says, there are many dependencies that are missing from the maven repository. I suppose you support ivy, but not maven fully.

But since I'm using maven, I want to figure out the right set of dependencies to do what I need. I want to be able to use declarative caching with JCS, so I want to exclude everything else. But I'm not 100% sure what I can exclude, so it'll be great if you can let me know what are the dependencies that I need for sure.

Thank you very much!

[arh14]

This is a PITA. I just had to explicitly exclude ~10 dependencies in my POM, for 0.8a. That's not right. These should be marked optional.

[rburton]

After I included spring-modules-cache dependency in my project's pom,

<dependency>
<groupId>org.springmodules</groupId>
<artifactId>spring-modules-cache</artifactId>
<version>0.6</version>
</dependency>

maven is unable to resolve following dependencies:

1) gigaspaces:gigaspaces-ce:jar:5.1-1603-000
2) jini:webster:jar:20060125
3) jboss:jboss-jmx:jar:4.0.3
4) xpp3:xpp3_min:jar:1.1.3.4.I
5) jini:start:jar:2.1
6) jboss:jboss-minimal:jar:4.0.3
7) jini:reggie:jar:2.1
8) jboss:jboss-cache:jar:1.2.4
9) jcs:jcs:jar:1.2.6.5
10) jboss:jboss-system:jar:4.0.3
11) jini:jsk-platform:jar:2.1
12) jboss:jboss-common:jar:4.0.3
13) jini:mahalo:jar:2.1
14) jini:jsk-lib:jar:2.1
15) jini:boot:jar:20060125

I'm not sure if I am supposed to use some other maven2 repository (apart central)?
Or I have to provide all these dependencies manually?

I strongly believe that the Caching Module should be split up in the following manner.

The core classes should be placed in a 'project' called cache-core (Or something else) followed by multiple providers. A provider would be something like ehcache, jboss, etc. This allows the end developer to select only the provider(s) he needs in his project without having to add multiple excludes. E.g.,

<dependency>
<groupId>org.springmodules.cache</groupId>
<artifactId>cache-core</artifactId>
<version>0.9</version>
</dependency>
<dependency>
<groupId>org.springmodules.cache</groupId>
<artifactId>ehcache-provider</artifactId>
<version>0.9</version>
</dependency>

Is there any plan to do this for SpringModules? I'll be more than willing to submit a fix for this if Spring is willing to accept it.

Best Regards,
Richard L. Burton III

[paolo_denti]

I strongly believe that the Caching Module should be split up in the following manner.

The core classes should be placed in a 'project' called cache-core (Or something else) followed by multiple providers. A provider would be something like ehcache, jboss, etc. This allows the end developer to select only the provider(s) he needs in his project without having to add multiple excludes. E.g.,

<dependency>
<groupId>org.springmodules.cache</groupId>
<artifactId>cache-core</artifactId>
<version>0.9</version>
</dependency>
<dependency>
<groupId>org.springmodules.cache</groupId>
<artifactId>ehcache-provider</artifactId>
<version>0.9</version>
</dependency>

Is there any plan to do this for SpringModules? I'll be more than willing to submit a fix for this if Spring is willing to accept it.

Best Regards,
Richard L. Burton III

i fully agree on your suggestion. too bad using springmodules with maven.

[paolo_denti]

I strongly believe that the Caching Module should be split up in the following manner.

The core classes should be placed in a 'project' called cache-core (Or something else) followed by multiple providers. A provider would be something like ehcache, jboss, etc. This allows the end developer to select only the provider(s) he needs in his project without having to add multiple excludes. E.g.,

<dependency>
<groupId>org.springmodules.cache</groupId>
<artifactId>cache-core</artifactId>
<version>0.9</version>
</dependency>
<dependency>
<groupId>org.springmodules.cache</groupId>
<artifactId>ehcache-provider</artifactId>
<version>0.9</version>
</dependency>

Is there any plan to do this for SpringModules? I'll be more than willing to submit a fix for this if Spring is willing to accept it.

Best Regards,
Richard L. Burton III

even better should be including in your pom
<dependency>
<groupId>org.springmodules.cache</groupId>
<artifactId>ehcache-provider</artifactId>
<version>0.9</version>
</dependency>
and the cache-core should be a dependency of ehcache-provider

[rmangi]

Was there any resolution to this? Not supporting maven is a huge problem.

[jdilley]

I agree, this is a huge pain. I'm not a Maven user, but use Ivy instead. Ideally, Spring's own Ivy repository would include Spring Modules (It amazes me that they don't even publish to their own repository), but a Maven repository somewhere would be fine, too, as I can load my Ivy repo from a public Maven repo.

A huge part of the Spring community uses dependency mgmt tools like Maven and Ivy, so having to do it manually seems like an unnecessary step.