[jira] [Created] (MDEP-973) Make it possible to not fail on 'unneeded forced usage'

Hans Aikema created MDEP-973: Summary: Make it possible to not fail on 'unneeded forced usage' Key: MDEP-973 URL: https://issues.apache.org/jira/browse/MDEP-973 Project: Maven Dependency Plugin I

[jira] [Commented] (MNG-6883) MavenProject - replacement for deprecated method

[ https://issues.apache.org/jira/browse/MNG-6883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17877135#comment-17877135 ] Hans Aikema commented on MNG-6883: -- Bumping the maven API version from 3.1.0 to 3.6.3 in t

[jira] [Comment Edited] (MRELEASE-1141) maven release plugin overwrites project.build.outputTimestamp value

[ https://issues.apache.org/jira/browse/MRELEASE-1141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17828065#comment-17828065 ] Hans Aikema edited comment on MRELEASE-1141 at 3/18/24 5:54 PM:

[jira] [Commented] (MRELEASE-1141) maven release plugin overwrites project.build.outputTimestamp value

[ https://issues.apache.org/jira/browse/MRELEASE-1141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17828065#comment-17828065 ] Hans Aikema commented on MRELEASE-1141: --- This behavior changed from 2.5.3 to 3.x

[jira] [Commented] (MRELEASE-1141) maven release plugin overwrites project.build.outputTimestamp value

[ https://issues.apache.org/jira/browse/MRELEASE-1141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17828060#comment-17828060 ] Hans Aikema commented on MRELEASE-1141: --- [~michael-o]  I ran into this same issu

[jira] [Commented] (MSOURCES-141) Check duplication of attached jar should be configurable to not fail when using the build cache

[ https://issues.apache.org/jira/browse/MSOURCES-141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17766685#comment-17766685 ] Hans Aikema commented on MSOURCES-141: -- Ran into this issue as well, and in my vie

[jira] [Updated] (MSOURCES-141) Check duplication of attached jar should be configurable to not fail when using the build cache

[ https://issues.apache.org/jira/browse/MSOURCES-141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hans Aikema updated MSOURCES-141: - Attachment: issue-msources-141.zip > Check duplication of attached jar should be configurable t

[jira] [Commented] (MNG-7679) [REGRESSION] Build fails when executing a single mojo without a POM

[ https://issues.apache.org/jira/browse/MNG-7679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17686785#comment-17686785 ] Hans Aikema commented on MNG-7679: -- [~gnodet] Makes sense to keep it consistent. > [REGRE

[jira] [Comment Edited] (MNG-7679) [REGRESSION] Build fails when executing a single mojo without a POM

[ https://issues.apache.org/jira/browse/MNG-7679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17686781#comment-17686781 ] Hans Aikema edited comment on MNG-7679 at 2/9/23 9:50 PM: -- In my v

[jira] [Commented] (MNG-7679) [REGRESSION] Build fails when executing a single mojo without a POM

[ https://issues.apache.org/jira/browse/MNG-7679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17686781#comment-17686781 ] Hans Aikema commented on MNG-7679: -- In my view the root cause is in an improper return for

[jira] [Commented] (MSHARED-831) Configuration in reporting section not taken into account when running from cli

[ https://issues.apache.org/jira/browse/MSHARED-831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17543793#comment-17543793 ] Hans Aikema commented on MSHARED-831: - [~hboutemy] {quote}I have a question for [~ai

[jira] [Commented] (MRELEASE-1063) Maven release plugin should retain settings.security environment variable for its forked executions of release:prepare and release:perform

[ https://issues.apache.org/jira/browse/MRELEASE-1063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17533325#comment-17533325 ] Hans Aikema commented on MRELEASE-1063: --- {quote}Why can't you use MAVEN_OPTS to

[jira] [Commented] (MRELEASE-1063) Maven release plugin should retain settings.security environment variable for its forked executions of release:prepare and release:perform

[ https://issues.apache.org/jira/browse/MRELEASE-1063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17533320#comment-17533320 ] Hans Aikema commented on MRELEASE-1063: --- Note: If you think that password encryp

[jira] [Commented] (MRELEASE-1063) Maven release plugin should retain settings.security environment variable for its forked executions of release:prepare and release:perform

[ https://issues.apache.org/jira/browse/MRELEASE-1063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17533319#comment-17533319 ] Hans Aikema commented on MRELEASE-1063: --- [~michael-o] While I agree that the dir

[jira] [Updated] (MSHARED-998) NPE when resolving dependencies with PatternInclusionsFilter that holds a pattern with a classifier

[ https://issues.apache.org/jira/browse/MSHARED-998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hans Aikema updated MSHARED-998: Description: After migrating from ArtifactResolver to DependencyResolver in OWASP DependencyCheck

[jira] [Updated] (MSHARED-998) NPE when resolving dependencies with PatternInclusionsFilter that holds a pattern with a classifier

[ https://issues.apache.org/jira/browse/MSHARED-998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hans Aikema updated MSHARED-998: Issue Type: Bug (was: Improvement) > NPE when resolving dependencies with PatternInclusionsFilter

[jira] [Created] (MSHARED-998) NPE when resolving dependencies with PatternInclusionsFilter that holds a pattern with a classifier

Hans Aikema created MSHARED-998: --- Summary: NPE when resolving dependencies with PatternInclusionsFilter that holds a pattern with a classifier Key: MSHARED-998 URL: https://issues.apache.org/jira/browse/MSHARED-998

[jira] [Commented] (MENFORCER-392) Upgrading to Maven Enforcer 3.0.0 results in java.lang.NoSuchMethodError

[ https://issues.apache.org/jira/browse/MENFORCER-392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17408083#comment-17408083 ] Hans Aikema commented on MENFORCER-392: --- Ran into a similar issue. Is caused by

[jira] [Commented] (MRELEASE-1063) Maven release plugin should retain settings.security environment variable for its forked executions of release:prepare and release:perform

[ https://issues.apache.org/jira/browse/MRELEASE-1063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17324003#comment-17324003 ] Hans Aikema commented on MRELEASE-1063: --- Note that for the release:perform goal

[jira] [Created] (MRELEASE-1063) Maven release plugin should retain settings.security environment variable for its forked executions of release:prepare and release:perform

Hans Aikema created MRELEASE-1063: - Summary: Maven release plugin should retain settings.security environment variable for its forked executions of release:prepare and release:perform Key: MRELEASE-1063 URL: http

[jira] [Commented] (MNG-6540) Configuration in reporting section not taken into account when running from cli

[ https://issues.apache.org/jira/browse/MNG-6540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16725332#comment-16725332 ] Hans Aikema commented on MNG-6540: -- Whereas no dependencies report is created when called

[jira] [Commented] (MNG-6540) Configuration in reporting section not taken into account when running from cli

[ https://issues.apache.org/jira/browse/MNG-6540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16725329#comment-16725329 ] Hans Aikema commented on MNG-6540: -- The following POM will still generate a dependencies r

[jira] [Created] (MNG-6540) Configuration in reporting section not taken into account when running from cli

Hans Aikema created MNG-6540: Summary: Configuration in reporting section not taken into account when running from cli Key: MNG-6540 URL: https://issues.apache.org/jira/browse/MNG-6540 Project: Maven

[jira] (MNG-4226) Better detection of JAVA_HOME on Apple Mac OS X

[ https://jira.codehaus.org/browse/MNG-4226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=350383#comment-350383 ] Hans Aikema commented on MNG-4226: -- abu:classes aikebah$ whereis java /usr/bin/java And as mention

[jira] (MNG-4226) Better detection of JAVA_HOME on Apple Mac OS X

[ https://jira.codehaus.org/browse/MNG-4226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=350381#comment-350381 ] Hans Aikema commented on MNG-4226: -- Forgot to include the results of java_home: abu:bin aikebah$ /u

[jira] (MNG-4226) Better detection of JAVA_HOME on Apple Mac OS X

[ https://jira.codehaus.org/browse/MNG-4226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=350380#comment-350380 ] Hans Aikema commented on MNG-4226: -- This is not fixed, or broken again. On my MacPro running Maveric

[jira] (MRELEASE-594) release:prepare should stop when there is snapshots in dependencies management

[ https://jira.codehaus.org/browse/MRELEASE-594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=332916#comment-332916 ] Hans Aikema edited comment on MRELEASE-594 at 9/17/13 9:23 AM: --- I a

[jira] (MRELEASE-594) release:prepare should stop when there is snapshots in dependencies management

[ https://jira.codehaus.org/browse/MRELEASE-594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=332916#comment-332916 ] Hans Aikema commented on MRELEASE-594: -- I agree with previous commenters that DISallowing sn