[jira] Created: (MNG-4999) Maven should fail the build or give a warning when there are cyclic dependencies
Maven should fail the build or give a warning when there are cyclic dependencies Key: MNG-4999 URL: http://jira.codehaus.org/browse/MNG-4999 Project: Maven 2 & 3 Issue Type: Bug Components: POM Affects Versions: 3.0.2, 2.2.1 Environment: any Reporter: Phillip Hellewell Maven gives no warning or error when there are cyclic dependencies. It should give at least a warning, and have the ability to fail the build through an option. How to reproduce: 1. Make B that doesn't depend on anything. Deploy a snapshot of B. 2. Make A that depends on the snapshot of B . Deploy a snapshot of A. 3. Change B to depend on the snapshot of A. Now deploy a new snapshot of B (same version as in step 1). I would venture to say that the perc. of people who actually want to allow cycles is smaller than the percentage who want to catch it as an error. -- 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
[jira] Updated: (MASSEMBLY-544) DependencySet includes filter not working in 2.2
[
http://jira.codehaus.org/browse/MASSEMBLY-544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dennis Lundberg updated MASSEMBLY-544:
--
Summary: DependencySet includes filter not working in 2.2 (was:
DependencySet includes filter not working after 2.2-beta-2)
> DependencySet includes filter not working in 2.2
>
>
> Key: MASSEMBLY-544
> URL: http://jira.codehaus.org/browse/MASSEMBLY-544
> Project: Maven 2.x Assembly Plugin
> Issue Type: Bug
>Affects Versions: 2.2
> Environment: win32, Maven 2.2.1 and Maven 3.0.2
>Reporter: Omer A Kudat
>
> If the includes/include "subelements are present, they define a set of
> artifact coordinates to include." That's the definition from the assembly
> site. Until recently, we have been using this filter as advertised. However,
> yesterday we upgraded the plugin from 2.2-beta-2 to 2.2. Now, the inclusion
> filter has no effect, and all dependencies are included.
> {code}
>
> http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="http://maven.apache.org/xsd/assembly-1.1.0-SNAPSHOT.xsd";>
> dam
>
> tar
>
> true
> ${project.version}
>
>
>
> ${artifact.artifactId}.${artifact.extension}
> lib
> 0744
> 0755
>
> true
> true
>
> com.mycompany*
>
>
>
>
> {code}
--
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
[jira] Commented: (MENFORCER-42) Maven-Enforcer-Plugin fails in multimodule project when artifacts not in repository
[
http://jira.codehaus.org/browse/MENFORCER-42?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=253485#action_253485
]
Scott Carey commented on MENFORCER-42:
--
Same problem with 1.0, Maven 3.0.1.
Tries to locate artifact in local repo when the artifact is part of the current
reactor.
A simple multimodule project and 'mvn enforcer:enforce' fails due to this. It
is not bound to any phase, I only want to execute a rule by command line. The
rule is sipmle too -- enforce that a property (project.version) is set
consistently in the project and its children. This should require no more than
'mvn validate' does.
> Maven-Enforcer-Plugin fails in multimodule project when artifacts not in
> repository
> ---
>
> Key: MENFORCER-42
> URL: http://jira.codehaus.org/browse/MENFORCER-42
> Project: Maven 2.x Enforcer Plugin
> Issue Type: Bug
> Components: Plugin
>Affects Versions: 1.0-alpha-3, 1.0
> Environment: Tested with Maven 2.0.7 and 2.0.8 on Linux with Java 1.5
>Reporter: Martin Höller
>Assignee: Brian Fox
> Attachments: enforcer-test.tar.gz
>
>
> Create a new simple multimodule-project and call {{mvn validate}} at the
> toplevel. This leads to a build failure if none of the multimodule-artifacts
> are in your local repository.
> Attached is a simple test project for reproducing this bug.
--
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
