[
https://issues.apache.org/jira/browse/MNG-5983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15200308#comment-15200308
]
Karl Heinz Marbaise commented on MNG-5983:
------------------------------------------
I have taken a look into those large log files and both are representing a
failed build...After reading that log file i have found that the
utilsConvergeLib is defined as aar file type in the maven 3.2.5 build and with
scope provided where it is defined in maven 3.3.9 build as jar file type and
scope system ?
> Builds with Maven 3.3.x fail, where they worked with Maven 3.2.x
> ----------------------------------------------------------------
>
> Key: MNG-5983
> URL: https://issues.apache.org/jira/browse/MNG-5983
> Project: Maven
> Issue Type: Bug
> Affects Versions: 3.3.9
> Environment: Mac OS X 10.10.5
> java version "1.7.0_79"
> Java(TM) SE Runtime Environment (build 1.7.0_79-b15)
> Java HotSpot(TM) 64-Bit Server VM (build 24.79-b02, mixed mode)
> Reporter: Micah Koch
> Attachments: RulesEngine-Aware.maven3.2.5.pom.gz,
> RulesEngine-Aware.maven3.3.9.pom.gz, maven3.2.5.log.gz, maven3.3.9.log.gz
>
>
> When we try to build our multi-module project with Maven 3.3.x it fails,
> where it works with 3.2.5. It seems to fail saying it couldn't find a
> dependency, but that dependency does not exist for the project. Attaching
> build logs for both 3.2.5 and 3.3.9 builds, as well the effective pom for the
> component that fails on both.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
