Yes, although it will do weird things to your local maven repository/
cache since the patched releases are never published to our maven
repo. You'll just have to repeat the dist_maven again if you clean
out your local maven cache.
Chris
On Apr 21, 2010, at 12:38 PM, Sergio Bossa wrote:
Thanks for your answer, Chris.
The fix is checked into:
http://svn.terracotta.org/svn/tc/dso/trunk
http://svn.terracotta.org/svn/tc/dso/branches/3.2
http://svn.terracotta.org/svn/tc/dso/patches/patched_3.2.1/
So, if I checkout and build
http://svn.terracotta.org/svn/tc/dso/patches/patched_3.2.1/, I should
get a (patched) 3.2.1 terracotta instance, is that right?
There should be a tc-maven-plugin version that goes with the 3.2
branch. As
regards the 3.2.1 patch, I'm not entirely sure what artifacts that
generates
when you do ./tcbuild dist_maven so exactly how it would behave I
don't
know.
Maybe Jason could help here?
--
Sergio Bossa
http://www.linkedin.com/in/sergiob
_______________________________________________
tc-dev mailing list
tc-dev@lists.terracotta.org
http://lists.terracotta.org/mailman/listinfo/tc-dev
_______________________________________________
tc-dev mailing list
tc-dev@lists.terracotta.org
http://lists.terracotta.org/mailman/listinfo/tc-dev
