Btw, how good is IDE integration for Gradle? Until now I just pointed m2eclipse to the Tapestry SVN repo and it imported everything including setting up the multi-module project, populating the classpath with Maven dependencies and so on so that it was extremely easy to get up and running.
Uli On 24.05.2011 13:49, Igor Drobiazko wrote: > Gradle creates maven artifacts, so our users will not even know that we > switched to gradle. Tapestry jars will be still available in Maven repos. > However, I'm not sure about the status of the migration progress. > > On Tue, May 24, 2011 at 1:37 PM, Thiago H. de Paula Figueiredo < > [email protected]> wrote: > >> On Tue, 24 May 2011 07:10:27 -0300, Igor Drobiazko < >> [email protected]> wrote: >> >> Why do we actually still maintain Maven poms? Shouldn't we remove them as >>> we are on gradle now? >>> >> >> Unless Gradle is set up Maven POMs, removing the existing ones would be a >> pain to all the Maven users out there (including me), and there are too many >> of them imho for we to ignore them. >> >> -- >> Thiago H. de Paula Figueiredo >> Independent Java, Apache Tapestry 5 and Hibernate consultant, developer, >> and instructor >> Owner, Ars Machina Tecnologia da Informação Ltda. >> http://www.arsmachina.com.br >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
