tomcat-core artifacts missing from Maven Central

[bkoehm]

http://central.maven.org/maven2/com/hazelcast/hazelcast-tomcat-sessionmanager/1.1.2/ is present, but the tomcat-core dependencies are missing in central.maven.org.

[mesutcelik]

Hi @bkoehm ,
We do create uberJar including tomcat-core so those jars would work fine. Have you had any issue?

[mesutcelik]

closing this one. please send your further questions to https://groups.google.com/forum/#!forum/hazelcast

[anton-johansson]

Is the uberJar available from Maven Central? One could think that this is the uberJar for Tomcat 8, but it is not. It also has a dependency (tomcat-core) which does not exist, which can cause some really unnecessary headache for users (us). I believe this is the same issue that @bkoehm had. Why is the broken artifact deployed to Maven? And how can I find the uberJar in Maven Central?

EDIT: Only snapshots seems to be deployed for tomcat-core (see here).

[emre-aydin]

Hi @anton-johansson

The artifact is not broken. This is not an uberJar. As you've said, it has a dependency on tomcat-core. Since the JARs are to be put under Tomcat directory manually, we mostly focused on putting it under GitHub releases tab. You can download tomcat-core from the GitHub releases tab (https://github.com/hazelcast/hazelcast-tomcat-sessionmanager/releases).

I agree with making it more user friendly for people using it via Maven though, so I'm reopening the issue. I believe it will be a simple fix to deploy tomcat-core artifact to Maven central. We might also consider having all versions of the JARs as uber JARs which would further simplify deployment, both manual and via Maven.

[anton-johansson]

Just curious to why it is deployed at all if its not intended to be used. :) An example of where it would be useful with 100% Maven support: Building a Docker-image with our application and all of its dependencies. We can use Maven to make sure we get all the right artifacts, however, this is where we get the problem. Thanks for re-opening!

[emre-aydin]

@anton-johansson I think I understand the cause of confusion better now. The artifact is indeed an uber JAR but its pom.xml is incorrect as it lists tomcat-core as one of its dependencies. So the JAR is OK, but the pom.xml is incorrect.

[anton-johansson]

Allright. Since you can't overwrite artifacts in Central, I assume we'll wait for the next release. :)

An alternative would be to deploy empty tomcat-core artifacts, one for each "broken" version.

[emre-aydin]

@mesutcelik suggested that you might try excluding the tomcat-core dependency from hazelcast-tomcat-session-manager dep. in your pom.xml until then.

[anton-johansson]

Ahh, of course, that should work. Thanks!