On Tuesday 20 May 2008 1:07:08 pm Jim Bethancourt wrote:
> I was thinking it would be helpful to have a Maven 2 repo with TIM modules
> that have the same version numbers as the non-TIM artifacts, or instruct
> users on how to create their own local "clustered" TIM repository that has
> the latest TIM modules for the artifacts. Not sure if this idea is as
> fleshed out as it could be, but I believe it would help enable apps with
> TIM stuff a lot quicker, and allow the user to switch between normal and
> TIM modules very easily and quickly.
I'm assuming that by "non-TIM artifact" you are referring to the core
Terracotta Maven artifacts, such as terracotta.jar, terracotta-api.jar, etc.,
correct?
If so, then the problem is that the TIMs have a different lifecycle than the
core Terracotta artifacts, and therefore it isn't possible to keep the
version numbers in sync. We could perhaps come up with some clever schemes
using classifiers or somesuch, but we are limited in what we can accomplish
by the OSGi spec's very rigid definition of version numbers.
For the next release, we are planning on creating a "TIM Update Center" that
you'll be able to use to make sure you have the correct versions of TIMs for
your Terracotta installation.
Hope this helps.
--
Jason Voegele
Bad men live that they may eat and drink, whereas good men eat and drink
that they may live.
-- Socrates
_______________________________________________
tc-dev mailing list
[email protected]
http://lists.terracotta.org/mailman/listinfo/tc-dev
