Talk:Apache Maven

message: I remove the links to the Maven repositories; they contain no useful information about Maven. The official Maven sites (v.1 and v.2) link to the Maven repositories. --Philippe 12:46, 22 November 2006 (UTC)
thread_title:  repository links 

message: I removed the entire "key criticisms" section.  Above all considerations, that section was completely unsourced.  Unsourced content must be removed when challenged, and I hereby so challenge.   Secondarily, I think the documentation issue was a legitimate criticism, though not "key".  In my mind a useful dialogue would be the common complaint that Maven requires adherence to a certain project layout, followed by a discussion as to why that path was chosen and the benefits it purports to bring.   But above all, Wikipedia entries must have reputable external primary sources, and this section did not have any.   139.76.128.71 18:25, 26 March 2007 (UTC)
replies: text: http://www.oreillynet.com/onjava/blog/2006/03/maven_project_info_reports_con.html  —The preceding unsigned comment was added by 203.217.22.128 (talk) 01:45, August 23, 2007 (UTC) 
I have added the explanation/criticism of Maven's rigid "convention over configuration" doctrine.  This is one of the major aspects of Maven, which some consider its greatest weakness and others its greatest strength, and the article is not complete without some treatment of it.  Have linked back to the "what is maven" page which states, among other things, "If you decide to use Maven, and have an unusual build structure that you cannot reorganise, you may have to forgo some features or the use of Maven altogether." Lucky Bottlecap (talk) 15:03, 28 February 2008 (UTC)
replies: text:  Seems reasonable. Also there is an implicit assumption about lifecycle that is unchangeable. What if you test after deployment, go through staging operations, etc? I suppose that is dealt with by creating meta-projects. The other area of concern to me is POM quality in the m2 repository; POM files grandfathered in from the maven 1 repository are mediocre, and newer artifacts often have too many dependencies. SteveLoughran (talk)  —Preceding comment was added at 15:30, 28 February 2008 (UTC)
replies: text: If you test after deployment, that's integration testing that is done on the integration test phase. Default test phase is for unit tests. I don't see a problem with Maven approach on this. Slsh (talk) 10:09, 11 November 2013 (UTC)
thread_title:  Removing key criticisms 

message: The introduction is very misleading.  The second sentence: It is similar in functionality to the Apache Ant tool (and to a lesser extent, PHP's PEAR and Perl's CPAN), but has a simpler build configuration model, based on an XML format.
This leads the reader to believe that Maven is a combination procedural / declarative build tool (Like Ant or Make) combined with a global package management repository like CPAN or PEAR.  The first assertion is almost correct, as Maven does in fact bundle and include Ant (among many other tools).  The second is wildly off the mark - things like CPAN and PEAR serve as a single point of distribution for the collected body of user created code for their respective programming languages, whereas Maven's notion of repositories serve as a means of managing all the artifacts (both project specific and third party) required to build a particular project.  There are global Maven repositories being run by various parties, but all of those draw their artifacts from the sites their respective project teams released them on.
I realize it's not kosher to copy from other sites, but the first sentence of the Maven web site conveys the truth most succinctly: Maven is a software project management and comprehension tool. Based on the concept of a project object model (POM), Maven can manage a project's build, reporting and documentation from a central piece of information. 
--chrisfeohpatti  —Preceding comment was added at 18:45, 24 June 2008 (UTC)
thread_title:  Misleading Introduction 

message: isn't the phrase "has a simpler build configuration model" also POV?  who says it's simpler -- do the people who use/love ant agree?  —Preceding unsigned comment added by 71.222.108.142 (talk) 02:43, 28 January 2009 (UTC)
thread_title:  Question about Intro 

message: I added references for Netbeans & IntelliJ IDEA support. Some work may still need to be done on this section; at some point, it may even be removed completely: since the 'big 3' (nebeans/intellij/eclipse) & by extension their derivatives all support Maven (others may as well), this really isn't notable.  The only distinction will be the differing levels of maven-related features, which would be more appropriately listed on their respective IDE page.
I also rephrased the sentence "there are maven plugins for creating IDE configuration files from the POM", since that is an antiquated (and incomplete) solution for binding the IDE to the POM, originally implemented just to get maven working with the IDE.  Today, IDE's have Maven support more or less 'natively' (e.g., it comes by default w/ netbeans -- no longer needs to be manually added:  just "file -> open" on a maven project, with no intermediate "project" files). Note: it also may not be evident to casual readers that distinguishing a feature as a "plugin" or "supported natively" is largely irrelevant (e.g,. just about everything is a plugin in Eclipse), and really doesn't imply better or worse tool integration. Michael (talk|contrib)  —Preceding undated comment added 01:32, 2 September 2009 (UTC)
thread_title:  IDE support 

message: Could someone with better wiki-fu than mine please put a disambiguation link to the word "maven" at the top of the article? My feeble attempts yield a link to a nonexistent "Apache Maven (Disambiguation)" page. The correct page is at http://en.wikipedia.org/wiki/Maven_(disambiguation)  —Preceding unsigned comment added by 66.173.46.50 (talk) 18:35, 25 March 2011 (UTC)
replies: text: Seems strange that a person would end up here, but be looking for some other use of Maven, are you sure including the disambiguation link would be helpful? Monty845 18:45, 25 March 2011 (UTC)
thread_title:  Disambiguation 

message: Hello fellow Wikipedians,
I have just modified  on Apache Maven. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:
*Added archive http://web.archive.org/web/20150507014621/http://maven.apache.org:80/eclipse-plugin.html to https://maven.apache.org/eclipse-plugin.html
When you have finished reviewing my changes, please set the checked parameter below to true or failed to let others know (documentation at ).
Cheers.—cyberbot IITalk to my owner:Online 10:57, 24 June 2016 (UTC)
thread_title:  External links modified 

message: Hello fellow Wikipedians,
I have just modified one external link on Apache Maven. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:
*Added archive https://web.archive.org/web/20130421060027/http://www.sonatype.com/books/mvnref-book/reference/installation-sect-compare-ant-maven.html to http://www.sonatype.com/books/mvnref-book/reference/installation-sect-compare-ant-maven.html
When you have finished reviewing my changes, you may follow the instructions on the template below to fix any issues with the URLs.
Cheers.—InternetArchiveBot (Report bug) 21:52, 7 July 2017 (UTC)
thread_title:  External links modified