On Sat, Oct 10, 2009 at 1:58 AM, Antonio Petrelli <[email protected]> wrote: > Hi all! > I noticed that Velocity 2.0 is still at snapshot level, it seems a lot of > time to me :-)
yes, it is a long time. :( but we have had 4 beta releases, not just snapshots. > So I would like to ask: What's missing to release it? > > I took a look at the issues scheduled for 2.0: > https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&mode=hide&sorter/order=DESC&sorter/field=priority&resolution=-1&pid=12310130&fixfor=12312884 > I noticed that they are two: > * there is a pure documentation issue, that seems fixed (with the exception > of some alcohol-driven comments :-D ) > * the other is an issue that is really easily fixed with Maven with the > release plugin. yeah, documentation is/was the main holdup. some Maven improvement would be great too. i would love to see a little more doc completion, and i've really been hoping someone else would jump in and help with such things. but i'm kidding myself, i realize. it's probably time to just wrap up a few ends and release it. mostly, i have lacked time for OSS admin stuff at work or the right combo of idle personal time and motivation to wrap things up. i'm swamped in javascript and new products at work right now. my boss gave the ok to use betas of Velocity and friends, which really undercut my justification for doing the admin & doc work needed for a final release on company time. > Moreover this issue: > https://issues.apache.org/jira/browse/VELTOOLS-65 > seems driven from prejudice against Maven, and the comment was from 2006, a > lot of things have changed. my level of Maven expertise has only minimally improved since then. i won't support leaving the Ant build until either: a) i am confident Maven mavens will be available to help at all key times, or b) i feel confident that i am a Maven maven. i supported Henning in moving the main Velocity website over to Maven, only to have that become a massive pain point for the project. and that has yet to be resolved. we are still ultimately reliant upon Henning to pull the trigger for site updates. i don't think i'll feel like a) or b) have happened until that is resolved, at a minimum. > I think that the Maven move is easy, knowing what needs to be done. Since > the Ant build files are pretty big, I did not go too deep reading them. What > do they do? > I noticed that they: > * compile > * test > * make packages > Is there anything else? download dependencies, build examples, javadoc, jdoc, website, all three jars/artifacts build releases, upload releases and website stuff, and provide instructions that accompany both processes and most of all, they haven't become a massive pain point for the community yet. i'm always happy to have help learning and improving the Maven build, seriously, it's a great thing. it does seem like less work in the long run. so, i'm sorry i've been so slow to work on VELOCITY-122. my brain is just in a lot of other places these days. i'm trying to make some time today for it. > The only *small* problem is with the tests. I managed to execute tests under > Maven, see: > https://issues.apache.org/jira/browse/VELTOOLS-122 > There is only *one* test that I am not able to execute, since it needs a > container, i.e. it is an integration test and it needs, essentially, a web > project (correct me if I am wrong). > Is it the case to exclude the Maven path for merely a single *integration* > test? well, it wasn't/isn't a mere integration test. it was (is?) the key test for the VelocityView tools, as nothing else tested those. > > Thanks for your attention > Antonio > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
