that is really cool. any idea how they got that set up? do you have this for Tiles?
On Mon, Oct 12, 2009 at 1:57 AM, Antonio Petrelli <[email protected]> wrote: > Just another thing. > I would like to help, but it's difficult to do it since the patch mechanism > of Subversion is not perfect. > Why don't you open a sandbox directory, open to all Apache committers, so I > can "branch" the trunk and work on it? > Maven team has already done it: > http://docs.codehaus.org/display/MAVEN/The+Maven+Sandbox+is+for+all+Apache+Committers > ! > > Thanks > Antonio > > 2009/10/10 Antonio Petrelli <[email protected]> > >> Hi all! >> I noticed that Velocity 2.0 is still at snapshot level, it seems a lot of >> time to me :-) >> 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. >> >> 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. >> >> 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? >> >> 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? >> >> Thanks for your attention >> Antonio >> > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
