maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lukas Theussl (JIRA)" <j...@codehaus.org>
Subject [jira] Commented: (MSITE-623) lifecycle dependency failure with code generation versus javadocs versus the site plugin
Date Thu, 08 Dec 2011 07:25:39 GMT

    [ https://jira.codehaus.org/browse/MSITE-623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=285204#comment-285204
] 

Lukas Theussl commented on MSITE-623:
-------------------------------------

Seems related to MSITE-171?

> lifecycle dependency failure with code generation versus javadocs versus the site plugin
> ----------------------------------------------------------------------------------------
>
>                 Key: MSITE-623
>                 URL: https://jira.codehaus.org/browse/MSITE-623
>             Project: Maven 2.x and 3.x Site Plugin
>          Issue Type: Bug
>          Components: Maven 3
>    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

        

Mime
View raw message