Hi again,
Also, here is a dependency graph from maven:
[INFO] +- joda-time:joda-time-hibernate:jar:1.1:compile
[INFO] | +- (joda-time:joda-time:jar:1.4:compile - omitted for conflict
with 1.6)
[INFO] | +- commons-logging:commons-logging-api:jar:1.0.4:compile
[INFO] | +- (commons-collections:commons-collections:jar:3.1:compile -
omitted for conflict with 3.2)
[INFO] | +- (dom4j:dom4j:jar:1.6:compile - omitted for conflict with 1.6.1)
[INFO] | \- cglib:cglib-full:jar:2.0.2:compile
As you can see, getting cglib-full is a bad choice, because 2.2 is out, and
there are some big difference. When the two libraries conflict, it is NASTY.
Also, you should probably point hibernate to hibernate-core 3.3.1 GA,
because getting an old version of hibernate might cause problems as well (it
didn't for me, but I excluded it anyway).
Thanks!
Ken
--
Brand New Fraking Song! Listen NOW!
http://soundclick.com/share?songid=7908838
My Original Music: http://www.soundclick.com/KenEgervari
My Humorous Speeches: http://www.youtube.com/user/egervari
My Facebook:
http://www.new.facebook.com/profile.php?id=716270499/profile.php?id=716270499
On Sun, Sep 20, 2009 at 4:51 AM, Ken Egervari <ken.egerv...@gmail.com>wrote:
> Hi!
>
> Thanks so much for writing joda-time-hibernate. It's such a great library!
> I really like it and used it on my recent projects.
>
> I have a request, and I think it'll be for the greater good ;)
>
> Would it be possible to get a 1.1.1 version or 1.2 version of
> joda-time-hibernate that doesn't contain any code changes, but uses updated
> libraries?
>
> This package really messes up projects these days because the libraries are
> old. I have to do a number of exclusions to get my projects to work:
> <dependency>
> <groupId>joda-time</groupId>
> <artifactId>joda-time-hibernate</artifactId>
> <version>1.1</version>
> <exclusions>
> <exclusion>
> <groupId>hsqldb</groupId>
> <artifactId>hsqldb</artifactId>
> </exclusion>
> <exclusion>
> <artifactId>ehcache</artifactId>
> <groupId>ehcache</groupId>
> </exclusion>
> <exclusion>
> <artifactId>commons-logging</artifactId>
> <groupId>commons-logging</groupId>
> </exclusion>
> <exclusion>
> <artifactId>commons-logging</artifactId>
> <groupId>commons-logging-api</groupId>
> </exclusion>
> <exclusion>
> <artifactId>cglib</artifactId>
> <groupId>cglib-full</groupId>
> </exclusion>
> <exclusion>
> <artifactId>antlr</artifactId>
> <groupId>antlr</groupId>
> </exclusion>
> <exclusion>
> <artifactId>hibernate</artifactId>
> <groupId>hibernate</groupId>
> </exclusion>
> </exclusions>
>
> I think some of these projects might only be for testing as well? If that's
> the case, you should use <scope>test</scope> so that people don't get
> unwanted jars in their projects, or conflicts with existing jars.
>
> Also, commons-logging should not point to commons-logging-api. Even
> excluding it does not remove the problem for some reason - probably because
> your code relies on the old version. It would be fastastic if you would
> point to commons-logging 1.1.1 =)
>
> Thanks! Looking forward to a repackaging update ;)
>
> Ken
>
> --
> Brand New Fraking Song! Listen NOW!
> http://soundclick.com/share?songid=7908838
>
> My Original Music: http://www.soundclick.com/KenEgervari
> My Humorous Speeches: http://www.youtube.com/user/egervari
> My Facebook:
> http://www.new.facebook.com/profile.php?id=716270499/profile.php?id=716270499
>
------------------------------------------------------------------------------
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
_______________________________________________
Joda-interest mailing list
Joda-interest@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/joda-interest
