[jira] [Commented] (MNG-6169) Packaging plugin bindings version updates
[ https://issues.apache.org/jira/browse/MNG-6169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16735544#comment-16735544 ] Michael Osipov commented on MNG-6169: - [~hboutemy], there fore I have split to accomondate this issue. The failures require futher investigation. I want to merge MNG.6548 only into 3.6.1. I have reassigned this one. > Packaging plugin bindings version updates > - > > Key: MNG-6169 > URL: https://issues.apache.org/jira/browse/MNG-6169 > Project: Maven > Issue Type: Improvement > Components: core, Dependencies >Affects Versions: 3.3.9 >Reporter: Christian Schulte >Assignee: Michael Osipov >Priority: Minor > Fix For: Issues to be reviewed for 3.x > > > Regular plugin update to absorb changes if plugin version is not specified in > the client POM. > ||groupId||artifactId||[previous > version|http://maven.apache.org/ref/3.5.0/maven-core/default-bindings.html]||target > version|| > |org.apache.maven.plugins|maven-clean-plugin|2.5|3.1.0| > |org.apache.maven.plugins|maven-site-plugin|3.3|3.6| > |org.apache.maven.plugins|maven-install-plugin|2.4|3.0.0-M1| > |org.apache.maven.plugins|maven-deploy-plugin|2.7|3.0.0-M1| > |org.apache.maven.plugins|maven-resources-plugin|2.6|3.0.2| > |org.apache.maven.plugins|maven-compiler-plugin|3.1|3.5.1| > |org.apache.maven.plugins|maven-surefire-plugin|2.12.4|3.0.0-M3| > |org.apache.maven.plugins|maven-jar-plugin|2.4|3.0.2| > |org.apache.maven.plugins|maven-ejb-plugin|2.3|2.5.1 (api 3.0+)| > |org.apache.maven.plugins|maven-plugin-plugin|3.2|3.6.0| > |org.apache.maven.plugins|maven-war-plugin|2.2|3.0.0| > |org.apache.maven.plugins|maven-ear-plugin|2.8|3.0.1| > |org.apache.maven.plugins|maven-rar-plugin|2.2|2.4 (?)| -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (MNG-6169) Packaging plugin bindings version updates
[ https://issues.apache.org/jira/browse/MNG-6169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MNG-6169: Summary: Packaging plugin bindings version updates (was: Lifecycle/binding plugin version updates) > Packaging plugin bindings version updates > - > > Key: MNG-6169 > URL: https://issues.apache.org/jira/browse/MNG-6169 > Project: Maven > Issue Type: Improvement > Components: core, Dependencies >Affects Versions: 3.3.9 >Reporter: Christian Schulte >Assignee: Michael Osipov >Priority: Minor > Fix For: 3.6.x-candidate > > > Regular plugin update to absorb changes if plugin version is not specified in > the client POM. > ||groupId||artifactId||[previous > version|http://maven.apache.org/ref/3.5.0/maven-core/default-bindings.html]||target > version|| > |org.apache.maven.plugins|maven-clean-plugin|2.5|3.1.0| > |org.apache.maven.plugins|maven-site-plugin|3.3|3.6| > |org.apache.maven.plugins|maven-install-plugin|2.4|3.0.0-M1| > |org.apache.maven.plugins|maven-deploy-plugin|2.7|3.0.0-M1| > |org.apache.maven.plugins|maven-resources-plugin|2.6|3.0.2| > |org.apache.maven.plugins|maven-compiler-plugin|3.1|3.5.1| > |org.apache.maven.plugins|maven-surefire-plugin|2.12.4|3.0.0-M3| > |org.apache.maven.plugins|maven-jar-plugin|2.4|3.0.2| > |org.apache.maven.plugins|maven-ejb-plugin|2.3|2.5.1 (api 3.0+)| > |org.apache.maven.plugins|maven-plugin-plugin|3.2|3.6.0| > |org.apache.maven.plugins|maven-war-plugin|2.2|3.0.0| > |org.apache.maven.plugins|maven-ear-plugin|2.8|3.0.1| > |org.apache.maven.plugins|maven-rar-plugin|2.2|2.4 (?)| -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (MNG-6169) Packaging plugin bindings version updates
[ https://issues.apache.org/jira/browse/MNG-6169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MNG-6169: Fix Version/s: (was: 3.6.x-candidate) Issues to be reviewed for 3.x > Packaging plugin bindings version updates > - > > Key: MNG-6169 > URL: https://issues.apache.org/jira/browse/MNG-6169 > Project: Maven > Issue Type: Improvement > Components: core, Dependencies >Affects Versions: 3.3.9 >Reporter: Christian Schulte >Assignee: Michael Osipov >Priority: Minor > Fix For: Issues to be reviewed for 3.x > > > Regular plugin update to absorb changes if plugin version is not specified in > the client POM. > ||groupId||artifactId||[previous > version|http://maven.apache.org/ref/3.5.0/maven-core/default-bindings.html]||target > version|| > |org.apache.maven.plugins|maven-clean-plugin|2.5|3.1.0| > |org.apache.maven.plugins|maven-site-plugin|3.3|3.6| > |org.apache.maven.plugins|maven-install-plugin|2.4|3.0.0-M1| > |org.apache.maven.plugins|maven-deploy-plugin|2.7|3.0.0-M1| > |org.apache.maven.plugins|maven-resources-plugin|2.6|3.0.2| > |org.apache.maven.plugins|maven-compiler-plugin|3.1|3.5.1| > |org.apache.maven.plugins|maven-surefire-plugin|2.12.4|3.0.0-M3| > |org.apache.maven.plugins|maven-jar-plugin|2.4|3.0.2| > |org.apache.maven.plugins|maven-ejb-plugin|2.3|2.5.1 (api 3.0+)| > |org.apache.maven.plugins|maven-plugin-plugin|3.2|3.6.0| > |org.apache.maven.plugins|maven-war-plugin|2.2|3.0.0| > |org.apache.maven.plugins|maven-ear-plugin|2.8|3.0.1| > |org.apache.maven.plugins|maven-rar-plugin|2.2|2.4 (?)| -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Issue Comment Deleted] (MJAVADOC-551) Error if path to project contains a spaces
[
https://issues.apache.org/jira/browse/MJAVADOC-551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jesko Jochum updated MJAVADOC-551:
--
Comment: was deleted
(was: Sehr geehrte Damen und Herren,
vielen Dank für Ihre Nachricht. Ich bin ab Mo 07.01.2019 wieder im Büro für Sie
zu erreichen.
Mit freundlichen Grüßen,
Jesko Jochum
)
> Error if path to project contains a spaces
> --
>
> Key: MJAVADOC-551
> URL: https://issues.apache.org/jira/browse/MJAVADOC-551
> Project: Maven Javadoc Plugin
> Issue Type: Sub-task
> Components: fix
>Affects Versions: 3.0.1
> Environment: Windows 7 x64
> Apache Maven 3.5.4
>Reporter: Jesko Jochum
>Assignee: Robert Scholte
>Priority: Major
> Fix For: 3.1.0
>
>
> This was no problem in version 2.10.4!
> If a project (e.g. the one appended to MJAVADOC-549 ) is stored in a
> subfolder, e.g. {{C:\Sub Folder\mjavadoc-fix-goal-example}} and the command
> mentioned in MJAVADOC-549 is called, then the following "file not found"
> error gets thrown:
> {noformat}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-javadoc-plugin:3.0.1:fix (default-cli) on
> project mjavadoc-fix-goal-example: IOException:
> C:\Sub%20Folder\mjavadoc-fix-goal-example\src\main\java\my\group\id\mjavadoc\MyApplication.java
> (Das System kann den angegebenen Pfad nicht finden) -> [Help 1]
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (SUREFIRE-1542) Fractional per-core thread count
[ https://issues.apache.org/jira/browse/SUREFIRE-1542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16735510#comment-16735510 ] Chris Hennick commented on SUREFIRE-1542: - threadCount. (I use only 1 fork.) > Fractional per-core thread count > > > Key: SUREFIRE-1542 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1542 > Project: Maven Surefire > Issue Type: Improvement >Reporter: Chris Hennick >Priority: Major > > I have a lot of tests that each use 2 threads at once, and timeouts become a > problem when I try to run 1 test thread per core (because that amounts to 2 > actual active threads per core). Why not make the thread count > floating-point, so that I could fix this by specifying 0.5 threads per core? -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNG-5830) maven.multiModuleProjectDirectory system propery is not set
[
https://issues.apache.org/jira/browse/MNG-5830?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16735508#comment-16735508
]
Markus Karg commented on MNG-5830:
--
The Eclipse Foundation has this problem (maven.multiModuleProjectDirectory not
getting resolved) with Maven 3.5.4! [~khmarbaise] can you please help us fixing
this on our public EF build infrastructure? This is a showstopper for Jakarta
EE 8. Would be great, thanks! :)
> maven.multiModuleProjectDirectory system propery is not set
> ---
>
> Key: MNG-5830
> URL: https://issues.apache.org/jira/browse/MNG-5830
> Project: Maven
> Issue Type: Bug
> Components: Bootstrap Build, Command Line
>Affects Versions: 3.3.1, 3.3.3
>Reporter: Krzysztof Sobkowiak
>Assignee: Christian Schulte
>Priority: Major
> Labels: Linux
>
> I have downloaded the newest Maven 3.3.3 and point the M2_HOME to the
> directory with unpacked Maven. {{mvn -v}} produces following error (whereas
> the versions prior to 3.1.1 worked correctly)
> {code}
> kso@lenovo:/tmp$ export
> M2_HOME=/home/kso/work/pde/dev/maven/apache-maven-3.3.3/
> kso@lenovo:/tmp$ mvn -v
> -Dmaven.multiModuleProjectDirectory system propery is not set. Check $M2_HOME
> environment variable and mvn script match.kso@lenovo:/tmp$
> {code}
> The same problem when I want to build any maven project.
> Below the same output with Maven 3.2.5 to give you informations about my
> environment
> {code}
> kso@lenovo:/tmp$ export
> M2_HOME=/home/kso/work/pde/dev/maven/apache-maven-3.2.5/
> kso@lenovo:/tmp$ mvn -v
> Apache Maven 3.2.5 (12a6b3acb947671f09b81f49094c53f426d8cea1;
> 2014-12-14T18:29:23+01:00)
> Maven home: /home/kso/work/pde/dev/maven/apache-maven-3.2.5
> Java version: 1.7.0_71, vendor: Oracle Corporation
> Java home: /home/kso/work/pde/run/jvm/jdk1.7.0_71/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux", version: "3.16.0-38-generic", arch: "amd64", family: "unix"
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MNG-6169) Lifecycle/binding plugin version updates
[ https://issues.apache.org/jira/browse/MNG-6169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16735505#comment-16735505 ] Hervé Boutemy commented on MNG-6169: if we do such an update (which I still I'm not convinced it's a good idea), please don't do it in bugfix 3.6.1 but 3.7.0 or any new version if you want to do it in 3.6.1, ease show what updates are bugfixes (of what bugs?) > Lifecycle/binding plugin version updates > > > Key: MNG-6169 > URL: https://issues.apache.org/jira/browse/MNG-6169 > Project: Maven > Issue Type: Improvement > Components: core, Dependencies >Affects Versions: 3.3.9 >Reporter: Christian Schulte >Assignee: Michael Osipov >Priority: Minor > Fix For: 3.6.x-candidate > > > Regular plugin update to absorb changes if plugin version is not specified in > the client POM. > ||groupId||artifactId||[previous > version|http://maven.apache.org/ref/3.5.0/maven-core/default-bindings.html]||target > version|| > |org.apache.maven.plugins|maven-clean-plugin|2.5|3.1.0| > |org.apache.maven.plugins|maven-site-plugin|3.3|3.6| > |org.apache.maven.plugins|maven-install-plugin|2.4|3.0.0-M1| > |org.apache.maven.plugins|maven-deploy-plugin|2.7|3.0.0-M1| > |org.apache.maven.plugins|maven-resources-plugin|2.6|3.0.2| > |org.apache.maven.plugins|maven-compiler-plugin|3.1|3.5.1| > |org.apache.maven.plugins|maven-surefire-plugin|2.12.4|3.0.0-M3| > |org.apache.maven.plugins|maven-jar-plugin|2.4|3.0.2| > |org.apache.maven.plugins|maven-ejb-plugin|2.3|2.5.1 (api 3.0+)| > |org.apache.maven.plugins|maven-plugin-plugin|3.2|3.6.0| > |org.apache.maven.plugins|maven-war-plugin|2.2|3.0.0| > |org.apache.maven.plugins|maven-ear-plugin|2.8|3.0.1| > |org.apache.maven.plugins|maven-rar-plugin|2.2|2.4 (?)| -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (MASFRES-18) typo 'teh' on m23 announcement
[ https://issues.apache.org/jira/browse/MASFRES-18?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz updated MASFRES-18: Component/s: (was: apache-incubator-disclaimer-resource-bundle) > typo 'teh' on m23 announcement > -- > > Key: MASFRES-18 > URL: https://issues.apache.org/jira/browse/MASFRES-18 > Project: Apache Maven Resource Bundles > Issue Type: Improvement > Environment: https://directory.apache.org/apacheds/news.html >Reporter: David Misell >Priority: Trivial > > there is a typo on the latest m23 announcement -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (MASFRES-18) typo 'teh' on m23 announcement
[ https://issues.apache.org/jira/browse/MASFRES-18?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz closed MASFRES-18. --- Resolution: Fixed > typo 'teh' on m23 announcement > -- > > Key: MASFRES-18 > URL: https://issues.apache.org/jira/browse/MASFRES-18 > Project: Apache Maven Resource Bundles > Issue Type: Improvement > Environment: https://directory.apache.org/apacheds/news.html >Reporter: David Misell >Priority: Trivial > > there is a typo on the latest m23 announcement -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (MASFRES-19) I made an installer for Windows
[ https://issues.apache.org/jira/browse/MASFRES-19?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz closed MASFRES-19. --- Resolution: Won't Fix > I made an installer for Windows > --- > > Key: MASFRES-19 > URL: https://issues.apache.org/jira/browse/MASFRES-19 > Project: Apache Maven Resource Bundles > Issue Type: New Feature >Reporter: John Pratt >Priority: Minor > > I made an installer for Maven in case it helps: > [https://installmaven.weebly.com/] > Feel free to build your own using the instructions on my site or distribute > my installer, if that helps you in any way. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MASFRES-19) I made an installer for Windows
[ https://issues.apache.org/jira/browse/MASFRES-19?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16735373#comment-16735373 ] Sylwester Lachiewicz commented on MASFRES-19: - Thank You for support, but we only distribute zip package from our official webpage. > I made an installer for Windows > --- > > Key: MASFRES-19 > URL: https://issues.apache.org/jira/browse/MASFRES-19 > Project: Apache Maven Resource Bundles > Issue Type: New Feature >Reporter: John Pratt >Priority: Minor > > I made an installer for Maven in case it helps: > [https://installmaven.weebly.com/] > Feel free to build your own using the instructions on my site or distribute > my installer, if that helps you in any way. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (MNG-6548) Lifecycle plugin version updates
[ https://issues.apache.org/jira/browse/MNG-6548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MNG-6548: Affects Version/s: (was: 3.3.9) 3.5.0 > Lifecycle plugin version updates > > > Key: MNG-6548 > URL: https://issues.apache.org/jira/browse/MNG-6548 > Project: Maven > Issue Type: Improvement > Components: core, Dependencies >Affects Versions: 3.5.0, 3.6.0 >Reporter: Christian Schulte >Assignee: Michael Osipov >Priority: Minor > Fix For: 3.6.x-candidate > > > Regular plugin update to absorb changes if plugin version is not specified in > the client POM. > ||groupId||artifactId||[previous > version|https://maven.apache.org/ref/3.5.0/maven-core/lifecycles.html]||target > version|| > |org.apache.maven.plugins|maven-clean-plugin|2.5|3.1.0| > |org.apache.maven.plugins|maven-site-plugin|3.3|3.7.1| -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (MNG-6548) Lifecycle plugin version updates
[ https://issues.apache.org/jira/browse/MNG-6548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MNG-6548: Description: Regular plugin update to absorb changes if plugin version is not specified in the client POM. ||groupId||artifactId||[previous version|https://maven.apache.org/ref/3.5.0/maven-core/lifecycles.html]||target version|| |org.apache.maven.plugins|maven-clean-plugin|2.5|3.1.0| |org.apache.maven.plugins|maven-site-plugin|3.3|3.7.1| was: Regular plugin update to absorb changes if plugin version is not specified in the client POM. ||groupId||artifactId||[previous version|http://maven.apache.org/ref/3.5.0/maven-core/default-bindings.html]||target version|| |org.apache.maven.plugins|maven-clean-plugin|2.5|3.1.0| |org.apache.maven.plugins|maven-site-plugin|3.3|3.7.1| > Lifecycle plugin version updates > > > Key: MNG-6548 > URL: https://issues.apache.org/jira/browse/MNG-6548 > Project: Maven > Issue Type: Improvement > Components: core, Dependencies >Affects Versions: 3.3.9, 3.6.0 >Reporter: Christian Schulte >Assignee: Michael Osipov >Priority: Minor > Fix For: 3.6.x-candidate > > > Regular plugin update to absorb changes if plugin version is not specified in > the client POM. > ||groupId||artifactId||[previous > version|https://maven.apache.org/ref/3.5.0/maven-core/lifecycles.html]||target > version|| > |org.apache.maven.plugins|maven-clean-plugin|2.5|3.1.0| > |org.apache.maven.plugins|maven-site-plugin|3.3|3.7.1| -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (MNG-6548) Lifecycle plugin version updates
[ https://issues.apache.org/jira/browse/MNG-6548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MNG-6548: Description: Regular plugin update to absorb changes if plugin version is not specified in the client POM. ||groupId||artifactId||[previous version|http://maven.apache.org/ref/3.5.0/maven-core/default-bindings.html]||target version|| |org.apache.maven.plugins|maven-clean-plugin|2.5|3.1.0| |org.apache.maven.plugins|maven-site-plugin|3.3|3.7.1| was: Regular plugin update to absorb changes if plugin version is not specified in the client POM. ||groupId||artifactId||[previous version|http://maven.apache.org/ref/3.5.0/maven-core/default-bindings.html]||target version|| |org.apache.maven.plugins|maven-clean-plugin|2.5|3.1.0| |org.apache.maven.plugins|maven-site-plugin|3.3|3.6| |org.apache.maven.plugins|maven-install-plugin|2.4|3.0.0-M1| |org.apache.maven.plugins|maven-deploy-plugin|2.7|3.0.0-M1| |org.apache.maven.plugins|maven-resources-plugin|2.6|3.0.2| |org.apache.maven.plugins|maven-compiler-plugin|3.1|3.5.1| |org.apache.maven.plugins|maven-surefire-plugin|2.12.4|3.0.0-M3| |org.apache.maven.plugins|maven-jar-plugin|2.4|3.0.2| |org.apache.maven.plugins|maven-ejb-plugin|2.3|2.5.1 (api 3.0+)| |org.apache.maven.plugins|maven-plugin-plugin|3.2|3.6.0| |org.apache.maven.plugins|maven-war-plugin|2.2|3.0.0| |org.apache.maven.plugins|maven-ear-plugin|2.8|3.0.1| |org.apache.maven.plugins|maven-rar-plugin|2.2|2.4 (?)| > Lifecycle plugin version updates > > > Key: MNG-6548 > URL: https://issues.apache.org/jira/browse/MNG-6548 > Project: Maven > Issue Type: Improvement > Components: core, Dependencies >Affects Versions: 3.3.9, 3.6.0 >Reporter: Christian Schulte >Assignee: Michael Osipov >Priority: Minor > Fix For: 3.6.x-candidate > > > Regular plugin update to absorb changes if plugin version is not specified in > the client POM. > ||groupId||artifactId||[previous > version|http://maven.apache.org/ref/3.5.0/maven-core/default-bindings.html]||target > version|| > |org.apache.maven.plugins|maven-clean-plugin|2.5|3.1.0| > |org.apache.maven.plugins|maven-site-plugin|3.3|3.7.1| -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (MNG-6548) Lifecycle plugin version updates
[ https://issues.apache.org/jira/browse/MNG-6548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MNG-6548: Affects Version/s: 3.6.0 > Lifecycle plugin version updates > > > Key: MNG-6548 > URL: https://issues.apache.org/jira/browse/MNG-6548 > Project: Maven > Issue Type: Improvement > Components: core, Dependencies >Affects Versions: 3.3.9, 3.6.0 >Reporter: Christian Schulte >Assignee: Michael Osipov >Priority: Minor > Fix For: 3.6.x-candidate > > > Regular plugin update to absorb changes if plugin version is not specified in > the client POM. > ||groupId||artifactId||[previous > version|http://maven.apache.org/ref/3.5.0/maven-core/default-bindings.html]||target > version|| > |org.apache.maven.plugins|maven-clean-plugin|2.5|3.1.0| > |org.apache.maven.plugins|maven-site-plugin|3.3|3.6| > |org.apache.maven.plugins|maven-install-plugin|2.4|3.0.0-M1| > |org.apache.maven.plugins|maven-deploy-plugin|2.7|3.0.0-M1| > |org.apache.maven.plugins|maven-resources-plugin|2.6|3.0.2| > |org.apache.maven.plugins|maven-compiler-plugin|3.1|3.5.1| > |org.apache.maven.plugins|maven-surefire-plugin|2.12.4|3.0.0-M3| > |org.apache.maven.plugins|maven-jar-plugin|2.4|3.0.2| > |org.apache.maven.plugins|maven-ejb-plugin|2.3|2.5.1 (api 3.0+)| > |org.apache.maven.plugins|maven-plugin-plugin|3.2|3.6.0| > |org.apache.maven.plugins|maven-war-plugin|2.2|3.0.0| > |org.apache.maven.plugins|maven-ear-plugin|2.8|3.0.1| > |org.apache.maven.plugins|maven-rar-plugin|2.2|2.4 (?)| -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (MNG-6548) Lifecycle plugin version updates
Michael Osipov created MNG-6548: --- Summary: Lifecycle plugin version updates Key: MNG-6548 URL: https://issues.apache.org/jira/browse/MNG-6548 Project: Maven Issue Type: Improvement Components: core, Dependencies Affects Versions: 3.3.9 Reporter: Christian Schulte Assignee: Michael Osipov Fix For: 3.6.x-candidate Regular plugin update to absorb changes if plugin version is not specified in the client POM. ||groupId||artifactId||[previous version|http://maven.apache.org/ref/3.5.0/maven-core/default-bindings.html]||target version|| |org.apache.maven.plugins|maven-clean-plugin|2.5|3.1.0| |org.apache.maven.plugins|maven-site-plugin|3.3|3.6| |org.apache.maven.plugins|maven-install-plugin|2.4|3.0.0-M1| |org.apache.maven.plugins|maven-deploy-plugin|2.7|3.0.0-M1| |org.apache.maven.plugins|maven-resources-plugin|2.6|3.0.2| |org.apache.maven.plugins|maven-compiler-plugin|3.1|3.5.1| |org.apache.maven.plugins|maven-surefire-plugin|2.12.4|3.0.0-M3| |org.apache.maven.plugins|maven-jar-plugin|2.4|3.0.2| |org.apache.maven.plugins|maven-ejb-plugin|2.3|2.5.1 (api 3.0+)| |org.apache.maven.plugins|maven-plugin-plugin|3.2|3.6.0| |org.apache.maven.plugins|maven-war-plugin|2.2|3.0.0| |org.apache.maven.plugins|maven-ear-plugin|2.8|3.0.1| |org.apache.maven.plugins|maven-rar-plugin|2.2|2.4 (?)| -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNG-6169) Lifecycle/binding plugin version updates
[ https://issues.apache.org/jira/browse/MNG-6169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16735366#comment-16735366 ] Michael Osipov commented on MNG-6169: - I will split this into two tickets because several plugin updates cause failures in ITs. I guess the ITs are faulty. > Lifecycle/binding plugin version updates > > > Key: MNG-6169 > URL: https://issues.apache.org/jira/browse/MNG-6169 > Project: Maven > Issue Type: Improvement > Components: core, Dependencies >Affects Versions: 3.3.9 >Reporter: Christian Schulte >Assignee: Michael Osipov >Priority: Minor > Fix For: 3.6.x-candidate > > > Regular plugin update to absorb changes if plugin version is not specified in > the client POM. > ||groupId||artifactId||[previous > version|http://maven.apache.org/ref/3.5.0/maven-core/default-bindings.html]||target > version|| > |org.apache.maven.plugins|maven-clean-plugin|2.5|3.1.0| > |org.apache.maven.plugins|maven-site-plugin|3.3|3.6| > |org.apache.maven.plugins|maven-install-plugin|2.4|3.0.0-M1| > |org.apache.maven.plugins|maven-deploy-plugin|2.7|3.0.0-M1| > |org.apache.maven.plugins|maven-resources-plugin|2.6|3.0.2| > |org.apache.maven.plugins|maven-compiler-plugin|3.1|3.5.1| > |org.apache.maven.plugins|maven-surefire-plugin|2.12.4|3.0.0-M3| > |org.apache.maven.plugins|maven-jar-plugin|2.4|3.0.2| > |org.apache.maven.plugins|maven-ejb-plugin|2.3|2.5.1 (api 3.0+)| > |org.apache.maven.plugins|maven-plugin-plugin|3.2|3.6.0| > |org.apache.maven.plugins|maven-war-plugin|2.2|3.0.0| > |org.apache.maven.plugins|maven-ear-plugin|2.8|3.0.1| > |org.apache.maven.plugins|maven-rar-plugin|2.2|2.4 (?)| -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (MNG-6541) less restrictive "is referencing itself" check
[
https://issues.apache.org/jira/browse/MNG-6541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sylwester Lachiewicz closed MNG-6541.
-
Resolution: Duplicate
> less restrictive "is referencing itself" check
> --
>
> Key: MNG-6541
> URL: https://issues.apache.org/jira/browse/MNG-6541
> Project: Maven
> Issue Type: Wish
> Components: Dependencies
>Affects Versions: 3.5.4
>Reporter: Václav Haisman
>Priority: Major
>
> I have issues when building site:site in project with OpenJFX. The
> javafx-graphics artifact sort of references itself:
> {code:xml}
>
> http://maven.apache.org/POM/4.0.0;
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/xsd/maven-4.0.0.xsd;
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;>
> 4.0.0
> org.openjfx
> javafx-graphics
> 11.0.1
>
> org.openjfx
> javafx
> 11.0.1
>
>
>
> org.openjfx
> javafx-graphics
> 11.0.1
> ${javafx.platform}
>
>
> org.openjfx
> javafx-base
> 11.0.1
>
>
>
> {code}
> But it does so with additional classifier. When I run site:site, it gives me
> this:
> {code}
> [WARNING] Unable to create Maven project from repository.
> org.apache.maven.project.ProjectBuildingException: 1 problem was encountered
> while building the effective model for org.openjfx:javafx-graphics:11.0.1
> [FATAL] 'dependencies.dependency org.openjfx:javafx-graphics:11.0.1' for
> org.openjfx:javafx-graphics:11.0.1 is referencing itself. @ line 13, column 17
> for project org.openjfx:javafx-graphics:11.0.1
> at org.apache.maven.project.DefaultProjectBuilder.build
> (DefaultProjectBuilder.java:165)
> at org.apache.maven.project.DefaultProjectBuilder.build
> (DefaultProjectBuilder.java:327)
> at
> org.apache.maven.report.projectinfo.dependencies.RepositoryUtils.getMavenProjectFromRepository
> (RepositoryUtils.java:125)
> {code}
> I was wondering if the check could not be relaxed to accommodate this
> situation that seems to be common even in core Java components?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MNG-6541) less restrictive "is referencing itself" check
[
https://issues.apache.org/jira/browse/MNG-6541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16735361#comment-16735361
]
Sylwester Lachiewicz commented on MNG-6541:
---
(y)
> less restrictive "is referencing itself" check
> --
>
> Key: MNG-6541
> URL: https://issues.apache.org/jira/browse/MNG-6541
> Project: Maven
> Issue Type: Wish
> Components: Dependencies
>Affects Versions: 3.5.4
>Reporter: Václav Haisman
>Priority: Major
>
> I have issues when building site:site in project with OpenJFX. The
> javafx-graphics artifact sort of references itself:
> {code:xml}
>
> http://maven.apache.org/POM/4.0.0;
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/xsd/maven-4.0.0.xsd;
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;>
> 4.0.0
> org.openjfx
> javafx-graphics
> 11.0.1
>
> org.openjfx
> javafx
> 11.0.1
>
>
>
> org.openjfx
> javafx-graphics
> 11.0.1
> ${javafx.platform}
>
>
> org.openjfx
> javafx-base
> 11.0.1
>
>
>
> {code}
> But it does so with additional classifier. When I run site:site, it gives me
> this:
> {code}
> [WARNING] Unable to create Maven project from repository.
> org.apache.maven.project.ProjectBuildingException: 1 problem was encountered
> while building the effective model for org.openjfx:javafx-graphics:11.0.1
> [FATAL] 'dependencies.dependency org.openjfx:javafx-graphics:11.0.1' for
> org.openjfx:javafx-graphics:11.0.1 is referencing itself. @ line 13, column 17
> for project org.openjfx:javafx-graphics:11.0.1
> at org.apache.maven.project.DefaultProjectBuilder.build
> (DefaultProjectBuilder.java:165)
> at org.apache.maven.project.DefaultProjectBuilder.build
> (DefaultProjectBuilder.java:327)
> at
> org.apache.maven.report.projectinfo.dependencies.RepositoryUtils.getMavenProjectFromRepository
> (RepositoryUtils.java:125)
> {code}
> I was wondering if the check could not be relaxed to accommodate this
> situation that seems to be common even in core Java components?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Reopened] (MNG-6541) less restrictive "is referencing itself" check
[
https://issues.apache.org/jira/browse/MNG-6541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sylwester Lachiewicz reopened MNG-6541:
---
> less restrictive "is referencing itself" check
> --
>
> Key: MNG-6541
> URL: https://issues.apache.org/jira/browse/MNG-6541
> Project: Maven
> Issue Type: Wish
> Components: Dependencies
>Affects Versions: 3.5.4
>Reporter: Václav Haisman
>Priority: Major
>
> I have issues when building site:site in project with OpenJFX. The
> javafx-graphics artifact sort of references itself:
> {code:xml}
>
> http://maven.apache.org/POM/4.0.0;
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/xsd/maven-4.0.0.xsd;
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;>
> 4.0.0
> org.openjfx
> javafx-graphics
> 11.0.1
>
> org.openjfx
> javafx
> 11.0.1
>
>
>
> org.openjfx
> javafx-graphics
> 11.0.1
> ${javafx.platform}
>
>
> org.openjfx
> javafx-base
> 11.0.1
>
>
>
> {code}
> But it does so with additional classifier. When I run site:site, it gives me
> this:
> {code}
> [WARNING] Unable to create Maven project from repository.
> org.apache.maven.project.ProjectBuildingException: 1 problem was encountered
> while building the effective model for org.openjfx:javafx-graphics:11.0.1
> [FATAL] 'dependencies.dependency org.openjfx:javafx-graphics:11.0.1' for
> org.openjfx:javafx-graphics:11.0.1 is referencing itself. @ line 13, column 17
> for project org.openjfx:javafx-graphics:11.0.1
> at org.apache.maven.project.DefaultProjectBuilder.build
> (DefaultProjectBuilder.java:165)
> at org.apache.maven.project.DefaultProjectBuilder.build
> (DefaultProjectBuilder.java:327)
> at
> org.apache.maven.report.projectinfo.dependencies.RepositoryUtils.getMavenProjectFromRepository
> (RepositoryUtils.java:125)
> {code}
> I was wondering if the check could not be relaxed to accommodate this
> situation that seems to be common even in core Java components?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (MNG-6541) less restrictive "is referencing itself" check
[
https://issues.apache.org/jira/browse/MNG-6541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sylwester Lachiewicz updated MNG-6541:
--
Fix Version/s: (was: 3.6.0)
> less restrictive "is referencing itself" check
> --
>
> Key: MNG-6541
> URL: https://issues.apache.org/jira/browse/MNG-6541
> Project: Maven
> Issue Type: Wish
> Components: Dependencies
>Affects Versions: 3.5.4
>Reporter: Václav Haisman
>Priority: Major
>
> I have issues when building site:site in project with OpenJFX. The
> javafx-graphics artifact sort of references itself:
> {code:xml}
>
> http://maven.apache.org/POM/4.0.0;
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/xsd/maven-4.0.0.xsd;
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;>
> 4.0.0
> org.openjfx
> javafx-graphics
> 11.0.1
>
> org.openjfx
> javafx
> 11.0.1
>
>
>
> org.openjfx
> javafx-graphics
> 11.0.1
> ${javafx.platform}
>
>
> org.openjfx
> javafx-base
> 11.0.1
>
>
>
> {code}
> But it does so with additional classifier. When I run site:site, it gives me
> this:
> {code}
> [WARNING] Unable to create Maven project from repository.
> org.apache.maven.project.ProjectBuildingException: 1 problem was encountered
> while building the effective model for org.openjfx:javafx-graphics:11.0.1
> [FATAL] 'dependencies.dependency org.openjfx:javafx-graphics:11.0.1' for
> org.openjfx:javafx-graphics:11.0.1 is referencing itself. @ line 13, column 17
> for project org.openjfx:javafx-graphics:11.0.1
> at org.apache.maven.project.DefaultProjectBuilder.build
> (DefaultProjectBuilder.java:165)
> at org.apache.maven.project.DefaultProjectBuilder.build
> (DefaultProjectBuilder.java:327)
> at
> org.apache.maven.report.projectinfo.dependencies.RepositoryUtils.getMavenProjectFromRepository
> (RepositoryUtils.java:125)
> {code}
> I was wondering if the check could not be relaxed to accommodate this
> situation that seems to be common even in core Java components?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (MNG-6541) less restrictive "is referencing itself" check
[
https://issues.apache.org/jira/browse/MNG-6541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sylwester Lachiewicz updated MNG-6541:
--
Fix Version/s: 3.6.0
> less restrictive "is referencing itself" check
> --
>
> Key: MNG-6541
> URL: https://issues.apache.org/jira/browse/MNG-6541
> Project: Maven
> Issue Type: Wish
> Components: Dependencies
>Affects Versions: 3.5.4
>Reporter: Václav Haisman
>Priority: Major
> Fix For: 3.6.0
>
>
> I have issues when building site:site in project with OpenJFX. The
> javafx-graphics artifact sort of references itself:
> {code:xml}
>
> http://maven.apache.org/POM/4.0.0;
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/xsd/maven-4.0.0.xsd;
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;>
> 4.0.0
> org.openjfx
> javafx-graphics
> 11.0.1
>
> org.openjfx
> javafx
> 11.0.1
>
>
>
> org.openjfx
> javafx-graphics
> 11.0.1
> ${javafx.platform}
>
>
> org.openjfx
> javafx-base
> 11.0.1
>
>
>
> {code}
> But it does so with additional classifier. When I run site:site, it gives me
> this:
> {code}
> [WARNING] Unable to create Maven project from repository.
> org.apache.maven.project.ProjectBuildingException: 1 problem was encountered
> while building the effective model for org.openjfx:javafx-graphics:11.0.1
> [FATAL] 'dependencies.dependency org.openjfx:javafx-graphics:11.0.1' for
> org.openjfx:javafx-graphics:11.0.1 is referencing itself. @ line 13, column 17
> for project org.openjfx:javafx-graphics:11.0.1
> at org.apache.maven.project.DefaultProjectBuilder.build
> (DefaultProjectBuilder.java:165)
> at org.apache.maven.project.DefaultProjectBuilder.build
> (DefaultProjectBuilder.java:327)
> at
> org.apache.maven.report.projectinfo.dependencies.RepositoryUtils.getMavenProjectFromRepository
> (RepositoryUtils.java:125)
> {code}
> I was wondering if the check could not be relaxed to accommodate this
> situation that seems to be common even in core Java components?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MNG-6541) less restrictive "is referencing itself" check
[
https://issues.apache.org/jira/browse/MNG-6541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16735351#comment-16735351
]
Michael Osipov commented on MNG-6541:
-
I think we should remove the fix version and mark this issue as duplicate.
> less restrictive "is referencing itself" check
> --
>
> Key: MNG-6541
> URL: https://issues.apache.org/jira/browse/MNG-6541
> Project: Maven
> Issue Type: Wish
> Components: Dependencies
>Affects Versions: 3.5.4
>Reporter: Václav Haisman
>Priority: Major
> Fix For: 3.6.0
>
>
> I have issues when building site:site in project with OpenJFX. The
> javafx-graphics artifact sort of references itself:
> {code:xml}
>
> http://maven.apache.org/POM/4.0.0;
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/xsd/maven-4.0.0.xsd;
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;>
> 4.0.0
> org.openjfx
> javafx-graphics
> 11.0.1
>
> org.openjfx
> javafx
> 11.0.1
>
>
>
> org.openjfx
> javafx-graphics
> 11.0.1
> ${javafx.platform}
>
>
> org.openjfx
> javafx-base
> 11.0.1
>
>
>
> {code}
> But it does so with additional classifier. When I run site:site, it gives me
> this:
> {code}
> [WARNING] Unable to create Maven project from repository.
> org.apache.maven.project.ProjectBuildingException: 1 problem was encountered
> while building the effective model for org.openjfx:javafx-graphics:11.0.1
> [FATAL] 'dependencies.dependency org.openjfx:javafx-graphics:11.0.1' for
> org.openjfx:javafx-graphics:11.0.1 is referencing itself. @ line 13, column 17
> for project org.openjfx:javafx-graphics:11.0.1
> at org.apache.maven.project.DefaultProjectBuilder.build
> (DefaultProjectBuilder.java:165)
> at org.apache.maven.project.DefaultProjectBuilder.build
> (DefaultProjectBuilder.java:327)
> at
> org.apache.maven.report.projectinfo.dependencies.RepositoryUtils.getMavenProjectFromRepository
> (RepositoryUtils.java:125)
> {code}
> I was wondering if the check could not be relaxed to accommodate this
> situation that seems to be common even in core Java components?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MNG-6541) less restrictive "is referencing itself" check
[
https://issues.apache.org/jira/browse/MNG-6541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16735349#comment-16735349
]
Sylwester Lachiewicz commented on MNG-6541:
---
Great to hear that! I hope You can use the latest version - so I'm closing this
issue.
> less restrictive "is referencing itself" check
> --
>
> Key: MNG-6541
> URL: https://issues.apache.org/jira/browse/MNG-6541
> Project: Maven
> Issue Type: Wish
> Components: Dependencies
>Affects Versions: 3.5.4
>Reporter: Václav Haisman
>Priority: Major
> Fix For: 3.6.0
>
>
> I have issues when building site:site in project with OpenJFX. The
> javafx-graphics artifact sort of references itself:
> {code:xml}
>
> http://maven.apache.org/POM/4.0.0;
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/xsd/maven-4.0.0.xsd;
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;>
> 4.0.0
> org.openjfx
> javafx-graphics
> 11.0.1
>
> org.openjfx
> javafx
> 11.0.1
>
>
>
> org.openjfx
> javafx-graphics
> 11.0.1
> ${javafx.platform}
>
>
> org.openjfx
> javafx-base
> 11.0.1
>
>
>
> {code}
> But it does so with additional classifier. When I run site:site, it gives me
> this:
> {code}
> [WARNING] Unable to create Maven project from repository.
> org.apache.maven.project.ProjectBuildingException: 1 problem was encountered
> while building the effective model for org.openjfx:javafx-graphics:11.0.1
> [FATAL] 'dependencies.dependency org.openjfx:javafx-graphics:11.0.1' for
> org.openjfx:javafx-graphics:11.0.1 is referencing itself. @ line 13, column 17
> for project org.openjfx:javafx-graphics:11.0.1
> at org.apache.maven.project.DefaultProjectBuilder.build
> (DefaultProjectBuilder.java:165)
> at org.apache.maven.project.DefaultProjectBuilder.build
> (DefaultProjectBuilder.java:327)
> at
> org.apache.maven.report.projectinfo.dependencies.RepositoryUtils.getMavenProjectFromRepository
> (RepositoryUtils.java:125)
> {code}
> I was wondering if the check could not be relaxed to accommodate this
> situation that seems to be common even in core Java components?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (MNG-6541) less restrictive "is referencing itself" check
[
https://issues.apache.org/jira/browse/MNG-6541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sylwester Lachiewicz closed MNG-6541.
-
Resolution: Resolved
> less restrictive "is referencing itself" check
> --
>
> Key: MNG-6541
> URL: https://issues.apache.org/jira/browse/MNG-6541
> Project: Maven
> Issue Type: Wish
> Components: Dependencies
>Affects Versions: 3.5.4
>Reporter: Václav Haisman
>Priority: Major
> Fix For: 3.6.0
>
>
> I have issues when building site:site in project with OpenJFX. The
> javafx-graphics artifact sort of references itself:
> {code:xml}
>
> http://maven.apache.org/POM/4.0.0;
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/xsd/maven-4.0.0.xsd;
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;>
> 4.0.0
> org.openjfx
> javafx-graphics
> 11.0.1
>
> org.openjfx
> javafx
> 11.0.1
>
>
>
> org.openjfx
> javafx-graphics
> 11.0.1
> ${javafx.platform}
>
>
> org.openjfx
> javafx-base
> 11.0.1
>
>
>
> {code}
> But it does so with additional classifier. When I run site:site, it gives me
> this:
> {code}
> [WARNING] Unable to create Maven project from repository.
> org.apache.maven.project.ProjectBuildingException: 1 problem was encountered
> while building the effective model for org.openjfx:javafx-graphics:11.0.1
> [FATAL] 'dependencies.dependency org.openjfx:javafx-graphics:11.0.1' for
> org.openjfx:javafx-graphics:11.0.1 is referencing itself. @ line 13, column 17
> for project org.openjfx:javafx-graphics:11.0.1
> at org.apache.maven.project.DefaultProjectBuilder.build
> (DefaultProjectBuilder.java:165)
> at org.apache.maven.project.DefaultProjectBuilder.build
> (DefaultProjectBuilder.java:327)
> at
> org.apache.maven.report.projectinfo.dependencies.RepositoryUtils.getMavenProjectFromRepository
> (RepositoryUtils.java:125)
> {code}
> I was wondering if the check could not be relaxed to accommodate this
> situation that seems to be common even in core Java components?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (MDEP-594) Dependency reported as "unused declared" when runtime-retention type annotation is used
[
https://issues.apache.org/jira/browse/MDEP-594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sylwester Lachiewicz closed MDEP-594.
-
Resolution: Resolved
> Dependency reported as "unused declared" when runtime-retention type
> annotation is used
> ---
>
> Key: MDEP-594
> URL: https://issues.apache.org/jira/browse/MDEP-594
> Project: Maven Dependency Plugin
> Issue Type: Bug
> Components: analyze
>Affects Versions: 3.0.0
> Environment: Apache Maven 3.5.0,
> Oracle Java version: 1.8.0_144
>Reporter: Andreas Hubold
>Priority: Major
> Fix For: 3.1.0
>
> Attachments: example.tgz
>
>
> In the attached example project, module "usage" uses annotation {{@Example}}:
> {code}
> public interface Usage {
> @Example String getEmail();
> }
> {code}
> which is defined in module "annotation" as:
> {code}
> @Target({ElementType.TYPE_USE, ElementType.TYPE_PARAMETER})
> @Retention(RetentionPolicy.RUNTIME)
> public @interface Example {
> }
> {code}
> Consequently, the pom.xml of module "usage" defines a compile-dependency to
> module "annotation" but the dependency:analyze-only goal incorrectly reports
> this as unused dependency:
> {noformat}
> [main] [INFO] --- maven-dependency-plugin:3.0.0:analyze-only
> (analyze-dependencies) @ usage ---
> [main] [WARNING] Unused declared dependencies found:
> [main] [WARNING]com.example:annotation:jar:1.0-SNAPSHOT:compile
> {noformat}
> This false positive is only reported if
> * the annotation is meta-annotated with target TYPE_USE + TYPE_PARAMETER
> * and the source.version/target.version of the compiler plugin for module
> "usage" is 1.8
> There's no false positive if the {{@Target}} meta-annotation is removed or if
> compiler's source/target version is set to 1.7.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (MDEP-594) Dependency reported as "unused declared" when runtime-retention type annotation is used
[
https://issues.apache.org/jira/browse/MDEP-594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sylwester Lachiewicz updated MDEP-594:
--
Fix Version/s: 3.1.0
> Dependency reported as "unused declared" when runtime-retention type
> annotation is used
> ---
>
> Key: MDEP-594
> URL: https://issues.apache.org/jira/browse/MDEP-594
> Project: Maven Dependency Plugin
> Issue Type: Bug
> Components: analyze
>Affects Versions: 3.0.0
> Environment: Apache Maven 3.5.0,
> Oracle Java version: 1.8.0_144
>Reporter: Andreas Hubold
>Priority: Major
> Fix For: 3.1.0
>
> Attachments: example.tgz
>
>
> In the attached example project, module "usage" uses annotation {{@Example}}:
> {code}
> public interface Usage {
> @Example String getEmail();
> }
> {code}
> which is defined in module "annotation" as:
> {code}
> @Target({ElementType.TYPE_USE, ElementType.TYPE_PARAMETER})
> @Retention(RetentionPolicy.RUNTIME)
> public @interface Example {
> }
> {code}
> Consequently, the pom.xml of module "usage" defines a compile-dependency to
> module "annotation" but the dependency:analyze-only goal incorrectly reports
> this as unused dependency:
> {noformat}
> [main] [INFO] --- maven-dependency-plugin:3.0.0:analyze-only
> (analyze-dependencies) @ usage ---
> [main] [WARNING] Unused declared dependencies found:
> [main] [WARNING]com.example:annotation:jar:1.0-SNAPSHOT:compile
> {noformat}
> This false positive is only reported if
> * the annotation is meta-annotated with target TYPE_USE + TYPE_PARAMETER
> * and the source.version/target.version of the compiler plugin for module
> "usage" is 1.8
> There's no false positive if the {{@Target}} meta-annotation is removed or if
> compiler's source/target version is set to 1.7.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MDEP-82) go-offline / resolve-plugins does not resolve all plugin dependencies
[
https://issues.apache.org/jira/browse/MDEP-82?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16735337#comment-16735337
]
Sylwester Lachiewicz commented on MDEP-82:
--
For [~antoine-morvan] sample project issue is with
org.apache.maven.plugin.internal.PluginDependencyResolutionListener#isWagonProvider
where old 2.x Maven's Wagon was excluded from dependences. I hope after
org.jacoco:jacoco-maven-plugin will be updated to 3+ API it can be solved.
> go-offline / resolve-plugins does not resolve all plugin dependencies
> -
>
> Key: MDEP-82
> URL: https://issues.apache.org/jira/browse/MDEP-82
> Project: Maven Dependency Plugin
> Issue Type: Bug
> Components: go-offline, resolve-plugins
>Affects Versions: 2.0-alpha-4, 2.8, 2.10
> Environment: Maven 2.0.6
>Reporter: Arne Degenring
>Assignee: Sylwester Lachiewicz
>Priority: Major
> Fix For: 3.0.0
>
> Attachments: maven-dependency-plugin-2.3.patch, pom.xml
>
>
> The attached pom.xml is a very simple JAR project, without any direct
> dependencies or plugin dependencies.
> Start with an empty local repository, and run mvn dependency:go-offline on
> it. Some files get downloaded, but not everything that is needed for the
> build. If you run "mvn -o package" afterwards, you end up with the following
> error:
> {noformat}[ERROR] BUILD ERROR
> [INFO]
>
> [INFO] The plugin 'org.apache.maven.plugins:maven-resources-plugin' does not
> exist or no valid version could be found{noformat}
> Afterwards, even "mvn package" without the "-o" parameter does not work any
> longer.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (MNG-6169) Lifecycle/binding plugin version updates
[ https://issues.apache.org/jira/browse/MNG-6169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16735319#comment-16735319 ] Sylwester Lachiewicz edited comment on MNG-6169 at 1/6/19 8:44 PM: --- Yes, I just updated a few mins ago. So we have only maven-rar-plugin left from Mave 2 word. Anyone volunteers to do, and why me? ;) Update: we only need to retest and release, uff.. was (Author: slachiewicz): Yes, I just updated a few mins ago. So we have only maven-rar-plugin left from Mave 2 word. Anyone volunteers to do, and why me? ;) > Lifecycle/binding plugin version updates > > > Key: MNG-6169 > URL: https://issues.apache.org/jira/browse/MNG-6169 > Project: Maven > Issue Type: Improvement > Components: core, Dependencies >Affects Versions: 3.3.9 >Reporter: Christian Schulte >Assignee: Michael Osipov >Priority: Minor > Fix For: 3.6.x-candidate > > > Regular plugin update to absorb changes if plugin version is not specified in > the client POM. > ||groupId||artifactId||[previous > version|http://maven.apache.org/ref/3.5.0/maven-core/default-bindings.html]||target > version|| > |org.apache.maven.plugins|maven-clean-plugin|2.5|3.1.0| > |org.apache.maven.plugins|maven-site-plugin|3.3|3.6| > |org.apache.maven.plugins|maven-install-plugin|2.4|3.0.0-M1| > |org.apache.maven.plugins|maven-deploy-plugin|2.7|3.0.0-M1| > |org.apache.maven.plugins|maven-resources-plugin|2.6|3.0.2| > |org.apache.maven.plugins|maven-compiler-plugin|3.1|3.5.1| > |org.apache.maven.plugins|maven-surefire-plugin|2.12.4|3.0.0-M3| > |org.apache.maven.plugins|maven-jar-plugin|2.4|3.0.2| > |org.apache.maven.plugins|maven-ejb-plugin|2.3|2.5.1 (api 3.0+)| > |org.apache.maven.plugins|maven-plugin-plugin|3.2|3.6.0| > |org.apache.maven.plugins|maven-war-plugin|2.2|3.0.0| > |org.apache.maven.plugins|maven-ear-plugin|2.8|3.0.1| > |org.apache.maven.plugins|maven-rar-plugin|2.2|2.4 (?)| -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (MDEP-82) go-offline / resolve-plugins does not resolve all plugin dependencies
[
https://issues.apache.org/jira/browse/MDEP-82?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sylwester Lachiewicz reassigned MDEP-82:
Assignee: Sylwester Lachiewicz
> go-offline / resolve-plugins does not resolve all plugin dependencies
> -
>
> Key: MDEP-82
> URL: https://issues.apache.org/jira/browse/MDEP-82
> Project: Maven Dependency Plugin
> Issue Type: Bug
> Components: go-offline, resolve-plugins
>Affects Versions: 2.0-alpha-4, 2.8, 2.10
> Environment: Maven 2.0.6
>Reporter: Arne Degenring
>Assignee: Sylwester Lachiewicz
>Priority: Major
> Fix For: 3.0.0
>
> Attachments: maven-dependency-plugin-2.3.patch, pom.xml
>
>
> The attached pom.xml is a very simple JAR project, without any direct
> dependencies or plugin dependencies.
> Start with an empty local repository, and run mvn dependency:go-offline on
> it. Some files get downloaded, but not everything that is needed for the
> build. If you run "mvn -o package" afterwards, you end up with the following
> error:
> {noformat}[ERROR] BUILD ERROR
> [INFO]
>
> [INFO] The plugin 'org.apache.maven.plugins:maven-resources-plugin' does not
> exist or no valid version could be found{noformat}
> Afterwards, even "mvn package" without the "-o" parameter does not work any
> longer.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MNG-6169) Lifecycle/binding plugin version updates
[
https://issues.apache.org/jira/browse/MNG-6169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16735324#comment-16735324
]
Robert Scholte commented on MNG-6169:
-
Yes, I was indeed referring to {{default-bindings.xml}}, the rest will remain.
{{pom}} is not really a packaging-type (it doesn't create an artifact), that
one must remain in Maven Core, just like a default version for all the known
packaging plugins.
btw, reason behind this is that custom packaging plugins are forced to embed
these bindings, hence for consistency our packaging plugins should do the same.
And this is not logic that belongs to Maven core.
> Lifecycle/binding plugin version updates
>
>
> Key: MNG-6169
> URL: https://issues.apache.org/jira/browse/MNG-6169
> Project: Maven
> Issue Type: Improvement
> Components: core, Dependencies
>Affects Versions: 3.3.9
>Reporter: Christian Schulte
>Assignee: Michael Osipov
>Priority: Minor
> Fix For: 3.6.x-candidate
>
>
> Regular plugin update to absorb changes if plugin version is not specified in
> the client POM.
> ||groupId||artifactId||[previous
> version|http://maven.apache.org/ref/3.5.0/maven-core/default-bindings.html]||target
> version||
> |org.apache.maven.plugins|maven-clean-plugin|2.5|3.1.0|
> |org.apache.maven.plugins|maven-site-plugin|3.3|3.6|
> |org.apache.maven.plugins|maven-install-plugin|2.4|3.0.0-M1|
> |org.apache.maven.plugins|maven-deploy-plugin|2.7|3.0.0-M1|
> |org.apache.maven.plugins|maven-resources-plugin|2.6|3.0.2|
> |org.apache.maven.plugins|maven-compiler-plugin|3.1|3.5.1|
> |org.apache.maven.plugins|maven-surefire-plugin|2.12.4|3.0.0-M3|
> |org.apache.maven.plugins|maven-jar-plugin|2.4|3.0.2|
> |org.apache.maven.plugins|maven-ejb-plugin|2.3|2.5.1 (api 3.0+)|
> |org.apache.maven.plugins|maven-plugin-plugin|3.2|3.6.0|
> |org.apache.maven.plugins|maven-war-plugin|2.2|3.0.0|
> |org.apache.maven.plugins|maven-ear-plugin|2.8|3.0.1|
> |org.apache.maven.plugins|maven-rar-plugin|2.2|2.4 (?)|
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MNG-6169) Lifecycle/binding plugin version updates
[ https://issues.apache.org/jira/browse/MNG-6169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16735319#comment-16735319 ] Sylwester Lachiewicz commented on MNG-6169: --- Yes, I just updated a few mins ago. So we have only maven-rar-plugin left from Mave 2 word. Anyone volunteers to do, and why me? ;) > Lifecycle/binding plugin version updates > > > Key: MNG-6169 > URL: https://issues.apache.org/jira/browse/MNG-6169 > Project: Maven > Issue Type: Improvement > Components: core, Dependencies >Affects Versions: 3.3.9 >Reporter: Christian Schulte >Assignee: Michael Osipov >Priority: Minor > Fix For: 3.6.x-candidate > > > Regular plugin update to absorb changes if plugin version is not specified in > the client POM. > ||groupId||artifactId||[previous > version|http://maven.apache.org/ref/3.5.0/maven-core/default-bindings.html]||target > version|| > |org.apache.maven.plugins|maven-clean-plugin|2.5|3.1.0| > |org.apache.maven.plugins|maven-site-plugin|3.3|3.6| > |org.apache.maven.plugins|maven-install-plugin|2.4|3.0.0-M1| > |org.apache.maven.plugins|maven-deploy-plugin|2.7|3.0.0-M1| > |org.apache.maven.plugins|maven-resources-plugin|2.6|3.0.2| > |org.apache.maven.plugins|maven-compiler-plugin|3.1|3.5.1| > |org.apache.maven.plugins|maven-surefire-plugin|2.12.4|3.0.0-M3| > |org.apache.maven.plugins|maven-jar-plugin|2.4|3.0.2| > |org.apache.maven.plugins|maven-ejb-plugin|2.3|2.5.1 (api 3.0+)| > |org.apache.maven.plugins|maven-plugin-plugin|3.2|3.6.0| > |org.apache.maven.plugins|maven-war-plugin|2.2|3.0.0| > |org.apache.maven.plugins|maven-ear-plugin|2.8|3.0.1| > |org.apache.maven.plugins|maven-rar-plugin|2.2|2.4 (?)| -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] tcollignon commented on issue #5: MASSEMBLY-617 : add ability to set fileMappers in FileSet in maven as…
tcollignon commented on issue #5: MASSEMBLY-617 : add ability to set fileMappers in FileSet in maven as… URL: https://github.com/apache/maven-assembly-plugin/pull/5#issuecomment-451772714 Note : This PR could close https://issues.apache.org/jira/browse/MASSEMBLY-886 too This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[jira] [Updated] (MNG-6169) Lifecycle/binding plugin version updates
[ https://issues.apache.org/jira/browse/MNG-6169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz updated MNG-6169: -- Description: Regular plugin update to absorb changes if plugin version is not specified in the client POM. ||groupId||artifactId||[previous version|http://maven.apache.org/ref/3.5.0/maven-core/default-bindings.html]||target version|| |org.apache.maven.plugins|maven-clean-plugin|2.5|3.1.0| |org.apache.maven.plugins|maven-site-plugin|3.3|3.6| |org.apache.maven.plugins|maven-install-plugin|2.4|3.0.0-M1| |org.apache.maven.plugins|maven-deploy-plugin|2.7|3.0.0-M1| |org.apache.maven.plugins|maven-resources-plugin|2.6|3.0.2| |org.apache.maven.plugins|maven-compiler-plugin|3.1|3.5.1| |org.apache.maven.plugins|maven-surefire-plugin|2.12.4|3.0.0-M3| |org.apache.maven.plugins|maven-jar-plugin|2.4|3.0.2| |org.apache.maven.plugins|maven-ejb-plugin|2.3|2.5.1 (api 3.0+)| |org.apache.maven.plugins|maven-plugin-plugin|3.2|3.6.0| |org.apache.maven.plugins|maven-war-plugin|2.2|3.0.0| |org.apache.maven.plugins|maven-ear-plugin|2.8|3.0.1| |org.apache.maven.plugins|maven-rar-plugin|2.2|2.4 (?)| was: Regular plugin update to absorb changes if plugin version is not specified in the client POM. ||groupId||artifactId||[previous version|http://maven.apache.org/ref/3.5.0/maven-core/default-bindings.html]||target version|| |org.apache.maven.plugins|maven-clean-plugin|2.5|3.1.0| |org.apache.maven.plugins|maven-site-plugin|3.3|3.6| |org.apache.maven.plugins|maven-install-plugin|2.4|3.0.0-M1| |org.apache.maven.plugins|maven-deploy-plugin|2.7|3.0.0-M1| |org.apache.maven.plugins|maven-resources-plugin|2.6|3.0.2| |org.apache.maven.plugins|maven-compiler-plugin|3.1|3.5.1| |org.apache.maven.plugins|maven-surefire-plugin|2.12.4|3.0.0-M3| |org.apache.maven.plugins|maven-jar-plugin|2.4|3.0.2| |org.apache.maven.plugins|maven-ejb-plugin|2.3|2.5.1 (?)| |org.apache.maven.plugins|maven-plugin-plugin|3.2|3.6.0| |org.apache.maven.plugins|maven-war-plugin|2.2|3.0.0| |org.apache.maven.plugins|maven-ear-plugin|2.8|3.0.1| |org.apache.maven.plugins|maven-rar-plugin|2.2|2.4 (?)| > Lifecycle/binding plugin version updates > > > Key: MNG-6169 > URL: https://issues.apache.org/jira/browse/MNG-6169 > Project: Maven > Issue Type: Improvement > Components: core, Dependencies >Affects Versions: 3.3.9 >Reporter: Christian Schulte >Assignee: Michael Osipov >Priority: Minor > Fix For: 3.6.x-candidate > > > Regular plugin update to absorb changes if plugin version is not specified in > the client POM. > ||groupId||artifactId||[previous > version|http://maven.apache.org/ref/3.5.0/maven-core/default-bindings.html]||target > version|| > |org.apache.maven.plugins|maven-clean-plugin|2.5|3.1.0| > |org.apache.maven.plugins|maven-site-plugin|3.3|3.6| > |org.apache.maven.plugins|maven-install-plugin|2.4|3.0.0-M1| > |org.apache.maven.plugins|maven-deploy-plugin|2.7|3.0.0-M1| > |org.apache.maven.plugins|maven-resources-plugin|2.6|3.0.2| > |org.apache.maven.plugins|maven-compiler-plugin|3.1|3.5.1| > |org.apache.maven.plugins|maven-surefire-plugin|2.12.4|3.0.0-M3| > |org.apache.maven.plugins|maven-jar-plugin|2.4|3.0.2| > |org.apache.maven.plugins|maven-ejb-plugin|2.3|2.5.1 (api 3.0+)| > |org.apache.maven.plugins|maven-plugin-plugin|3.2|3.6.0| > |org.apache.maven.plugins|maven-war-plugin|2.2|3.0.0| > |org.apache.maven.plugins|maven-ear-plugin|2.8|3.0.1| > |org.apache.maven.plugins|maven-rar-plugin|2.2|2.4 (?)| -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (MNG-6169) Lifecycle/binding plugin version updates
[ https://issues.apache.org/jira/browse/MNG-6169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16735310#comment-16735310 ] Michael Osipov edited comment on MNG-6169 at 1/6/19 8:30 PM: - [~slachiewicz], isn't this implictly done by the 3.x versions we see in the table? maven-ejb-plugin in already 3.0.x. was (Author: michael-o): [~slachiewicz], isn't this implictly done by the 3.x versions we see in the table? > Lifecycle/binding plugin version updates > > > Key: MNG-6169 > URL: https://issues.apache.org/jira/browse/MNG-6169 > Project: Maven > Issue Type: Improvement > Components: core, Dependencies >Affects Versions: 3.3.9 >Reporter: Christian Schulte >Assignee: Michael Osipov >Priority: Minor > Fix For: 3.6.x-candidate > > > Regular plugin update to absorb changes if plugin version is not specified in > the client POM. > ||groupId||artifactId||[previous > version|http://maven.apache.org/ref/3.5.0/maven-core/default-bindings.html]||target > version|| > |org.apache.maven.plugins|maven-clean-plugin|2.5|3.1.0| > |org.apache.maven.plugins|maven-site-plugin|3.3|3.6| > |org.apache.maven.plugins|maven-install-plugin|2.4|3.0.0-M1| > |org.apache.maven.plugins|maven-deploy-plugin|2.7|3.0.0-M1| > |org.apache.maven.plugins|maven-resources-plugin|2.6|3.0.2| > |org.apache.maven.plugins|maven-compiler-plugin|3.1|3.5.1| > |org.apache.maven.plugins|maven-surefire-plugin|2.12.4|3.0.0-M3| > |org.apache.maven.plugins|maven-jar-plugin|2.4|3.0.2| > |org.apache.maven.plugins|maven-ejb-plugin|2.3|2.5.1 (?)| > |org.apache.maven.plugins|maven-plugin-plugin|3.2|3.6.0| > |org.apache.maven.plugins|maven-war-plugin|2.2|3.0.0| > |org.apache.maven.plugins|maven-ear-plugin|2.8|3.0.1| > |org.apache.maven.plugins|maven-rar-plugin|2.2|2.4 (?)| -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNG-6169) Lifecycle/binding plugin version updates
[ https://issues.apache.org/jira/browse/MNG-6169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16735310#comment-16735310 ] Michael Osipov commented on MNG-6169: - [~slachiewicz], isn't this implictly done by the 3.x versions we see in the table? > Lifecycle/binding plugin version updates > > > Key: MNG-6169 > URL: https://issues.apache.org/jira/browse/MNG-6169 > Project: Maven > Issue Type: Improvement > Components: core, Dependencies >Affects Versions: 3.3.9 >Reporter: Christian Schulte >Assignee: Michael Osipov >Priority: Minor > Fix For: 3.6.x-candidate > > > Regular plugin update to absorb changes if plugin version is not specified in > the client POM. > ||groupId||artifactId||[previous > version|http://maven.apache.org/ref/3.5.0/maven-core/default-bindings.html]||target > version|| > |org.apache.maven.plugins|maven-clean-plugin|2.5|3.1.0| > |org.apache.maven.plugins|maven-site-plugin|3.3|3.6| > |org.apache.maven.plugins|maven-install-plugin|2.4|3.0.0-M1| > |org.apache.maven.plugins|maven-deploy-plugin|2.7|3.0.0-M1| > |org.apache.maven.plugins|maven-resources-plugin|2.6|3.0.2| > |org.apache.maven.plugins|maven-compiler-plugin|3.1|3.5.1| > |org.apache.maven.plugins|maven-surefire-plugin|2.12.4|3.0.0-M3| > |org.apache.maven.plugins|maven-jar-plugin|2.4|3.0.2| > |org.apache.maven.plugins|maven-ejb-plugin|2.3|2.5.1 (?)| > |org.apache.maven.plugins|maven-plugin-plugin|3.2|3.6.0| > |org.apache.maven.plugins|maven-war-plugin|2.2|3.0.0| > |org.apache.maven.plugins|maven-ear-plugin|2.8|3.0.1| > |org.apache.maven.plugins|maven-rar-plugin|2.2|2.4 (?)| -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNG-6169) Lifecycle/binding plugin version updates
[ https://issues.apache.org/jira/browse/MNG-6169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16735309#comment-16735309 ] Sylwester Lachiewicz commented on MNG-6169: --- What about force only update to use plugins with Maven API 3.0+? > Lifecycle/binding plugin version updates > > > Key: MNG-6169 > URL: https://issues.apache.org/jira/browse/MNG-6169 > Project: Maven > Issue Type: Improvement > Components: core, Dependencies >Affects Versions: 3.3.9 >Reporter: Christian Schulte >Assignee: Michael Osipov >Priority: Minor > Fix For: 3.6.x-candidate > > > Regular plugin update to absorb changes if plugin version is not specified in > the client POM. > ||groupId||artifactId||[previous > version|http://maven.apache.org/ref/3.5.0/maven-core/default-bindings.html]||target > version|| > |org.apache.maven.plugins|maven-clean-plugin|2.5|3.1.0| > |org.apache.maven.plugins|maven-site-plugin|3.3|3.6| > |org.apache.maven.plugins|maven-install-plugin|2.4|3.0.0-M1| > |org.apache.maven.plugins|maven-deploy-plugin|2.7|3.0.0-M1| > |org.apache.maven.plugins|maven-resources-plugin|2.6|3.0.2| > |org.apache.maven.plugins|maven-compiler-plugin|3.1|3.5.1| > |org.apache.maven.plugins|maven-surefire-plugin|2.12.4|3.0.0-M3| > |org.apache.maven.plugins|maven-jar-plugin|2.4|3.0.2| > |org.apache.maven.plugins|maven-ejb-plugin|2.3|2.5.1 (?)| > |org.apache.maven.plugins|maven-plugin-plugin|3.2|3.6.0| > |org.apache.maven.plugins|maven-war-plugin|2.2|3.0.0| > |org.apache.maven.plugins|maven-ear-plugin|2.8|3.0.1| > |org.apache.maven.plugins|maven-rar-plugin|2.2|2.4 (?)| -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (MNG-6169) Lifecycle/binding plugin version updates
[ https://issues.apache.org/jira/browse/MNG-6169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz updated MNG-6169: -- Description: Regular plugin update to absorb changes if plugin version is not specified in the client POM. ||groupId||artifactId||[previous version|http://maven.apache.org/ref/3.5.0/maven-core/default-bindings.html]||target version|| |org.apache.maven.plugins|maven-clean-plugin|2.5|3.1.0| |org.apache.maven.plugins|maven-site-plugin|3.3|3.6| |org.apache.maven.plugins|maven-install-plugin|2.4|3.0.0-M1| |org.apache.maven.plugins|maven-deploy-plugin|2.7|3.0.0-M1| |org.apache.maven.plugins|maven-resources-plugin|2.6|3.0.2| |org.apache.maven.plugins|maven-compiler-plugin|3.1|3.5.1| |org.apache.maven.plugins|maven-surefire-plugin|2.12.4|3.0.0-M3| |org.apache.maven.plugins|maven-jar-plugin|2.4|3.0.2| |org.apache.maven.plugins|maven-ejb-plugin|2.3|2.5.1 (?)| |org.apache.maven.plugins|maven-plugin-plugin|3.2|3.6.0| |org.apache.maven.plugins|maven-war-plugin|2.2|3.0.0| |org.apache.maven.plugins|maven-ear-plugin|2.8|3.0.1| |org.apache.maven.plugins|maven-rar-plugin|2.2|2.4 (?)| was: Regular plugin update to absorb changes if plugin version is not specified in the client POM. ||groupId||artifactId||[previous version|http://maven.apache.org/ref/3.5.0/maven-core/default-bindings.html]||target version|| |org.apache.maven.plugins |maven-clean-plugin|2.5|2.6.1| |org.apache.maven.plugins |maven-site-plugin|3.3|3.6| |org.apache.maven.plugins |maven-install-plugin|2.4|2.5.2| |org.apache.maven.plugins |maven-deploy-plugin|2.7|2.8.2| |org.apache.maven.plugins |maven-resources-plugin|2.6|3.0.2| |org.apache.maven.plugins |maven-compiler-plugin|3.1|3.5.1| |org.apache.maven.plugins |maven-surefire-plugin|2.12.4|2.20| |org.apache.maven.plugins |maven-jar-plugin|2.4|3.0.2| |org.apache.maven.plugins |maven-ejb-plugin|2.3|2.5.1| |org.apache.maven.plugins |maven-plugin-plugin|3.2|3.3| |org.apache.maven.plugins |maven-war-plugin|2.2|3.0.0| |org.apache.maven.plugins |maven-ear-plugin|2.8|2.9.1| |org.apache.maven.plugins |maven-rar-plugin|2.2|2.4| > Lifecycle/binding plugin version updates > > > Key: MNG-6169 > URL: https://issues.apache.org/jira/browse/MNG-6169 > Project: Maven > Issue Type: Improvement > Components: core, Dependencies >Affects Versions: 3.3.9 >Reporter: Christian Schulte >Assignee: Michael Osipov >Priority: Minor > Fix For: 3.6.x-candidate > > > Regular plugin update to absorb changes if plugin version is not specified in > the client POM. > ||groupId||artifactId||[previous > version|http://maven.apache.org/ref/3.5.0/maven-core/default-bindings.html]||target > version|| > |org.apache.maven.plugins|maven-clean-plugin|2.5|3.1.0| > |org.apache.maven.plugins|maven-site-plugin|3.3|3.6| > |org.apache.maven.plugins|maven-install-plugin|2.4|3.0.0-M1| > |org.apache.maven.plugins|maven-deploy-plugin|2.7|3.0.0-M1| > |org.apache.maven.plugins|maven-resources-plugin|2.6|3.0.2| > |org.apache.maven.plugins|maven-compiler-plugin|3.1|3.5.1| > |org.apache.maven.plugins|maven-surefire-plugin|2.12.4|3.0.0-M3| > |org.apache.maven.plugins|maven-jar-plugin|2.4|3.0.2| > |org.apache.maven.plugins|maven-ejb-plugin|2.3|2.5.1 (?)| > |org.apache.maven.plugins|maven-plugin-plugin|3.2|3.6.0| > |org.apache.maven.plugins|maven-war-plugin|2.2|3.0.0| > |org.apache.maven.plugins|maven-ear-plugin|2.8|3.0.1| > |org.apache.maven.plugins|maven-rar-plugin|2.2|2.4 (?)| -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] michael-o commented on issue #185: [MNG-5995] Remove dependency to maven-compat
michael-o commented on issue #185: [MNG-5995] Remove dependency to maven-compat URL: https://github.com/apache/maven/pull/185#issuecomment-451770423 @slachiewicz alright, thank you! This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] slachiewicz commented on issue #185: [MNG-5995] Remove dependency to maven-compat
slachiewicz commented on issue #185: [MNG-5995] Remove dependency to maven-compat URL: https://github.com/apache/maven/pull/185#issuecomment-451770357 Few days of testing.. Critical part was replacement RepositorySystem with MavenRepositorySystem from Maven Core And _getEffectiveRepositories_ is method from _org.apache.maven.repository.legacy.LegacyRepositorySystem#getEffectiveRepositories_ used by _org.apache.maven.project.DefaultProjectBuildingHelper_ This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] michael-o commented on a change in pull request #153: [MNG-6069] Migrate to non deprecated parts of Commons CLI
michael-o commented on a change in pull request #153: [MNG-6069] Migrate to non deprecated parts of Commons CLI URL: https://github.com/apache/maven/pull/153#discussion_r245520451 ## File path: maven-embedder/src/main/java/org/apache/maven/cli/CLIManager.java ## @@ -167,7 +170,7 @@ public void displayHelp( PrintStream stdout ) HelpFormatter formatter = new HelpFormatter(); -formatter.printHelp( pw, HelpFormatter.DEFAULT_WIDTH, "mvn [options] [] []", "\nOptions:", +formatter.printHelp( pw, 120, "mvn [options] [] []", "\nOptions:", Review comment: I think we should replace those `\n` with `System.lineSeparator()`. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] michael-o commented on a change in pull request #153: [MNG-6069] Migrate to non deprecated parts of Commons CLI
michael-o commented on a change in pull request #153: [MNG-6069] Migrate to non deprecated parts of Commons CLI URL: https://github.com/apache/maven/pull/153#discussion_r245520413 ## File path: maven-embedder/src/main/java/org/apache/maven/cli/CLIManager.java ## @@ -167,7 +170,7 @@ public void displayHelp( PrintStream stdout ) HelpFormatter formatter = new HelpFormatter(); -formatter.printHelp( pw, HelpFormatter.DEFAULT_WIDTH, "mvn [options] [] []", "\nOptions:", +formatter.printHelp( pw, 120, "mvn [options] [] []", "\nOptions:", Review comment: Why is this now a literal and not a static final? Ideally, we could calculate the width of the terminal, but this is out of scope here. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] michael-o edited a comment on issue #185: [MNG-5995] Remove dependency to maven-compat
michael-o edited a comment on issue #185: [MNG-5995] Remove dependency to maven-compat URL: https://github.com/apache/maven/pull/185#issuecomment-451769738 This might sound like a stupid question, but how do you know that `#getEffectiveRepositories()` is all you need to make it work? What about the rest in Maven Compat? This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] michael-o commented on issue #185: [MNG-5995] Remove dependency to maven-compat
michael-o commented on issue #185: [MNG-5995] Remove dependency to maven-compat URL: https://github.com/apache/maven/pull/185#issuecomment-451769738 This might sound like a stupid question, but how do you know that `#getEffectiveRepositories()` is all you need to make it work? This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[jira] [Commented] (MNG-6169) Lifecycle/binding plugin version updates
[
https://issues.apache.org/jira/browse/MNG-6169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16735284#comment-16735284
]
Michael Osipov commented on MNG-6169:
-
[~rfscholte], I guess you are referring to {{default-bindings.xml}}. The
{{components.xml}} remains though? It does contain version information for the
lifecycles. One thing to note is that we don't have a {{maven-pom-plugin}}
which covers this as the other packaging plugins.
> Lifecycle/binding plugin version updates
>
>
> Key: MNG-6169
> URL: https://issues.apache.org/jira/browse/MNG-6169
> Project: Maven
> Issue Type: Improvement
> Components: core, Dependencies
>Affects Versions: 3.3.9
>Reporter: Christian Schulte
>Assignee: Michael Osipov
>Priority: Minor
> Fix For: 3.6.x-candidate
>
>
> Regular plugin update to absorb changes if plugin version is not specified in
> the client POM.
> ||groupId||artifactId||[previous
> version|http://maven.apache.org/ref/3.5.0/maven-core/default-bindings.html]||target
> version||
> |org.apache.maven.plugins |maven-clean-plugin|2.5|2.6.1|
> |org.apache.maven.plugins |maven-site-plugin|3.3|3.6|
> |org.apache.maven.plugins |maven-install-plugin|2.4|2.5.2|
> |org.apache.maven.plugins |maven-deploy-plugin|2.7|2.8.2|
> |org.apache.maven.plugins |maven-resources-plugin|2.6|3.0.2|
> |org.apache.maven.plugins |maven-compiler-plugin|3.1|3.5.1|
> |org.apache.maven.plugins |maven-surefire-plugin|2.12.4|2.20|
> |org.apache.maven.plugins |maven-jar-plugin|2.4|3.0.2|
> |org.apache.maven.plugins |maven-ejb-plugin|2.3|2.5.1|
> |org.apache.maven.plugins |maven-plugin-plugin|3.2|3.3|
> |org.apache.maven.plugins |maven-war-plugin|2.2|3.0.0|
> |org.apache.maven.plugins |maven-ear-plugin|2.8|2.9.1|
> |org.apache.maven.plugins |maven-rar-plugin|2.2|2.4|
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MNG-6526) Upgrade to Wagon 3.3.1
[ https://issues.apache.org/jira/browse/MNG-6526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16735283#comment-16735283 ] Hudson commented on MNG-6526: - Build succeeded in Jenkins: Maven TLP » maven » master #123 See https://builds.apache.org/job/maven-box/job/maven/job/master/123/ > Upgrade to Wagon 3.3.1 > -- > > Key: MNG-6526 > URL: https://issues.apache.org/jira/browse/MNG-6526 > Project: Maven > Issue Type: Dependency upgrade > Components: Dependencies >Affects Versions: 3.6.0 >Reporter: Olaf Otto >Assignee: Michael Osipov >Priority: Major > Fix For: 3.6.1 > > > Wagon 3.3.0 contains an important improvement for the transfer speed of large > artifacts (see WAGON-537). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNG-6169) Lifecycle/binding plugin version updates
[ https://issues.apache.org/jira/browse/MNG-6169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16735282#comment-16735282 ] Robert Scholte commented on MNG-6169: - Keep in mind that all the packaging-plugins contain the plugins+version per phase bindings, which overrules this configuration. In the future Maven won't contain this kind of information anymore, the packaging plugin is responsible for that. > Lifecycle/binding plugin version updates > > > Key: MNG-6169 > URL: https://issues.apache.org/jira/browse/MNG-6169 > Project: Maven > Issue Type: Improvement > Components: core, Dependencies >Affects Versions: 3.3.9 >Reporter: Christian Schulte >Assignee: Michael Osipov >Priority: Minor > Fix For: 3.6.x-candidate > > > Regular plugin update to absorb changes if plugin version is not specified in > the client POM. > ||groupId||artifactId||[previous > version|http://maven.apache.org/ref/3.5.0/maven-core/default-bindings.html]||target > version|| > |org.apache.maven.plugins |maven-clean-plugin|2.5|2.6.1| > |org.apache.maven.plugins |maven-site-plugin|3.3|3.6| > |org.apache.maven.plugins |maven-install-plugin|2.4|2.5.2| > |org.apache.maven.plugins |maven-deploy-plugin|2.7|2.8.2| > |org.apache.maven.plugins |maven-resources-plugin|2.6|3.0.2| > |org.apache.maven.plugins |maven-compiler-plugin|3.1|3.5.1| > |org.apache.maven.plugins |maven-surefire-plugin|2.12.4|2.20| > |org.apache.maven.plugins |maven-jar-plugin|2.4|3.0.2| > |org.apache.maven.plugins |maven-ejb-plugin|2.3|2.5.1| > |org.apache.maven.plugins |maven-plugin-plugin|3.2|3.3| > |org.apache.maven.plugins |maven-war-plugin|2.2|3.0.0| > |org.apache.maven.plugins |maven-ear-plugin|2.8|2.9.1| > |org.apache.maven.plugins |maven-rar-plugin|2.2|2.4| -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (MNG-6526) Upgrade to Wagon 3.3.1
[ https://issues.apache.org/jira/browse/MNG-6526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed MNG-6526. --- Resolution: Fixed Fixed with [391a1118fa96ff580d6704a8e7083da76c911035|https://gitbox.apache.org/repos/asf?p=maven.git;a=commit;h=391a1118fa96ff580d6704a8e7083da76c911035]. > Upgrade to Wagon 3.3.1 > -- > > Key: MNG-6526 > URL: https://issues.apache.org/jira/browse/MNG-6526 > Project: Maven > Issue Type: Dependency upgrade > Components: Dependencies >Affects Versions: 3.6.0 >Reporter: Olaf Otto >Assignee: Michael Osipov >Priority: Major > Fix For: 3.6.1 > > > Wagon 3.3.0 contains an important improvement for the transfer speed of large > artifacts (see WAGON-537). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (SCM-880) Maven SCM Client fails to be assembled on Java 10
[
https://issues.apache.org/jira/browse/SCM-880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed SCM-880.
--
Resolution: Cannot Reproduce
Since Java 10 is EOL, tried with JAva 11.0.1 on CentOS 7 and Windows 10 with
current master and cannot reproduce issue.
> Maven SCM Client fails to be assembled on Java 10
> -
>
> Key: SCM-880
> URL: https://issues.apache.org/jira/browse/SCM-880
> Project: Maven SCM
> Issue Type: Bug
> Components: maven-scm-client
>Affects Versions: 1.9.5
> Environment: Apache Maven 3.5.3
> (3383c37e1f9e9b3bc3df5050c29c8aff9f295297; 2018-02-24T20:49:05+01:00)
> Maven home: /opt/apache-maven-3.5.3
> Java version: 10, vendor: Azul Systems, Inc.
> Java home: /usr/lib/jvm/zulu-10
> Default locale: de_DE, platform encoding: UTF-8
> OS name: "linux", version: "4.13.16-100.fc25.x86_64", arch: "amd64", family:
> "unix"
>Reporter: Michael Osipov
>Priority: Major
>
> {{mvn clean verify}} fails with:
> {noformat}
> [INFO] Maven SCM Client ... FAILURE [ 2.317
> s]
> [INFO] Maven SCM Plugin 1.9.6-SNAPSHOT SUCCESS [ 16.081
> s]
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 03:08 min
> [INFO] Finished at: 2018-04-02T01:50:55+02:00
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-assembly-plugin:2.6:single (default) on
> project maven-scm-client: Execution default of goal
> org.apache.maven.plugins:maven-assembly-plugin:2.6:single failed: An API
> incompatibility was encountered while executing
> org.apache.maven.plugins:maven-assembly-plugin:2.6:single:
> java.lang.ExceptionInInitializerError: null
> [ERROR] -
> [ERROR] realm = plugin>org.apache.maven.plugins:maven-assembly-plugin:2.6
> [ERROR] strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
> [ERROR] urls[0] =
> file:/home/mosipov/.m2/repository/org/apache/maven/plugins/maven-assembly-plugin/2.6/maven-assembly-plugin-2.6.jar
> [ERROR] urls[1] =
> file:/home/mosipov/.m2/repository/org/slf4j/slf4j-jdk14/1.5.6/slf4j-jdk14-1.5.6.jar
> [ERROR] urls[2] =
> file:/home/mosipov/.m2/repository/org/slf4j/jcl-over-slf4j/1.5.6/jcl-over-slf4j-1.5.6.jar
> [ERROR] urls[3] =
> file:/home/mosipov/.m2/repository/org/apache/maven/reporting/maven-reporting-api/2.2.1/maven-reporting-api-2.2.1.jar
> [ERROR] urls[4] =
> file:/home/mosipov/.m2/repository/org/apache/maven/doxia/doxia-sink-api/1.1/doxia-sink-api-1.1.jar
> [ERROR] urls[5] =
> file:/home/mosipov/.m2/repository/org/apache/maven/doxia/doxia-logging-api/1.1/doxia-logging-api-1.1.jar
> [ERROR] urls[6] =
> file:/home/mosipov/.m2/repository/junit/junit/3.8.1/junit-3.8.1.jar
> [ERROR] urls[7] =
> file:/home/mosipov/.m2/repository/commons-cli/commons-cli/1.2/commons-cli-1.2.jar
> [ERROR] urls[8] =
> file:/home/mosipov/.m2/repository/org/codehaus/plexus/plexus-interactivity-api/1.0-alpha-4/plexus-interactivity-api-1.0-alpha-4.jar
> [ERROR] urls[9] =
> file:/home/mosipov/.m2/repository/backport-util-concurrent/backport-util-concurrent/3.1/backport-util-concurrent-3.1.jar
> [ERROR] urls[10] =
> file:/home/mosipov/.m2/repository/org/sonatype/plexus/plexus-sec-dispatcher/1.3/plexus-sec-dispatcher-1.3.jar
> [ERROR] urls[11] =
> file:/home/mosipov/.m2/repository/org/sonatype/plexus/plexus-cipher/1.4/plexus-cipher-1.4.jar
> [ERROR] urls[12] =
> file:/home/mosipov/.m2/repository/org/apache/maven/shared/maven-common-artifact-filters/1.4/maven-common-artifact-filters-1.4.jar
> [ERROR] urls[13] =
> file:/home/mosipov/.m2/repository/org/codehaus/plexus/plexus-interpolation/1.22/plexus-interpolation-1.22.jar
> [ERROR] urls[14] =
> file:/home/mosipov/.m2/repository/org/codehaus/plexus/plexus-archiver/3.0.1/plexus-archiver-3.0.1.jar
> [ERROR] urls[15] =
> file:/home/mosipov/.m2/repository/org/iq80/snappy/snappy/0.3/snappy-0.3.jar
> [ERROR] urls[16] =
> file:/home/mosipov/.m2/repository/org/apache/maven/shared/file-management/1.1/file-management-1.1.jar
> [ERROR] urls[17] =
> file:/home/mosipov/.m2/repository/org/apache/maven/shared/maven-shared-io/1.1/maven-shared-io-1.1.jar
> [ERROR] urls[18] =
> file:/home/mosipov/.m2/repository/commons-io/commons-io/2.2/commons-io-2.2.jar
> [ERROR] urls[19] =
> file:/home/mosipov/.m2/repository/org/apache/maven/shared/maven-filtering/1.3/maven-filtering-1.3.jar
> [ERROR] urls[20] =
> file:/home/mosipov/.m2/repository/org/apache/maven/shared/maven-shared-utils/0.6/maven-shared-utils-0.6.jar
> [ERROR] urls[21] =
>
[jira] [Updated] (MNG-6526) Upgrade to Wagon 3.3.1
[ https://issues.apache.org/jira/browse/MNG-6526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MNG-6526: Fix Version/s: 3.6.1 > Upgrade to Wagon 3.3.1 > -- > > Key: MNG-6526 > URL: https://issues.apache.org/jira/browse/MNG-6526 > Project: Maven > Issue Type: Dependency upgrade > Components: Dependencies >Affects Versions: 3.6.0 >Reporter: Olaf Otto >Assignee: Michael Osipov >Priority: Major > Fix For: 3.6.1 > > > Wagon 3.3.0 contains an important improvement for the transfer speed of large > artifacts (see WAGON-537). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (MNG-6526) Upgrade to Wagon 3.3.1
[ https://issues.apache.org/jira/browse/MNG-6526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MNG-6526: Summary: Upgrade to Wagon 3.3.1 (was: Upgrade to Wagon 3.3.0) > Upgrade to Wagon 3.3.1 > -- > > Key: MNG-6526 > URL: https://issues.apache.org/jira/browse/MNG-6526 > Project: Maven > Issue Type: Dependency upgrade > Components: Dependencies >Affects Versions: 3.6.0 >Reporter: Olaf Otto >Assignee: Michael Osipov >Priority: Major > > Wagon 3.3.0 contains an important improvement for the transfer speed of large > artifacts (see WAGON-537). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (WAGON-446) SSH agent authentication is no longer working in wagon-ssh 2.10
[ https://issues.apache.org/jira/browse/WAGON-446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated WAGON-446: - Fix Version/s: (was: waiting-for-feedback) > SSH agent authentication is no longer working in wagon-ssh 2.10 > --- > > Key: WAGON-446 > URL: https://issues.apache.org/jira/browse/WAGON-446 > Project: Maven Wagon > Issue Type: Bug > Components: wagon-ssh >Affects Versions: 2.10 >Reporter: Per Landberg >Assignee: Dan Tran >Priority: Major > Attachments: wagon-446.patch > > > After upgrading to wagon-2.10, SSH Agent authentication doesn't seems to > work anymore. I got the following error when trying to publish a site, using > maven-site-plugin 3.4: > Using private key: > : Error uploading site: Cannot connect. Reason: Auth fail -> [Help 1] > I have no server for this site defined in my settings.xml > After some investigation, I suspect that the cause is WAGON-413 since the > logic in AbstractJschWagon was changed to not use the agent if > ScpHelper.getPrivateKey() returns a File. > Unfortunate, ScpHelper.getPrivateKey() seems to have a fallback behavior that > always returns the id_rsa key (if one exists) even when no matching server > element exists in settings.xml and the effect is that the agent is never > consulted. > The authentication will then fail since no server element provides a key > password. > My current workaround is to set the wagon.privateKeyDirectory System Property > to an empty directory. This will prevent the ScpHelper.getPrivateKey() > fallback to kick in. > Has anybody else got SSH agent working in combination with existing id_rsa > files? -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (WAGON-491) Being able to set certificate via byte[] not only a file
[ https://issues.apache.org/jira/browse/WAGON-491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16735212#comment-16735212 ] Michael Osipov commented on WAGON-491: -- I will evaluate this for the next iteration. > Being able to set certificate via byte[] not only a file > > > Key: WAGON-491 > URL: https://issues.apache.org/jira/browse/WAGON-491 > Project: Maven Wagon > Issue Type: New Feature > Components: wagon-ssh >Reporter: Laurent Granié >Priority: Major > Attachments: 20181206-wagon-ssh.patch > > > I'm using wagon outside Maven. > I would like to authenticate on sftp servers via a certificate. > It's possible today via a file with a file path but not if I include the > certificate in the .jar. > I would like to be able to set the certificate with a byte[]. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (WAGON-491) Being able to set certificate via byte[] not only a file
[ https://issues.apache.org/jira/browse/WAGON-491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated WAGON-491: - Fix Version/s: (was: waiting-for-feedback) > Being able to set certificate via byte[] not only a file > > > Key: WAGON-491 > URL: https://issues.apache.org/jira/browse/WAGON-491 > Project: Maven Wagon > Issue Type: New Feature > Components: wagon-ssh >Reporter: Laurent Granié >Priority: Major > Attachments: 20181206-wagon-ssh.patch > > > I'm using wagon outside Maven. > I would like to authenticate on sftp servers via a certificate. > It's possible today via a file with a file path but not if I include the > certificate in the .jar. > I would like to be able to set the certificate with a byte[]. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MJAVADOC-527) detectLinks may pass invalid URLs to javadoc(1)
[ https://issues.apache.org/jira/browse/MJAVADOC-527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16735206#comment-16735206 ] Hudson commented on MJAVADOC-527: - Build failed in Jenkins: Maven TLP » maven-javadoc-plugin » MJAVADOC-555 #4 See https://builds.apache.org/job/maven-box/job/maven-javadoc-plugin/job/MJAVADOC-555/4/ > detectLinks may pass invalid URLs to javadoc(1) > --- > > Key: MJAVADOC-527 > URL: https://issues.apache.org/jira/browse/MJAVADOC-527 > Project: Maven Javadoc Plugin > Issue Type: Bug > Components: javadoc >Affects Versions: 3.0.1 > Environment: Windows 10 > JDK 8 > Maven 3.5.2 >Reporter: Roberto Benedetti >Assignee: Michael Osipov >Priority: Major > Labels: detectLinks > Fix For: 3.1.0 > > Time Spent: 10m > Remaining Estimate: 0h > > The url of artifact com.sun.mail:mailapi:1.5.5 is > [http://javamail.java.net/mailapi], so the plugin tests if > [http://javamail.java.net/mailapi/apidocs/package-list] is valid. > That url redirects to [https://javaee.github.io/javamail/] which is JavaMail > home page, so the plugin thinks the url is valid and passes it to javadoc. > javadoc warns about invalid link. > Maybe checking if the effective url is still "package-list" would be safer. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MJAVADOC-555) Javadoc:aggregate, Javadoc:jar fail if one of the modules does not contain module-info.java
[
https://issues.apache.org/jira/browse/MJAVADOC-555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16735207#comment-16735207
]
Hudson commented on MJAVADOC-555:
-
Build failed in Jenkins: Maven TLP » maven-javadoc-plugin » MJAVADOC-555 #4
See
https://builds.apache.org/job/maven-box/job/maven-javadoc-plugin/job/MJAVADOC-555/4/
> Javadoc:aggregate, Javadoc:jar fail if one of the modules does not contain
> module-info.java
> ---
>
> Key: MJAVADOC-555
> URL: https://issues.apache.org/jira/browse/MJAVADOC-555
> Project: Maven Javadoc Plugin
> Issue Type: Bug
> Components: jar, javadoc
>Affects Versions: 3.1.0
> Environment: Maven 3.6.0
> maven-javadoc-plugin 3.0.2-SNAPSHOT (required for Java 11 support)
>Reporter: Gili
>Priority: Major
> Attachments: javadoc-cannot-link-to-automatic-modules.zip,
> testcase.zip, toolchains.xml
>
>
> # Unzip testcase
> # Run {{mvn clean install javadoc:aggregate}}
> # Build fails with: {{Exit code: 2 - javadoc: error - No source files for
> package module2}}
> Per MPLUGIN-341, Maven plugins cannot contain {{module.info.java}}. One of my
> projects builds under Java 11 and is fully modularized except for one module
> which is a Maven plugin. Due to the aforementioned issue, I cannot use
> {{javadoc:aggregate.}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (SUREFIRE-1621) package-private class/method supported in JUnit5 is not executed
Alex Chacha created SUREFIRE-1621:
-
Summary: package-private class/method supported in JUnit5 is not
executed
Key: SUREFIRE-1621
URL: https://issues.apache.org/jira/browse/SUREFIRE-1621
Project: Maven Surefire
Issue Type: Bug
Components: JUnit 5.x support
Affects Versions: 3.0.0-M3
Environment: Java openJDK11, Maven 3.6.0
Reporter: Alex Chacha
Test classes/methods have to be made pubic in order for maven/surefire to
execute them.
Following will not execute (DebugTest.java) with surefire but will work with
IntelliJ, eclipse, Gradle, etc that support JUnit5:
class DebugTest {
@Test
void failAlways() {
assertTrue(false);
}
}
However changing it to following will work with Surefire but cause IDEs to flag
public scope that can be changed to package-private:
public class DebugTest {
@Test
public void failAlways() {
assertTrue(false);
}
}
JUnit 5 is supposed to support package-private declaration for test classes and
test methods and IDEs like IntelliJ and eclipse are suggesting this, creating
issues for people writing new tests that are not aware of the surefire anomaly.
Also automatic code cleanup in some IDEs are changing the tests to be
package-private and causing them to no longer run.
Package-private tests are running correctly inside the IDEs and via Gradle, but
being skipped with Maven+Surefire.
from POM (basically a simple java project):(
${project.basedir}/src/test/java
org.apache.maven.plugins
maven-surefire-plugin
3.0.0-M3
and in dependencies:
...
org.junit.jupiter
junit-jupiter-api
5.3.2
test
org.apache.maven.plugins
maven-surefire-plugin
3.0.0-M3
test
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (SUREFIRE-1621) package-private class/method supported in JUnit5 is not executed
[
https://issues.apache.org/jira/browse/SUREFIRE-1621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Chacha updated SUREFIRE-1621:
--
Description:
Test classes/methods have to be made pubic in order for maven/surefire to
execute them.
Following will not execute (DebugTest.java) with surefire but will work with
IntelliJ, eclipse, Gradle, etc that support JUnit5:
{code:java}
class DebugTest {
@Test
void failAlways() { assertTrue(false); }
}
{code}
However changing it to following will work with Surefire but cause IDEs to flag
public scope that can be changed to package-private:
{code:java}
public class DebugTest {
@Test
public void failAlways() { assertTrue(false); }
}
{code}
JUnit 5 is supposed to support package-private declaration for test classes and
test methods and IDEs like IntelliJ and eclipse are suggesting this, creating
issues for people writing new tests that are not aware of the surefire anomaly.
Also automatic code cleanup in some IDEs are changing the tests to be
package-private and causing them to no longer run.
Package-private tests are running correctly inside the IDEs and via Gradle, but
being skipped with Maven+Surefire.
from POM (basically a simple java project)
{code:java}
${project.basedir}/src/test/java
org.apache.maven.plugins
maven-surefire-plugin
3.0.0-M3
{code}
and in dependencies:
{code:java}
...
org.junit.jupiter
junit-jupiter-api
5.3.2
test
org.apache.maven.plugins
maven-surefire-plugin
3.0.0-M3
test
{code}
was:
Test classes/methods have to be made pubic in order for maven/surefire to
execute them.
Following will not execute (DebugTest.java) with surefire but will work with
IntelliJ, eclipse, Gradle, etc that support JUnit5:
{code:java}
class DebugTest {
@Test
void failAlways() { assertTrue(false); }
}
{code}
However changing it to following will work with Surefire but cause IDEs to flag
public scope that can be changed to package-private:
{code:java}
public class DebugTest {
@Test
public void failAlways() { assertTrue(false); }
}
{code}
JUnit 5 is supposed to support package-private declaration for test classes and
test methods and IDEs like IntelliJ and eclipse are suggesting this, creating
issues for people writing new tests that are not aware of the surefire anomaly.
Also automatic code cleanup in some IDEs are changing the tests to be
package-private and causing them to no longer run.
Package-private tests are running correctly inside the IDEs and via Gradle, but
being skipped with Maven+Surefire.
from POM (basically a simple java project):(
{code:java}
${project.basedir}/src/test/java
org.apache.maven.plugins
maven-surefire-plugin
3.0.0-M3
{code}
and in dependencies:
{code:java}
...
org.junit.jupiter
junit-jupiter-api
5.3.2
test
org.apache.maven.plugins
maven-surefire-plugin
3.0.0-M3
test
{code}
> package-private class/method supported in JUnit5 is not executed
>
>
> Key: SUREFIRE-1621
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1621
> Project: Maven Surefire
> Issue Type: Bug
> Components: JUnit 5.x support
>Affects Versions: 3.0.0-M3
> Environment: Java openJDK11, Maven 3.6.0
>Reporter: Alex Chacha
>Priority: Major
>
> Test classes/methods have to be made pubic in order for maven/surefire to
> execute them.
>
> Following will not execute (DebugTest.java) with surefire but will work with
> IntelliJ, eclipse, Gradle, etc that support JUnit5:
>
> {code:java}
> class DebugTest {
> @Test
> void failAlways() { assertTrue(false); }
> }
> {code}
>
> However changing it to following will work with Surefire but cause IDEs to
> flag public scope that can be changed to package-private:
>
> {code:java}
> public class DebugTest {
> @Test
> public void failAlways() { assertTrue(false); }
> }
> {code}
>
> JUnit 5 is supposed to support package-private declaration for test classes
> and test methods and IDEs like IntelliJ and eclipse are suggesting this,
> creating issues for people writing new tests that are not aware of the
> surefire anomaly. Also automatic code cleanup in some IDEs are changing the
> tests to be package-private and causing them to no longer run.
>
> Package-private tests are running correctly inside the IDEs and via Gradle,
> but being skipped with Maven+Surefire.
>
> from POM (basically a simple java project)
> {code:java}
>
> ${project.basedir}/src/test/java
>
>
> org.apache.maven.plugins
> maven-surefire-plugin
[jira] [Updated] (SUREFIRE-1621) package-private class/method supported in JUnit5 is not executed
[
https://issues.apache.org/jira/browse/SUREFIRE-1621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Chacha updated SUREFIRE-1621:
--
Description:
Test classes/methods have to be made pubic in order for maven/surefire to
execute them.
Following will not execute (DebugTest.java) with surefire but will work with
IntelliJ, eclipse, Gradle, etc that support JUnit5:
{code:java}
class DebugTest {
@Test
void failAlways() { assertTrue(false); }
}
{code}
However changing it to following will work with Surefire but cause IDEs to flag
public scope that can be changed to package-private:
{code:java}
public class DebugTest {
@Test
public void failAlways() { assertTrue(false); }
}
{code}
JUnit 5 is supposed to support package-private declaration for test classes and
test methods and IDEs like IntelliJ and eclipse are suggesting this, creating
issues for people writing new tests that are not aware of the surefire anomaly.
Also automatic code cleanup in some IDEs are changing the tests to be
package-private and causing them to no longer run.
Package-private tests are running correctly inside the IDEs and via Gradle, but
being skipped with Maven+Surefire.
from POM (basically a simple java project):(
{code:java}
${project.basedir}/src/test/java
org.apache.maven.plugins
maven-surefire-plugin
3.0.0-M3
{code}
and in dependencies:
{code:java}
...
org.junit.jupiter
junit-jupiter-api
5.3.2
test
org.apache.maven.plugins
maven-surefire-plugin
3.0.0-M3
test
{code}
was:
Test classes/methods have to be made pubic in order for maven/surefire to
execute them.
Following will not execute (DebugTest.java) with surefire but will work with
IntelliJ, eclipse, Gradle, etc that support JUnit5:
class DebugTest {
@Test
void failAlways() {
assertTrue(false);
}
}
However changing it to following will work with Surefire but cause IDEs to flag
public scope that can be changed to package-private:
public class DebugTest {
@Test
public void failAlways() {
assertTrue(false);
}
}
JUnit 5 is supposed to support package-private declaration for test classes and
test methods and IDEs like IntelliJ and eclipse are suggesting this, creating
issues for people writing new tests that are not aware of the surefire anomaly.
Also automatic code cleanup in some IDEs are changing the tests to be
package-private and causing them to no longer run.
Package-private tests are running correctly inside the IDEs and via Gradle, but
being skipped with Maven+Surefire.
from POM (basically a simple java project):(
${project.basedir}/src/test/java
org.apache.maven.plugins
maven-surefire-plugin
3.0.0-M3
and in dependencies:
...
org.junit.jupiter
junit-jupiter-api
5.3.2
test
org.apache.maven.plugins
maven-surefire-plugin
3.0.0-M3
test
> package-private class/method supported in JUnit5 is not executed
>
>
> Key: SUREFIRE-1621
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1621
> Project: Maven Surefire
> Issue Type: Bug
> Components: JUnit 5.x support
>Affects Versions: 3.0.0-M3
> Environment: Java openJDK11, Maven 3.6.0
>Reporter: Alex Chacha
>Priority: Major
>
> Test classes/methods have to be made pubic in order for maven/surefire to
> execute them.
>
> Following will not execute (DebugTest.java) with surefire but will work with
> IntelliJ, eclipse, Gradle, etc that support JUnit5:
>
> {code:java}
> class DebugTest {
> @Test
> void failAlways() { assertTrue(false); }
> }
> {code}
>
> However changing it to following will work with Surefire but cause IDEs to
> flag public scope that can be changed to package-private:
>
> {code:java}
> public class DebugTest {
> @Test
> public void failAlways() { assertTrue(false); }
> }
> {code}
>
> JUnit 5 is supposed to support package-private declaration for test classes
> and test methods and IDEs like IntelliJ and eclipse are suggesting this,
> creating issues for people writing new tests that are not aware of the
> surefire anomaly. Also automatic code cleanup in some IDEs are changing the
> tests to be package-private and causing them to no longer run.
>
> Package-private tests are running correctly inside the IDEs and via Gradle,
> but being skipped with Maven+Surefire.
>
> from POM (basically a simple java project):(
>
> {code:java}
>
> ${project.basedir}/src/test/java
>
>
> org.apache.maven.plugins
> maven-surefire-plugin
> 3.0.0-M3
>
>
>
> {code}
>
>
>
[GitHub] rfscholte commented on a change in pull request #229: [MNG-5693] Change logging of MojoExceptions to console
rfscholte commented on a change in pull request #229: [MNG-5693] Change logging of MojoExceptions to console URL: https://github.com/apache/maven/pull/229#discussion_r245506465 ## File path: maven-core/src/main/java/org/apache/maven/exception/DefaultExceptionHandler.java ## @@ -124,7 +115,7 @@ private ExceptionSummary handle( String message, Throwable exception ) message = getMessage( message, exception ); } -return new ExceptionSummary( exception, message, reference, children ); +return new ExceptionSummary( exception, message, null, children ); Review comment: I think it should be possible for some Maven Exceptions to provide their own reference, so plugins and extensions can refer to their own documentation. This cleanup looks a bit too agressive to me. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
