[jira] [Commented] (SCM-777) scm:validate ignores scmCheckWorkingDirectoryUrl configuration in favor of system property

2019-01-02 Thread JIRA
[ https://issues.apache.org/jira/browse/SCM-777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16732733#comment-16732733 ] Hervé Boutemy commented on SCM-777: --- [~michael-o] I don't remember anything on that easily: do you need me

[GitHub] rpopov commented on a change in pull request #1: Allow scripting in files

2019-01-02 Thread GitBox
rpopov commented on a change in pull request #1: Allow scripting in files URL: https://github.com/apache/maven-scripting-plugin/pull/1#discussion_r244915726 ## File path: pom.xml ## @@ -92,13 +93,6 @@ under the License. provided - - Review

[GitHub] rpopov commented on a change in pull request #1: Allow scripting in files

2019-01-02 Thread GitBox
rpopov commented on a change in pull request #1: Allow scripting in files URL: https://github.com/apache/maven-scripting-plugin/pull/1#discussion_r244914478 ## File path: pom.xml ## @@ -92,13 +93,6 @@ under the License. provided - - Review

[jira] [Updated] (MJAVADOC-561) Not possible to link to JDK classes since Java 11

2019-01-02 Thread Gili (JIRA)
[ https://issues.apache.org/jira/browse/MJAVADOC-561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gili updated MJAVADOC-561: -- Priority: Critical (was: Major) Increased priority due to the fact that there are no known workarounds and

[jira] [Updated] (MJAVADOC-561) Not possible to link to JDK classes since Java 11

2019-01-02 Thread Gili (JIRA)
[ https://issues.apache.org/jira/browse/MJAVADOC-561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gili updated MJAVADOC-561: -- Description: 1. Open testcase 2. {{mvn javadoc:jar}} 3. Notice that generated Javadoc contains broken link

[jira] [Updated] (MJAVADOC-561) Not possible to link to JDK classes since Java 11

2019-01-02 Thread Gili (JIRA)
[ https://issues.apache.org/jira/browse/MJAVADOC-561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gili updated MJAVADOC-561: -- Description: 1. Open testcase 2. {{mvn javadoc:jar}} 3. Notice that generated Javadoc contains broken link

[jira] [Created] (MJAVADOC-561) Not possible to link to JDK classes since Java 9

2019-01-02 Thread Gili (JIRA)
Gili created MJAVADOC-561: - Summary: Not possible to link to JDK classes since Java 9 Key: MJAVADOC-561 URL: https://issues.apache.org/jira/browse/MJAVADOC-561 Project: Maven Javadoc Plugin Issue

[GitHub] dedabob commented on issue #4: [MJAVADOC-527] - detectLinks may pass invalid urls to javadoc

2019-01-02 Thread GitBox
dedabob commented on issue #4: [MJAVADOC-527] - detectLinks may pass invalid urls to javadoc URL: https://github.com/apache/maven-javadoc-plugin/pull/4#issuecomment-451033153 Changes rebased and squashed but a merge was required anyway. I hope it's fine, otherwise i could provide a patch

[jira] [Commented] (MJAVADOC-555) Javadoc:aggregate fails if one of the modules does not contain module-info.java

2019-01-02 Thread Gili (JIRA)
[ https://issues.apache.org/jira/browse/MJAVADOC-555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16732526#comment-16732526 ] Gili commented on MJAVADOC-555: --- Regarding #4, how would that work exactly? If you look at the testcase,

[jira] [Commented] (MJAVADOC-560) Clarify outputDirectory, reportOutputDirectory in javadoc:javadoc documentation

2019-01-02 Thread Gili (JIRA)
[ https://issues.apache.org/jira/browse/MJAVADOC-560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16732519#comment-16732519 ] Gili commented on MJAVADOC-560: --- The *javadoc:aggregate* documentation contains the same issues. Maybe

[jira] [Created] (MJAVADOC-560) Clarify outputDirectory, reportOutputDirectory in javadoc:javadoc documentation

2019-01-02 Thread Gili (JIRA)
Gili created MJAVADOC-560: - Summary: Clarify outputDirectory, reportOutputDirectory in javadoc:javadoc documentation Key: MJAVADOC-560 URL: https://issues.apache.org/jira/browse/MJAVADOC-560 Project: Maven

[GitHub] rpopov commented on issue #1: Allow scripting in files

2019-01-02 Thread GitBox
rpopov commented on issue #1: Allow scripting in files URL: https://github.com/apache/maven-scripting-plugin/pull/1#issuecomment-451006710 > Hi @rpopov our JIRA is public, you can freely subscribe. > Please create an issue describing your idea. I registered in JIRA as a regular user

[jira] [Updated] (WAGON-540) Switch to modern-day encoding (UTF-8) of auth credentials

2019-01-02 Thread Michael Osipov (JIRA)
[ https://issues.apache.org/jira/browse/WAGON-540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated WAGON-540: - Fix Version/s: 3.3.1 > Switch to modern-day encoding (UTF-8) of auth credentials >

[jira] [Updated] (WAGON-537) Maven transfer speed of large artifacts is slow due to unsuitable buffer strategy

2019-01-02 Thread Michael Osipov (JIRA)
[ https://issues.apache.org/jira/browse/WAGON-537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated WAGON-537: - Fix Version/s: 3.3.1 > Maven transfer speed of large artifacts is slow due to unsuitable buffer

[jira] [Updated] (WAGON-538) Basic authentication fails if the password contains non-ASCII characters

2019-01-02 Thread Michael Osipov (JIRA)
[ https://issues.apache.org/jira/browse/WAGON-538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated WAGON-538: - Fix Version/s: 3.3.1 > Basic authentication fails if the password contains non-ASCII characters >

[jira] [Updated] (WAGON-539) Explicitly register only supported auth schemes

2019-01-02 Thread Michael Osipov (JIRA)
[ https://issues.apache.org/jira/browse/WAGON-539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated WAGON-539: - Fix Version/s: 3.3.1 > Explicitly register only supported auth schemes >

[jira] [Updated] (WAGON-543) wagon-ssh download hangs

2019-01-02 Thread Michael Osipov (JIRA)
[ https://issues.apache.org/jira/browse/WAGON-543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated WAGON-543: - Fix Version/s: 3.3.1 > wagon-ssh download hangs > > >

[jira] [Created] (WAGON-544) Work around JSch issue #122

2019-01-02 Thread Michael Osipov (JIRA)
Michael Osipov created WAGON-544: Summary: Work around JSch issue #122 Key: WAGON-544 URL: https://issues.apache.org/jira/browse/WAGON-544 Project: Maven Wagon Issue Type: Task

[jira] [Commented] (WAGON-543) wagon-ssh download hangs

2019-01-02 Thread Dan Tran (JIRA)
[ https://issues.apache.org/jira/browse/WAGON-543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16732297#comment-16732297 ] Dan Tran commented on WAGON-543: Let's go with that option > wagon-ssh download hangs >

[jira] [Commented] (WAGON-543) wagon-ssh download hangs

2019-01-02 Thread Michael Osipov (JIRA)
[ https://issues.apache.org/jira/browse/WAGON-543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16732272#comment-16732272 ] Michael Osipov commented on WAGON-543: -- I think the only option is to restore the old transfer method

[jira] [Commented] (WAGON-543) wagon-ssh download hangs

2019-01-02 Thread Michael Osipov (JIRA)
[ https://issues.apache.org/jira/browse/WAGON-543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16732239#comment-16732239 ] Michael Osipov commented on WAGON-543: -- Running Wagon master against {{scpexe}} works flawlessly. So

[jira] [Commented] (WAGON-543) wagon-ssh download hangs

2019-01-02 Thread Michael Osipov (JIRA)
[ https://issues.apache.org/jira/browse/WAGON-543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16732235#comment-16732235 ] Michael Osipov commented on WAGON-543: -- I have modified the wagon-maven-plugin to use {{scpexe}}

[jira] [Commented] (WAGON-543) wagon-ssh download hangs

2019-01-02 Thread Michael Osipov (JIRA)
[ https://issues.apache.org/jira/browse/WAGON-543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1673#comment-1673 ] Michael Osipov commented on WAGON-543: -- [~dantran], I have uploaded branch {{no-channels}} in Wagon

[jira] [Updated] (WAGON-543) wagon-ssh download hangs

2019-01-02 Thread Michael Osipov (JIRA)
[ https://issues.apache.org/jira/browse/WAGON-543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated WAGON-543: - Attachment: debugger screenshot.png > wagon-ssh download hangs > > >

[GitHub] mickaelistria commented on issue #197: [MNG-6533] Test: ProjectBuildingException miss reference to MavenProject

2019-01-02 Thread GitBox
mickaelistria commented on issue #197: [MNG-6533] Test: ProjectBuildingException miss reference to MavenProject URL: https://github.com/apache/maven/pull/197#issuecomment-450911058 > I reworked the PR, creating 2 initial little refactoring commits that make the later modification a lot

[jira] [Comment Edited] (WAGON-543) wagon-ssh download hangs

2019-01-02 Thread Michael Osipov (JIRA)
[ https://issues.apache.org/jira/browse/WAGON-543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16732174#comment-16732174 ] Michael Osipov edited comment on WAGON-543 at 1/2/19 4:25 PM: -- [~dantran], I

[jira] [Commented] (WAGON-543) wagon-ssh download hangs

2019-01-02 Thread Michael Osipov (JIRA)
[ https://issues.apache.org/jira/browse/WAGON-543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16732183#comment-16732183 ] Michael Osipov commented on WAGON-543: -- The byte at position 916 is {{NUL}}. > wagon-ssh download

[jira] [Commented] (WAGON-543) wagon-ssh download hangs

2019-01-02 Thread Michael Osipov (JIRA)
[ https://issues.apache.org/jira/browse/WAGON-543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16732193#comment-16732193 ] Michael Osipov commented on WAGON-543: -- Thread dump at blocked state: {noformat} [mosipov@mika-ion

[jira] [Commented] (WAGON-543) wagon-ssh download hangs

2019-01-02 Thread Michael Osipov (JIRA)
[ https://issues.apache.org/jira/browse/WAGON-543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16732174#comment-16732174 ] Michael Osipov commented on WAGON-543: -- [~dantran], I believe the current code does not hav a bug,

[GitHub] eolivelli commented on issue #2: [MJAR-238] Allow setting of module main class

2019-01-02 Thread GitBox
eolivelli commented on issue #2: [MJAR-238] Allow setting of module main class URL: https://github.com/apache/maven-jar-plugin/pull/2#issuecomment-450897788 @plamentotev check out the logs here: https://builds.apache.org/job/maven-box/job/maven-jar-plugin/job/MJAR-238/

[jira] [Commented] (DOXIA-575) Add support for (X)HTML5

2019-01-02 Thread Graham Leggett (JIRA)
[ https://issues.apache.org/jira/browse/DOXIA-575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16732135#comment-16732135 ] Graham Leggett commented on DOXIA-575: -- A quick bump, and a happy new year! :) The patch consists

[jira] [Comment Edited] (MSHARED-787) Add optional buildEnvironment information to the manifest

2019-01-02 Thread Michael Osipov (JIRA)
[ https://issues.apache.org/jira/browse/MSHARED-787?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16732105#comment-16732105 ] Michael Osipov edited comment on MSHARED-787 at 1/2/19 2:38 PM: If I

[jira] [Updated] (MSHARED-787) Add optional buildEnvironment information to the manifest

2019-01-02 Thread Michael Osipov (JIRA)
[ https://issues.apache.org/jira/browse/MSHARED-787?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MSHARED-787: --- Fix Version/s: maven-archiver-3.3.1 > Add optional buildEnvironment information to the

[jira] [Commented] (MSHARED-787) Add optional buildEnvironment information to the manifest

2019-01-02 Thread Michael Osipov (JIRA)
[ https://issues.apache.org/jira/browse/MSHARED-787?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16732105#comment-16732105 ] Michael Osipov commented on MSHARED-787: If I don't hear any objections by the end of next week,

[jira] [Commented] (SCM-777) scm:validate ignores scmCheckWorkingDirectoryUrl configuration in favor of system property

2019-01-02 Thread Michael Osipov (JIRA)
[ https://issues.apache.org/jira/browse/SCM-777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16732075#comment-16732075 ] Michael Osipov commented on SCM-777: [~schaller], that's great. If I don't hear any objections from the

[jira] [Commented] (SCM-777) scm:validate ignores scmCheckWorkingDirectoryUrl configuration in favor of system property

2019-01-02 Thread Andreas Schaller (JIRA)
[ https://issues.apache.org/jira/browse/SCM-777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16732021#comment-16732021 ] Andreas Schaller commented on SCM-777: -- [~michael-o] your fix works for me, thanks! > scm:validate

[GitHub] eolivelli commented on issue #48: [MENFORCER-324] - Shouldn't we use System.lineSeparator() instead?

2019-01-02 Thread GitBox
eolivelli commented on issue #48: [MENFORCER-324] - Shouldn't we use System.lineSeparator() instead? URL: https://github.com/apache/maven-enforcer/pull/48#issuecomment-450839532 Okay so I will continue with this ticket and eventually merge it to master.

[GitHub] michael-o commented on issue #48: [MENFORCER-324] - Shouldn't we use System.lineSeparator() instead?

2019-01-02 Thread GitBox
michael-o commented on issue #48: [MENFORCER-324] - Shouldn't we use System.lineSeparator() instead? URL: https://github.com/apache/maven-enforcer/pull/48#issuecomment-450838658 @eolivelli I have done that actually in places I have found. Feel free to work on that kind of stuff and

[GitHub] eolivelli commented on issue #48: [MENFORCER-324] - Shouldn't we use System.lineSeparator() instead?

2019-01-02 Thread GitBox
eolivelli commented on issue #48: [MENFORCER-324] - Shouldn't we use System.lineSeparator() instead? URL: https://github.com/apache/maven-enforcer/pull/48#issuecomment-450837815 @michael-o fine to me, let's merge this one. Thank you for your clarification. I feel it would be

[GitHub] michael-o commented on issue #48: [MENFORCER-324] - Shouldn't we use System.lineSeparator() instead?

2019-01-02 Thread GitBox
michael-o commented on issue #48: [MENFORCER-324] - Shouldn't we use System.lineSeparator() instead? URL: https://github.com/apache/maven-enforcer/pull/48#issuecomment-450836787 No one needs to complain to make things better. I fixed a lot of stuff last year in Maven SCM where no one

[GitHub] eolivelli commented on issue #48: [MENFORCER-324] - Shouldn't we use System.lineSeparator() instead?

2019-01-02 Thread GitBox
eolivelli commented on issue #48: [MENFORCER-324] - Shouldn't we use System.lineSeparator() instead? URL: https://github.com/apache/maven-enforcer/pull/48#issuecomment-450835806 @michael-o does any user ever reported any problem with the output of this plugin ? I think that somehow

[jira] [Updated] (SCM-777) scm:validate ignores scmCheckWorkingDirectoryUrl configuration in favor of system property

2019-01-02 Thread Michael Osipov (JIRA)
[ https://issues.apache.org/jira/browse/SCM-777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated SCM-777: --- Fix Version/s: 1.11.2 > scm:validate ignores scmCheckWorkingDirectoryUrl configuration in favor of >

[jira] [Comment Edited] (SCM-777) scm:validate ignores scmCheckWorkingDirectoryUrl configuration in favor of system property

2019-01-02 Thread Michael Osipov (JIRA)
[ https://issues.apache.org/jira/browse/SCM-777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16731939#comment-16731939 ] Michael Osipov edited comment on SCM-777 at 1/2/19 10:56 AM: - [~hboutemy],

[jira] [Updated] (SCM-777) scm:validate ignores scmCheckWorkingDirectoryUrl configuration in favor of system property

2019-01-02 Thread Michael Osipov (JIRA)
[ https://issues.apache.org/jira/browse/SCM-777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated SCM-777: --- Summary: scm:validate ignores scmCheckWorkingDirectoryUrl configuration in favor of system property

[jira] [Comment Edited] (SUREFIRE-1496) Dump file error for java.lang.module.ResolutionException

2019-01-02 Thread Tibor Digana (JIRA)
[ https://issues.apache.org/jira/browse/SUREFIRE-1496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16731937#comment-16731937 ] Tibor Digana edited comment on SUREFIRE-1496 at 1/2/19 10:54 AM: -

[jira] [Commented] (SCM-777) Maven plugin's scm:validate ignores scmCheckWorkingDirectoryUrl configuration in favor of system property

2019-01-02 Thread Michael Osipov (JIRA)
[ https://issues.apache.org/jira/browse/SCM-777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16731939#comment-16731939 ] Michael Osipov commented on SCM-777: [~hboutemy], [~olamy], I know it has been sometime since you

[jira] [Commented] (SUREFIRE-1496) Dump file error for java.lang.module.ResolutionException

2019-01-02 Thread Tibor Digana (JIRA)
[ https://issues.apache.org/jira/browse/SUREFIRE-1496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16731937#comment-16731937 ] Tibor Digana commented on SUREFIRE-1496: [~scolebou...@joda.org] [~earcam] [~triceo85] I have

[GitHub] michael-o edited a comment on issue #48: [MENFORCER-324] - Shouldn't we use System.lineSeparator() instead?

2019-01-02 Thread GitBox
michael-o edited a comment on issue #48: [MENFORCER-324] - Shouldn't we use System.lineSeparator() instead? URL: https://github.com/apache/maven-enforcer/pull/48#issuecomment-450832136 @eolivelli why? Line ending consistency is important. There a hundreds of spots in our codebase which

[GitHub] michael-o edited a comment on issue #48: [MENFORCER-324] - Shouldn't we use System.lineSeparator() instead?

2019-01-02 Thread GitBox
michael-o edited a comment on issue #48: [MENFORCER-324] - Shouldn't we use System.lineSeparator() instead? URL: https://github.com/apache/maven-enforcer/pull/48#issuecomment-450832136 @eolivelli why? Line ending consistency is important. There a hundreds of spots in our codebase which is

[GitHub] michael-o commented on issue #48: [MENFORCER-324] - Shouldn't we use System.lineSeparator() instead?

2019-01-02 Thread GitBox
michael-o commented on issue #48: [MENFORCER-324] - Shouldn't we use System.lineSeparator() instead? URL: https://github.com/apache/maven-enforcer/pull/48#issuecomment-450832136 @eolivelli why? Line ending consistency is important. There a hundreds of spots in our codebase which is

[jira] [Commented] (SUREFIRE-1496) Dump file error for java.lang.module.ResolutionException

2019-01-02 Thread Lukas Petrovicky (JIRA)
[ https://issues.apache.org/jira/browse/SUREFIRE-1496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16731927#comment-16731927 ] Lukas Petrovicky commented on SUREFIRE-1496: I am also running into (possibly) a similar

[jira] [Updated] (MNG-6547) MavenProject.writeModel(Writer writer) outputs an error-sorted pom.xml

2019-01-02 Thread Bo Wang (JIRA)
[ https://issues.apache.org/jira/browse/MNG-6547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bo Wang updated MNG-6547: - Description: When I try to rewrite a _pom.xml_ to add a plugin configuration via  *MavenProject.write(Writer

[jira] [Updated] (MNG-6547) MavenProject.writeModel(Writer writer) outputs an error-sorted pom.xml

2019-01-02 Thread Bo Wang (JIRA)
[ https://issues.apache.org/jira/browse/MNG-6547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bo Wang updated MNG-6547: - Description: When I try to rewrite a _pom.xml_ to add a plugin configuration via  *MavenProject.write(Writer

[jira] [Created] (MNG-6547) MavenProject.writeModel(Writer writer) outputs an error-sorted pom.xml

2019-01-02 Thread Bo Wang (JIRA)
Bo Wang created MNG-6547: Summary: MavenProject.writeModel(Writer writer) outputs an error-sorted pom.xml Key: MNG-6547 URL: https://issues.apache.org/jira/browse/MNG-6547 Project: Maven Issue

[GitHub] eolivelli commented on issue #48: [MENFORCER-324] - Shouldn't we use System.lineSeparator() instead?

2019-01-02 Thread GitBox
eolivelli commented on issue #48: [MENFORCER-324] - Shouldn't we use System.lineSeparator() instead? URL: https://github.com/apache/maven-enforcer/pull/48#issuecomment-450826573 Seems to me and to the contributor himself that this change is not needed. Are there any other cases in other

[GitHub] eolivelli edited a comment on issue #48: [MENFORCER-324] - Shouldn't we use System.lineSeparator() instead?

2019-01-02 Thread GitBox
eolivelli edited a comment on issue #48: [MENFORCER-324] - Shouldn't we use System.lineSeparator() instead? URL: https://github.com/apache/maven-enforcer/pull/48#issuecomment-450826573 Seems to me and to the contributor himself that this change is not needed. Are there any other cases

[GitHub] Tibor17 commented on issue #48: [MENFORCER-324] - Shouldn't we use System.lineSeparator() instead?

2019-01-02 Thread GitBox
Tibor17 commented on issue #48: [MENFORCER-324] - Shouldn't we use System.lineSeparator() instead? URL: https://github.com/apache/maven-enforcer/pull/48#issuecomment-450821200 No objections from me. Go ahead! This is an

[jira] [Commented] (SCM-777) Maven plugin's scm:validate ignores scmCheckWorkingDirectoryUrl configuration in favor of system property

2019-01-02 Thread Andreas Schaller (JIRA)
[ https://issues.apache.org/jira/browse/SCM-777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16731877#comment-16731877 ] Andreas Schaller commented on SCM-777: -- Yes, I know... here's a minimal test case: {code:xml}

[jira] [Reopened] (SCM-777) Maven plugin's scm:validate ignores scmCheckWorkingDirectoryUrl configuration in favor of system property

2019-01-02 Thread Michael Osipov (JIRA)
[ https://issues.apache.org/jira/browse/SCM-777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov reopened SCM-777: Assignee: Michael Osipov Thanks for the case, reopening... > Maven plugin's scm:validate ignores

[jira] [Comment Edited] (SCM-777) Maven plugin's scm:validate ignores scmCheckWorkingDirectoryUrl configuration in favor of system property

2019-01-02 Thread Michael Osipov (JIRA)
[ https://issues.apache.org/jira/browse/SCM-777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16731877#comment-16731877 ] Michael Osipov edited comment on SCM-777 at 1/2/19 9:40 AM: Yes, I know...

[GitHub] michael-o commented on issue #4: [MJAVADOC-527] - detectLinks may pass invalid urls to javadoc

2019-01-02 Thread GitBox
michael-o commented on issue #4: [MJAVADOC-527] - detectLinks may pass invalid urls to javadoc URL: https://github.com/apache/maven-javadoc-plugin/pull/4#issuecomment-450820038 Something is still fishy about this: mosipov@mikaw10 MINGW64

[GitHub] michael-o commented on issue #48: [MENFORCER-324] - Shouldn't we use System.lineSeparator() instead?

2019-01-02 Thread GitBox
michael-o commented on issue #48: [MENFORCER-324] - Shouldn't we use System.lineSeparator() instead? URL: https://github.com/apache/maven-enforcer/pull/48#issuecomment-450818400 @eolivelli @Tibor17 anything holding us off merging @jsoref's work? Looks good to me now.

[jira] [Commented] (SCM-777) Maven plugin's scm:validate ignores scmCheckWorkingDirectoryUrl configuration in favor of system property

2019-01-02 Thread Michael Osipov (JIRA)
[ https://issues.apache.org/jira/browse/SCM-777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16731857#comment-16731857 ] Michael Osipov commented on SCM-777: [~schaller], if you can provide me a test case, I'd be happy to

[jira] [Commented] (SCM-777) Maven plugin's scm:validate ignores scmCheckWorkingDirectoryUrl configuration in favor of system property

2019-01-02 Thread Andreas Schaller (JIRA)
[ https://issues.apache.org/jira/browse/SCM-777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16731833#comment-16731833 ] Andreas Schaller commented on SCM-777: -- This bug is reported over 4 years ago and you close it because