[jira] [Commented] (MNG-6455) ci-friendly version in parent pom displays build warning in child project

[ https://issues.apache.org/jira/browse/MNG-6455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16676157#comment-16676157 ] Robert Thornton commented on MNG-6455: -- Note that this issue does not happen when the parent is

[jira] [Commented] (MNG-6455) ci-friendly version in parent pom displays build warning in child project

[ https://issues.apache.org/jira/browse/MNG-6455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16676149#comment-16676149 ] Robert Thornton commented on MNG-6455: -- I've attached the steps to reproduce. Please verify and reopen

[jira] [Commented] (MNG-6455) ci-friendly version in parent pom displays build warning in child project

[ https://issues.apache.org/jira/browse/MNG-6455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16676146#comment-16676146 ] Robert Thornton commented on MNG-6455: -- [^mng-6455.zip] ^Steps to reproduce:^ # Unzip the attached

[jira] [Updated] (MNG-6455) ci-friendly version in parent pom displays build warning in child project

[ https://issues.apache.org/jira/browse/MNG-6455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Thornton updated MNG-6455: - Attachment: mng-6455.zip > ci-friendly version in parent pom displays build warning in child

[jira] [Comment Edited] (SUREFIRE-1539) Surefire causes Jigwaw runtime errors when forkCount > 0

[ https://issues.apache.org/jira/browse/SUREFIRE-1539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16676104#comment-16676104 ] Tibor Digana edited comment on SUREFIRE-1539 at 11/6/18 4:07 AM: - I

[jira] [Commented] (SUREFIRE-1539) Surefire causes Jigwaw runtime errors when forkCount > 0

[ https://issues.apache.org/jira/browse/SUREFIRE-1539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16676104#comment-16676104 ] Tibor Digana commented on SUREFIRE-1539: I used your project on GH. If there is

[jira] [Closed] (MSHADE-302) maven-shade-plugin fails to minimize JAR with Java 11

[ https://issues.apache.org/jira/browse/MSHADE-302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy (*$^¨%`£) closed MSHADE-302. - Resolution: Fixed > maven-shade-plugin fails to minimize JAR with Java 11 >

[jira] [Commented] (MSHADE-302) maven-shade-plugin fails to minimize JAR with Java 11

[ https://issues.apache.org/jira/browse/MSHADE-302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16676060#comment-16676060 ] Hudson commented on MSHADE-302: --- Build succeeded in Jenkins: Maven TLP » maven-shade-plugin » master #52

[jira] [Updated] (MJARSIGNER-50) Upgrade maven-shared-utils to 3.1.0

[ https://issues.apache.org/jira/browse/MJARSIGNER-50?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hervé Boutemy updated MJARSIGNER-50: Issue Type: Dependency upgrade (was: Improvement) > Upgrade maven-shared-utils to

[jira] [Updated] (MJARSIGNER-49) Upgrade maven-shared-components parent to version 30

[ https://issues.apache.org/jira/browse/MJARSIGNER-49?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hervé Boutemy updated MJARSIGNER-49: Issue Type: Dependency upgrade (was: Improvement) > Upgrade maven-shared-components

[jira] [Updated] (MNG-6507) CI-friendly versioning doesn't work when included as dependency

[ https://issues.apache.org/jira/browse/MNG-6507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] mike duigou updated MNG-6507: - Description: I saw in the 3.6.0 release notes that several issues for CI friendly versions had been fixed

[jira] [Commented] (MNG-6444) Internal code should prefer Path over File

[ https://issues.apache.org/jira/browse/MNG-6444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16675715#comment-16675715 ] Robert Scholte commented on MNG-6444: - Changing the returnType for getFile() would break a a lot of

[jira] [Updated] (MNG-6507) CI-friendly versioning doesn't work when included as dependency

[ https://issues.apache.org/jira/browse/MNG-6507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] mike duigou updated MNG-6507: - Description: I saw in the 3.6.0 release notes that several issues for CI friendly versions had been fixed

[jira] [Updated] (MNG-6507) CI-friendly versioning doesn't work when included as dependency

[ https://issues.apache.org/jira/browse/MNG-6507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] mike duigou updated MNG-6507: - Description: I saw in the 3.6.0 release notes that several issues for CI friendly versions had been fixed

[jira] [Created] (MNG-6507) CI-friendly versioning doesn't work when included as dependency

mike duigou created MNG-6507: Summary: CI-friendly versioning doesn't work when included as dependency Key: MNG-6507 URL: https://issues.apache.org/jira/browse/MNG-6507 Project: Maven Issue

[jira] [Updated] (MEAR-271) Support lookup-name in resource-ref section

[ https://issues.apache.org/jira/browse/MEAR-271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise updated MEAR-271: - Fix Version/s: 3.0.2 > Support lookup-name in resource-ref section >

[jira] [Assigned] (MEAR-271) Support lookup-name in resource-ref section

[ https://issues.apache.org/jira/browse/MEAR-271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise reassigned MEAR-271: Assignee: Karl Heinz Marbaise > Support lookup-name in resource-ref section >

[jira] [Commented] (MEAR-271) Support lookup-name in resource-ref section

[ https://issues.apache.org/jira/browse/MEAR-271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16675445#comment-16675445 ] ASF GitHub Bot commented on MEAR-271: - fabio-boldrini opened a new pull request #1: [MEAR-271] added

[GitHub] fabio-boldrini opened a new pull request #1: [MEAR-271] added support for property

fabio-boldrini opened a new pull request #1: [MEAR-271] added support for property URL: https://github.com/apache/maven-ear-plugin/pull/1 NO JIRA Issue [MEAR-271] add support for **lookup-name** tag inside **resourceRef** - [x] I hereby declare this

[jira] [Commented] (MSHADE-302) maven-shade-plugin fails to minimize JAR with Java 11

[ https://issues.apache.org/jira/browse/MSHADE-302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16675417#comment-16675417 ] Yuri commented on MSHADE-302: - Hi [~cowwoc], you are right. Master as-is doesn't resolve this issue. It works

[jira] [Comment Edited] (MSHADE-302) maven-shade-plugin fails to minimize JAR with Java 11

[ https://issues.apache.org/jira/browse/MSHADE-302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16675304#comment-16675304 ] Gili edited comment on MSHADE-302 at 11/5/18 3:28 PM: -- [~ydewit] I just checked and

[jira] [Commented] (MSHADE-302) maven-shade-plugin fails to minimize JAR with Java 11

[ https://issues.apache.org/jira/browse/MSHADE-302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16675304#comment-16675304 ] Gili commented on MSHADE-302: - @Yuri I just checked and it still does not work for me. Are you sure you have

[jira] [Commented] (MSHADE-302) maven-shade-plugin fails to minimize JAR with Java 11

[ https://issues.apache.org/jira/browse/MSHADE-302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16675248#comment-16675248 ] Yuri commented on MSHADE-302: - FWIW, I just verified that the latest on master (3.2.1-SNAPSHOT) is able to

[jira] [Comment Edited] (SUREFIRE-1587) Forked execution prevents correct ServerSocket closing

[ https://issues.apache.org/jira/browse/SUREFIRE-1587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16674915#comment-16674915 ] Johannes Wienke edited comment on SUREFIRE-1587 at 11/5/18 10:18 AM:

[jira] [Commented] (SUREFIRE-1587) Forked execution prevents correct ServerSocket closing

[ https://issues.apache.org/jira/browse/SUREFIRE-1587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16674915#comment-16674915 ] Johannes Wienke commented on SUREFIRE-1587: --- Could you give me a hint how forking is done? I

[GitHub] effrafax opened a new pull request #1: Changing delete pattern matching to relative path

effrafax opened a new pull request #1: Changing delete pattern matching to relative path URL: https://github.com/apache/maven-scm-publish-plugin/pull/1 Hi, the ignorePathsToDelete parameter uses only the file names and not the relative path for matching against the patterns. This