<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Coffee, Code and Fiction - Latest Comments in Is Maven going away?</title><link>http://blackboxblog.disqus.com/</link><description>Thoughts on software development, writing fiction, fueled by coffee.</description><atom:link href="https://blackboxblog.disqus.com/is_maven_going_away/latest.rss" rel="self"></atom:link><language>en</language><lastBuildDate>Tue, 08 Jul 2008 07:18:56 -0000</lastBuildDate><item><title>Re: Is Maven going away?</title><link>http://www.warneronstine.com/2008/07/06/is-maven-going-away/#comment-16215805</link><description>&lt;p&gt;Our entire company is on the verge of being completely Maven. Team development using Maven in our IDEs makes development so much easier than anything else. The infrastructure provided behind every tag in the POM provides so much to our environment. The fact that things aren't willy-nilly added to the manifest and is performed by Maven plugins makes things structured really well. Our stack is CVS+Archiva+Hudson+(Mevenide2/EclipseMaven) and works great once you understand it.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Ravi</dc:creator><pubDate>Tue, 08 Jul 2008 07:18:56 -0000</pubDate></item><item><title>Re: Is Maven going away?</title><link>http://www.warneronstine.com/2008/07/06/is-maven-going-away/#comment-16215804</link><description>&lt;p&gt;This looks a lot better than Maven 2.&lt;/p&gt;&lt;p&gt;Less verbose, real scripting, simple, smaller concept set.&lt;/p&gt;&lt;p&gt;Maybe I've found something I can use to migrate away from Maven 1&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dion Gillard</dc:creator><pubDate>Mon, 07 Jul 2008 05:00:47 -0000</pubDate></item><item><title>Re: Is Maven going away?</title><link>http://www.warneronstine.com/2008/07/06/is-maven-going-away/#comment-16215803</link><description>&lt;p&gt;@Brian&lt;/p&gt;&lt;p&gt;Alright, that plugin does look like it solves the multiple source problem, but honestly this should be part of Maven core IMO. I think I'm ready to move on to something else though as I've seen [other](&lt;a href="http://tapestryjava.blogspot.com/2007/11/maven-wont-get-fooled-again.html)" rel="nofollow noopener" target="_blank" title="http://tapestryjava.blogspot.com/2007/11/maven-wont-get-fooled-again.html)"&gt;http://tapestryjava.blogspo...&lt;/a&gt; [issues](&lt;a href="http://tapestryjava.blogspot.com/2008/06/maven-for-dependencies-not-building.html)" rel="nofollow noopener" target="_blank" title="http://tapestryjava.blogspot.com/2008/06/maven-for-dependencies-not-building.html)"&gt;http://tapestryjava.blogspo...&lt;/a&gt; with Maven builds so [Buildr](&lt;a href="http://incubator.apache.org/buildr)" rel="nofollow noopener" target="_blank" title="http://incubator.apache.org/buildr)"&gt;http://incubator.apache.org...&lt;/a&gt; and [Gradle](&lt;a href="http://gradle.org" rel="nofollow noopener" target="_blank" title="http://gradle.org"&gt;http://gradle.org&lt;/a&gt;) look like good alternatives.&lt;/p&gt;&lt;p&gt;As I said I've been a big proponent of Maven for a long time so this isn't an easy switch for me, while I'm not looking for a drop-in replacement I am looking for something that makes my life easier as a developer, not more complex (as Ant does inherently).&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Warner Onstine</dc:creator><pubDate>Mon, 07 Jul 2008 03:34:28 -0000</pubDate></item><item><title>Re: Is Maven going away?</title><link>http://www.warneronstine.com/2008/07/06/is-maven-going-away/#comment-16215802</link><description>&lt;p&gt;Buildr is a nice tool. But though the basic approach is similar to Gradle (Buildr was there first) there are also significant differences. Some of them are:&lt;/p&gt;&lt;p&gt;* Gradle is based on Ivy, the most advanced dependency management solution in the Java world.&lt;br&gt;* Gradle calculates the graph of tasks which actually gets executed beforehand. This is a very powerful feature. This graph for example is provided to the tasks during execution.&lt;br&gt;* Gradle offers sophisticated ways to configure multi-project builds.&lt;br&gt;* Gradle has a java-core which will eventually enable it to support multiple build script languages (e.g. JRuby). Though for a Java team (building Java projects is what Buildr and Gradle is mostly about) we think that Groovy is usually the language which offers the highest transparency to the developers.&lt;/p&gt;&lt;p&gt;Regarding the conciseness. I would be very interested in concrete examples to improve Gradle here.&lt;/p&gt;&lt;p&gt;Hans Dockter (Gradle Project lead)&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Hans Dockter</dc:creator><pubDate>Mon, 07 Jul 2008 00:45:30 -0000</pubDate></item><item><title>Re: Is Maven going away?</title><link>http://www.warneronstine.com/2008/07/06/is-maven-going-away/#comment-16215801</link><description>&lt;p&gt;Buildr is a nice tool. But though the basic approach is similar to Gradle (Buildr was there first) there are also significant differences. Some of them are:&lt;/p&gt;&lt;p&gt;* Gradle is based on Ivy, the most advanced dependency management solution in the Java world.&lt;br&gt;* Gradle calculates the graph of tasks which actually gets executed beforehand. This is a very powerful feature. This graph for example is provided to the tasks during execution.&lt;br&gt;* Gradle offers sophisticated ways to configure multi-project builds.&lt;br&gt;* Gradle has a java-core which will eventually enable it to support multiple build script languages (e.g. JRuby). Though for a Java team (building Java projects is what Buildr and Gradle is mostly about) we think that Groovy is usually the language which offers the highest transparency to the developers.&lt;/p&gt;&lt;p&gt;Regarding the conciseness. I would be very interested in concrete examples to improve Gradle here.&lt;/p&gt;&lt;p&gt;--&lt;br&gt;&lt;br&gt;Hans Dockter&lt;br&gt;&lt;br&gt;&lt;br&gt;Gradle Project lead&lt;br&gt;&lt;br&gt;&lt;br&gt;&lt;a href="http://www.gradle.org" rel="nofollow noopener" target="_blank" title="http://www.gradle.org"&gt;http://www.gradle.org&lt;/a&gt;&lt;br&gt;&lt;br&gt;&lt;br&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Hans Dockter</dc:creator><pubDate>Mon, 07 Jul 2008 00:44:12 -0000</pubDate></item><item><title>Re: Is Maven going away?</title><link>http://www.warneronstine.com/2008/07/06/is-maven-going-away/#comment-16215800</link><description>&lt;p&gt;Buildr is a nice tool. But though the basic approach is similar to Gradle (Buildr was there first) there are also significant differences. Some of them are:&lt;/p&gt;&lt;p&gt;* Gradle is based on Ivy, the most advanced dependency management solution in the Java world.&lt;br&gt;* Gradle calculates the graph of tasks which actually gets executed beforehand. This is a very powerful feature. This graph for example is provided to the tasks during execution.&lt;br&gt;* Gradle offers sophisticated ways to configure multi-project builds.&lt;br&gt;* Gradle has a java-core which will eventually enable it to support multiple build script languages (e.g. JRuby). Though for a Java team (building Java projects is what Buildr and Gradle is mostly about) we think that Groovy is usually the language which offers the highest transparency to the developers.&lt;/p&gt;&lt;p&gt;Regarding the conciseness. I would be very interested in concrete examples to improve Gradle here.&lt;/p&gt;&lt;p&gt;--&lt;br&gt;&lt;br&gt;Hans Dockter&lt;br&gt;&lt;br&gt;&lt;br&gt;Gradle Project lead&lt;br&gt;&lt;br&gt;&lt;br&gt;&lt;a href="http://www.gradle.org" rel="nofollow noopener" target="_blank" title="http://www.gradle.org"&gt;http://www.gradle.org&lt;/a&gt;&lt;br&gt;&lt;br&gt;&lt;br&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Hans Dockter</dc:creator><pubDate>Mon, 07 Jul 2008 00:42:45 -0000</pubDate></item><item><title>Re: Is Maven going away?</title><link>http://www.warneronstine.com/2008/07/06/is-maven-going-away/#comment-16215799</link><description>&lt;p&gt;&amp;gt;First, let me say, I like Maven - a lot.&lt;br&gt;&amp;gt;I’ve liked the idea, if not the execution&lt;/p&gt;&lt;p&gt;100% agree. I am using maven for hobby projects, but I don't know if I would recommend it on the workplace. Too complicate, lack of documentation, plenty of bugs.&lt;/p&gt;&lt;p&gt;I don't think that maven is really chained to a specific language: some plugins can add support to other languages. Well, I'm not aware of those plugins, but itself maven doesn't preclude to other languages.&lt;br&gt;The reason why ant and maven use XML is to be language agnostic.&lt;br&gt;I find interesting gant and gmaven...&lt;/p&gt;&lt;p&gt;I wondering why nobody is writing jant and jmaven, now... :)&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Luigi</dc:creator><pubDate>Sun, 06 Jul 2008 22:53:02 -0000</pubDate></item><item><title>Re: Is Maven going away?</title><link>http://www.warneronstine.com/2008/07/06/is-maven-going-away/#comment-16215798</link><description>&lt;p&gt;Buildr is a nice tool. But though the basic approach is similar to Gradle (Buildr was there first) there are also significant differences. Some of them are:&lt;/p&gt;&lt;p&gt;* Gradle is based on Ivy, the most advanced dependency management solution in the Java world.&lt;br&gt;* Gradle calculates the graph of tasks which actually gets executed beforehand. This is a very powerful feature. This graph for example is provided to the tasks during execution.&lt;br&gt;* Gradle offers sophisticated ways to configure multi-project builds.&lt;br&gt;* Gradle has a java-core which will eventually enable it to support multiple build script languages (e.g. JRuby). Though for a Java team (building Java projects is what Buildr and Gradle is mostly about) we think that Groovy is usually the language which offers the highest transparency to the developers.&lt;/p&gt;&lt;p&gt;Regarding the conciseness. I would be very interested in concrete examples to improve Gradle here.&lt;/p&gt;&lt;p&gt;--&lt;br&gt;&lt;br&gt;Hans Dockter&lt;br&gt;&lt;br&gt;&lt;br&gt;Gradle Project lead&lt;br&gt;&lt;br&gt;&lt;br&gt;&lt;a href="http://www.gradle.org" rel="nofollow noopener" target="_blank" title="http://www.gradle.org"&gt;http://www.gradle.org&lt;/a&gt;&lt;br&gt;&lt;br&gt;&lt;br&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Hans Dockter</dc:creator><pubDate>Sun, 06 Jul 2008 21:14:36 -0000</pubDate></item><item><title>Re: Is Maven going away?</title><link>http://www.warneronstine.com/2008/07/06/is-maven-going-away/#comment-16215797</link><description>&lt;p&gt;Buildr is a nice tool. But though the basic approach is similar to Gradle (Buildr was there first) there are also significant differences. Some of them are:&lt;/p&gt;&lt;p&gt;* Gradle is based on Ivy, the most advanced dependency management solution in the Java world.&lt;br&gt;* Gradle calculates the graph of tasks which actually gets executed beforehand. This is a very powerful feature. This graph for example is provided to the tasks during execution.&lt;br&gt;* Gradle offers sophisticated ways to configure multi-project builds.&lt;br&gt;* Gradle has a java-core which will eventually enable it to support multiple build script languages (e.g. JRuby). Though for a Java team (building Java projects is what Buildr and Gradle is mostly about) we think that Groovy is usually the language which offers the highest transparency to the developers.&lt;/p&gt;&lt;p&gt;Regarding the conciseness. I would be very interested in concrete examples to improve Gradle here.&lt;/p&gt;&lt;p&gt;--&lt;br&gt;&lt;br&gt;Hans Dockter&lt;br&gt;&lt;br&gt;&lt;br&gt;Gradle Project lead&lt;br&gt;&lt;br&gt;&lt;br&gt;&lt;a href="http://www.gradle.org" rel="nofollow noopener" target="_blank" title="http://www.gradle.org"&gt;http://www.gradle.org&lt;/a&gt;&lt;br&gt;&lt;br&gt;&lt;br&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Hans Dockter</dc:creator><pubDate>Sun, 06 Jul 2008 21:13:04 -0000</pubDate></item><item><title>Re: Is Maven going away?</title><link>http://www.warneronstine.com/2008/07/06/is-maven-going-away/#comment-16215796</link><description>&lt;p&gt;To add multiple source directories, simply use the build-helper-maven-plugin, or better...the plugin implementing the compiler should define and add them itself.&lt;br&gt;The intent was to provide one default to the default java compiler, but the plugin api makes it possible (and desired) for new compiler plugins to be able to define their own standard and tell Maven about it.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Brian Fox</dc:creator><pubDate>Sun, 06 Jul 2008 17:27:40 -0000</pubDate></item><item><title>Re: Is Maven going away?</title><link>http://www.warneronstine.com/2008/07/06/is-maven-going-away/#comment-16215795</link><description>&lt;p&gt;You should give Buildr a try.  I've had some issues with it (particularly installation), but they seem to be working hard to resolve them.  It's somewhat similar to Gradle in that it is a drop-in replacement for Maven2, but quite a bit more concise (at least based on the examples I've seen).&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Daniel Spiewak</dc:creator><pubDate>Sun, 06 Jul 2008 13:20:14 -0000</pubDate></item></channel></rss>