[jira] [Created] (SUREFIRE-1292) Includes misbehaves with extensions other than java
Ittai Zeidman created SUREFIRE-1292: --- Summary: Includes misbehaves with extensions other than java Key: SUREFIRE-1292 URL: https://issues.apache.org/jira/browse/SUREFIRE-1292 Project: Maven Surefire Issue Type: Bug Reporter: Ittai Zeidman Hi, When defining an for maven failsafe plugin it ignores ones with file endings other than java. See this report for groovy (https://prometheuscomputing.com/company_site/blogs/26) and I had the same for scala. basically **/*E2E.scala doesn't run a test which sits in FooE2E.scala but this **/*E2E.java does run the scala test -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] (MSHARED-396) Created manifest contains versions of test scope
[ https://jira.codehaus.org/browse/MSHARED-396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=360879#comment-360879 ] Ittai Zeidman commented on MSHARED-396: --- Hi, I've actually given it some more thought and I think that my suggestion isn't correct since it can cause fragmentation between test and runtime classpaths. Instead I will open a ticket to maven core to allow custom algorithms for dependency conflict resolution. Created manifest contains versions of test scope Key: MSHARED-396 URL: https://jira.codehaus.org/browse/MSHARED-396 Project: Maven Shared Components Issue Type: Bug Components: maven-archiver Reporter: Ittai Zeidman Attachments: dependency-bug.zip Hi, I'm not 100% sure this issue belongs here and not in maven-project itself but seeing as this is where I'm having the issue I thought I'd start here. When building the classpath for a manifest the chosen version of an artifact is based on all scopes and not only on compile/runtime. This is an issue in the following layout: Main-Artifact test-dependency-which-directly-depends-on-old-javassist (test) javassist: 3.15.0-GA compile-dependency-which-transitively-depends-on-new-javassist (compile) dependency-which-directly-depends-on-new-javassist javassist: 3.16.1-GA I'm getting javassist 3.15.0-GA in my classpath and getting a method not found during runtime when using methods from the newer version. I would expect maven to do the nearest path resolution on the subset of artifacts which actually compete on the same classpath (i.e. runtime). I know that maven-archiver is just using project.getRuntimeClasspathElements which uses project.getArtifacts which returns the old version but I think maven-archiver can decide to use a different resolution mechanism. I say this because we also use the maven-assembly-plugin to copy the dependencies and that does the correct, IMO, resolution. I've attached a multi-module project which demonstrates this. Simply run jar:jar in the main-artifact module and take a look in the manifest file of that jar [I'm using archiver via jar-plugin since that is my use-case]. I'm really willing to try and submit a patch or even just test-cases but I wanted to know what you think of the issue first. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MSHARED-396) Created manifest contains versions of test scope
[ https://jira.codehaus.org/browse/MSHARED-396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ittai Zeidman closed MSHARED-396. - Resolution: Not A Bug I think it's not a bug in maven-archiver but in maven core. see my comment for more details Created manifest contains versions of test scope Key: MSHARED-396 URL: https://jira.codehaus.org/browse/MSHARED-396 Project: Maven Shared Components Issue Type: Bug Components: maven-archiver Reporter: Ittai Zeidman Attachments: dependency-bug.zip Hi, I'm not 100% sure this issue belongs here and not in maven-project itself but seeing as this is where I'm having the issue I thought I'd start here. When building the classpath for a manifest the chosen version of an artifact is based on all scopes and not only on compile/runtime. This is an issue in the following layout: Main-Artifact test-dependency-which-directly-depends-on-old-javassist (test) javassist: 3.15.0-GA compile-dependency-which-transitively-depends-on-new-javassist (compile) dependency-which-directly-depends-on-new-javassist javassist: 3.16.1-GA I'm getting javassist 3.15.0-GA in my classpath and getting a method not found during runtime when using methods from the newer version. I would expect maven to do the nearest path resolution on the subset of artifacts which actually compete on the same classpath (i.e. runtime). I know that maven-archiver is just using project.getRuntimeClasspathElements which uses project.getArtifacts which returns the old version but I think maven-archiver can decide to use a different resolution mechanism. I say this because we also use the maven-assembly-plugin to copy the dependencies and that does the correct, IMO, resolution. I've attached a multi-module project which demonstrates this. Simply run jar:jar in the main-artifact module and take a look in the manifest file of that jar [I'm using archiver via jar-plugin since that is my use-case]. I'm really willing to try and submit a patch or even just test-cases but I wanted to know what you think of the issue first. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MSHARED-396) Created manifest contains versions of test scope
Ittai Zeidman created MSHARED-396: - Summary: Created manifest contains versions of test scope Key: MSHARED-396 URL: https://jira.codehaus.org/browse/MSHARED-396 Project: Maven Shared Components Issue Type: Bug Components: maven-archiver Reporter: Ittai Zeidman Attachments: dependency-bug.zip Hi, I'm not 100% sure this issue belongs here and not in maven-project itself but seeing as this is where I'm having the issue I thought I'd start here. When building the classpath for a manifest the chosen version of an artifact is based on all scopes and not only on compile/runtime. This is an issue in the following layout: Main-Artifact test-dependency-which-directly-depends-on-old-javassist (test) javassist: 3.15.0-GA compile-dependency-which-transitively-depends-on-new-javassist (compile) dependency-which-directly-depends-on-new-javassist javassist: 3.16.1-GA I'm getting javassist 3.15.0-GA in my classpath and getting a method not found during runtime when using methods from the newer version. I would expect maven to do the nearest path resolution on the subset of artifacts which actually compete on the same classpath (i.e. runtime). I know that maven-archiver is just using project.getRuntimeClasspathElements which uses project.getArtifacts which returns the old version but I think maven-archiver can decide to use a different resolution mechanism. I say this because we also use the maven-assembly-plugin to copy the dependencies and that does the correct, IMO, resolution. I've attached a multi-module project which demonstrates this. Simply run jar:jar in the main-artifact module and take a look in the manifest file of that jar [I'm using archiver via jar-plugin since that is my use-case]. I'm really willing to try and submit a patch or even just test-cases but I wanted to know what you think of the issue first. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MDEP-374) dependency:tree -Dverbose isn't verbose anymore
[ https://jira.codehaus.org/browse/MDEP-374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=351899#comment-351899 ] Ittai Zeidman commented on MDEP-374: @hboutemy Any update? dependency:tree -Dverbose isn't verbose anymore --- Key: MDEP-374 URL: https://jira.codehaus.org/browse/MDEP-374 Project: Maven Dependency Plugin Issue Type: Bug Components: tree Affects Versions: 2.5, 2.5.1 Environment: maven 3.0.4 windows7 and linux Reporter: Arne Brix Assignee: Herve Boutemy Priority: Minor Fix For: 2.8 Older versions of the plugin (for example 2.4) show information about duplicates when invoked with -Dverbose. The current versions show no reaction to -Dverbose at all. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MDEP-374) dependency:tree -Dverbose isn't verbose anymore
[ https://jira.codehaus.org/browse/MDEP-374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=329745#comment-329745 ] Ittai Zeidman commented on MDEP-374: Any chance of revisiting this to an actual maven3 resolution? Now that maven 3.1 is out maybe that makes it easier for you (don't know just asking) dependency:tree -Dverbose isn't verbose anymore --- Key: MDEP-374 URL: https://jira.codehaus.org/browse/MDEP-374 Project: Maven 2.x Dependency Plugin Issue Type: Bug Components: tree Affects Versions: 2.5, 2.5.1 Environment: maven 3.0.4 windows7 and linux Reporter: Arne Brix Assignee: Herve Boutemy Priority: Minor Fix For: 2.8 Older versions of the plugin (for example 2.4) show information about duplicates when invoked with -Dverbose. The current versions show no reaction to -Dverbose at all. -- 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
