Hi Did you find anything, any progress?
I would like to know if I can workaround this problem on my side. Thanks Grzegorz On 2013-11-04 16:55, Jason van Zyl wrote: > Danke. > > On Nov 4, 2013, at 10:51 AM, Grzegorz Słowikowski > <gslowikow...@gmail.com <mailto:gslowikow...@gmail.com>> wrote: > >> Simplified version commited here: >> >> http://maven-play-plugin.googlecode.com/svn/tmp/test-projects/reactor-problem/ >> >> Grzegorz >> >> On 4 listopad 2013 15:12:45, Jason van Zyl wrote: >>> If I checkout your test project it doesn't build. If you make a self >>> contained example that builds I'll take a look. It is most >>> definitely a problem with the WorkspaceReader which should be >>> relatively easy to fix. >>> >>> On Nov 4, 2013, at 3:08 AM, Grzegorz Słowikowski >>> <gslowikow...@gmail.com> wrote: >>> >>>> Hi >>>> >>>> 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. >>>> >>>> >>>> "play" packaging is defined here, for reference: >>>> http://maven-play-plugin.googlecode.com/svn/tags/plugin-1.0.0-beta6/play-maven-plugin/src/main/resources/META-INF/plexus/components.xml >>>> >>>> Calling "mvn initialize": >>>> >>>> with Maven 2.2.1: >>>> >>>> [INFO] Scanning for projects... >>>> [INFO] Reactor build order: >>>> [INFO] Play! Framework Maven Test Projects : Packagings : Default : >>>> Inter-App Dependency : App1 >>>> [INFO] Play! Framework Maven Test Projects : Packagings : Default : >>>> Inter-App Dependency : App2 >>>> [INFO] Play! Framework Maven Test Projects : Packagings : Default : >>>> Inter-App Dependency >>>> [INFO] >>>> ------------------------------------------------------------------------ >>>> [INFO] Building Play! Framework Maven Test Projects : Packagings : >>>> Default : Inter-App Dependency : App1 >>>> [INFO] task-segment: [initialize] >>>> [INFO] >>>> ------------------------------------------------------------------------ >>>> [INFO] [enforcer:enforce {execution: enforce-maven}] >>>> [INFO] [play:initialize {execution: default-initialize}] >>>> [INFO] >>>> ------------------------------------------------------------------------ >>>> [INFO] Building Play! Framework Maven Test Projects : Packagings : >>>> Default : Inter-App Dependency : App2 >>>> [INFO] task-segment: [initialize] >>>> [INFO] >>>> ------------------------------------------------------------------------ >>>> Downloading: >>>> http://repo1.maven.org/maven2/com/google/code/maven-play-plugin/test-projects/packagings/default/inter-app-dependency/app1/1.0.0-beta6/app1-1.0.0-beta6.zip >>>> [INFO] Unable to find resource >>>> 'com.google.code.maven-play-plugin.test-projects.packagings.default.inter-app-dependency:app1:play:1.0.0-beta6' >>>> in repository central (http://repo1.maven.org/maven2) >>>> [INFO] >>>> ------------------------------------------------------------------------ >>>> [ERROR] BUILD ERROR >>>> [INFO] >>>> ------------------------------------------------------------------------ >>>> [INFO] Failed to resolve artifact. >>>> >>>> Missing: >>>> ---------- >>>> 1) >>>> com.google.code.maven-play-plugin.test-projects.packagings.default.inter-app-dependency:app1:play:1.0.0-beta6 >>>> >>>> Try downloading the file manually from the project website. >>>> >>>> Then, install it using the command: >>>> mvn install:install-file >>>> -DgroupId=com.google.code.maven-play-plugin.test-projects.packagings.default.inter-app-dependency >>>> -DartifactId=app1 -Dversion=1.0.0-beta6 -Dpackaging=play >>>> -Dfile=/path/to/file >>>> >>>> Alternatively, if you host your own repository you can deploy the file >>>> there: >>>> mvn deploy:deploy-file >>>> -DgroupId=com.google.code.maven-play-plugin.test-projects.packagings.default.inter-app-dependency >>>> -DartifactId=app1 -Dversion=1.0.0-beta6 -Dpackaging=play >>>> -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] >>>> >>>> Path to dependency: >>>> 1) >>>> com.google.code.maven-play-plugin.test-projects.packagings.default.inter-app-dependency:app2:play:1.0.0-beta6 >>>> 2) >>>> com.google.code.maven-play-plugin.test-projects.packagings.default.inter-app-dependency:app1:play:1.0.0-beta6 >>>> >>>> ---------- >>>> 1 required artifact is missing. >>>> >>>> for artifact: >>>> >>>> com.google.code.maven-play-plugin.test-projects.packagings.default.inter-app-dependency:app2:play:1.0.0-beta6 >>>> >>>> from the specified remote repositories: >>>> central (http://repo1.maven.org/maven2), >>>> sonatype-nexus-snapshots >>>> (https://oss.sonatype.org/content/repositories/snapshots) >>>> >>>> >>>> >>>> [INFO] >>>> ------------------------------------------------------------------------ >>>> [INFO] For more information, run Maven with the -e switch >>>> [INFO] >>>> ------------------------------------------------------------------------ >>>> [INFO] Total time: 5 seconds >>>> [INFO] Finished at: Mon Nov 04 08:52:36 CET 2013 >>>> [INFO] Final Memory: 22M/54M >>>> [INFO] >>>> ------------------------------------------------------------------------ >>>> >>>> ============================================================================================== >>>> >>>> with Maven 3.0.5 and 3.1.1: >>>> >>>> [INFO] Scanning for projects... >>>> [WARNING] >>>> [WARNING] Some problems were encountered while building the effective >>>> model for >>>> com.google.code.maven-play-plugin.test-projects.packagings.default.inter-app-dependency:app1:play:1.0.0-beta6 >>>> [WARNING] 'parent.relativePath' points at >>>> com.google.code.maven-play-plugin.test-projects.packagings.default:inter-app-dependency >>>> instead of com.google.code.maven-play-plugin:play-app-default-parent, >>>> please verify your project structure @ line 21, column 13 >>>> [WARNING] >>>> [WARNING] It is highly recommended to fix these problems because they >>>> threaten the stability of your build. >>>> [WARNING] >>>> [WARNING] For this reason, future Maven versions might no longer >>>> support >>>> building such malformed projects. >>>> [WARNING] >>>> [INFO] >>>> ------------------------------------------------------------------------ >>>> [INFO] Reactor Build Order: >>>> [INFO] >>>> [INFO] Play! Framework Maven Test Projects : Packagings : Default : >>>> Inter-App Dependency : App1 >>>> [INFO] Play! Framework Maven Test Projects : Packagings : Default : >>>> Inter-App Dependency : App2 >>>> [INFO] Play! Framework Maven Test Projects : Packagings : Default : >>>> Inter-App Dependency >>>> [INFO] >>>> >>>> >>>> [INFO] >>>> ------------------------------------------------------------------------ >>>> [INFO] Building Play! Framework Maven Test Projects : Packagings : >>>> Default : Inter-App Dependency : App1 1.0.0-beta6 >>>> [INFO] >>>> ------------------------------------------------------------------------ >>>> [INFO] >>>> [INFO] --- maven-enforcer-plugin:1.0:enforce (enforce-maven) @ app1 --- >>>> [INFO] >>>> [INFO] --- play-maven-plugin:1.0.0-beta6:initialize >>>> (default-initialize) >>>> @ app1 --- >>>> [INFO] >>>> >>>> >>>> [INFO] >>>> ------------------------------------------------------------------------ >>>> [INFO] Building Play! Framework Maven Test Projects : Packagings : >>>> Default : Inter-App Dependency : App2 1.0.0-beta6 >>>> [INFO] >>>> ------------------------------------------------------------------------ >>>> [INFO] >>>> ------------------------------------------------------------------------ >>>> [INFO] Reactor Summary: >>>> [INFO] >>>> [INFO] Play! Framework Maven Test Projects : Packagings : Default : >>>> Inter-App Dependency : App1 SUCCESS [2.562s] >>>> [INFO] Play! Framework Maven Test Projects : Packagings : Default : >>>> Inter-App Dependency : App2 FAILURE [0.110s] >>>> [INFO] Play! Framework Maven Test Projects : Packagings : Default : >>>> Inter-App Dependency SKIPPED >>>> [INFO] >>>> ------------------------------------------------------------------------ >>>> [INFO] BUILD FAILURE >>>> [INFO] >>>> ------------------------------------------------------------------------ >>>> [INFO] Total time: 3.735s >>>> [INFO] Finished at: Mon Nov 04 08:53:41 CET 2013 >>>> [INFO] Final Memory: 6M/16M >>>> [INFO] >>>> ------------------------------------------------------------------------ >>>> [ERROR] Failed to execute goal on project app2: Could not resolve >>>> dependencies for project >>>> com.google.code.maven-play-plugin.test-projects.packagings.default.inter-app-dependency:app2:play:1.0.0-beta6: >>>> Failure to find >>>> com.google.code.maven-play-plugin.test-projects.packagings.default.inter-app-dependency:app1:zip:1.0.0-beta6 >>>> in http://repo.maven.apache.org/maven2 was cached in the local >>>> repository, resolution will not be reattempted until the update >>>> interval >>>> of central has elapsed or updates are forced -> [Help 1] >>>> [ERROR] >>>> [ERROR] To see the full stack trace of the errors, re-run Maven >>>> with the >>>> -e switch. >>>> [ERROR] Re-run Maven using the -X switch to enable full debug logging. >>>> [ERROR] >>>> [ERROR] For more information about the errors and possible solutions, >>>> please read the following articles: >>>> [ERROR] [Help 1] >>>> http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException >>>> [ERROR] >>>> [ERROR] After correcting the problems, you can resume the build >>>> with the >>>> command >>>> [ERROR] mvn <goals> -rf :app2 >>>> >>>> P.S. >>>> >>>> Adding: >>>> >>>> <build> >>>> <plugins> >>>> <plugin> >>>> <groupId>com.google.code.maven-play-plugin</groupId> >>>> <artifactId>play-maven-plugin</artifactId> >>>> <version>1.0.0-beta6</version> >>>> <extensions>true</extensions> >>>> </plugin> >>>> </plugins> >>>> </build> >>>> >>>> to parent pom doesn't help. >>>> >>>> Regards >>>> Grzegorz Slowikowski >>>> >>>> >>>> --------------------------------------------------------------------- >>>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org >>>> For additional commands, e-mail: dev-h...@maven.apache.org >>>> >>> >>> Thanks, >>> >>> Jason >>> >>> ---------------------------------------------------------- >>> Jason van Zyl >>> Founder, Apache Maven >>> http://twitter.com/jvanzyl >>> --------------------------------------------------------- >>> >>> >>> >>> >>> >>> >>> >>> > > Thanks, > > Jason > > ---------------------------------------------------------- > Jason van Zyl > Founder, Apache Maven > http://twitter.com/jvanzyl > --------------------------------------------------------- > > > > > > >
