[
https://jira.codehaus.org/browse/MENFORCER-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=340268#comment-340268
]
Karl Heinz Marbaise edited comment on MENFORCER-168 at 1/27/14 3:12 PM:
------------------------------------------------------------------------
After checking your pull request i've tested with Maven 3.0.4, Maven 3.0.5,
Maven 3.1.0 and Maven 3.1.1. and it does not work with **none** of them.
But:
I've taken a deeper look into it and realized that the integration tests are
running by calling maven (via maven-invoker-plugin) like this:
{code}mvn validate{code}
LIfecylce. If you do that directly on the command with the example project it
will fail also. The problem is causes that during the validate lifecycle no
artifact (jar) has been created. That means in other words the artifacts are
not available in the reactor as well.
If you call Maven via:
{code}mvn package{code}
It works without any problem.
Furthermore if you add an {{invoker.properties}} into your root of your project
with the following content:
{code}invoker.goals=clean package{code}
everything is fine.
was (Author: khmarbaise):
After checking your pull request i've tested with Maven 3.0.4, Maven 3.0.5,
Maven 3.1.0 and Maven 3.1.1. and it does not work with **none** of them.
But:
I've taken a deeper look into it and realized that the integration tests are
running by calling maven (via maven-invoker-plugin) like this:
{code}mvn validate{code}
LIfecylce. If you do that directly on the command with the example project it
will fail also. The problem is causes that during the validate lifecycle no
artifact (jar) has been created. That means in other words the artifacts are
not available in the reactor as well.
If you call Maven via:
{code}mvn package{code}
It works without any problem.
Furthermore if you add an {{invoker.properties}} into your root of your project
everything is fine.
> In a multi module project "bannedDependencies" rule tries to resolve project
> artifacts from external repository
> ---------------------------------------------------------------------------------------------------------------
>
> Key: MENFORCER-168
> URL: https://jira.codehaus.org/browse/MENFORCER-168
> Project: Maven Enforcer Plugin
> Issue Type: Bug
> Components: Standard Rules
> Affects Versions: 1.3.1
> Reporter: Conny Kreyssel
> Priority: Critical
>
> I have created a pull request with a IT case on github.
> see https://github.com/apache/maven-enforcer/pull/6
> Seems to be a problem with maven 3.1.1. The IT runs with maven 3.0.4 but
> fails with 3.1.1.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
