Cambridge, Jersey 2.x, etc

[Ray Vanderborght]

Anyone still using Cambridge? Seems like it's gone a little dark lately.

Anyhow, I just did a Jersey 1.x to 2.x upgrade on a toy project of mine that integrates with Cambridge Templates:

https://github.com/depsypher/flapjack

Should save some pain for anyone thinking of doing that upgrade. Esp. if you also use Guice. They did not make that integration easy!

The main classes involved for cambridge are these:

https://github.com/depsypher/flapjack/blob/master/src/main/java/flapjack/conf/CambridgeTemplateProcessor.java

https://github.com/depsypher/flapjack/blob/master/src/main/java/flapjack/conf/CambridgeMvcFeature.java

Also, any chance of getting cambridge into maven central? It's a real shame it's not there.

[Erdinc Yilmazel]

Ray, thanks for your fixes. I will look into pulling your changes into main Cambridge repo on github. Yes Cambridge should be on maven central and I never looked into how to set that up. If there is interest I certainly will try to push it to maven central too.

Erdinç

--
You received this message because you are subscribed to the Google Groups "Cambridge Template Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email to cambridgetempla...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Jon Stevens]

Absolutely push it to maven. It's a pain to get setup, but once you do it's easy to push.

Once you are all setup: http://central.sonatype.org/pages/ossrh-guide.html

All you need to do is: 'mvn clean deploy; mvn release:clean; mvn release:prepare; mvn release:perform'

[Ray Vanderborght]

Awesome, thanks guys.

I'm very reluctantly only now starting to use maven, and gotta say it doesn't make for a pleasant experience when jars aren't in central.

In any case, Cambridge deserves to be there and it can only help adoption. I hope the push setup isn't too painful.

[Patrick Buchheit]

So was there ever any progress on this? I have a project that used to depend on cambridge-core 0.8 and now I can't deploy it since that repo seems to no longer exists in maven central.