2009/10/14 Nathan Bubna <[email protected]>: >> 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.
Almost all these things can be done by Maven plugins. However, the site should be generated by some Ant task, or the site should be converted to Maven style (Doxia formats), that seems a lot of work. What is "jdoc" BTW? >> 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. Ok a functional test then. It still needs a container. Thanks Antonio --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
