The source jar can be obtained from http://christophertownson.com/mvn/com/christophertownson/spring-velocity/0.0.1/spring-velocity-0.0.1-sources.jar (I need to update the pom details so this gets put into the mvn site properly).
I should probably move scm at some point, too, so that others can potentially have access to that. Maybe github. As for GPL, that was a religious/political decision ... one can debate the many the finer legal points of the various oss licences endlessly but, since this was something that I did in my own time free-of-charge, I wanted to make it available but I did not want it to be utilised and/or distributed as part of a proprietary/commercial software system (but could still be used by in-house systems where these are not sold/distributed under non-GPL compatible licences). The GNU is also, to my mind at least, the strongest symbol of open source software. There are others, but those are the 2 basic reasons - the GPL stipulates these, whereas apache/bsd do not, afaik. However, if you can make a case for the others, please feel free -- but probably best done off-list ;-) Cheers, Chris On 11 May 2011 22:23, Nathan Bubna <nbu...@gmail.com> wrote: > It's not something i can use yet, and i wasn't able to get the source > in any form. But the javadoc makes it look thorough, and this is > certainly something that has been sorely missing from Spring > integration. In general, it sounds great. But why GPL? That's > prohibitive for us in future spring/velocity projects. Apache or BSD > licensing would be great. :) > > On Wed, May 11, 2011 at 3:00 AM, Christopher Townson > <christopher.town...@gmail.com> wrote: >> I thought some on this list might like to know about a small "glue >> library" I wrote recently as a programming exercise for integrating >> Velocity with Spring and released on GPL for any interested parties: >> >> http://christophertownson.com/projects/spring-velocity/ >> >> I have often thought that the integration with Velocity currently >> provided by Spring, whilst adequate, could be significantly improved >> -- and this is my attempt to do so. >> >> I had 4 main aims in this exercise: >> >> 1. Support the changes to Velocity & Velocity Tools (esp. tools) since >> 1.5 and 2.0 (new toolbox format, no deprecation messages etc) >> >> 2. Provide a standard, Spring-style means to utilise Spring context >> support to augment velocity tools infrastructure (@ViewHelper >> annotation as a component stereotype which can have a Spring @Scope >> specified automatically added to Velocity context) >> >> 3. Most importantly: work nicely with ContentNegotiatingViewResolver >> so that a single velocity-based Spring View can be used to generate >> multiple text-based formats simply by dropping in additional templates >> (+ specifying in ContentNegotiatingViewResolver's mediaTypes map) >> >> 4. Get all of the above to work transparently, out-of-the-box via >> annotations, and correctly determine what sort of "context" the app is >> running in (e.g. web app [access to servlet context] or plain token >> replacer with/without toolbox) >> >> Any thoughts or feedback would be most welcome ... and, of course, >> feel free to use! >> >> All the best, >> >> Chris >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: user-unsubscr...@velocity.apache.org >> For additional commands, e-mail: user-h...@velocity.apache.org >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: user-unsubscr...@velocity.apache.org > For additional commands, e-mail: user-h...@velocity.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscr...@velocity.apache.org For additional commands, e-mail: user-h...@velocity.apache.org
