On Tuesday 20 May 2008 4:21:18 pm Jim Bethancourt wrote:
> I apologize for my lack of clarity -- by non-TIM artifacts I was thinking
> along the lines of normal versions of jetty, hibernate, wicket, etc. The
> idea would be that the user could swap out normal versions of hibernate &
> ehcache without having to change the artifacts throughout the POM, but
> instead list the TIM repository first since Maven 2 will look there first
> for artifacts.
The TIMs are not really drop-in replacements for the "non-TIM artifacts".
Rather, they are pre-packaged Terracotta configurations for integrating the
non-TIM artifacts with Terracotta. For instance, tim-hibernate is not a
version of Hibernate that's been modified to work with Terracotta, but is
instead a Terracotta configuration snippet (along with some instrumentation
code) that allows Hibernate to be used easily with Terracotta.
That said, I don't think it would be a good idea to rename the TIMs so that
they have the same groupId/artifactId/version as the frameworks themselves.
If we did that we would have two very different things advertising themselves
as the same thing, and I think it could lead to subtle and hard to find bugs.
Does that make sense? Did I understand your question correctly?
--
Jason Voegele
Yes I have a Machintosh, please don't scream at me.
-- Larry Blumette on linux-kernel
_______________________________________________
tc-dev mailing list
[email protected]
http://lists.terracotta.org/mailman/listinfo/tc-dev
