[jira] Moved: (MNG-5214) lifecycle dependency failure with code generation versus javadocs versus the site plugin

["Benson Margulies (JIRA)" <ji...@codehaus.org>]

     [ https://jira.codehaus.org/browse/MNG-5214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Benson Margulies moved MSITE-623 to MNG-5214:
---------------------------------------------

           Complexity: Intermediate
          Component/s:     (was: Maven 3)
                       Dependencies
    Affects Version/s:     (was: 3.0)
                       3.0
                  Key: MNG-5214  (was: MSITE-623)
              Project: Maven 2 & 3  (was: Maven 2.x and 3.x Site Plugin)

> lifecycle dependency failure with code generation versus javadocs versus the site plugin
> ----------------------------------------------------------------------------------------
>
>                 Key: MNG-5214
>                 URL: https://jira.codehaus.org/browse/MNG-5214
>             Project: Maven 2 & 3
>          Issue Type: Bug
>          Components: Dependencies
>    Affects Versions: 3.0
>            Reporter: Benson Margulies
>
> This is related to MSITE-622.
> In a multi-module project, one module has a plugin execution in phase 'process-classes' that produces an attached artifact (with type 'wsdl').
> A second module depends on it, and has another plugin execution in phase 'generate-sources' that depends on the artifact from the first one.
> The second project declares this dependency.
> When I run site:site, it does not run compile, or process-classes, so the wsdl artifact is not in the reactor, and then the second plugin can't find it, and the build fails (and, as per -622, no explanation is shown without -X). (That's particularly odd, since it should be sitting in the local repo from a previous build.)
> How is something like this supposed to work?

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira