[GitHub] [maven-scm] cquoss edited a comment on pull request #119: SCM-948 - Make limit parameter work for svnexe and gitexe changelog goal

cquoss edited a comment on pull request #119: URL: https://github.com/apache/maven-scm/pull/119#issuecomment-886156115 Happily. The old PR was better documented but got erased after resetting hard to upstream master and force pushing. At our company we use a customized version of maven-r

[GitHub] [maven-scm] cquoss edited a comment on pull request #119: SCM-948 - Make limit parameter work for svnexe and gitexe changelog goal

cquoss edited a comment on pull request #119: URL: https://github.com/apache/maven-scm/pull/119#issuecomment-886156115 Happily. The old PR was better documented but got erased after resetting hard to upstream master and force pushing. At our company we use a customized version of maven-r

[GitHub] [maven-scm] cquoss commented on pull request #119: SCM-948 - Make limit parameter work for svnexe and gitexe changelog goal

cquoss commented on pull request #119: URL: https://github.com/apache/maven-scm/pull/119#issuecomment-886156115 Happily. The old PR was better documented but got erased after resetting hard to upstream master and force pushing. At our company we use a customized version of maven-release

[GitHub] [maven-scm] eolivelli commented on pull request #119: SCM-948 - Make limit parameter work for svnexe and gitexe changelog goal

eolivelli commented on pull request #119: URL: https://github.com/apache/maven-scm/pull/119#issuecomment-886149569 Can you please explain more your patch? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above

[jira] [Commented] (MCOMPILER-461) Compile fails when class references a class generated by an annotation processor and module-info.java is present

[ https://issues.apache.org/jira/browse/MCOMPILER-461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17386788#comment-17386788 ] Matt Sicker commented on MCOMPILER-461: --- Double-problem caused the lack of error

[jira] [Commented] (MNG-7194) PluginParameterExpressionEvaluator incorrectly interpolates unknown subexpression

[ https://issues.apache.org/jira/browse/MNG-7194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17386769#comment-17386769 ] Michael Osipov commented on MNG-7194: - It should be just pre? > PluginParameterExpress

[jira] [Commented] (SCM-849) SCM:EXPORT Goal for Synergy SCM does not work (or even is not implemented)

[ https://issues.apache.org/jira/browse/SCM-849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17386767#comment-17386767 ] Michael Osipov commented on SCM-849: What do you expect? No one has access to this SCM,

[jira] [Commented] (MCOMPILER-461) Compile fails when class references a class generated by an annotation processor and module-info.java is present

[ https://issues.apache.org/jira/browse/MCOMPILER-461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17386760#comment-17386760 ] Matt Sicker commented on MCOMPILER-461: --- Oh that above useless error appears to

[jira] [Commented] (SCM-849) SCM:EXPORT Goal for Synergy SCM does not work (or even is not implemented)

[ https://issues.apache.org/jira/browse/SCM-849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17386759#comment-17386759 ] Raphaël MARTIN commented on SCM-849: In fact I do not remember when exactly I post this

[jira] [Commented] (SCM-849) SCM:EXPORT Goal for Synergy SCM does not work (or even is not implemented)

[ https://issues.apache.org/jira/browse/SCM-849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17386757#comment-17386757 ] Michael Osipov commented on SCM-849: I don't who added this module, but as [~cquoss] sai

[jira] [Closed] (MENFORCER-191) bannedDependencies should work with regex pattern as banTransitiveDependencies does

[ https://issues.apache.org/jira/browse/MENFORCER-191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte closed MENFORCER-191. Assignee: Robert Scholte Resolution: Cannot Reproduce Based on documentation and u

[GitHub] [maven-invoker-plugin] slachiewicz merged pull request #53: Fix jenkins address in anchors

slachiewicz merged pull request #53: URL: https://github.com/apache/maven-invoker-plugin/pull/53 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: i

[jira] [Commented] (MENFORCER-316) requireUpperBoundDeps sometimes still ineffective when dependencyManagement is used

[ https://issues.apache.org/jira/browse/MENFORCER-316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17386742#comment-17386742 ] Robert Scholte commented on MENFORCER-316: -- If you can reproduce it with the

[jira] [Commented] (MENFORCER-363) Unexpected result from requireProperty with regex when the property is not fully resolved

[ https://issues.apache.org/jira/browse/MENFORCER-363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17386739#comment-17386739 ] Robert Scholte commented on MENFORCER-363: -- This bug is caused by MNG-7194. 

[jira] [Created] (MNG-7194) PluginParameterExpressionEvaluator incorrectly interpolates unknown subexpression

Robert Scholte created MNG-7194: --- Summary: PluginParameterExpressionEvaluator incorrectly interpolates unknown subexpression Key: MNG-7194 URL: https://issues.apache.org/jira/browse/MNG-7194 Project: Ma

[jira] [Commented] (MENFORCER-316) requireUpperBoundDeps sometimes still ineffective when dependencyManagement is used

[ https://issues.apache.org/jira/browse/MENFORCER-316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17386736#comment-17386736 ] Chris Povirk commented on MENFORCER-316: Thanks. Should I open a bug about {{d

[jira] [Closed] (MENFORCER-316) requireUpperBoundDeps sometimes still ineffective when dependencyManagement is used

[ https://issues.apache.org/jira/browse/MENFORCER-316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte closed MENFORCER-316. Assignee: Robert Scholte Resolution: Not A Bug If you specify a version in depende

[jira] [Commented] (MENFORCER-241) DependencyConverge - allow ignoring minor and patch level mismatches

[ https://issues.apache.org/jira/browse/MENFORCER-241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17386731#comment-17386731 ] Robert Scholte commented on MENFORCER-241: -- This was actually duplicated by M

[jira] [Issue Comment Deleted] (MENFORCER-241) DependencyConverge - allow ignoring minor and patch level mismatches

[ https://issues.apache.org/jira/browse/MENFORCER-241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte updated MENFORCER-241: - Comment: was deleted (was: GitHub user sfussenegger opened a pull request: https:

[jira] [Closed] (MENFORCER-360) requireUpperBoundDeps should have option to check for same major version

[ https://issues.apache.org/jira/browse/MENFORCER-360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte closed MENFORCER-360. Assignee: Robert Scholte Resolution: Duplicate This is actually a duplicate MENFOR

[jira] [Issue Comment Deleted] (MENFORCER-241) DependencyConverge - allow ignoring minor and patch level mismatches

[ https://issues.apache.org/jira/browse/MENFORCER-241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte updated MENFORCER-241: - Comment: was deleted (was: asfgit closed pull request #16: MENFORCER-241 allow ignorin

[jira] [Commented] (MENFORCER-211) wildcard ignore in requireReleaseDeps

[ https://issues.apache.org/jira/browse/MENFORCER-211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17386713#comment-17386713 ] Hudson commented on MENFORCER-211: -- Build failed in Jenkins: Maven » Maven TLP » mave

[jira] [Updated] (MENFORCER-307) Removed deprecated marked unCheckedPlugins in favour of unCheckedPluginList

[ https://issues.apache.org/jira/browse/MENFORCER-307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte updated MENFORCER-307: - Fix Version/s: (was: 3.0.0) > Removed deprecated marked unCheckedPlugins in favour

[jira] [Closed] (MENFORCER-211) wildcard ignore in requireReleaseDeps

[ https://issues.apache.org/jira/browse/MENFORCER-211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte closed MENFORCER-211. Fix Version/s: (was: waiting-for-feedback) 3.0.0 Assignee

[GitHub] [maven-invoker-plugin] slawekjaranowski opened a new pull request #53: Fix jenkins address in anchors

slawekjaranowski opened a new pull request #53: URL: https://github.com/apache/maven-invoker-plugin/pull/53 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe

[GitHub] [maven-invoker-plugin] slachiewicz merged pull request #52: Fix jenkins address in badges

slachiewicz merged pull request #52: URL: https://github.com/apache/maven-invoker-plugin/pull/52 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: i

[GitHub] [maven-invoker-plugin] slawekjaranowski opened a new pull request #52: Fix jenkins address in badges

slawekjaranowski opened a new pull request #52: URL: https://github.com/apache/maven-invoker-plugin/pull/52 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe

[jira] [Commented] (MJAVADOC-684) maven-javadoc and reproducible builds

[ https://issues.apache.org/jira/browse/MJAVADOC-684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17386703#comment-17386703 ] Hudson commented on MJAVADOC-684: - Build failed in Jenkins: Maven » Maven TLP » maven-j

[jira] [Commented] (MCOMPILER-380) docs claim copyright for future years

[ https://issues.apache.org/jira/browse/MCOMPILER-380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17386700#comment-17386700 ] Bernhard M. Wiedemann commented on MCOMPILER-380: - > one question: whe

[jira] [Closed] (MJAVADOC-684) maven-javadoc and reproducible builds

[ https://issues.apache.org/jira/browse/MJAVADOC-684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy closed MJAVADOC-684. -- Fix Version/s: 3.3.1 Assignee: Herve Boutemy Resolution: Fixed fixed in http

[jira] [Commented] (SCM-849) SCM:EXPORT Goal for Synergy SCM does not work (or even is not implemented)

[ https://issues.apache.org/jira/browse/SCM-849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17386692#comment-17386692 ] Clemens Quoß commented on SCM-849: -- Raphael, your disappointment about how this has been ha

[jira] [Reopened] (MCOMPILER-380) docs claim copyright for future years

[ https://issues.apache.org/jira/browse/MCOMPILER-380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy reopened MCOMPILER-380: - > docs claim copyright for future years > - > >

[jira] [Commented] (MCOMPILER-380) docs claim copyright for future years

[ https://issues.apache.org/jira/browse/MCOMPILER-380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17386691#comment-17386691 ] Herve Boutemy commented on MCOMPILER-380: - one question: when rebuilding packa

[jira] [Closed] (MCOMPILER-380) docs claim copyright for future years

[ https://issues.apache.org/jira/browse/MCOMPILER-380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy closed MCOMPILER-380. --- Fix Version/s: (was: waiting-for-feedback) Resolution: Duplicate > docs claim c

[jira] [Commented] (MJAVADOC-684) maven-javadoc and reproducible builds

[ https://issues.apache.org/jira/browse/MJAVADOC-684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17386689#comment-17386689 ] Herve Boutemy commented on MJAVADOC-684: MJAVADOC-619 tried to reimplement outp

[jira] [Updated] (MJAVADOC-684) maven-javadoc and reproducible builds

[ https://issues.apache.org/jira/browse/MJAVADOC-684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy updated MJAVADOC-684: --- Description: I'm a bit confused with documentation   This [1] guide instruct me to set {cod

[jira] [Commented] (SCM-849) SCM:EXPORT Goal for Synergy SCM does not work (or even is not implemented)

[ https://issues.apache.org/jira/browse/SCM-849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17386687#comment-17386687 ] Raphaël MARTIN commented on SCM-849: As I can see it is completely useless to post issue

[jira] [Commented] (MNG-7131) maven.config doesn't handle arguments with spaces in them

[ https://issues.apache.org/jira/browse/MNG-7131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17386682#comment-17386682 ] Stefan Oehme commented on MNG-7131: --- Lgtm > maven.config doesn't handle arguments wit

[jira] [Commented] (MNG-7010) Omit "NB: JAVA_HOME should point to a JDK not a JRE" except when that is the problem

[ https://issues.apache.org/jira/browse/MNG-7010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17386681#comment-17386681 ] Robert Scholte commented on MNG-7010: - It is not needed anymore to set JAVA_HOME. If it