[jira] [Updated] (MENFORCER-301) banDuplicatePomDependencyVersions does not check managementDependencies
[
https://issues.apache.org/jira/browse/MENFORCER-301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Kudrevatykh updated MENFORCER-301:
Description:
MENFORCER-152 added rule for ban duplicate depndencies, but
dependencyManagement section does not checked correctly
code {code:java} if ( model.getDependencyManagement() != null )
{
List managementDependencies = model.getDependencies();
Map duplicateManagementDependencies =
validateDependencies( managementDependencies );{code} should be written as
{code}
if ( model.getDependencyManagement() != null )
{
List managementDependencies =
model.getDependencyManagement().getDependencies();
Map duplicateManagementDependencies =
validateDependencies( managementDependencies );{code}
and same fix should be applied to {noformat}profiles{noformat} checking code
was:MENFORCER-152 added rule for ban duplicate depndencies, but
dependencyManagement section does not checked correctly code \{code:java} if (
model.getDependencyManagement() != null ) \{ List
managementDependencies = model.getDependencies(); Map
duplicateManagementDependencies = validateDependencies( managementDependencies
);{code} should be written as \{code} if ( model.getDependencyManagement() !=
null ) \{ List managementDependencies =
model.getDependencyManagement().getDependencies(); Map
duplicateManagementDependencies = validateDependencies( managementDependencies
);{code} and same fix should be applied to \{noformat}profiles\{noformat}
checking code
> banDuplicatePomDependencyVersions does not check managementDependencies
> ---
>
> Key: MENFORCER-301
> URL: https://issues.apache.org/jira/browse/MENFORCER-301
> Project: Maven Enforcer Plugin
> Issue Type: Bug
> Components: Standard Rules
>Affects Versions: 3.0.0-M1
>Reporter: Alexander Kudrevatykh
>Priority: Major
>
> MENFORCER-152 added rule for ban duplicate depndencies, but
> dependencyManagement section does not checked correctly
> code {code:java} if ( model.getDependencyManagement() != null )
> {
> List managementDependencies = model.getDependencies();
> Map duplicateManagementDependencies =
> validateDependencies( managementDependencies );{code} should be written as
> {code}
> if ( model.getDependencyManagement() != null )
> {
> List managementDependencies =
> model.getDependencyManagement().getDependencies();
> Map duplicateManagementDependencies =
> validateDependencies( managementDependencies );{code}
> and same fix should be applied to {noformat}profiles{noformat} checking code
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (MENFORCER-301) banDuplicatePomDependencyVersions does not check managementDependencies
Alexander Kudrevatykh created MENFORCER-301:
---
Summary: banDuplicatePomDependencyVersions does not check
managementDependencies
Key: MENFORCER-301
URL: https://issues.apache.org/jira/browse/MENFORCER-301
Project: Maven Enforcer Plugin
Issue Type: Bug
Components: Standard Rules
Affects Versions: 3.0.0-M1
Reporter: Alexander Kudrevatykh
MENFORCER-152 added rule for ban duplicate depndencies, but
dependencyManagement section does not checked correctly code \{code:java} if (
model.getDependencyManagement() != null ) \{ List
managementDependencies = model.getDependencies(); Map
duplicateManagementDependencies = validateDependencies( managementDependencies
);{code} should be written as \{code} if ( model.getDependencyManagement() !=
null ) \{ List managementDependencies =
model.getDependencyManagement().getDependencies(); Map
duplicateManagementDependencies = validateDependencies( managementDependencies
);{code} and same fix should be applied to \{noformat}profiles\{noformat}
checking code
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] (MASSEMBLY-533) Outputidrectory appended by dependencyset include name on filtered=true
[
https://jira.codehaus.org/browse/MASSEMBLY-533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=345126#comment-345126
]
Alexander Kudrevatykh commented on MASSEMBLY-533:
-
also directory name appended when using with any value
> Outputidrectory appended by dependencyset include name on filtered=true
> ---
>
> Key: MASSEMBLY-533
> URL: https://jira.codehaus.org/browse/MASSEMBLY-533
> Project: Maven Assembly Plugin
> Issue Type: Bug
> Components: filtering
>Affects Versions: 2.2
>Reporter: Christian Rapp
>Priority: Critical
> Attachments: delivery_zip.xml, filtered_false.zip, filtered_true.zip,
> pom.xml
>
>
> We are using this assembly descriptor:
> {code:type=xml}
> xmlns="http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.0";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
>
> xsi:schemaLocation="http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.0
> http://maven.apache.org/xsd/assembly-1.1.0.xsd";>
>
> Delivery
>
>
> zip
>
>
> true
>
>
>
> .
> true
>
> commons-collections:commons-collections:*
>
> true
>
>
> META-INF/MANIFEST.MF
>
> true
>
>
>
>
> {code}.
> When setting the property *filtered* to {{true}} in the second
> {{dependencySet}} an additional directory is created in assembly where the
> filtered {{build.properties}} file is included. If the property is set to
> {{false}} the additional directory is gone and the non-filtered file is set
> to the root of the assembly.
> Attached you'll find 2 zip files:
> * filtered_true.zip
> * filtered_false.zip
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MNG-4831) artifact.getDependencyTrail() doesn't include full information; causes problems filtering artifacts by transitive dependency trail
[ https://jira.codehaus.org/browse/MNG-4831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=343280#comment-343280 ] Alexander Kudrevatykh commented on MNG-4831: may be we should reopen this issue, because it have attached simple example? > artifact.getDependencyTrail() doesn't include full information; causes > problems filtering artifacts by transitive dependency trail > -- > > Key: MNG-4831 > URL: https://jira.codehaus.org/browse/MNG-4831 > Project: Maven 2 & 3 > Issue Type: Improvement > Components: Artifacts and Repositories >Affects Versions: 2.2.1, 3.0-beta-3 >Reporter: John Casey > Attachments: maven-bug-simulation-MNG-4831.zip > > > Artifact.getDependencyTrail() is a List, not a graph. This means the artifact > doesn't include information about every artifact that depends on that > artifact. > In cases where the project's artifacts are filtered using the dependency > trail, it can become impossible to capture the full dependency closure for an > included artifact if that artifact depends on something that an excluded > artifact also depends on. > For a concrete example / test case of this, see MASSEMBLY-504. > In this example, A and B both depend on C. However, the dependencySet > _excludes_ B from the assembly. By luck of the draw, profile dependencies are > appended to the project's other dependencies, and B is in the dependencyTrail > of C, not A (both are valid to be there). Since transitive filtering is > enabled, C is _excluded_ from the assembly along with B, and the classpath > for A is not fully represented. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MDEP-369) fails :get using remoteRepositories and maven3
[
https://jira.codehaus.org/browse/MDEP-369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=311507#comment-311507
]
Alexander Kudrevatykh edited comment on MDEP-369 at 10/15/12 9:20 AM:
--
problem actually was in mingw-escaping of arguments
in maven 2 we have code
{code}QUOTED_ARGS=""
while [ "$1" != "" ] ; do
QUOTED_ARGS="$QUOTED_ARGS \"$1\""
shift
done{code}
but in maven 3 it code deleted, and arguments go to java unescaped
was (Author: kudrevatykh):
problem actually was in mingw-escaping of arguments
in maven 2 we have code
[code]QUOTED_ARGS=""
while [ "$1" != "" ] ; do
QUOTED_ARGS="$QUOTED_ARGS \"$1\""
shift
done[/code]
but in maven 3 it code deleted, and arguments go to java unescaped
> fails :get using remoteRepositories and maven3
> --
>
> Key: MDEP-369
> URL: https://jira.codehaus.org/browse/MDEP-369
> Project: Maven 2.x Dependency Plugin
> Issue Type: Bug
> Components: get
>Affects Versions: 2.4, 2.5
> Environment: maven3.0.4
> windows7
> jdk1.7.0_01
>Reporter: Alexander Kudrevatykh
> Attachments: out2.txt, out.txt
>
>
> When I type mvn org.apache.maven.plugins:maven-dependency-plugin:2.5:get
> -DremoteRepositories=url ... plugin fails to download artifact from
> remote repository.
> When using repoId and repoUrl properties or maven 2.2.1 all works fine.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MDEP-369) fails :get using remoteRepositories and maven3
[ https://jira.codehaus.org/browse/MDEP-369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=311507#comment-311507 ] Alexander Kudrevatykh commented on MDEP-369: problem actually was in mingw-escaping of arguments in maven 2 we have code [code]QUOTED_ARGS="" while [ "$1" != "" ] ; do QUOTED_ARGS="$QUOTED_ARGS \"$1\"" shift done[/code] but in maven 3 it code deleted, and arguments go to java unescaped > fails :get using remoteRepositories and maven3 > -- > > Key: MDEP-369 > URL: https://jira.codehaus.org/browse/MDEP-369 > Project: Maven 2.x Dependency Plugin > Issue Type: Bug > Components: get >Affects Versions: 2.4, 2.5 > Environment: maven3.0.4 > windows7 > jdk1.7.0_01 >Reporter: Alexander Kudrevatykh > Attachments: out2.txt, out.txt > > > When I type mvn org.apache.maven.plugins:maven-dependency-plugin:2.5:get > -DremoteRepositories=url ... plugin fails to download artifact from > remote repository. > When using repoId and repoUrl properties or maven 2.2.1 all works fine. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MDEP-369) fails :get using remoteRepositories and maven3
[ https://jira.codehaus.org/browse/MDEP-369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=311501#comment-311501 ] Alexander Kudrevatykh edited comment on MDEP-369 at 10/15/12 8:47 AM: -- command line is mvn -X org.apache.maven.plugins:maven-dependency-plugin:2.5:get -DremoteRepositories=chttp://akudrevatykh:7081/nexus/content/groups/dbclear-all -Dartifact=org.supercsv:supercsv:1.5.2 was (Author: kudrevatykh): command line is org.apache.maven.plugins:maven-dependency-plugin:2.5:get -DremoteRepositories=chttp://akudrevatykh:7081/nexus/content/groups/dbclear-all -Dartifact=org.supercsv:supercsv:1.5.2 > fails :get using remoteRepositories and maven3 > -- > > Key: MDEP-369 > URL: https://jira.codehaus.org/browse/MDEP-369 > Project: Maven 2.x Dependency Plugin > Issue Type: Bug > Components: get >Affects Versions: 2.4, 2.5 > Environment: maven3.0.4 > windows7 > jdk1.7.0_01 >Reporter: Alexander Kudrevatykh > Attachments: out2.txt, out.txt > > > When I type mvn org.apache.maven.plugins:maven-dependency-plugin:2.5:get > -DremoteRepositories=url ... plugin fails to download artifact from > remote repository. > When using repoId and repoUrl properties or maven 2.2.1 all works fine. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MDEP-369) fails :get using remoteRepositories and maven3
[ https://jira.codehaus.org/browse/MDEP-369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Kudrevatykh updated MDEP-369: --- Attachment: out2.txt out.txt command line is org.apache.maven.plugins:maven-dependency-plugin:2.5:get -DremoteRepositories=chttp://akudrevatykh:7081/nexus/content/groups/dbclear-all -Dartifact=org.supercsv:supercsv:1.5.2 > fails :get using remoteRepositories and maven3 > -- > > Key: MDEP-369 > URL: https://jira.codehaus.org/browse/MDEP-369 > Project: Maven 2.x Dependency Plugin > Issue Type: Bug > Components: get >Affects Versions: 2.4, 2.5 > Environment: maven3.0.4 > windows7 > jdk1.7.0_01 >Reporter: Alexander Kudrevatykh > Attachments: out2.txt, out.txt > > > When I type mvn org.apache.maven.plugins:maven-dependency-plugin:2.5:get > -DremoteRepositories=url ... plugin fails to download artifact from > remote repository. > When using repoId and repoUrl properties or maven 2.2.1 all works fine. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MDEP-369) fails :get using remoteRepositories and maven3
[ https://jira.codehaus.org/browse/MDEP-369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=306779#comment-306779 ] Alexander Kudrevatykh commented on MDEP-369: maven 3.0.4 not 3.0.5 > fails :get using remoteRepositories and maven3 > -- > > Key: MDEP-369 > URL: https://jira.codehaus.org/browse/MDEP-369 > Project: Maven 2.x Dependency Plugin > Issue Type: Bug > Components: get >Affects Versions: 2.4, 2.5 > Environment: maven3.0.5 windows7 jdk1.7.0_01 >Reporter: Alexander Kudrevatykh > > When I type mvn org.apache.maven.plugins:maven-dependency-plugin:2.5:get > -DremoteRepositories=url ... plugin fails to download artifact from > remote repository. > When using repoId and repoUrl properties or maven 2.2.1 all works fine. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MDEP-369) fails :get using remoteRepositories and maven3
Alexander Kudrevatykh created MDEP-369: -- Summary: fails :get using remoteRepositories and maven3 Key: MDEP-369 URL: https://jira.codehaus.org/browse/MDEP-369 Project: Maven 2.x Dependency Plugin Issue Type: Bug Components: get Affects Versions: 2.5, 2.4 Environment: maven3.0.5 windows7 jdk1.7.0_01 Reporter: Alexander Kudrevatykh When I type mvn org.apache.maven.plugins:maven-dependency-plugin:2.5:get -DremoteRepositories=url ... plugin fails to download artifact from remote repository. When using repoId and repoUrl properties or maven 2.2.1 all works fine. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MNG-5330) properties not substituted on dependency resolution
Alexander Kudrevatykh created MNG-5330: -- Summary: properties not substituted on dependency resolution Key: MNG-5330 URL: https://jira.codehaus.org/browse/MNG-5330 Project: Maven 2 & 3 Issue Type: Bug Components: Dependencies Affects Versions: 3.0.4, 3.0.3 Environment: Windows 7, jdk1.7.0_01 Reporter: Alexander Kudrevatykh Attachments: test.zip I have project dependency with classifier, setted by property. This property not substituted on dependency resolution. sample project attached. mvn clean install -Ptest2 fails with maven 3.0.4 and succeed with maven 2.2.1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
