[jira] [Closed] (MJLINK-13) Remove hard code version for maven-site-plugin
[ https://issues.apache.org/jira/browse/MJLINK-13?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise closed MJLINK-13. - Resolution: Fixed Done in [23898eec0e7cd4cb1d97c12bfbc384f57dc12a73|https://gitbox.apache.org/repos/asf?p=maven-jlink-plugin.git;a=commitdiff;h=23898eec0e7cd4cb1d97c12bfbc384f57dc12a73] > Remove hard code version for maven-site-plugin > -- > > Key: MJLINK-13 > URL: https://issues.apache.org/jira/browse/MJLINK-13 > Project: Maven JLink Plugin > Issue Type: Dependency upgrade >Affects Versions: 3.0.0-alpha-1 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.0.0-alpha-2 > > > Currently we overwrite the maven-site-plugin with version 3.6 which should be > removed to let the parent do it's work. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MJLINK-13) Remove hard code version for maven-site-plugin
[ https://issues.apache.org/jira/browse/MJLINK-13?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16393679#comment-16393679 ] Hudson commented on MJLINK-13: -- Build succeeded in Jenkins: Maven TLP » maven-jlink-plugin » master #5 See https://builds.apache.org/job/maven-box/job/maven-jlink-plugin/job/master/5/ > Remove hard code version for maven-site-plugin > -- > > Key: MJLINK-13 > URL: https://issues.apache.org/jira/browse/MJLINK-13 > Project: Maven JLink Plugin > Issue Type: Dependency upgrade >Affects Versions: 3.0.0-alpha-1 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.0.0-alpha-2 > > > Currently we overwrite the maven-site-plugin with version 3.6 which should be > removed to let the parent do it's work. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (MJLINK-13) Remove hard code version for maven-site-plugin
Karl Heinz Marbaise created MJLINK-13: - Summary: Remove hard code version for maven-site-plugin Key: MJLINK-13 URL: https://issues.apache.org/jira/browse/MJLINK-13 Project: Maven JLink Plugin Issue Type: Dependency upgrade Affects Versions: 3.0.0-alpha-1 Reporter: Karl Heinz Marbaise Assignee: Karl Heinz Marbaise Fix For: 3.0.0-alpha-2 Currently we overwrite the maven-site-plugin with version 3.6 which should be removed to let the parent do it's work. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (MEAR-263) Wrong docs in examples/customize-file-name-mapping.html
[ https://issues.apache.org/jira/browse/MEAR-263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise closed MEAR-263. Resolution: Fixed Done in [5f37267eeb7f9a264d823d3a9b7ea2114e8c8a63|https://gitbox.apache.org/repos/asf?p=maven-ear-plugin.git;a=commitdiff;h=5f37267eeb7f9a264d823d3a9b7ea2114e8c8a63] > Wrong docs in examples/customize-file-name-mapping.html > --- > > Key: MEAR-263 > URL: https://issues.apache.org/jira/browse/MEAR-263 > Project: Maven Ear Plugin > Issue Type: Improvement >Affects Versions: 3.0.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Trivial > Fix For: 3.0.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (MEAR-262) Missing since for outputFileNameMapping parameter
[ https://issues.apache.org/jira/browse/MEAR-262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise closed MEAR-262. Resolution: Fixed Done in [cc56c40e9392bb83f71968151d7c18dc23b10b3f|https://gitbox.apache.org/repos/asf?p=maven-ear-plugin.git;a=commitdiff;h=cc56c40e9392bb83f71968151d7c18dc23b10b3f] > Missing since for outputFileNameMapping parameter > - > > Key: MEAR-262 > URL: https://issues.apache.org/jira/browse/MEAR-262 > Project: Maven Ear Plugin > Issue Type: Improvement >Affects Versions: 3.0.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Trivial > Fix For: 3.0.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MEAR-262) Missing since for outputFileNameMapping parameter
[ https://issues.apache.org/jira/browse/MEAR-262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16393490#comment-16393490 ] Hudson commented on MEAR-262: - Build succeeded in Jenkins: Maven TLP » maven-ear-plugin » master #20 See https://builds.apache.org/job/maven-box/job/maven-ear-plugin/job/master/20/ > Missing since for outputFileNameMapping parameter > - > > Key: MEAR-262 > URL: https://issues.apache.org/jira/browse/MEAR-262 > Project: Maven Ear Plugin > Issue Type: Improvement >Affects Versions: 3.0.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Trivial > Fix For: 3.0.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (MEAR-261) In cases where fileNameMapping is used fail the build
[ https://issues.apache.org/jira/browse/MEAR-261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise closed MEAR-261. Resolution: Fixed Done in [16ce3cdd91b78e0d453d3a932df486212a404718|https://gitbox.apache.org/repos/asf?p=maven-ear-plugin.git;a=commitdiff;h=16ce3cdd91b78e0d453d3a932df486212a404718] > In cases where fileNameMapping is used fail the build > - > > Key: MEAR-261 > URL: https://issues.apache.org/jira/browse/MEAR-261 > Project: Maven Ear Plugin > Issue Type: Improvement >Affects Versions: 3.0.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Critical > Fix For: 3.0.0 > > > The parameter has been removed fileNameMapping and has no influence but might > be used in older builds. During migration it should fail the build if this > parameter is being used to show the users there is something todo.. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MEAR-263) Wrong docs in examples/customize-file-name-mapping.html
[ https://issues.apache.org/jira/browse/MEAR-263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16393474#comment-16393474 ] Hudson commented on MEAR-263: - Build succeeded in Jenkins: Maven TLP » maven-ear-plugin » MEAR-263 #3 See https://builds.apache.org/job/maven-box/job/maven-ear-plugin/job/MEAR-263/3/ > Wrong docs in examples/customize-file-name-mapping.html > --- > > Key: MEAR-263 > URL: https://issues.apache.org/jira/browse/MEAR-263 > Project: Maven Ear Plugin > Issue Type: Improvement >Affects Versions: 3.0.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Trivial > Fix For: 3.0.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MEAR-261) In cases where fileNameMapping is used fail the build
[ https://issues.apache.org/jira/browse/MEAR-261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16393473#comment-16393473 ] Hudson commented on MEAR-261: - Build succeeded in Jenkins: Maven TLP » maven-ear-plugin » MEAR-263 #3 See https://builds.apache.org/job/maven-box/job/maven-ear-plugin/job/MEAR-263/3/ > In cases where fileNameMapping is used fail the build > - > > Key: MEAR-261 > URL: https://issues.apache.org/jira/browse/MEAR-261 > Project: Maven Ear Plugin > Issue Type: Improvement >Affects Versions: 3.0.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Critical > Fix For: 3.0.0 > > > The parameter has been removed fileNameMapping and has no influence but might > be used in older builds. During migration it should fail the build if this > parameter is being used to show the users there is something todo.. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MEAR-262) Missing since for outputFileNameMapping parameter
[ https://issues.apache.org/jira/browse/MEAR-262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16393469#comment-16393469 ] Hudson commented on MEAR-262: - Build succeeded in Jenkins: Maven TLP » maven-ear-plugin » MEAR-262 #3 See https://builds.apache.org/job/maven-box/job/maven-ear-plugin/job/MEAR-262/3/ > Missing since for outputFileNameMapping parameter > - > > Key: MEAR-262 > URL: https://issues.apache.org/jira/browse/MEAR-262 > Project: Maven Ear Plugin > Issue Type: Improvement >Affects Versions: 3.0.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Trivial > Fix For: 3.0.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MEAR-261) In cases where fileNameMapping is used fail the build
[ https://issues.apache.org/jira/browse/MEAR-261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16393468#comment-16393468 ] Hudson commented on MEAR-261: - Build succeeded in Jenkins: Maven TLP » maven-ear-plugin » MEAR-262 #3 See https://builds.apache.org/job/maven-box/job/maven-ear-plugin/job/MEAR-262/3/ > In cases where fileNameMapping is used fail the build > - > > Key: MEAR-261 > URL: https://issues.apache.org/jira/browse/MEAR-261 > Project: Maven Ear Plugin > Issue Type: Improvement >Affects Versions: 3.0.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Critical > Fix For: 3.0.0 > > > The parameter has been removed fileNameMapping and has no influence but might > be used in older builds. During migration it should fail the build if this > parameter is being used to show the users there is something todo.. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MEAR-261) In cases where fileNameMapping is used fail the build
[ https://issues.apache.org/jira/browse/MEAR-261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16393462#comment-16393462 ] Hudson commented on MEAR-261: - Build succeeded in Jenkins: Maven TLP » maven-ear-plugin » master #19 See https://builds.apache.org/job/maven-box/job/maven-ear-plugin/job/master/19/ > In cases where fileNameMapping is used fail the build > - > > Key: MEAR-261 > URL: https://issues.apache.org/jira/browse/MEAR-261 > Project: Maven Ear Plugin > Issue Type: Improvement >Affects Versions: 3.0.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Critical > Fix For: 3.0.0 > > > The parameter has been removed fileNameMapping and has no influence but might > be used in older builds. During migration it should fail the build if this > parameter is being used to show the users there is something todo.. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MEAR-259) Fix formatting date issues in apt files
[
https://issues.apache.org/jira/browse/MEAR-259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16393440#comment-16393440
]
Hudson commented on MEAR-259:
-
Build succeeded in Jenkins: Maven TLP » maven-ear-plugin » MEAR-263 #2
See https://builds.apache.org/job/maven-box/job/maven-ear-plugin/job/MEAR-263/2/
> Fix formatting date issues in apt files
> ---
>
> Key: MEAR-259
> URL: https://issues.apache.org/jira/browse/MEAR-259
> Project: Maven Ear Plugin
> Issue Type: Task
>Affects Versions: 3.0.0
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Trivial
> Fix For: 3.0.0
>
>
> During the site generation the APT parser shows wrong formats for dates in
> APT file. This should be fixed.
> {code}
> [INFO] Rendering 25 Doxia documents: 23 apt, 1 fml, 1 xdoc
> [WARNING] Could not parse date 'November 19, 2006' from
> examples/customize-file-name-mapping.apt.vm (expected -MM-dd format),
> ignoring!
> [WARNING] Could not parse date 'September 23, 2005' from
> examples/customizing-a-module-filename.apt.vm (expected -MM-dd format),
> ignoring!
> [WARNING] Could not parse date 'September 23, 2005' from
> examples/customizing-context-root.apt.vm (expected -MM-dd format),
> ignoring!
> [WARNING] Could not parse date 'September 23, 2005' from
> examples/customizing-module-uri.apt.vm (expected -MM-dd format), ignoring!
> [WARNING] Could not parse date 'November 19, 2013' from
> examples/eclipse-and-maven-integration.apt.vm (expected -MM-dd format),
> ignoring!
> [WARNING] Could not parse date 'September 23, 2005' from
> examples/excluding-a-module.apt.vm (expected -MM-dd format), ignoring!
> [WARNING] Could not parse date 'January 3, 2009' from
> examples/filtering-advanced.apt.vm (expected -MM-dd format), ignoring!
> [WARNING] Could not parse date 'January 3, 2009' from
> examples/filtering-sources.apt.vm (expected -MM-dd format), ignoring!
> [WARNING] Could not parse date 'August 06, 2006' from
> examples/generating-jboss-app.apt.vm (expected -MM-dd format), ignoring!
> [WARNING] Could not parse date 'September 4, 2010' from
> examples/generating-modules-id.apt.vm (expected -MM-dd format), ignoring!
> [WARNING] Could not parse date 'September 23, 2005' from
> examples/including-a-third-party-library-in-application-xml.apt.vm (expected
> -MM-dd format), ignoring!
> [WARNING] Could not parse date 'August 27, 2017' from
> examples/specifying-env-entries-for-the-generated-application-xml.apt.vm
> (expected -MM-dd format), ignoring!
> [WARNING] Could not parse date 'August 27, 2017' from
> examples/specifying-resource-ref-entries-for-the-generated-application-xml.apt.vm
> (expected -MM-dd format), ignoring!
> [WARNING] Could not parse date 'September 23, 2005' from
> examples/specifying-security-roles-for-the-generated-application-xml.apt.vm
> (expected -MM-dd format), ignoring!
> [WARNING] Could not parse date 'Augustus 14, 2006' from
> examples/unpacking-a-module.apt.vm (expected -MM-dd format), ignoring!
> [WARNING] Could not parse date 'April 3, 2011' from
> examples/using-app-client.apt.vm (expected -MM-dd format), ignoring!
> [WARNING] Could not parse date '31 July 2006' from modules.apt.vm (expected
> -MM-dd format), ignoring!
> [WARNING] Could not parse date '29 October 2006' from tests.apt (expected
> -MM-dd format), ignoring!
> [INFO] Generating "Summary" report ---
> maven-project-info-reports-plugin:2.9:summary{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MEAR-260) Remove finalName as a parameter
[ https://issues.apache.org/jira/browse/MEAR-260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16393439#comment-16393439 ] Hudson commented on MEAR-260: - Build succeeded in Jenkins: Maven TLP » maven-ear-plugin » MEAR-263 #2 See https://builds.apache.org/job/maven-box/job/maven-ear-plugin/job/MEAR-263/2/ > Remove finalName as a parameter > --- > > Key: MEAR-260 > URL: https://issues.apache.org/jira/browse/MEAR-260 > Project: Maven Ear Plugin > Issue Type: Improvement >Affects Versions: 3.0.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Critical > Fix For: 3.0.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MEAR-263) Wrong docs in examples/customize-file-name-mapping.html
[ https://issues.apache.org/jira/browse/MEAR-263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16393441#comment-16393441 ] Hudson commented on MEAR-263: - Build succeeded in Jenkins: Maven TLP » maven-ear-plugin » MEAR-263 #2 See https://builds.apache.org/job/maven-box/job/maven-ear-plugin/job/MEAR-263/2/ > Wrong docs in examples/customize-file-name-mapping.html > --- > > Key: MEAR-263 > URL: https://issues.apache.org/jira/browse/MEAR-263 > Project: Maven Ear Plugin > Issue Type: Improvement >Affects Versions: 3.0.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Trivial > Fix For: 3.0.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (SUREFIRE-1422) Forking fails on Linux if /bin/ps isn't available
[
https://issues.apache.org/jira/browse/SUREFIRE-1422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16393437#comment-16393437
]
Andrew Potter commented on SUREFIRE-1422:
-
Yes, it failed immediately (less than 1 second)
> Forking fails on Linux if /bin/ps isn't available
> -
>
> Key: SUREFIRE-1422
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1422
> Project: Maven Surefire
> Issue Type: Bug
> Components: process forking
>Affects Versions: 2.20.1
> Environment: Linux (Debian 9 with OpenJDK 8)
>Reporter: Emmanuel Bourg
>Assignee: Tibor Digana
>Priority: Major
> Fix For: 2.21.0
>
>
> Hi,
> With the changes introduced by SUREFIRE-1302 I'm now experiencing a failure
> on Linux when the fork mode is enabled:
> {code}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-surefire-plugin:2.20.1:test (default-test) on
> project foo: There are test failures.
> [ERROR]
> [ERROR] Please refer to /foo/target/surefire-reports for the individual test
> results.
> [ERROR] Please refer to dump files (if any exist) [date]-jvmRun[N].dump,
> [date].dumpstream and [date]-jvmRun[N].dumpstream.
> [ERROR] The forked VM terminated without properly saying goodbye. VM crash or
> System.exit called?
> {code}
> I traced the issue back to the PpidChecker class, the code assumes that
> {{/bin/ps}} or {{/usr/bin/ps}} exist but this isn't guaranteed (especially on
> trimmed down containers commonly used for continuous integration).
> It would be nice to have a fallback mechanism when ps isn't available, or at
> least check its existence and display an explicit message stating that it
> must be installed.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MEAR-262) Missing since for outputFileNameMapping parameter
[ https://issues.apache.org/jira/browse/MEAR-262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16393435#comment-16393435 ] Hudson commented on MEAR-262: - Build succeeded in Jenkins: Maven TLP » maven-ear-plugin » MEAR-262 #2 See https://builds.apache.org/job/maven-box/job/maven-ear-plugin/job/MEAR-262/2/ > Missing since for outputFileNameMapping parameter > - > > Key: MEAR-262 > URL: https://issues.apache.org/jira/browse/MEAR-262 > Project: Maven Ear Plugin > Issue Type: Improvement >Affects Versions: 3.0.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Trivial > Fix For: 3.0.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MEAR-259) Fix formatting date issues in apt files
[
https://issues.apache.org/jira/browse/MEAR-259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16393434#comment-16393434
]
Hudson commented on MEAR-259:
-
Build succeeded in Jenkins: Maven TLP » maven-ear-plugin » MEAR-262 #2
See https://builds.apache.org/job/maven-box/job/maven-ear-plugin/job/MEAR-262/2/
> Fix formatting date issues in apt files
> ---
>
> Key: MEAR-259
> URL: https://issues.apache.org/jira/browse/MEAR-259
> Project: Maven Ear Plugin
> Issue Type: Task
>Affects Versions: 3.0.0
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Trivial
> Fix For: 3.0.0
>
>
> During the site generation the APT parser shows wrong formats for dates in
> APT file. This should be fixed.
> {code}
> [INFO] Rendering 25 Doxia documents: 23 apt, 1 fml, 1 xdoc
> [WARNING] Could not parse date 'November 19, 2006' from
> examples/customize-file-name-mapping.apt.vm (expected -MM-dd format),
> ignoring!
> [WARNING] Could not parse date 'September 23, 2005' from
> examples/customizing-a-module-filename.apt.vm (expected -MM-dd format),
> ignoring!
> [WARNING] Could not parse date 'September 23, 2005' from
> examples/customizing-context-root.apt.vm (expected -MM-dd format),
> ignoring!
> [WARNING] Could not parse date 'September 23, 2005' from
> examples/customizing-module-uri.apt.vm (expected -MM-dd format), ignoring!
> [WARNING] Could not parse date 'November 19, 2013' from
> examples/eclipse-and-maven-integration.apt.vm (expected -MM-dd format),
> ignoring!
> [WARNING] Could not parse date 'September 23, 2005' from
> examples/excluding-a-module.apt.vm (expected -MM-dd format), ignoring!
> [WARNING] Could not parse date 'January 3, 2009' from
> examples/filtering-advanced.apt.vm (expected -MM-dd format), ignoring!
> [WARNING] Could not parse date 'January 3, 2009' from
> examples/filtering-sources.apt.vm (expected -MM-dd format), ignoring!
> [WARNING] Could not parse date 'August 06, 2006' from
> examples/generating-jboss-app.apt.vm (expected -MM-dd format), ignoring!
> [WARNING] Could not parse date 'September 4, 2010' from
> examples/generating-modules-id.apt.vm (expected -MM-dd format), ignoring!
> [WARNING] Could not parse date 'September 23, 2005' from
> examples/including-a-third-party-library-in-application-xml.apt.vm (expected
> -MM-dd format), ignoring!
> [WARNING] Could not parse date 'August 27, 2017' from
> examples/specifying-env-entries-for-the-generated-application-xml.apt.vm
> (expected -MM-dd format), ignoring!
> [WARNING] Could not parse date 'August 27, 2017' from
> examples/specifying-resource-ref-entries-for-the-generated-application-xml.apt.vm
> (expected -MM-dd format), ignoring!
> [WARNING] Could not parse date 'September 23, 2005' from
> examples/specifying-security-roles-for-the-generated-application-xml.apt.vm
> (expected -MM-dd format), ignoring!
> [WARNING] Could not parse date 'Augustus 14, 2006' from
> examples/unpacking-a-module.apt.vm (expected -MM-dd format), ignoring!
> [WARNING] Could not parse date 'April 3, 2011' from
> examples/using-app-client.apt.vm (expected -MM-dd format), ignoring!
> [WARNING] Could not parse date '31 July 2006' from modules.apt.vm (expected
> -MM-dd format), ignoring!
> [WARNING] Could not parse date '29 October 2006' from tests.apt (expected
> -MM-dd format), ignoring!
> [INFO] Generating "Summary" report ---
> maven-project-info-reports-plugin:2.9:summary{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MEAR-260) Remove finalName as a parameter
[ https://issues.apache.org/jira/browse/MEAR-260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16393433#comment-16393433 ] Hudson commented on MEAR-260: - Build succeeded in Jenkins: Maven TLP » maven-ear-plugin » MEAR-262 #2 See https://builds.apache.org/job/maven-box/job/maven-ear-plugin/job/MEAR-262/2/ > Remove finalName as a parameter > --- > > Key: MEAR-260 > URL: https://issues.apache.org/jira/browse/MEAR-260 > Project: Maven Ear Plugin > Issue Type: Improvement >Affects Versions: 3.0.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Critical > Fix For: 3.0.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MEAR-261) In cases where fileNameMapping is used fail the build
[ https://issues.apache.org/jira/browse/MEAR-261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16393426#comment-16393426 ] Hudson commented on MEAR-261: - Build succeeded in Jenkins: Maven TLP » maven-ear-plugin » MEAR-261 #2 See https://builds.apache.org/job/maven-box/job/maven-ear-plugin/job/MEAR-261/2/ > In cases where fileNameMapping is used fail the build > - > > Key: MEAR-261 > URL: https://issues.apache.org/jira/browse/MEAR-261 > Project: Maven Ear Plugin > Issue Type: Improvement >Affects Versions: 3.0.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Critical > Fix For: 3.0.0 > > > The parameter has been removed fileNameMapping and has no influence but might > be used in older builds. During migration it should fail the build if this > parameter is being used to show the users there is something todo.. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MEAR-259) Fix formatting date issues in apt files
[
https://issues.apache.org/jira/browse/MEAR-259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16393425#comment-16393425
]
Hudson commented on MEAR-259:
-
Build succeeded in Jenkins: Maven TLP » maven-ear-plugin » MEAR-261 #2
See https://builds.apache.org/job/maven-box/job/maven-ear-plugin/job/MEAR-261/2/
> Fix formatting date issues in apt files
> ---
>
> Key: MEAR-259
> URL: https://issues.apache.org/jira/browse/MEAR-259
> Project: Maven Ear Plugin
> Issue Type: Task
>Affects Versions: 3.0.0
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Trivial
> Fix For: 3.0.0
>
>
> During the site generation the APT parser shows wrong formats for dates in
> APT file. This should be fixed.
> {code}
> [INFO] Rendering 25 Doxia documents: 23 apt, 1 fml, 1 xdoc
> [WARNING] Could not parse date 'November 19, 2006' from
> examples/customize-file-name-mapping.apt.vm (expected -MM-dd format),
> ignoring!
> [WARNING] Could not parse date 'September 23, 2005' from
> examples/customizing-a-module-filename.apt.vm (expected -MM-dd format),
> ignoring!
> [WARNING] Could not parse date 'September 23, 2005' from
> examples/customizing-context-root.apt.vm (expected -MM-dd format),
> ignoring!
> [WARNING] Could not parse date 'September 23, 2005' from
> examples/customizing-module-uri.apt.vm (expected -MM-dd format), ignoring!
> [WARNING] Could not parse date 'November 19, 2013' from
> examples/eclipse-and-maven-integration.apt.vm (expected -MM-dd format),
> ignoring!
> [WARNING] Could not parse date 'September 23, 2005' from
> examples/excluding-a-module.apt.vm (expected -MM-dd format), ignoring!
> [WARNING] Could not parse date 'January 3, 2009' from
> examples/filtering-advanced.apt.vm (expected -MM-dd format), ignoring!
> [WARNING] Could not parse date 'January 3, 2009' from
> examples/filtering-sources.apt.vm (expected -MM-dd format), ignoring!
> [WARNING] Could not parse date 'August 06, 2006' from
> examples/generating-jboss-app.apt.vm (expected -MM-dd format), ignoring!
> [WARNING] Could not parse date 'September 4, 2010' from
> examples/generating-modules-id.apt.vm (expected -MM-dd format), ignoring!
> [WARNING] Could not parse date 'September 23, 2005' from
> examples/including-a-third-party-library-in-application-xml.apt.vm (expected
> -MM-dd format), ignoring!
> [WARNING] Could not parse date 'August 27, 2017' from
> examples/specifying-env-entries-for-the-generated-application-xml.apt.vm
> (expected -MM-dd format), ignoring!
> [WARNING] Could not parse date 'August 27, 2017' from
> examples/specifying-resource-ref-entries-for-the-generated-application-xml.apt.vm
> (expected -MM-dd format), ignoring!
> [WARNING] Could not parse date 'September 23, 2005' from
> examples/specifying-security-roles-for-the-generated-application-xml.apt.vm
> (expected -MM-dd format), ignoring!
> [WARNING] Could not parse date 'Augustus 14, 2006' from
> examples/unpacking-a-module.apt.vm (expected -MM-dd format), ignoring!
> [WARNING] Could not parse date 'April 3, 2011' from
> examples/using-app-client.apt.vm (expected -MM-dd format), ignoring!
> [WARNING] Could not parse date '31 July 2006' from modules.apt.vm (expected
> -MM-dd format), ignoring!
> [WARNING] Could not parse date '29 October 2006' from tests.apt (expected
> -MM-dd format), ignoring!
> [INFO] Generating "Summary" report ---
> maven-project-info-reports-plugin:2.9:summary{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MEAR-260) Remove finalName as a parameter
[ https://issues.apache.org/jira/browse/MEAR-260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16393424#comment-16393424 ] Hudson commented on MEAR-260: - Build succeeded in Jenkins: Maven TLP » maven-ear-plugin » MEAR-261 #2 See https://builds.apache.org/job/maven-box/job/maven-ear-plugin/job/MEAR-261/2/ > Remove finalName as a parameter > --- > > Key: MEAR-260 > URL: https://issues.apache.org/jira/browse/MEAR-260 > Project: Maven Ear Plugin > Issue Type: Improvement >Affects Versions: 3.0.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Critical > Fix For: 3.0.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MEAR-259) Fix formatting date issues in apt files
[
https://issues.apache.org/jira/browse/MEAR-259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16393420#comment-16393420
]
Hudson commented on MEAR-259:
-
Build succeeded in Jenkins: Maven TLP » maven-ear-plugin » master #18
See https://builds.apache.org/job/maven-box/job/maven-ear-plugin/job/master/18/
> Fix formatting date issues in apt files
> ---
>
> Key: MEAR-259
> URL: https://issues.apache.org/jira/browse/MEAR-259
> Project: Maven Ear Plugin
> Issue Type: Task
>Affects Versions: 3.0.0
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Trivial
> Fix For: 3.0.0
>
>
> During the site generation the APT parser shows wrong formats for dates in
> APT file. This should be fixed.
> {code}
> [INFO] Rendering 25 Doxia documents: 23 apt, 1 fml, 1 xdoc
> [WARNING] Could not parse date 'November 19, 2006' from
> examples/customize-file-name-mapping.apt.vm (expected -MM-dd format),
> ignoring!
> [WARNING] Could not parse date 'September 23, 2005' from
> examples/customizing-a-module-filename.apt.vm (expected -MM-dd format),
> ignoring!
> [WARNING] Could not parse date 'September 23, 2005' from
> examples/customizing-context-root.apt.vm (expected -MM-dd format),
> ignoring!
> [WARNING] Could not parse date 'September 23, 2005' from
> examples/customizing-module-uri.apt.vm (expected -MM-dd format), ignoring!
> [WARNING] Could not parse date 'November 19, 2013' from
> examples/eclipse-and-maven-integration.apt.vm (expected -MM-dd format),
> ignoring!
> [WARNING] Could not parse date 'September 23, 2005' from
> examples/excluding-a-module.apt.vm (expected -MM-dd format), ignoring!
> [WARNING] Could not parse date 'January 3, 2009' from
> examples/filtering-advanced.apt.vm (expected -MM-dd format), ignoring!
> [WARNING] Could not parse date 'January 3, 2009' from
> examples/filtering-sources.apt.vm (expected -MM-dd format), ignoring!
> [WARNING] Could not parse date 'August 06, 2006' from
> examples/generating-jboss-app.apt.vm (expected -MM-dd format), ignoring!
> [WARNING] Could not parse date 'September 4, 2010' from
> examples/generating-modules-id.apt.vm (expected -MM-dd format), ignoring!
> [WARNING] Could not parse date 'September 23, 2005' from
> examples/including-a-third-party-library-in-application-xml.apt.vm (expected
> -MM-dd format), ignoring!
> [WARNING] Could not parse date 'August 27, 2017' from
> examples/specifying-env-entries-for-the-generated-application-xml.apt.vm
> (expected -MM-dd format), ignoring!
> [WARNING] Could not parse date 'August 27, 2017' from
> examples/specifying-resource-ref-entries-for-the-generated-application-xml.apt.vm
> (expected -MM-dd format), ignoring!
> [WARNING] Could not parse date 'September 23, 2005' from
> examples/specifying-security-roles-for-the-generated-application-xml.apt.vm
> (expected -MM-dd format), ignoring!
> [WARNING] Could not parse date 'Augustus 14, 2006' from
> examples/unpacking-a-module.apt.vm (expected -MM-dd format), ignoring!
> [WARNING] Could not parse date 'April 3, 2011' from
> examples/using-app-client.apt.vm (expected -MM-dd format), ignoring!
> [WARNING] Could not parse date '31 July 2006' from modules.apt.vm (expected
> -MM-dd format), ignoring!
> [WARNING] Could not parse date '29 October 2006' from tests.apt (expected
> -MM-dd format), ignoring!
> [INFO] Generating "Summary" report ---
> maven-project-info-reports-plugin:2.9:summary{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (MEAR-259) Fix formatting date issues in apt files
[
https://issues.apache.org/jira/browse/MEAR-259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Heinz Marbaise closed MEAR-259.
Resolution: Fixed
Done in
[032dfa36dbd16a3bedff92076acd1d2cf66d1ed0|https://gitbox.apache.org/repos/asf?p=maven-ear-plugin.git;a=commitdiff;h=032dfa36dbd16a3bedff92076acd1d2cf66d1ed0]
> Fix formatting date issues in apt files
> ---
>
> Key: MEAR-259
> URL: https://issues.apache.org/jira/browse/MEAR-259
> Project: Maven Ear Plugin
> Issue Type: Task
>Affects Versions: 3.0.0
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Trivial
> Fix For: 3.0.0
>
>
> During the site generation the APT parser shows wrong formats for dates in
> APT file. This should be fixed.
> {code}
> [INFO] Rendering 25 Doxia documents: 23 apt, 1 fml, 1 xdoc
> [WARNING] Could not parse date 'November 19, 2006' from
> examples/customize-file-name-mapping.apt.vm (expected -MM-dd format),
> ignoring!
> [WARNING] Could not parse date 'September 23, 2005' from
> examples/customizing-a-module-filename.apt.vm (expected -MM-dd format),
> ignoring!
> [WARNING] Could not parse date 'September 23, 2005' from
> examples/customizing-context-root.apt.vm (expected -MM-dd format),
> ignoring!
> [WARNING] Could not parse date 'September 23, 2005' from
> examples/customizing-module-uri.apt.vm (expected -MM-dd format), ignoring!
> [WARNING] Could not parse date 'November 19, 2013' from
> examples/eclipse-and-maven-integration.apt.vm (expected -MM-dd format),
> ignoring!
> [WARNING] Could not parse date 'September 23, 2005' from
> examples/excluding-a-module.apt.vm (expected -MM-dd format), ignoring!
> [WARNING] Could not parse date 'January 3, 2009' from
> examples/filtering-advanced.apt.vm (expected -MM-dd format), ignoring!
> [WARNING] Could not parse date 'January 3, 2009' from
> examples/filtering-sources.apt.vm (expected -MM-dd format), ignoring!
> [WARNING] Could not parse date 'August 06, 2006' from
> examples/generating-jboss-app.apt.vm (expected -MM-dd format), ignoring!
> [WARNING] Could not parse date 'September 4, 2010' from
> examples/generating-modules-id.apt.vm (expected -MM-dd format), ignoring!
> [WARNING] Could not parse date 'September 23, 2005' from
> examples/including-a-third-party-library-in-application-xml.apt.vm (expected
> -MM-dd format), ignoring!
> [WARNING] Could not parse date 'August 27, 2017' from
> examples/specifying-env-entries-for-the-generated-application-xml.apt.vm
> (expected -MM-dd format), ignoring!
> [WARNING] Could not parse date 'August 27, 2017' from
> examples/specifying-resource-ref-entries-for-the-generated-application-xml.apt.vm
> (expected -MM-dd format), ignoring!
> [WARNING] Could not parse date 'September 23, 2005' from
> examples/specifying-security-roles-for-the-generated-application-xml.apt.vm
> (expected -MM-dd format), ignoring!
> [WARNING] Could not parse date 'Augustus 14, 2006' from
> examples/unpacking-a-module.apt.vm (expected -MM-dd format), ignoring!
> [WARNING] Could not parse date 'April 3, 2011' from
> examples/using-app-client.apt.vm (expected -MM-dd format), ignoring!
> [WARNING] Could not parse date '31 July 2006' from modules.apt.vm (expected
> -MM-dd format), ignoring!
> [WARNING] Could not parse date '29 October 2006' from tests.apt (expected
> -MM-dd format), ignoring!
> [INFO] Generating "Summary" report ---
> maven-project-info-reports-plugin:2.9:summary{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (MEAR-260) Remove finalName as a parameter
[ https://issues.apache.org/jira/browse/MEAR-260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise closed MEAR-260. Resolution: Fixed Done in [2568cd383c10330efd6766bb9f25fef079c204dd|https://gitbox.apache.org/repos/asf?p=maven-ear-plugin.git;a=commitdiff;h=2568cd383c10330efd6766bb9f25fef079c204dd] > Remove finalName as a parameter > --- > > Key: MEAR-260 > URL: https://issues.apache.org/jira/browse/MEAR-260 > Project: Maven Ear Plugin > Issue Type: Improvement >Affects Versions: 3.0.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Critical > Fix For: 3.0.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MEAR-259) Fix formatting date issues in apt files
[
https://issues.apache.org/jira/browse/MEAR-259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16393395#comment-16393395
]
Hudson commented on MEAR-259:
-
Build succeeded in Jenkins: Maven TLP » maven-ear-plugin » MEAR-259 #2
See https://builds.apache.org/job/maven-box/job/maven-ear-plugin/job/MEAR-259/2/
> Fix formatting date issues in apt files
> ---
>
> Key: MEAR-259
> URL: https://issues.apache.org/jira/browse/MEAR-259
> Project: Maven Ear Plugin
> Issue Type: Task
>Affects Versions: 3.0.0
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Trivial
> Fix For: 3.0.0
>
>
> During the site generation the APT parser shows wrong formats for dates in
> APT file. This should be fixed.
> {code}
> [INFO] Rendering 25 Doxia documents: 23 apt, 1 fml, 1 xdoc
> [WARNING] Could not parse date 'November 19, 2006' from
> examples/customize-file-name-mapping.apt.vm (expected -MM-dd format),
> ignoring!
> [WARNING] Could not parse date 'September 23, 2005' from
> examples/customizing-a-module-filename.apt.vm (expected -MM-dd format),
> ignoring!
> [WARNING] Could not parse date 'September 23, 2005' from
> examples/customizing-context-root.apt.vm (expected -MM-dd format),
> ignoring!
> [WARNING] Could not parse date 'September 23, 2005' from
> examples/customizing-module-uri.apt.vm (expected -MM-dd format), ignoring!
> [WARNING] Could not parse date 'November 19, 2013' from
> examples/eclipse-and-maven-integration.apt.vm (expected -MM-dd format),
> ignoring!
> [WARNING] Could not parse date 'September 23, 2005' from
> examples/excluding-a-module.apt.vm (expected -MM-dd format), ignoring!
> [WARNING] Could not parse date 'January 3, 2009' from
> examples/filtering-advanced.apt.vm (expected -MM-dd format), ignoring!
> [WARNING] Could not parse date 'January 3, 2009' from
> examples/filtering-sources.apt.vm (expected -MM-dd format), ignoring!
> [WARNING] Could not parse date 'August 06, 2006' from
> examples/generating-jboss-app.apt.vm (expected -MM-dd format), ignoring!
> [WARNING] Could not parse date 'September 4, 2010' from
> examples/generating-modules-id.apt.vm (expected -MM-dd format), ignoring!
> [WARNING] Could not parse date 'September 23, 2005' from
> examples/including-a-third-party-library-in-application-xml.apt.vm (expected
> -MM-dd format), ignoring!
> [WARNING] Could not parse date 'August 27, 2017' from
> examples/specifying-env-entries-for-the-generated-application-xml.apt.vm
> (expected -MM-dd format), ignoring!
> [WARNING] Could not parse date 'August 27, 2017' from
> examples/specifying-resource-ref-entries-for-the-generated-application-xml.apt.vm
> (expected -MM-dd format), ignoring!
> [WARNING] Could not parse date 'September 23, 2005' from
> examples/specifying-security-roles-for-the-generated-application-xml.apt.vm
> (expected -MM-dd format), ignoring!
> [WARNING] Could not parse date 'Augustus 14, 2006' from
> examples/unpacking-a-module.apt.vm (expected -MM-dd format), ignoring!
> [WARNING] Could not parse date 'April 3, 2011' from
> examples/using-app-client.apt.vm (expected -MM-dd format), ignoring!
> [WARNING] Could not parse date '31 July 2006' from modules.apt.vm (expected
> -MM-dd format), ignoring!
> [WARNING] Could not parse date '29 October 2006' from tests.apt (expected
> -MM-dd format), ignoring!
> [INFO] Generating "Summary" report ---
> maven-project-info-reports-plugin:2.9:summary{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MEAR-260) Remove finalName as a parameter
[ https://issues.apache.org/jira/browse/MEAR-260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16393394#comment-16393394 ] Hudson commented on MEAR-260: - Build succeeded in Jenkins: Maven TLP » maven-ear-plugin » master #17 See https://builds.apache.org/job/maven-box/job/maven-ear-plugin/job/master/17/ > Remove finalName as a parameter > --- > > Key: MEAR-260 > URL: https://issues.apache.org/jira/browse/MEAR-260 > Project: Maven Ear Plugin > Issue Type: Improvement >Affects Versions: 3.0.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Critical > Fix For: 3.0.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (SUREFIRE-1422) Forking fails on Linux if /bin/ps isn't available
[
https://issues.apache.org/jira/browse/SUREFIRE-1422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16393068#comment-16393068
]
Tibor Digana commented on SUREFIRE-1422:
Thx [~carlos]. Anyway I am still wondering why the old mechanism (which does
not use native calls) did not work.
[~raehalme]
[~apottere]
[~ebourg]
How long did the test-set run? Was it less than 30 seconds?
> Forking fails on Linux if /bin/ps isn't available
> -
>
> Key: SUREFIRE-1422
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1422
> Project: Maven Surefire
> Issue Type: Bug
> Components: process forking
>Affects Versions: 2.20.1
> Environment: Linux (Debian 9 with OpenJDK 8)
>Reporter: Emmanuel Bourg
>Assignee: Tibor Digana
>Priority: Major
> Fix For: 2.21.0
>
>
> Hi,
> With the changes introduced by SUREFIRE-1302 I'm now experiencing a failure
> on Linux when the fork mode is enabled:
> {code}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-surefire-plugin:2.20.1:test (default-test) on
> project foo: There are test failures.
> [ERROR]
> [ERROR] Please refer to /foo/target/surefire-reports for the individual test
> results.
> [ERROR] Please refer to dump files (if any exist) [date]-jvmRun[N].dump,
> [date].dumpstream and [date]-jvmRun[N].dumpstream.
> [ERROR] The forked VM terminated without properly saying goodbye. VM crash or
> System.exit called?
> {code}
> I traced the issue back to the PpidChecker class, the code assumes that
> {{/bin/ps}} or {{/usr/bin/ps}} exist but this isn't guaranteed (especially on
> trimmed down containers commonly used for continuous integration).
> It would be nice to have a fallback mechanism when ps isn't available, or at
> least check its existence and display an explicit message stating that it
> must be installed.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (MNG-6373) Despite inherited=false, plugin version and dependencies are inherited
Marcin Zarębski created MNG-6373:
Summary: Despite inherited=false, plugin version and dependencies
are inherited
Key: MNG-6373
URL: https://issues.apache.org/jira/browse/MNG-6373
Project: Maven
Issue Type: Bug
Components: Inheritance and Interpolation, Plugins and Lifecycle
Affects Versions: 3.5.3, 3.5.0, 3.2.1, 3.1.0
Reporter: Marcin Zarębski
There seems to be an issue with skipping plugin inheritance. If the
documentation is right, build plugin with property
{{false}} should not be inherited in child projects.
This is inconsistent with observed behavior. Having POM inheritance chain of 3
projects (let's name them uber-parent, parent and child) and build plugin
definition in uber-parent marked with {{inherited=false}}, the plugin's version
and dependencies are still inherited in child projects.
The behavior was reproduced on versions 3.1.0, 3.2.1, 3.5.0, 3.5.3.
h3. Steps to reproduce
This is an example of the weird behavior. Problem can be seen in effective POM
for either parent or child project.
Here are three POM definitions inheriting each other:
h4. Uber-parent pom.xml
{code}
4.0.0
com.example
uber-parent
1.0-SNAPSHOT
pom
org.codehaus.gmavenplus
gmavenplus-plugin
1.1
execute
test
file:///${project.basedir}/src/main/groovyScripts/generateBomPropertiesFile.groovy
org.codehaus.groovy
groovy-all
2.3.0
false
{code}
h4. Parent pom.xml
{code}
4.0.0
com.example
uber-parent
1.0-SNAPSHOT
parent
pom
org.codehaus.gmavenplus
gmavenplus-plugin
1.6
compileTests
org.codehaus.groovy
groovy-all
2.4.14
org.codehaus.gmavenplus
gmavenplus-plugin
{code}
h4. Child pom.xml
{code}
4.0.0
com.example
parent
1.0-SNAPSHOT
child
jar
org.codehaus.gmavenplus
gmavenplus-plugin
{code}
h4. Excerpt from effective POM for either parent or child project
{code}
org.codehaus.gmavenplus
gmavenplus-plugin
1.6
compileTests
org.codehaus.groovy
groovy-all
2.4.14
org.codehaus.gmavenplus
gmavenplus-plugin
1.1
compileTests
org.codehaus.groovy
groovy-all
2.3.0
compile
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (SUREFIRE-1422) Forking fails on Linux if /bin/ps isn't available
[
https://issues.apache.org/jira/browse/SUREFIRE-1422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16392903#comment-16392903
]
Carlos Sanchez commented on SUREFIRE-1422:
--
Fixed in docker images for 3.5.3
https://github.com/carlossg/docker-maven/pull/71
> Forking fails on Linux if /bin/ps isn't available
> -
>
> Key: SUREFIRE-1422
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1422
> Project: Maven Surefire
> Issue Type: Bug
> Components: process forking
>Affects Versions: 2.20.1
> Environment: Linux (Debian 9 with OpenJDK 8)
>Reporter: Emmanuel Bourg
>Assignee: Tibor Digana
>Priority: Major
> Fix For: 2.21.0
>
>
> Hi,
> With the changes introduced by SUREFIRE-1302 I'm now experiencing a failure
> on Linux when the fork mode is enabled:
> {code}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-surefire-plugin:2.20.1:test (default-test) on
> project foo: There are test failures.
> [ERROR]
> [ERROR] Please refer to /foo/target/surefire-reports for the individual test
> results.
> [ERROR] Please refer to dump files (if any exist) [date]-jvmRun[N].dump,
> [date].dumpstream and [date]-jvmRun[N].dumpstream.
> [ERROR] The forked VM terminated without properly saying goodbye. VM crash or
> System.exit called?
> {code}
> I traced the issue back to the PpidChecker class, the code assumes that
> {{/bin/ps}} or {{/usr/bin/ps}} exist but this isn't guaranteed (especially on
> trimmed down containers commonly used for continuous integration).
> It would be nice to have a fallback mechanism when ps isn't available, or at
> least check its existence and display an explicit message stating that it
> must be installed.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MENFORCER-142) Specify enforcer rule in command line without updateing any pom
[ https://issues.apache.org/jira/browse/MENFORCER-142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16392836#comment-16392836 ] ASF GitHub Bot commented on MENFORCER-142: -- Chuckame commented on issue #31: MENFORCER-142 Initial poc implementation of adding rules from cmdline (WIP) URL: https://github.com/apache/maven-enforcer/pull/31#issuecomment-371795845 +1 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 > Specify enforcer rule in command line without updateing any pom > --- > > Key: MENFORCER-142 > URL: https://issues.apache.org/jira/browse/MENFORCER-142 > Project: Maven Enforcer Plugin > Issue Type: Improvement > Components: Plugin >Reporter: Arnaud Bourrée >Priority: Major > Fix For: more-investigation > > > Hello, > How could we specify enforcer:enforce rules from command line? > I want to run command line like following without updating any pom.xml: > mvn enforcer:enforce -Drules=com.acme.UseAcmeParentPom > The goal of this enforcer:enforce rule is to check that Acme's > developers write pom.xml which inherit from acme's parent pom.xml > And because they may not inherit from acme's parent pom.xml, I cannot > specify enforcer rule in. > Regards, > Arnaud. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] Chuckame commented on issue #31: MENFORCER-142 Initial poc implementation of adding rules from cmdline (WIP)
Chuckame commented on issue #31: MENFORCER-142 Initial poc implementation of adding rules from cmdline (WIP) URL: https://github.com/apache/maven-enforcer/pull/31#issuecomment-371795845 +1 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] (MENFORCER-142) Specify enforcer rule in command line without updateing any pom
[ https://issues.apache.org/jira/browse/MENFORCER-142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16392835#comment-16392835 ] ASF GitHub Bot commented on MENFORCER-142: -- Chuckame commented on issue #31: MENFORCER-142 Initial poc implementation of adding rules from cmdline (WIP) URL: https://github.com/apache/maven-enforcer/pull/31#issuecomment-371803425 Hi ! On CI, I want to check if my project version is snapshot on develop and feature branches, and NOT snapshot on master and tags. So it is really useful with `requireSnapshotVersion` and `requireReleaseVersion` rules. 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 > Specify enforcer rule in command line without updateing any pom > --- > > Key: MENFORCER-142 > URL: https://issues.apache.org/jira/browse/MENFORCER-142 > Project: Maven Enforcer Plugin > Issue Type: Improvement > Components: Plugin >Reporter: Arnaud Bourrée >Priority: Major > Fix For: more-investigation > > > Hello, > How could we specify enforcer:enforce rules from command line? > I want to run command line like following without updating any pom.xml: > mvn enforcer:enforce -Drules=com.acme.UseAcmeParentPom > The goal of this enforcer:enforce rule is to check that Acme's > developers write pom.xml which inherit from acme's parent pom.xml > And because they may not inherit from acme's parent pom.xml, I cannot > specify enforcer rule in. > Regards, > Arnaud. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] Chuckame commented on issue #31: MENFORCER-142 Initial poc implementation of adding rules from cmdline (WIP)
Chuckame commented on issue #31: MENFORCER-142 Initial poc implementation of adding rules from cmdline (WIP) URL: https://github.com/apache/maven-enforcer/pull/31#issuecomment-371803425 Hi ! On CI, I want to check if my project version is snapshot on develop and feature branches, and NOT snapshot on master and tags. So it is really useful with `requireSnapshotVersion` and `requireReleaseVersion` rules. 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] (MENFORCER-142) Specify enforcer rule in command line without updateing any pom
[ https://issues.apache.org/jira/browse/MENFORCER-142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16392773#comment-16392773 ] ASF GitHub Bot commented on MENFORCER-142: -- Chuckame commented on issue #31: MENFORCER-142 Initial poc implementation of adding rules from cmdline (WIP) URL: https://github.com/apache/maven-enforcer/pull/31#issuecomment-371795845 +1 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 > Specify enforcer rule in command line without updateing any pom > --- > > Key: MENFORCER-142 > URL: https://issues.apache.org/jira/browse/MENFORCER-142 > Project: Maven Enforcer Plugin > Issue Type: Improvement > Components: Plugin >Reporter: Arnaud Bourrée >Priority: Major > Fix For: more-investigation > > > Hello, > How could we specify enforcer:enforce rules from command line? > I want to run command line like following without updating any pom.xml: > mvn enforcer:enforce -Drules=com.acme.UseAcmeParentPom > The goal of this enforcer:enforce rule is to check that Acme's > developers write pom.xml which inherit from acme's parent pom.xml > And because they may not inherit from acme's parent pom.xml, I cannot > specify enforcer rule in. > Regards, > Arnaud. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] Chuckame commented on issue #31: MENFORCER-142 Initial poc implementation of adding rules from cmdline (WIP)
Chuckame commented on issue #31: MENFORCER-142 Initial poc implementation of adding rules from cmdline (WIP) URL: https://github.com/apache/maven-enforcer/pull/31#issuecomment-371795845 +1 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] (MEAR-240) Upgrade of maven-archiver to 3.1.1.
[ https://issues.apache.org/jira/browse/MEAR-240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise updated MEAR-240: - Issue Type: Dependency upgrade (was: Task) > Upgrade of maven-archiver to 3.1.1. > --- > > Key: MEAR-240 > URL: https://issues.apache.org/jira/browse/MEAR-240 > Project: Maven Ear Plugin > Issue Type: Dependency upgrade >Reporter: Christian Schulte >Assignee: Christian Schulte >Priority: Trivial > Fix For: 3.0.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (MEAR-236) Upgrade maven-filtering to 3.1.1
[ https://issues.apache.org/jira/browse/MEAR-236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise updated MEAR-236: - Issue Type: Dependency upgrade (was: Improvement) > Upgrade maven-filtering to 3.1.1 > > > Key: MEAR-236 > URL: https://issues.apache.org/jira/browse/MEAR-236 > Project: Maven Ear Plugin > Issue Type: Dependency upgrade >Affects Versions: 3.0.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.0.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (MEAR-237) Upgrade plexus-archiver to 3.3
[ https://issues.apache.org/jira/browse/MEAR-237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise updated MEAR-237: - Issue Type: Dependency upgrade (was: Improvement) > Upgrade plexus-archiver to 3.3 > -- > > Key: MEAR-237 > URL: https://issues.apache.org/jira/browse/MEAR-237 > Project: Maven Ear Plugin > Issue Type: Dependency upgrade >Affects Versions: 3.0.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.0.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (MEAR-224) Upgrade plexus-archiver from 2.10.3 to 3.0.1
[ https://issues.apache.org/jira/browse/MEAR-224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise updated MEAR-224: - Issue Type: Dependency upgrade (was: Improvement) > Upgrade plexus-archiver from 2.10.3 to 3.0.1 > > > Key: MEAR-224 > URL: https://issues.apache.org/jira/browse/MEAR-224 > Project: Maven Ear Plugin > Issue Type: Dependency upgrade >Affects Versions: 3.0.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Major > Fix For: 3.0.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (MEAR-238) Upgrade of plexus-archiver to 3.4.
[ https://issues.apache.org/jira/browse/MEAR-238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise updated MEAR-238: - Issue Type: Dependency upgrade (was: Task) > Upgrade of plexus-archiver to 3.4. > -- > > Key: MEAR-238 > URL: https://issues.apache.org/jira/browse/MEAR-238 > Project: Maven Ear Plugin > Issue Type: Dependency upgrade >Reporter: Christian Schulte >Assignee: Christian Schulte >Priority: Trivial > Fix For: 3.0.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (MEAR-233) Upgrade plexus-archiver from 3.0.3 to 3.1.1
[ https://issues.apache.org/jira/browse/MEAR-233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise updated MEAR-233: - Issue Type: Dependency upgrade (was: Improvement) > Upgrade plexus-archiver from 3.0.3 to 3.1.1 > --- > > Key: MEAR-233 > URL: https://issues.apache.org/jira/browse/MEAR-233 > Project: Maven Ear Plugin > Issue Type: Dependency upgrade >Affects Versions: 3.0.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.0.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (MEAR-235) Upgrade maven-archiver to 3.1.0
[ https://issues.apache.org/jira/browse/MEAR-235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise updated MEAR-235: - Issue Type: Dependency upgrade (was: Improvement) > Upgrade maven-archiver to 3.1.0 > --- > > Key: MEAR-235 > URL: https://issues.apache.org/jira/browse/MEAR-235 > Project: Maven Ear Plugin > Issue Type: Dependency upgrade >Affects Versions: 3.0.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.0.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (MEAR-245) Upgrade of plexus-interpolation to 1.24.
[ https://issues.apache.org/jira/browse/MEAR-245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise updated MEAR-245: - Issue Type: Dependency upgrade (was: Task) > Upgrade of plexus-interpolation to 1.24. > > > Key: MEAR-245 > URL: https://issues.apache.org/jira/browse/MEAR-245 > Project: Maven Ear Plugin > Issue Type: Dependency upgrade >Reporter: Christian Schulte >Assignee: Christian Schulte >Priority: Trivial > Fix For: 3.0.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (MEAR-252) Upgrade plexus-archiver to 3.5.
[ https://issues.apache.org/jira/browse/MEAR-252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise updated MEAR-252: - Issue Type: Dependency upgrade (was: Task) > Upgrade plexus-archiver to 3.5. > --- > > Key: MEAR-252 > URL: https://issues.apache.org/jira/browse/MEAR-252 > Project: Maven Ear Plugin > Issue Type: Dependency upgrade >Affects Versions: 3.0.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.0.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (MEAR-251) Upgrade maven-archiver to 3.2.0
[ https://issues.apache.org/jira/browse/MEAR-251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise updated MEAR-251: - Issue Type: Dependency upgrade (was: Task) > Upgrade maven-archiver to 3.2.0 > --- > > Key: MEAR-251 > URL: https://issues.apache.org/jira/browse/MEAR-251 > Project: Maven Ear Plugin > Issue Type: Dependency upgrade >Affects Versions: 3.0.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.0.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
