On 2013-11-04 10:03, Mikolaj Izdebski wrote: > On 11/04/2013 09:08 AM, Grzegorz Słowikowski wrote: >> Maybe I'm doing something wrong and maybe it's Maven bug. >> Failing with many Maven versions: 2.2.1, 3.0.x, 3.1.x >> >> I have multi-module test project for my plugin: >> https://maven-play-plugin.googlecode.com/svn/tags/test-projects-1.0.0-beta6/packagings/default/inter-app-dependency >> >> There are two submodules: "app1" and "app2", both with custom "play" >> packaging. "app2" depends on "app1". >> "play" packaging lifecycle is producing zip file (you can see "zip" in >> the logs). >> >> Everything starts working after installing "app1" in local repo, but >> this shouldn't be required. > This looks like MNG-5503 [1,2], which was fixed in Maven 3.1.1. > > [1] http://jira.codehaus.org/browse/MNG-5503 > [2] http://bugzilla.redhat.com/991454 > 1. In my case this does not work with Maven 3.1.1, even if I run "mvn package" first for "app1" module (produce "zip" file) 2. I have a mojo doing something if it finds reactor intermodule dependencies (lets say I want to log these dependencies only). I don't need "zip" files for this mojo at all.
Grzegorz Slowikowski --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org