I should have been more specific: > Case in point today the trunk is fine and quite "usable" as you put it > but tomorrow after some "next commit" it might not be the case...
I agree. What I did was take a snapshot of the trunk and called it 1.6-SNAPSHOT, but I don't update it at every commit. I put it in a Maven repo and just use that in my projects. I won't update it unless something happens in the trunk that I need. Like I said, this isn't for everyone. But for my purposes, it fits the bill. Cheers, Freddy ------------------------------------------------------------------------------ _______________________________________________ Stripes-development mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/stripes-development
