Hi all, 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.
For example, tim-ehcache would have the same groupId, artifactId, and version as the non-TIM artifact, and the user would only have to list their local TIM repo in their pom instead of having to change the artifacts in their POM and keep track of which version of TIM correlates to the actual artifact version. The biggest problem I can think of offhand is when the TIM code is updated for the same artifact, so I'm not sure what could be done to work around that other than datestamp comparison. Maybe there could be some kind of Maven 2 TIM plugin that could scan the POM and tell Maven to use the TIM artifact instead? Cheers, Jim
_______________________________________________ tc-dev mailing list [email protected] http://lists.terracotta.org/mailman/listinfo/tc-dev
