maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "M. Hansen (JIRA)" <j...@codehaus.org>
Subject [jira] Commented: (MNG-3763) Site / Dependency / Classifier Issue
Date Thu, 12 Feb 2009 22:46:20 GMT

    [ http://jira.codehaus.org/browse/MNG-3763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=165365#action_165365
] 

M. Hansen commented on MNG-3763:
--------------------------------

Yes, I see this problem as well. We have a bamboo server doing 'mvn clean deploy site:site
site:deploy' for most of our builds. Our builds are multi-projects (ear with war, ejb and
some jars). In a couple of cases we have jar X that produces both a jar and a test-jar. If
another jar Y has dependencies to X's test-jar and jar then the EAR will include X's test-jar
and not the jar version of X.

> Site / Dependency / Classifier Issue
> ------------------------------------
>
>                 Key: MNG-3763
>                 URL: http://jira.codehaus.org/browse/MNG-3763
>             Project: Maven 2
>          Issue Type: Bug
>          Components: Dependencies
>    Affects Versions: 2.0.9, 2.1.0-M1
>         Environment: Maven 2.0.9, Maven 2.1.0-M1, Windows, CentOS
>            Reporter: Geoffrey Wiseman
>             Fix For: 2.0.x
>
>         Attachments: dependency-site-bug.zip
>
>
> When the attached project is run with "mvn clean install" it's successful.  When "mvn
clean install site" is run, the build fails to compile.  Seems like it's a bug, not sure where
the bug lies.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message