Re: [ANN] Apache Maven 3.0-beta-1 Released
Excellent stuff, I ran my own 2 projects through maven 3 and got errors but all of them came down either to my own ones (double setting of a repository) or a deprecated plugin which had a successor. So for me, no error to report. Werner Am 23.04.10 15:05, schrieb Benjamin Bentmann: The Maven team is pleased to announce the release of Apache Maven 3.0-beta-1. Maven is a project comprehension and build tool, designed to simplify the process of maintaining a healthy development lifecycle for your project. You can read more here: http://maven.apache.org/ Downloads of source and binary distributions are listed in our download section: http://maven.apache.org/download.html A major goal of Maven 3.0 is to be compatible, to the extent possible, with existing plugins and projects designed for Maven 2.x. Users interested in testing this beta release should have a glance at the compatibility notes for known differences between Maven 3.0 and Maven 2.x: http://cwiki.apache.org/MAVEN/maven-3x-compatibility-notes.html If you encounter unexpected problems while using Maven 3.0-beta-1, please feel free to contact us via the Maven developer list: http://maven.apache.org/mail-lists.html Release Notes - Maven 2 3 - Version 3.0-beta-1 ** Bug * [MNG-1751] - merging metadata doesn't fail when timestamp is in the future * [MNG-2103] - Inheritance of plugin overrides that of execution * [MNG-] - dependency to dependency without source code fails * [MNG-2276] - profile activation by property doesn't work with properties defined in settings. * [MNG-2994] - Snapshot repositories are not checked when using ranges * [MNG-3092] - Version ranges with non-snapshot bounds can contain snapshot versions * [MNG-3133] - DefaultModelInheritence::appendPath assumes it is operating on interpolated/literal paths * [MNG-3470] - Build does not fail on corrupted POM even with checksumPolicy=fail * [MNG-3477] - Authentication failures on dependency download aren't reported * [MNG-3529] - mvn -Da= throws an excepltion * [MNG-3616] - Null Pointer Exception when mirrorOf missing from mirror in settings.xml * [MNG-3700] - ModelUtils.clone doesn't clone plugin entries where inherited == false * [MNG-4022] - Incorrect merge behavior using profile driven plugin configuration * [MNG-4326] - Maven should not check snapshot repositories for dependencies in the reactor * [MNG-4418] - Dependency resolution appears to misbehave if a remote repository uses the id local * [MNG-4453] - [regression] Plugin versions defined in a lifecycle mapping are not respected * [MNG-4555] - mvn archetype:generate -o (offline) still results in a checking updates from central * [MNG-4580] - Plugin dependencies for module ignored when building from aggregator project using direct plugin invocation * [MNG-4586] - Plugin prefix can't be resolved from plugin management if management entry is missing plugin version * [MNG-4590] - [regression] System properties are no longer interpolated in imported POMs * [MNG-4600] - [regression] Optional flag from dependency management applied to dependencies * [MNG-4618] - maven-javadoc-plugin aggregate-jar fails with maven3 and multiple modules * [MNG-4625] - Interpolation of settings.xml fails if an expression's value contains XML markup * [MNG-4629] - [regression] POM validation fails upon non-existing system-scope dependency * [MNG-4632] - Class loading is not thread-safe ** Improvement * [MNG-1701] - Validate that a plugin is not configured twice in the pom * [MNG-2187] - Improve error message when the pom is encoded in the wrong charset * [MNG-2741] - [regression] Meaningless error message: Error transferring file * [MNG-3004] - Allow build lifecycle to execute projects in parallel * [MNG-3779] - Improve error message when trying to execute mojo with no pom.xml * [MNG-4162] - Removal of all reporting logic from the core of Maven * [MNG-4194] - API to safely release of plugin realms * [MNG-4591] - Enhance the download rate output to include downloaded file name * [MNG-4610] - Bump maven-release-plugin to v2.0 in super POM * [MNG-4619] - Issue warning in case parent.relativePath points at POM with different groupId/artifactId * [MNG-4623] - model parsing errors can be less helpful in Maven 3 * [MNG-4628] - ReactorArtifactRepository is not setup soon enough for AbstractMavenLifecycleParticipant#afterProjectsRead * [MNG-4634] - Allow custom lifecycles ** Task * [MNG-3917] - Complete the POM construction tests which will be the validation for the specification Enjoy, -The Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Unclear about maven web app directory structure
Hi all, I've recently started learning/using maven, and I'm unclear where my source code is supposed to go. I used the maven archetype:create goal to create a webapp. In Maven by Example the servlet source code is placed in 'src/main/java/'. However, according to Introduction to the Standard Directory Layout on the maven website 'src/main/webapp' is for the web application sources. Can someone explain: 1. The difference between the two directories, i.e. /src/main/webapp /src/main/java 2. Where the source code is supposed to go? Thanks. -Dan - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Unclear about maven web app directory structure
The java folder is for your java source code, while the webapp folder is for your web application source files such as jsp files. Create a jar project through the quickstart archetype to get an example of the former and the webapp archetype shows the latter. /Anders On Sun, Apr 25, 2010 at 21:59, Dan King dan.king...@yahoo.com wrote: Hi all, I've recently started learning/using maven, and I'm unclear where my source code is supposed to go. I used the maven archetype:create goal to create a webapp. In Maven by Example the servlet source code is placed in 'src/main/java/'. However, according to Introduction to the Standard Directory Layout on the maven website 'src/main/webapp' is for the web application sources. Can someone explain: 1. The difference between the two directories, i.e. /src/main/webapp /src/main/java 2. Where the source code is supposed to go? Thanks. -Dan - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Unclear about maven web app directory structure
From: Anders Hammar and...@hammar.net To: Maven Users List users@maven.apache.org Sent: Sun, April 25, 2010 4:11:57 PM Subject: Re: Unclear about maven web app directory structure The java folder is for your java source code, while the webapp folder is for your web application source files such as jsp files. Create a jar project through the quickstart archetype to get an example of the former and the webapp archetype shows the latter. /Anders So, if I understand correctly for 'jar' projects the source code goes in the src/main/java directory, while in webapps the source code (such as jsps, servlets, daos, models, etc.) go into the src/main/webapp directory. Not to be belabor the question, but why in Maven by Example is the source code for the simple servlet in the src/main/java directory? Link to the example follows: http://www.sonatype.com/books/mvnex-book/reference/web-sect-adding-simple-servlet.html Thanks, Dan - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Cobertura Maven Plugin 2.4 released
The Mojo team is pleased to announce the release of the Cobertura Maven Plugin, version 2.4. Documentation on the plugin can be found here: http://mojo.codehaus.org/cobertura-maven-plugin/ Release Notes ** Bug * [MCOBERTURA-49] - Fails if JRE is not on System Path * [MCOBERTURA-67] - mvn cobertura:cobertura class loader problem * [MCOBERTURA-98] - Trivial typos in CommandLineArguments and CoberturaReportMojo javadocs * [MCOBERTURA-105] - AbstractCoberturaTestCase hasn't been upgraded to cobertura 1.9.2 ** Improvement * [MCOBERTURA-113] - Upgrade to cobertura 1.9.3 * [MCOBERTURA-120] - Update to Cobertura 1.9.4.1 * [MCOBERTURA-122] - Upgrade plexus-utils version to 2.0.2 ** New Feature * [MCOBERTURA-85] - Configuration for different report encodings (other than UTF-8) ** Task * [MCOBERTURA-111] - Missing url tag in pom.xml -- Simon Brandhof
Re: Unclear about maven web app directory structure
So, if I understand correctly for 'jar' projects the source code goes in the src/main/java directory, while in webapps the source code (such as jsps, servlets, daos, models, etc.) go into the src/main/webapp directory. The only thing that should go in webapp is jsps, in my opinion. The rest (including servlets) goes in src/main/java and is included as a dependency (of type jar) to the war. And obviously the daos, models etc go in src/main/java too. Not to be belabor the question, but why in Maven by Example is the source code for the simple servlet in the src/main/java directory? This is how I'd suggest doing it as well. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
