[jira] [Updated] (SUREFIRE-1242) Surefire should honour @javax.annotation.concurrent.NotThreadSafe as well
[
https://issues.apache.org/jira/browse/SUREFIRE-1242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Frank Jakop updated SUREFIRE-1242:
--
Description:
In SUREFIRE-1093 the single-threaded execution of
{{net.jcip.annotations.NotThreadSafe}} annotated test classes was introduced.
This annotation is also present as
{{javax.annotation.concurrent.NotThreadSafe}} in the widely used
JSR-305-library _com.google.code.findbugs:jsr305_.
Surefire should respect this annotation also, as the danger of mis-importing
the annotations leads to confusion.
(if this is a desired feature, I will provide a PR)
was:
In SUREFIRE-1093 the single-threaded execution of
{{net.jcip.annotations.NotThreadSafe}} annotated test classes was introduced.
This annotation is also present as
{{javax.annotation.concurrent.NotThreadSafe}} in the widely used
JSR-305-library _com.google.code.findbugs:jsr305_.
Surefire should respect this annotation also, as the danger of mis-importing
the annotations leads to confusion.
> Surefire should honour @javax.annotation.concurrent.NotThreadSafe as well
> -
>
> Key: SUREFIRE-1242
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1242
> Project: Maven Surefire
> Issue Type: Bug
> Components: Junit 4.7+ (parallel) support
>Affects Versions: 2.19.1
>Reporter: Frank Jakop
>
> In SUREFIRE-1093 the single-threaded execution of
> {{net.jcip.annotations.NotThreadSafe}} annotated test classes was introduced.
> This annotation is also present as
> {{javax.annotation.concurrent.NotThreadSafe}} in the widely used
> JSR-305-library _com.google.code.findbugs:jsr305_.
> Surefire should respect this annotation also, as the danger of mis-importing
> the annotations leads to confusion.
> (if this is a desired feature, I will provide a PR)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (SUREFIRE-1242) Surefire should honour @javax.annotation.concurrent.NotThreadSafe as well
Frank Jakop created SUREFIRE-1242:
-
Summary: Surefire should honour
@javax.annotation.concurrent.NotThreadSafe as well
Key: SUREFIRE-1242
URL: https://issues.apache.org/jira/browse/SUREFIRE-1242
Project: Maven Surefire
Issue Type: Bug
Components: Junit 4.7+ (parallel) support
Affects Versions: 2.19.1
Reporter: Frank Jakop
In SUREFIRE-1093 the single-threaded execution of
{{net.jcip.annotations.NotThreadSafe}} annotated test classes was introduced.
This annotation is also present as
{{javax.annotation.concurrent.NotThreadSafe}} in the widely used
JSR-305-library _com.google.code.findbugs:jsr305_.
Surefire should respect this annotation also, as the danger of mis-importing
the annotations leads to confusion.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (MPOM-106) Update maven-assembly-plugin
Christopher Tubbs created MPOM-106:
--
Summary: Update maven-assembly-plugin
Key: MPOM-106
URL: https://issues.apache.org/jira/browse/MPOM-106
Project: Maven POMs
Issue Type: Task
Components: asf
Affects Versions: ASF-17
Reporter: Christopher Tubbs
Fix For: ASF-18
The {{maven-assembly-plugin}} needs updating. The latest is at version 2.6.
Updating one's pom.xml to use version 2.6 results in the warning on MASFRES-16
So, this should probably wait until that issue is fixed with a release of
{{apache-source-release-assembly-descriptor:1.0.6}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (MASFRES-16) Bad outputDirectory in descriptor
Christopher Tubbs created MASFRES-16:
Summary: Bad outputDirectory in descriptor
Key: MASFRES-16
URL: https://issues.apache.org/jira/browse/MASFRES-16
Project: Apache Maven Resource Bundles
Issue Type: Improvement
Components: apache-source-release-assembly-descriptor
Affects Versions: apache-source-release-assembly-descriptor-1.0.5
Reporter: Christopher Tubbs
Fix For: apache-source-release-assembly-descriptor-1.0.6
In two locations in
[source-shared.xml|https://svn.apache.org/repos/asf/maven/resources/trunk/apache-source-release-assembly-descriptor/src/main/resources/assemblies/source-shared.xml],
the lines {{/}} occurs, causing this
warning:
bq. \[WARNING\] The assembly descriptor contains a filesystem-root relative
reference, which is not cross platform compatible /
[This StackOverflow answer|http://stackoverflow.com/a/28506199/196405] suggests
using {{}} instead.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (WAGON-453) java.net.useSystemProxies don't work with wagon-http-lightweight
*JY Cr created WAGON-453:
Summary: java.net.useSystemProxies don't work with
wagon-http-lightweight
Key: WAGON-453
URL: https://issues.apache.org/jira/browse/WAGON-453
Project: Maven Wagon
Issue Type: Bug
Components: wagon-http-lightweight
Affects Versions: 2.10
Environment: Apache Maven 3.3.9
(bb52d8502b132ec0a5a3f4c09453c07478323dc5; 2015-11-10T17:41:47+01:00)
Java version: 1.8.0_74, vendor: Oracle Corporation
Default locale: fr_FR, platform encoding: Cp1252
OS name: "windows 7", version: "6.1", arch: "amd64", family: "dos"
Reporter: *JY Cr
Priority: Blocker
In my job, we must use a "corporate proxy" with "NTLM+SPNEGO authentication" to
access Internet.
Unfortunately, we haven't got any nominative proxy credential because Windows
use current user session to authenticate against proxy (we we login to Windows
session with a smart card).
The only way for Java application to connect to internet is to launch JVM with
{{-Djava.net.useSystemProxies=true}} standard parameter.
It work perfectly with "standard" URLConnection , but unfortunately not with
wagon-http-lightweight.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MJAR-215) Upgrade plexus-archiver from 3.1 to 3.1.1 in synch with maven-archiver 3.0.1
[ https://issues.apache.org/jira/browse/MJAR-215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15239949#comment-15239949 ] Hudson commented on MJAR-215: - UNSTABLE: Integrated in maven-plugins #5677 (See [https://builds.apache.org/job/maven-plugins/5677/]) [MJAR-215] Upgrade plexus-archiver from 3.1 to 3.1.1 in synch with maven-archiver 3.0.1 (khmarbaise: [http://svn.apache.org/viewvc/?view=rev&rev=1739003]) * maven-jar-plugin/pom.xml > Upgrade plexus-archiver from 3.1 to 3.1.1 in synch with maven-archiver 3.0.1 > > > Key: MJAR-215 > URL: https://issues.apache.org/jira/browse/MJAR-215 > Project: Maven JAR Plugin > Issue Type: Improvement >Affects Versions: 3.0.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.0.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (MJAR-215) Upgrade plexus-archiver from 3.1 to 3.1.1 in synch with maven-archiver 3.0.1
[ https://issues.apache.org/jira/browse/MJAR-215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise closed MJAR-215. Resolution: Fixed Done in [r1739003|http://svn.apache.org/r1739003] > Upgrade plexus-archiver from 3.1 to 3.1.1 in synch with maven-archiver 3.0.1 > > > Key: MJAR-215 > URL: https://issues.apache.org/jira/browse/MJAR-215 > Project: Maven JAR Plugin > Issue Type: Improvement >Affects Versions: 3.0.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.0.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MJAR-215) Upgrade plexus-archiver from 3.1 to 3.1.1 in synch with maven-archiver 3.0.1
Karl Heinz Marbaise created MJAR-215: Summary: Upgrade plexus-archiver from 3.1 to 3.1.1 in synch with maven-archiver 3.0.1 Key: MJAR-215 URL: https://issues.apache.org/jira/browse/MJAR-215 Project: Maven JAR Plugin Issue Type: Improvement Affects Versions: 3.0.0 Reporter: Karl Heinz Marbaise Assignee: Karl Heinz Marbaise Priority: Minor Fix For: 3.0.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
issues@maven.apache.org
[ https://issues.apache.org/jira/browse/MNG-5999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brad Daniels resolved MNG-5999. --- Resolution: Duplicate Fix Version/s: 3.3.10 I see this was recently fixed as part of commit a035d9026f45518f430dace7ba930835d0d3e85a > MVN.CMD fails on windows if current directory contains an "&" > - > > Key: MNG-5999 > URL: https://issues.apache.org/jira/browse/MNG-5999 > Project: Maven > Issue Type: Bug > Components: Command Line >Affects Versions: 3.3.9 >Reporter: Brad Daniels >Priority: Minor > Fix For: 3.3.10 > > > On any version of Windows, copy any valid maven project to a directory whose > name contains an ampersand (e.g. "C:\Users\myname\projects & > stuff\mavenproject"). CD to the project directory and run "mvn clean install". > Expected result: > Build proceeds normally > Actual result: > Build fails with output similar to: > The system cannot find the path specified. > The system cannot find the path specified. > The system cannot find the path specified. > The system cannot find the path specified. > 'stuff' is not recognized as an internal or external command, > operable program or batch file. > The system cannot find the path specified. > [INFO] Scanning for projects... > [INFO] > > [INFO] BUILD FAILURE > [INFO] > > [INFO] Total time: 0.141 s > [INFO] Finished at: 2016-04-12T01:41:56+00:00 > [INFO] Final Memory: 6M/58M > [INFO] > > [ERROR] The goal you specified requires a project to execute but there is no > POM in this directory (C:\). Please verify you invoked Maven from the correct > direc > tory. -> [Help 1] > [ERROR] > [ERROR] To see the full stack trace of the errors, re-run Maven with the -e > switch. > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > [ERROR] > [ERROR] For more information about the errors and possible solutions, please > read the following articles: > [ERROR] [Help 1] > http://cwiki.apache.org/confluence/display/MAVEN/MissingProjectException > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
issues@maven.apache.org
[ https://issues.apache.org/jira/browse/MNG-5999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brad Daniels updated MNG-5999: -- Description: On any version of Windows, copy any valid maven project to a directory whose name contains an ampersand (e.g. "C:\Users\myname\projects & stuff\mavenproject"). CD to the project directory and run "mvn clean install". Expected result: Build proceeds normally Actual result: Build fails with output similar to: The system cannot find the path specified. The system cannot find the path specified. The system cannot find the path specified. The system cannot find the path specified. 'stuff' is not recognized as an internal or external command, operable program or batch file. The system cannot find the path specified. [INFO] Scanning for projects... [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 0.141 s [INFO] Finished at: 2016-04-12T01:41:56+00:00 [INFO] Final Memory: 6M/58M [INFO] [ERROR] The goal you specified requires a project to execute but there is no POM in this directory (C:\). Please verify you invoked Maven from the correct direc tory. -> [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MissingProjectException was: Copy any valid maven project to a directory whose name contains an ampersand (e.g. "C:\Users\myname\projects & stuff\mavenproject"). CD to the project directory and run "mvn clean install". Expected result: Build proceeds normally Actual result: Build fails with output similar to: The system cannot find the path specified. The system cannot find the path specified. The system cannot find the path specified. The system cannot find the path specified. 'stuff' is not recognized as an internal or external command, operable program or batch file. The system cannot find the path specified. [INFO] Scanning for projects... [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 0.141 s [INFO] Finished at: 2016-04-12T01:41:56+00:00 [INFO] Final Memory: 6M/58M [INFO] [ERROR] The goal you specified requires a project to execute but there is no POM in this directory (C:\). Please verify you invoked Maven from the correct direc tory. -> [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MissingProjectException > MVN.CMD fails on windows if current directory contains an "&" > - > > Key: MNG-5999 > URL: https://issues.apache.org/jira/browse/MNG-5999 > Project: Maven > Issue Type: Bug > Components: Command Line >Affects Versions: 3.3.9 >Reporter: Brad Daniels >Priority: Minor > > On any version of Windows, copy any valid maven project to a directory whose > name contains an ampersand (e.g. "C:\Users\myname\projects & > stuff\mavenproject"). CD to the project directory and run "mvn clean install". > Expected result: > Build proceeds normally > Actual result: > Build fails with output similar to: > The system cannot find the path specified. > The system cannot find the path specified. > The system cannot find the path specified. > The system cannot find the path specified. > 'stuff' is not recognized as an internal or external command, > operable program or batch file. > The system cannot find the path specified. > [INFO] Scanning for projects... > [INFO] > > [INFO] BUILD FAILURE > [INFO] > > [INFO] Total time: 0.141 s > [INFO] Finished at: 2016-04-12T01:41:56+00:00 > [INFO] Final Memory: 6M/58M > [INFO] > > [ERROR] The goal yo
issues@maven.apache.org
[ https://issues.apache.org/jira/browse/MNG-5999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brad Daniels updated MNG-5999: -- Priority: Minor (was: Major) > MVN.CMD fails on windows if current directory contains an "&" > - > > Key: MNG-5999 > URL: https://issues.apache.org/jira/browse/MNG-5999 > Project: Maven > Issue Type: Bug > Components: Command Line >Affects Versions: 3.3.9 >Reporter: Brad Daniels >Priority: Minor > > Copy any valid maven project to a directory whose name contains an ampersand > (e.g. "C:\Users\myname\projects & stuff\mavenproject"). CD to the project > directory and run "mvn clean install". > Expected result: > Build proceeds normally > Actual result: > Build fails with output similar to: > The system cannot find the path specified. > The system cannot find the path specified. > The system cannot find the path specified. > The system cannot find the path specified. > 'stuff' is not recognized as an internal or external command, > operable program or batch file. > The system cannot find the path specified. > [INFO] Scanning for projects... > [INFO] > > [INFO] BUILD FAILURE > [INFO] > > [INFO] Total time: 0.141 s > [INFO] Finished at: 2016-04-12T01:41:56+00:00 > [INFO] Final Memory: 6M/58M > [INFO] > > [ERROR] The goal you specified requires a project to execute but there is no > POM in this directory (C:\). Please verify you invoked Maven from the correct > direc > tory. -> [Help 1] > [ERROR] > [ERROR] To see the full stack trace of the errors, re-run Maven with the -e > switch. > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > [ERROR] > [ERROR] For more information about the errors and possible solutions, please > read the following articles: > [ERROR] [Help 1] > http://cwiki.apache.org/confluence/display/MAVEN/MissingProjectException > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
issues@maven.apache.org
[ https://issues.apache.org/jira/browse/MNG-5999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brad Daniels updated MNG-5999: -- Description: Copy any valid maven project to a directory whose name contains an ampersand (e.g. "C:\Users\myname\projects & stuff\mavenproject"). CD to the project directory and run "mvn clean install". Expected result: Build proceeds normally Actual result: Build fails with output similar to: The system cannot find the path specified. The system cannot find the path specified. The system cannot find the path specified. The system cannot find the path specified. 'stuff' is not recognized as an internal or external command, operable program or batch file. The system cannot find the path specified. [INFO] Scanning for projects... [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 0.141 s [INFO] Finished at: 2016-04-12T01:41:56+00:00 [INFO] Final Memory: 6M/58M [INFO] [ERROR] The goal you specified requires a project to execute but there is no POM in this directory (C:\). Please verify you invoked Maven from the correct direc tory. -> [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MissingProjectException > MVN.CMD fails on windows if current directory contains an "&" > - > > Key: MNG-5999 > URL: https://issues.apache.org/jira/browse/MNG-5999 > Project: Maven > Issue Type: Bug > Components: Command Line >Affects Versions: 3.3.9 >Reporter: Brad Daniels > > Copy any valid maven project to a directory whose name contains an ampersand > (e.g. "C:\Users\myname\projects & stuff\mavenproject"). CD to the project > directory and run "mvn clean install". > Expected result: > Build proceeds normally > Actual result: > Build fails with output similar to: > The system cannot find the path specified. > The system cannot find the path specified. > The system cannot find the path specified. > The system cannot find the path specified. > 'stuff' is not recognized as an internal or external command, > operable program or batch file. > The system cannot find the path specified. > [INFO] Scanning for projects... > [INFO] > > [INFO] BUILD FAILURE > [INFO] > > [INFO] Total time: 0.141 s > [INFO] Finished at: 2016-04-12T01:41:56+00:00 > [INFO] Final Memory: 6M/58M > [INFO] > > [ERROR] The goal you specified requires a project to execute but there is no > POM in this directory (C:\). Please verify you invoked Maven from the correct > direc > tory. -> [Help 1] > [ERROR] > [ERROR] To see the full stack trace of the errors, re-run Maven with the -e > switch. > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > [ERROR] > [ERROR] For more information about the errors and possible solutions, please > read the following articles: > [ERROR] [Help 1] > http://cwiki.apache.org/confluence/display/MAVEN/MissingProjectException > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
issues@maven.apache.org
[ https://issues.apache.org/jira/browse/MNG-5999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brad Daniels updated MNG-5999: -- Comment: was deleted (was: I have a working fix on my machine. I'll upload a patch shortly.) > MVN.CMD fails on windows if current directory contains an "&" > - > > Key: MNG-5999 > URL: https://issues.apache.org/jira/browse/MNG-5999 > Project: Maven > Issue Type: Bug > Components: Command Line >Affects Versions: 3.3.9 >Reporter: Brad Daniels >Priority: Minor > > Copy any valid maven project to a directory whose name contains an ampersand > (e.g. "C:\Users\myname\projects & stuff\mavenproject"). CD to the project > directory and run "mvn clean install". > Expected result: > Build proceeds normally > Actual result: > Build fails with output similar to: > The system cannot find the path specified. > The system cannot find the path specified. > The system cannot find the path specified. > The system cannot find the path specified. > 'stuff' is not recognized as an internal or external command, > operable program or batch file. > The system cannot find the path specified. > [INFO] Scanning for projects... > [INFO] > > [INFO] BUILD FAILURE > [INFO] > > [INFO] Total time: 0.141 s > [INFO] Finished at: 2016-04-12T01:41:56+00:00 > [INFO] Final Memory: 6M/58M > [INFO] > > [ERROR] The goal you specified requires a project to execute but there is no > POM in this directory (C:\). Please verify you invoked Maven from the correct > direc > tory. -> [Help 1] > [ERROR] > [ERROR] To see the full stack trace of the errors, re-run Maven with the -e > switch. > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > [ERROR] > [ERROR] For more information about the errors and possible solutions, please > read the following articles: > [ERROR] [Help 1] > http://cwiki.apache.org/confluence/display/MAVEN/MissingProjectException > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
issues@maven.apache.org
Brad Daniels created MNG-5999: - Summary: MVN.CMD fails on windows if current directory contains an "&" Key: MNG-5999 URL: https://issues.apache.org/jira/browse/MNG-5999 Project: Maven Issue Type: Bug Reporter: Brad Daniels -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MWAR-371) Overlays break first-win rule for web resource with target path ending with '/'
[
https://issues.apache.org/jira/browse/MWAR-371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michal Domagala updated MWAR-371:
-
Description:
I have WAR 'generic' containing 2 files: x/a1.txt and x/a2.txt
I have WAR 'custom' with two source files: src/main/custom/a1.txt and
src/main/custom/a2.txt and settings:
{code:xml}
maven-war-plugin
src/main/custom
a1.txt
x/
src/main/custom
a2.txt
x
{code}
Note that *targetPath* is different: *x/* vs *x*
When I build WAR 'custom'
Actual: a1.txt is generic, a2.txt is custom
Expected a1.txt and a2.txt are custom
was:
I have WAR 'generic' containing 2 files: x/a1.txt and x/a2.txt
I have WAR 'custom' with two source files: src/main/custom/a1.txt and
src/main/custom/a1.txt and settings:
{code:xml}
maven-war-plugin
src/main/custom
a1.txt
x/
src/main/custom
a2.txt
x
{code}
Note that *targetPath* is different: *x/* vs *x*
When I build WAR 'custom'
Actual: a1.txt is generic, a2.txt is custom
Expected a1.txt and a2.txt are custom
> Overlays break first-win rule for web resource with target path ending with
> '/'
> ---
>
> Key: MWAR-371
> URL: https://issues.apache.org/jira/browse/MWAR-371
> Project: Maven WAR Plugin
> Issue Type: Bug
> Components: overlay
>Affects Versions: 2.6
>Reporter: Michal Domagala
>Priority: Minor
>
> I have WAR 'generic' containing 2 files: x/a1.txt and x/a2.txt
> I have WAR 'custom' with two source files: src/main/custom/a1.txt and
> src/main/custom/a2.txt and settings:
> {code:xml}
> maven-war-plugin
>
>
>
> src/main/custom
> a1.txt
> x/
>
>
> src/main/custom
> a2.txt
> x
>
>
>
> {code}
> Note that *targetPath* is different: *x/* vs *x*
> When I build WAR 'custom'
> Actual: a1.txt is generic, a2.txt is custom
> Expected a1.txt and a2.txt are custom
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MSHADE-86) dependencies of excluded dependencies are included
[
https://issues.apache.org/jira/browse/MSHADE-86?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15239118#comment-15239118
]
William Bakker commented on MSHADE-86:
--
It seems the dependency exclusion is broken when the
'promoteTransitiveDependencies' parameter is set to true. First, all transitive
dependencies are promoted. Then, maven only excludes the dependencies from
artifacts you specified. However, the previous step introduced new dependencies
on which the exclusions rules do not match.
*Example*
projectA depends on guava 16.0
projectB depends on guava 17.0 and on projectA
projectC depends on guava 18.0 and on projectB, but excludes guava.
projectC-shaded shades projectC using promoteTransitiveDependencies
projectD depends on guava 19.0 and projectC-shaded.
This gives dependency tree:
{noformat}
[INFO] mshade-86:projectD:jar:1.0-SNAPSHOT
[INFO] +- mshade-86:projectC-shaded:jar:1.0-SNAPSHOT:compile
[INFO] | +- mshade-86:projectB:jar:1.0-SNAPSHOT:compile
[INFO] | | +- (mshade-86:projectA:jar:1.0-SNAPSHOT:compile - omitted for
duplicate)
[INFO] | | \- (com.google.guava:guava:jar:17.0:compile - omitted for conflict
with 18.0)
[INFO] | +- mshade-86:projectA:jar:1.0-SNAPSHOT:compile
[INFO] | | \- (com.google.guava:guava:jar:16.0:compile - omitted for conflict
with 17.0)
[INFO] | \- (com.google.guava:guava:jar:18.0:compile - omitted for conflict
with 19.0)
[INFO] \- com.google.guava:guava:jar:19.0:compile
{noformat}
*Gist*
A full reproduction scenario of this issue has been logged at
https://gist.github.com/wjbakker/328a05382e466de7fef3e07fc664d44f
> dependencies of excluded dependencies are included
> --
>
> Key: MSHADE-86
> URL: https://issues.apache.org/jira/browse/MSHADE-86
> Project: Maven Shade Plugin
> Issue Type: Bug
>Affects Versions: 1.4
>Reporter: Benson Margulies
>
> Please let me know if you need a test case here.
> Pom has two executions of shade on separate classifiers. One of them uses
> excludes to leave some things out. Final jar includes contents of a slew of
> other artifacts. Dependency:tree shows those artifacts as being dependencies
> of the excluded artifacts, not the included ones.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MWAR-371) Overlays break first-win rule for web resource with target path ending with '/'
[
https://issues.apache.org/jira/browse/MWAR-371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15239088#comment-15239088
]
Michal Domagala commented on MWAR-371:
--
Example: https://github.com/michaldo/mwar371
Call mvn package and inspect WAR 'custom'
> Overlays break first-win rule for web resource with target path ending with
> '/'
> ---
>
> Key: MWAR-371
> URL: https://issues.apache.org/jira/browse/MWAR-371
> Project: Maven WAR Plugin
> Issue Type: Bug
> Components: overlay
>Affects Versions: 2.6
>Reporter: Michal Domagala
>Priority: Minor
>
> I have WAR 'generic' containing 2 files: x/a1.txt and x/a2.txt
> I have WAR 'custom' with two source files: src/main/custom/a1.txt and
> src/main/custom/a1.txt and settings:
> {code:xml}
> maven-war-plugin
>
>
>
> src/main/custom
> a1.txt
> x/
>
>
> src/main/custom
> a2.txt
> x
>
>
>
> {code}
> Note that *targetPath* is different: *x/* vs *x*
> When I build WAR 'custom'
> Actual: a1.txt is generic, a2.txt is custom
> Expected a1.txt and a2.txt are custom
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MWAR-371) Overlays break first-win rule for web resource with target path ending with '/'
[
https://issues.apache.org/jira/browse/MWAR-371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michal Domagala updated MWAR-371:
-
Priority: Minor (was: Major)
> Overlays break first-win rule for web resource with target path ending with
> '/'
> ---
>
> Key: MWAR-371
> URL: https://issues.apache.org/jira/browse/MWAR-371
> Project: Maven WAR Plugin
> Issue Type: Bug
> Components: overlay
>Affects Versions: 2.6
>Reporter: Michal Domagala
>Priority: Minor
>
> I have WAR 'generic' containing 2 files: x/a1.txt and x/a2.txt
> I have WAR 'custom' with two source files: src/main/custom/a1.txt and
> src/main/custom/a1.txt and settings:
> {code:xml}
> maven-war-plugin
>
>
>
> src/main/custom
> a1.txt
> x/
>
>
> src/main/custom
> a2.txt
> x
>
>
>
> {code}
> Note that **targetPath** is different: **x/** vs **x**
> When I build WAR 'custom'
> Actual: a1.txt is generic, a2.txt is custom
> Expected a1.txt and a2.txt are custom
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MWAR-371) Overlays break first-win rule for web resource with target path ending with '/'
[
https://issues.apache.org/jira/browse/MWAR-371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michal Domagala updated MWAR-371:
-
Description:
I have WAR 'generic' containing 2 files: x/a1.txt and x/a2.txt
I have WAR 'custom' with two source files: src/main/custom/a1.txt and
src/main/custom/a1.txt and settings:
{code:xml}
maven-war-plugin
src/main/custom
a1.txt
x/
src/main/custom
a2.txt
x
{code}
Note that *targetPath* is different: *x/* vs *x*
When I build WAR 'custom'
Actual: a1.txt is generic, a2.txt is custom
Expected a1.txt and a2.txt are custom
was:
I have WAR 'generic' containing 2 files: x/a1.txt and x/a2.txt
I have WAR 'custom' with two source files: src/main/custom/a1.txt and
src/main/custom/a1.txt and settings:
{code:xml}
maven-war-plugin
src/main/custom
a1.txt
x/
src/main/custom
a2.txt
x
{code}
Note that **targetPath** is different: **x/** vs **x**
When I build WAR 'custom'
Actual: a1.txt is generic, a2.txt is custom
Expected a1.txt and a2.txt are custom
> Overlays break first-win rule for web resource with target path ending with
> '/'
> ---
>
> Key: MWAR-371
> URL: https://issues.apache.org/jira/browse/MWAR-371
> Project: Maven WAR Plugin
> Issue Type: Bug
> Components: overlay
>Affects Versions: 2.6
>Reporter: Michal Domagala
>Priority: Minor
>
> I have WAR 'generic' containing 2 files: x/a1.txt and x/a2.txt
> I have WAR 'custom' with two source files: src/main/custom/a1.txt and
> src/main/custom/a1.txt and settings:
> {code:xml}
> maven-war-plugin
>
>
>
> src/main/custom
> a1.txt
> x/
>
>
> src/main/custom
> a2.txt
> x
>
>
>
> {code}
> Note that *targetPath* is different: *x/* vs *x*
> When I build WAR 'custom'
> Actual: a1.txt is generic, a2.txt is custom
> Expected a1.txt and a2.txt are custom
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (MWAR-371) Overlays break first-win rule for web resource with target path ending with '/'
Michal Domagala created MWAR-371:
Summary: Overlays break first-win rule for web resource with
target path ending with '/'
Key: MWAR-371
URL: https://issues.apache.org/jira/browse/MWAR-371
Project: Maven WAR Plugin
Issue Type: Bug
Components: overlay
Affects Versions: 2.6
Reporter: Michal Domagala
I have WAR 'generic' containing 2 files: x/a1.txt and x/a2.txt
I have WAR 'custom' with two source files: src/main/custom/a1.txt and
src/main/custom/a1.txt and settings:
{code:xml}
maven-war-plugin
src/main/custom
a1.txt
x/
src/main/custom
a2.txt
x
{code}
Note that **targetPath** is different: **x/** vs **x**
When I build WAR 'custom'
Actual: a1.txt is generic, a2.txt is custom
Expected a1.txt and a2.txt are custom
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Closed] (SCM-734) SVN branching fails with svn+ssh://username@host URL
[
https://issues.apache.org/jira/browse/SCM-734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Raúl Wegmann closed SCM-734.
Resolution: Fixed
Fix Version/s: 1.9.5
Closing as the pull request has been merged (see SCM-822).
> SVN branching fails with svn+ssh://username@host URL
>
>
> Key: SCM-734
> URL: https://issues.apache.org/jira/browse/SCM-734
> Project: Maven SCM
> Issue Type: Bug
> Components: maven-scm-provider-svn
>Affects Versions: 1.8.1
>Reporter: Raúl Wegmann
> Fix For: 1.9.5
>
>
> When using the "branch" goal of the maven-release-plugin, the following error
> occurs when the SVN URL of the working copy includes the username (e.g.
> svn+ssh://u...@svn.example.com/svn/test/trunk):
> {code}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-release-plugin:2.4.1:branch (default-cli) on
> project test: Unable to branch SCM
> [ERROR] Provider message:
> [ERROR] The svn branch command failed.
> [ERROR] Command output:
> [ERROR] svn: Source and dest appear not to be in the same repository (src:
> 'svn+ssh://svn.example.com/svn/test/trunk'; dst:
> 'svn+ssh://u...@svn.example.com/svn/test/branches/test-3.x')
> {code}
> This error is similar to the problem described by SCM-696.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[Aether] Result of resolution request w/NearestVersionSelector has conflicting transitive deps. versions
Hi,
I posted this on the aether mailing list already but it doesn't seem
very active so I'd ask here too, especially considering
https://projects.eclipse.org/projects/technology.aether/reviews/termination-review
(I also opened an issue about that:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=490962). I apologize in
advance if this is not the right place to ask, in that case could
someone point to the right one? TIA.
--
Conflict resolution seems not to work correctly in my case (but I'm no
Aether expert). It can be tried out by cloning
https://github.com/circlespainter/capsule-maven-13, which is meant to
reproduce more easily
https://github.com/puniverse/capsule-maven/issues/13, and running
`gradlew run`.
Shortly: I'm using a "RepositorySystemSession" built from
"MavenRepositorySystemUtils" ("maven-aether-provider"); I tried both by
explicitly setting a " ConflictResolver" graph transformer that includes
a "NearestVersionSelector" and by not setting it (it looks like it is
already setup in this way by "MavenRepositorySystemUtils.newSession") so
I'd expect Aether to resolve automatically a conflict between
"org.slf4j:slf4j-api" 1.7.18 and 1.7.19, which are transitive
dependencies of my resolution request about
"ch.qos.logback:logback-classic:1.1.6" and
"org.slf4j:slf4j-simple:1.7.19" resp.
This doesn't seem to happen though (I get both), and I don't understand
why. The versions I tried are " 1.0.2.v20150114" and "1.1" for Aether
and " 3.3.3" and "3.3.3" for "maven-aether-provider".
Any help would be greatly appreciated!
Thanks,
-- Fabio
[jira] [Commented] (SCM-734) SVN branching fails with svn+ssh://username@host URL
[
https://issues.apache.org/jira/browse/SCM-734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15238761#comment-15238761
]
ASF GitHub Bot commented on SCM-734:
Github user rwegmann closed the pull request at:
https://github.com/apache/maven-scm/pull/38
> SVN branching fails with svn+ssh://username@host URL
>
>
> Key: SCM-734
> URL: https://issues.apache.org/jira/browse/SCM-734
> Project: Maven SCM
> Issue Type: Bug
> Components: maven-scm-provider-svn
>Affects Versions: 1.8.1
>Reporter: Raúl Wegmann
>
> When using the "branch" goal of the maven-release-plugin, the following error
> occurs when the SVN URL of the working copy includes the username (e.g.
> svn+ssh://u...@svn.example.com/svn/test/trunk):
> {code}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-release-plugin:2.4.1:branch (default-cli) on
> project test: Unable to branch SCM
> [ERROR] Provider message:
> [ERROR] The svn branch command failed.
> [ERROR] Command output:
> [ERROR] svn: Source and dest appear not to be in the same repository (src:
> 'svn+ssh://svn.example.com/svn/test/trunk'; dst:
> 'svn+ssh://u...@svn.example.com/svn/test/branches/test-3.x')
> {code}
> This error is similar to the problem described by SCM-696.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
