maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Scholte (JIRA)" <j...@codehaus.org>
Subject [jira] (MASSEMBLY-678) Assembly using <repositories> mucks with classpath for later portions of the build
Date Sun, 05 Jan 2014 21:12:45 GMT

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

Robert Scholte moved MNG-5531 to MASSEMBLY-678:
-----------------------------------------------

           Complexity:   (was: Intermediate)
          Component/s:     (was: Plugins and Lifecycle)
    Affects Version/s:     (was: 3.1.0)
                  Key: MASSEMBLY-678  (was: MNG-5531)
              Project: Maven Assembly Plugin  (was: Maven 2 & 3)
    
> Assembly using <repositories> mucks with classpath for later portions of the build
> ----------------------------------------------------------------------------------
>
>                 Key: MASSEMBLY-678
>                 URL: https://jira.codehaus.org/browse/MASSEMBLY-678
>             Project: Maven Assembly Plugin
>          Issue Type: Bug
>         Environment: OSX, jdk8
>            Reporter: bob mcwhirter
>
> If a maven-assembly-plugin execution run during the 'package' phase includes a <repositories>
element to gather up dependencies, it appears that dependency filtering is performed, removing
dependencies with scope of 'test'.
> This breaks integration tests that run subsequent to 'package' phase.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message