[ https://issues.apache.org/jira/browse/MDEP-516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16009622#comment-16009622 ]
Archimedes Trajano commented on MDEP-516: ----------------------------------------- One thing I noticed though, EJBs will work correctly but not WAR packaging. Based on my build result [INFO] Java EE Sample App ................................. SUCCESS [ 3.660 s] [INFO] Database Administration ............................ SUCCESS [ 1.354 s] [INFO] Domain objects API ................................. SUCCESS [ 1.042 s] [INFO] Domain objects implementation ...................... SUCCESS [ 1.697 s] [INFO] JASPIC Implementation .............................. SUCCESS [ 0.974 s] [INFO] Natural Language Processing API .................... SUCCESS [ 0.860 s] [INFO] Web Application Archive ............................ FAILURE [ 0.908 s] [INFO] Web Services ....................................... SKIPPED [INFO] Natural Language Processing backend ................ SKIPPED [INFO] ReactJS Application ................................ SKIPPED [INFO] Web API ............................................ SKIPPED [INFO] Enterprise Application Archive ..................... SKIPPED > Go-offline does not find module dependencies in multi-module build. > ------------------------------------------------------------------- > > Key: MDEP-516 > URL: https://issues.apache.org/jira/browse/MDEP-516 > Project: Maven Dependency Plugin > Issue Type: Bug > Components: go-offline > Affects Versions: 2.10 > Reporter: Petar Tahchiev > > Hello, > I've recently hit the exact same problem that these guys are having: > http://stackoverflow.com/questions/14694139/how-to-resolve-dependencies-between-modules-within-multi-module-project > and I thought it must be a very normal scenario so probably a lot of other > people are hitting. > So basically I have a multi-module build where {{moduleA}} is built first and > them {{moduleB}} depends on {{moduleA}}. However when I do {{mvn > dependency:go-offline}} it comes to resolve the dependencies of {{moduleB}} > and it fails with {{Artifact not found: moduleA}}. > That seems to happen because only modules that have been packaged are put in > the reactor and so later modules will know about them. So to fix it I have to > do the following: > {code} > mvn package dependency:go-offline -U -Pquick,test -DskipTests -s > src/main/resources/settings.xml > {code} > which I really don't like, because it does an extra package that I don't > need, and then the whole build gets a lot slower. > of course, {{mvn install}} at any time fixes the issue also, but I don't want > to install -- This message was sent by Atlassian JIRA (v6.3.15#6346)