[GitHub] michael-o commented on issue #52: add --chache option for git rm

michael-o commented on issue #52: add --chache option for git rm URL: https://github.com/apache/maven-scm/pull/52#issuecomment-414157161 Still waiting for updates... This is an automated message from the Apache Git Service. To

[jira] [Updated] (SCM-853) Bootstrap changes for checkout and update.

[ https://issues.apache.org/jira/browse/SCM-853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated SCM-853: --- Fix Version/s: waiting-for-feedback > Bootstrap changes for checkout and update. > -

[jira] [Commented] (SCM-853) Bootstrap changes for checkout and update.

[ https://issues.apache.org/jira/browse/SCM-853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16585277#comment-16585277 ] Michael Osipov commented on SCM-853: What is actually the motivation for this change? >

[jira] [Commented] (SCM-835) includes directive doesn't work correctly when other files in directory changes

[ https://issues.apache.org/jira/browse/SCM-835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16585275#comment-16585275 ] ASF GitHub Bot commented on SCM-835: asfgit closed pull request #51: fix SCM-835 collisi

[jira] [Closed] (SCM-835) includes directive doesn't work correctly when other files in directory changes

[ https://issues.apache.org/jira/browse/SCM-835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed SCM-835. -- Resolution: Fixed Fixed with [13775da2dbb30e7fc553d449672bb74dd8d02a14|https://gitbox.apache.org/repos/as

[GitHub] asfgit closed pull request #51: fix SCM-835 collision

asfgit closed pull request #51: fix SCM-835 collision URL: https://github.com/apache/maven-scm/pull/51 This is a PR merged from a forked repository. As GitHub hides the original diff on merge, it is displayed below for the sake of provenance: As this is a foreign pull request (from a fork

[jira] [Commented] (SCM-706) prepare-with-pom deletes release-pom.xml then tries to git add it (presumably so the next commit records the fact)

[ https://issues.apache.org/jira/browse/SCM-706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16585274#comment-16585274 ] ASF GitHub Bot commented on SCM-706: michael-o commented on issue #31: SCM-706 finer-gra

[GitHub] michael-o commented on issue #31: SCM-706 finer-grained handling of file rename status for gitexe provider...

michael-o commented on issue #31: SCM-706 finer-grained handling of file rename status for gitexe provider... URL: https://github.com/apache/maven-scm/pull/31#issuecomment-414156828 Can someone please rebase and drop unaffected changes even if they are correct? We also need a proper IT whi

[jira] [Commented] (SCM-318) Allow tags to be removed

[ https://issues.apache.org/jira/browse/SCM-318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16585271#comment-16585271 ] ASF GitHub Bot commented on SCM-318: michael-o commented on issue #79: [SCM-318] Untag c

[GitHub] michael-o commented on issue #79: [SCM-318] Untag command, with Git implementations

michael-o commented on issue #79: [SCM-318] Untag command, with Git implementations URL: https://github.com/apache/maven-scm/pull/79#issuecomment-414156073 Please revise formatting. It does not fully correspond to our format.

[jira] [Commented] (SCM-835) includes directive doesn't work correctly when other files in directory changes

[ https://issues.apache.org/jira/browse/SCM-835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16585269#comment-16585269 ] ASF GitHub Bot commented on SCM-835: michael-o commented on a change in pull request #51

[GitHub] michael-o commented on a change in pull request #51: fix SCM-835 collision

michael-o commented on a change in pull request #51: fix SCM-835 collision URL: https://github.com/apache/maven-scm/pull/51#discussion_r23794 ## File path: maven-scm-providers/maven-scm-providers-git/maven-scm-provider-gitexe/src/test/java/org/apache/maven/scm/provider/git/gitex

[jira] [Updated] (SCM-835) includes directive doesn't work correctly when other files in directory changes

[ https://issues.apache.org/jira/browse/SCM-835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated SCM-835: --- Fix Version/s: 1.10.1 > includes directive doesn't work correctly when other files in directory > chang

[jira] [Assigned] (SCM-835) includes directive doesn't work correctly when other files in directory changes

[ https://issues.apache.org/jira/browse/SCM-835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov reassigned SCM-835: -- Assignee: Michael Osipov > includes directive doesn't work correctly when other files in director

[jira] [Commented] (SCM-835) includes directive doesn't work correctly when other files in directory changes

[ https://issues.apache.org/jira/browse/SCM-835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16585268#comment-16585268 ] ASF GitHub Bot commented on SCM-835: michael-o commented on issue #51: fix SCM-835 colli

[GitHub] michael-o commented on issue #51: fix SCM-835 collision

michael-o commented on issue #51: fix SCM-835 collision URL: https://github.com/apache/maven-scm/pull/51#issuecomment-414153426 Just checked `SvnCheckInCommand` and it looks fine to me. `createCommandLine` does `SvnCommandLineUtils.addTarget( cl, fileSet.getFileList() );`. `svn st` is neve

[jira] [Commented] (SCM-835) includes directive doesn't work correctly when other files in directory changes

[ https://issues.apache.org/jira/browse/SCM-835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16585266#comment-16585266 ] ASF GitHub Bot commented on SCM-835: michael-o commented on a change in pull request #51

[GitHub] michael-o commented on a change in pull request #51: fix SCM-835 collision

michael-o commented on a change in pull request #51: fix SCM-835 collision URL: https://github.com/apache/maven-scm/pull/51#discussion_r23794 ## File path: maven-scm-providers/maven-scm-providers-git/maven-scm-provider-gitexe/src/test/java/org/apache/maven/scm/provider/git/gitex

[jira] [Commented] (SUREFIRE-1550) The surefire XSD published on maven site lacks of some rerun element

[ https://issues.apache.org/jira/browse/SUREFIRE-1550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16585265#comment-16585265 ] ASF GitHub Bot commented on SUREFIRE-1550: -- Tibor17 commented on issue #192:

[GitHub] Tibor17 commented on issue #192: [SUREFIRE-1550] The surefire XSD published on maven site lacks of some

Tibor17 commented on issue #192: [SUREFIRE-1550] The surefire XSD published on maven site lacks of some URL: https://github.com/apache/maven-surefire/pull/192#issuecomment-414151673 @nfalco79 Ths for introducing the missing elements but I have to remove the `time` because the code know

[GitHub] michael-o commented on a change in pull request #37: making the retry handle of http client configurable

michael-o commented on a change in pull request #37: making the retry handle of http client configurable URL: https://github.com/apache/maven-wagon/pull/37#discussion_r22918 ## File path: wagon-providers/wagon-http-shared/src/main/java/org/apache/maven/wagon/shared/http/Abstrac

[GitHub] michael-o commented on a change in pull request #37: making the retry handle of http client configurable

michael-o commented on a change in pull request #37: making the retry handle of http client configurable URL: https://github.com/apache/maven-wagon/pull/37#discussion_r23013 ## File path: wagon-providers/wagon-http/src/test/java/org/apache/maven/wagon/providers/http/AbstractHtt

[GitHub] michael-o commented on a change in pull request #37: making the retry handle of http client configurable

michael-o commented on a change in pull request #37: making the retry handle of http client configurable URL: https://github.com/apache/maven-wagon/pull/37#discussion_r22644 ## File path: wagon-providers/wagon-http-shared/src/main/java/org/apache/maven/wagon/shared/http/Abstrac

[GitHub] michael-o commented on a change in pull request #37: making the retry handle of http client configurable

michael-o commented on a change in pull request #37: making the retry handle of http client configurable URL: https://github.com/apache/maven-wagon/pull/37#discussion_r22754 ## File path: wagon-providers/wagon-http-shared/src/main/java/org/apache/maven/wagon/shared/http/Abstrac

[GitHub] michael-o commented on a change in pull request #37: making the retry handle of http client configurable

michael-o commented on a change in pull request #37: making the retry handle of http client configurable URL: https://github.com/apache/maven-wagon/pull/37#discussion_r22658 ## File path: wagon-providers/wagon-http-shared/src/main/java/org/apache/maven/wagon/shared/http/Abstrac

[GitHub] michael-o commented on a change in pull request #37: making the retry handle of http client configurable

michael-o commented on a change in pull request #37: making the retry handle of http client configurable URL: https://github.com/apache/maven-wagon/pull/37#discussion_r22855 ## File path: wagon-providers/wagon-http-shared/src/main/java/org/apache/maven/wagon/shared/http/Abstrac

[GitHub] michael-o commented on a change in pull request #37: making the retry handle of http client configurable

michael-o commented on a change in pull request #37: making the retry handle of http client configurable URL: https://github.com/apache/maven-wagon/pull/37#discussion_r22884 ## File path: wagon-providers/wagon-http-shared/src/main/java/org/apache/maven/wagon/shared/http/Abstrac

[GitHub] michael-o commented on a change in pull request #37: making the retry handle of http client configurable

michael-o commented on a change in pull request #37: making the retry handle of http client configurable URL: https://github.com/apache/maven-wagon/pull/37#discussion_r22974 ## File path: wagon-providers/wagon-http/src/site/apt/index.apt ## @@ -57,3 +57,22 @@ Features

[GitHub] michael-o commented on a change in pull request #37: making the retry handle of http client configurable

michael-o commented on a change in pull request #37: making the retry handle of http client configurable URL: https://github.com/apache/maven-wagon/pull/37#discussion_r23025 ## File path: wagon-providers/wagon-http/src/test/java/org/apache/maven/wagon/providers/http/AbstractHtt

[GitHub] michael-o commented on a change in pull request #37: making the retry handle of http client configurable

michael-o commented on a change in pull request #37: making the retry handle of http client configurable URL: https://github.com/apache/maven-wagon/pull/37#discussion_r22760 ## File path: wagon-providers/wagon-http-shared/src/main/java/org/apache/maven/wagon/shared/http/Abstrac

[GitHub] michael-o commented on a change in pull request #37: making the retry handle of http client configurable

michael-o commented on a change in pull request #37: making the retry handle of http client configurable URL: https://github.com/apache/maven-wagon/pull/37#discussion_r22986 ## File path: wagon-providers/wagon-http/src/site/apt/index.apt ## @@ -57,3 +57,22 @@ Features

[jira] [Commented] (SCM-835) includes directive doesn't work correctly when other files in directory changes

[ https://issues.apache.org/jira/browse/SCM-835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16585252#comment-16585252 ] ASF GitHub Bot commented on SCM-835: shvar commented on issue #51: fix SCM-835 collision

[GitHub] shvar commented on issue #51: fix SCM-835 collision

shvar commented on issue #51: fix SCM-835 collision URL: https://github.com/apache/maven-scm/pull/51#issuecomment-414149652 It's an interesting question. I checked now SvnExe and JGit and it looks like: 1) on SvnExe we don't have `fileSet` at all, only `workingDirectory`, so it will

[jira] [Commented] (WAGON-500) Re-enable ScmCvsExeWagonTest

[ https://issues.apache.org/jira/browse/WAGON-500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16585250#comment-16585250 ] ASF GitHub Bot commented on WAGON-500: -- asfgit closed pull request #44: [WAGON-500] r

[jira] [Closed] (WAGON-500) Re-enable ScmCvsExeWagonTest

[ https://issues.apache.org/jira/browse/WAGON-500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed WAGON-500. Resolution: Fixed Fixed with [7b72081eb449f0334a8d5d971b4cbb64ceb7641d|https://gitbox.apache.org/re

[GitHub] asfgit closed pull request #44: [WAGON-500] re-enable ScmCvsExeWagonTest

asfgit closed pull request #44: [WAGON-500] re-enable ScmCvsExeWagonTest URL: https://github.com/apache/maven-wagon/pull/44 This is a PR merged from a forked repository. As GitHub hides the original diff on merge, it is displayed below for the sake of provenance: As this is a foreign pull

[GitHub] michael-o commented on issue #51: fix SCM-835 collision

michael-o commented on issue #51: fix SCM-835 collision URL: https://github.com/apache/maven-scm/pull/51#issuecomment-414146910 Have you actually checked with other providers? JGit, SvnExe? I'd expect the exact same behavior across providers. I don't care for the remaining ones for now.

[jira] [Commented] (SCM-835) includes directive doesn't work correctly when other files in directory changes

[ https://issues.apache.org/jira/browse/SCM-835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16585241#comment-16585241 ] ASF GitHub Bot commented on SCM-835: michael-o commented on issue #51: fix SCM-835 colli

[jira] [Commented] (WAGON-521) Maven cannot use system default proxies

[ https://issues.apache.org/jira/browse/WAGON-521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16585239#comment-16585239 ] Michael Osipov commented on WAGON-521: -- No, we won't change JVM default values. This

[jira] [Commented] (SCM-835) includes directive doesn't work correctly when other files in directory changes

[ https://issues.apache.org/jira/browse/SCM-835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16585238#comment-16585238 ] ASF GitHub Bot commented on SCM-835: shvar commented on issue #51: fix SCM-835 collision

[GitHub] shvar commented on issue #51: fix SCM-835 collision

shvar commented on issue #51: fix SCM-835 collision URL: https://github.com/apache/maven-scm/pull/51#issuecomment-414146512 Rebased, @michael-o The context of the problem, if I remember correctly, was that the status consumer reported affected files, that were in `fileSet.getBasedir

[jira] [Commented] (MEAR-270) Upgrade maven-plugins parent to version 32

[ https://issues.apache.org/jira/browse/MEAR-270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16585228#comment-16585228 ] Hudson commented on MEAR-270: - Build succeeded in Jenkins: Maven TLP » maven-ear-plugin » maste

[jira] [Commented] (MRAR-80) Upgrade JUnit to 4.12

[ https://issues.apache.org/jira/browse/MRAR-80?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16585224#comment-16585224 ] Hudson commented on MRAR-80: Build succeeded in Jenkins: Maven TLP » maven-rar-plugin » master #

[jira] [Commented] (MRAR-80) Upgrade JUnit to 4.12

[ https://issues.apache.org/jira/browse/MRAR-80?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16585223#comment-16585223 ] Karl Heinz Marbaise commented on MRAR-80: - Done in [38fd933d26bfeb3020c465bd39fd120

[jira] [Closed] (MRAR-80) Upgrade JUnit to 4.12

[ https://issues.apache.org/jira/browse/MRAR-80?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise closed MRAR-80. --- Resolution: Done > Upgrade JUnit to 4.12 > - > > Key: MRAR-8

[jira] [Commented] (MEAR-270) Upgrade maven-plugins parent to version 32

[ https://issues.apache.org/jira/browse/MEAR-270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16585222#comment-16585222 ] Karl Heinz Marbaise commented on MEAR-270: -- Done in [ab0209461d351a67272e9afd4712

[jira] [Closed] (MEAR-270) Upgrade maven-plugins parent to version 32

[ https://issues.apache.org/jira/browse/MEAR-270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise closed MEAR-270. Resolution: Done > Upgrade maven-plugins parent to version 32 > -

[jira] [Created] (MVERIFIER-33) Download checksums via https

Karl Heinz Marbaise created MVERIFIER-33: Summary: Download checksums via https Key: MVERIFIER-33 URL: https://issues.apache.org/jira/browse/MVERIFIER-33 Project: Maven Verifier Plugin

[jira] [Created] (MRAR-80) Upgrade JUnit to 4.12

Karl Heinz Marbaise created MRAR-80: --- Summary: Upgrade JUnit to 4.12 Key: MRAR-80 URL: https://issues.apache.org/jira/browse/MRAR-80 Project: Maven Rar Plugin Issue Type: Dependency upgrade

[jira] [Commented] (MVERIFIER-32) Move model package to org.apache.maven.plugins.verifier.model

[ https://issues.apache.org/jira/browse/MVERIFIER-32?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16585214#comment-16585214 ] Hudson commented on MVERIFIER-32: - Build succeeded in Jenkins: Maven TLP » maven-verifi

[jira] [Closed] (MVERIFIER-32) Move model package to org.apache.maven.plugins.verifier.model

[ https://issues.apache.org/jira/browse/MVERIFIER-32?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise closed MVERIFIER-32. Resolution: Done > Move model package to org.apache.maven.plugins.verifier.model

[jira] [Commented] (MVERIFIER-32) Move model package to org.apache.maven.plugins.verifier.model

[ https://issues.apache.org/jira/browse/MVERIFIER-32?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16585213#comment-16585213 ] Karl Heinz Marbaise commented on MVERIFIER-32: -- Done in [f3c90e02d0fb902e

[jira] [Created] (MVERIFIER-32) Move model package to org.apache.maven.plugins.verifier.model

Karl Heinz Marbaise created MVERIFIER-32: Summary: Move model package to org.apache.maven.plugins.verifier.model Key: MVERIFIER-32 URL: https://issues.apache.org/jira/browse/MVERIFIER-32 Proje

[jira] [Commented] (MDEPLOY-177) Maven release:perform hangs when downloading maven-metadata.xml

[ https://issues.apache.org/jira/browse/MDEPLOY-177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16585202#comment-16585202 ] Karl Heinz Marbaise commented on MDEPLOY-177: - [~WolfgangFahl] Can you pleas

[jira] [Commented] (MDEPLOY-177) Maven release:perform hangs when downloading maven-metadata.xml

[ https://issues.apache.org/jira/browse/MDEPLOY-177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16585184#comment-16585184 ] Wolfgang Fahl commented on MDEPLOY-177: --- IMHO it still does not work "out of the b

[jira] [Closed] (MDEPLOY-177) Maven release:perform hangs when downloading maven-metadata.xml

[ https://issues.apache.org/jira/browse/MDEPLOY-177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise closed MDEPLOY-177. --- Resolution: Not A Problem Fix Version/s: (was: waiting-for-feedback) It s

[jira] [Commented] (MDEPLOY-240) Remove updateReleaseInfo parameter

[ https://issues.apache.org/jira/browse/MDEPLOY-240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16585180#comment-16585180 ] Hudson commented on MDEPLOY-240: Build succeeded in Jenkins: Maven TLP » maven-deploy-pl

[jira] [Commented] (MDEPLOY-240) Remove updateReleaseInfo parameter

[ https://issues.apache.org/jira/browse/MDEPLOY-240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16585179#comment-16585179 ] Karl Heinz Marbaise commented on MDEPLOY-240: - Done in [41a40f6892a3ebd818d

[jira] [Closed] (MDEPLOY-240) Remove updateReleaseInfo parameter

[ https://issues.apache.org/jira/browse/MDEPLOY-240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise closed MDEPLOY-240. --- Resolution: Done > Remove updateReleaseInfo parameter >

[jira] [Assigned] (MDEPLOY-240) Remove updateReleaseInfo parameter

[ https://issues.apache.org/jira/browse/MDEPLOY-240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise reassigned MDEPLOY-240: --- Assignee: Karl Heinz Marbaise > Remove updateReleaseInfo parameter > --

[jira] [Commented] (MINSTALL-147) Upgrade JUnit to 4.12

[ https://issues.apache.org/jira/browse/MINSTALL-147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16585164#comment-16585164 ] Hudson commented on MINSTALL-147: - Build succeeded in Jenkins: Maven TLP » maven-instal

[jira] [Updated] (MINSTALL-96) Skip option for install-file

[ https://issues.apache.org/jira/browse/MINSTALL-96?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise updated MINSTALL-96: Fix Version/s: waiting-for-feedback > Skip option for install-file > -

[jira] [Closed] (MINSTALL-147) Upgrade JUnit to 4.12

[ https://issues.apache.org/jira/browse/MINSTALL-147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise closed MINSTALL-147. Resolution: Done > Upgrade JUnit to 4.12 > - > >

[jira] [Commented] (MINSTALL-147) Upgrade JUnit to 4.12

[ https://issues.apache.org/jira/browse/MINSTALL-147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16585162#comment-16585162 ] Karl Heinz Marbaise commented on MINSTALL-147: -- Done in [0ec3344945c52e3f

[jira] [Assigned] (MINSTALL-147) Upgrade JUnit to 4.12

[ https://issues.apache.org/jira/browse/MINSTALL-147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise reassigned MINSTALL-147: Assignee: Karl Heinz Marbaise > Upgrade JUnit to 4.12 >

[jira] [Commented] (MSHADE-267) Transitive dependencies of test dependencies included in shaded jar

[ https://issues.apache.org/jira/browse/MSHADE-267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16585125#comment-16585125 ] Karl Heinz Marbaise commented on MSHADE-267: Do you have a complete working e

[jira] [Updated] (MSHADE-268) improving inclusion of open source code referenced by java projects.

[ https://issues.apache.org/jira/browse/MSHADE-268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise updated MSHADE-268: --- Fix Version/s: waiting-for-feedback > improving inclusion of open source code referen

[jira] [Updated] (MSHADE-270) relocation of classes with out a package name is not working

[ https://issues.apache.org/jira/browse/MSHADE-270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise updated MSHADE-270: --- Fix Version/s: waiting-for-feedback > relocation of classes with out a package name i

[jira] [Commented] (MSHADE-270) relocation of classes with out a package name is not working

[ https://issues.apache.org/jira/browse/MSHADE-270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16585124#comment-16585124 ] Karl Heinz Marbaise commented on MSHADE-270: To be honest I would already see

[jira] [Commented] (MSHADE-271) Suppress “[Jar list] define N overlapping classes” warning if classes from different jars are equal each other

[ https://issues.apache.org/jira/browse/MSHADE-271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16585123#comment-16585123 ] Karl Heinz Marbaise commented on MSHADE-271: Do you have a full working examp

[jira] [Updated] (MSHADE-271) Suppress “[Jar list] define N overlapping classes” warning if classes from different jars are equal each other

[ https://issues.apache.org/jira/browse/MSHADE-271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise updated MSHADE-271: --- Fix Version/s: waiting-for-feedback > Suppress “[Jar list] define N overlapping class

[jira] [Commented] (MSHADE-292) Relocation exclude works differently on Win and Unix platforms

[ https://issues.apache.org/jira/browse/MSHADE-292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16585118#comment-16585118 ] Karl Heinz Marbaise commented on MSHADE-292: First I don't see a difference b

[GitHub] khmarbaise closed pull request #4: (doc) - mention include tag

khmarbaise closed pull request #4: (doc) - mention include tag URL: https://github.com/apache/maven-shade-plugin/pull/4 This is a PR merged from a forked repository. As GitHub hides the original diff on merge, it is displayed below for the sake of provenance: As this is a foreign pull req

[GitHub] khmarbaise commented on issue #4: (doc) - mention include tag

khmarbaise commented on issue #4: (doc) - mention include tag URL: https://github.com/apache/maven-shade-plugin/pull/4#issuecomment-414117397 Thanks for your contribution. This has been merged into master. Result can be seen here: https://gitbox.apache.org/repos/asf?p=maven-shade-plugin.gi

[jira] [Commented] (MSHADE-296) Upgrade maven-artifact-transfer 0.10.0

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

[jira] [Commented] (MSHADE-296) Upgrade maven-artifact-transfer 0.10.0

[ https://issues.apache.org/jira/browse/MSHADE-296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16585097#comment-16585097 ] Karl Heinz Marbaise commented on MSHADE-296: Done in [0a54658a420e07da720728

[jira] [Closed] (MSHADE-296) Upgrade maven-artifact-transfer 0.10.0

[ https://issues.apache.org/jira/browse/MSHADE-296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise closed MSHADE-296. -- Resolution: Done > Upgrade maven-artifact-transfer 0.10.0 > ---

[jira] [Commented] (MSHADE-289) Maven Shade Plugin does not work under Java 10

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

[jira] [Created] (MSHADE-296) Upgrade maven-artifact-transfer 0.10.0

Karl Heinz Marbaise created MSHADE-296: -- Summary: Upgrade maven-artifact-transfer 0.10.0 Key: MSHADE-296 URL: https://issues.apache.org/jira/browse/MSHADE-296 Project: Maven Shade Plugin

[jira] [Commented] (MSHADE-289) Maven Shade Plugin does not work under Java 10

[ https://issues.apache.org/jira/browse/MSHADE-289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16585091#comment-16585091 ] Karl Heinz Marbaise commented on MSHADE-289: Done in [06aff7513f836328434057

[jira] [Commented] (MSHADE-289) Maven Shade Plugin does not work under Java 10

[ https://issues.apache.org/jira/browse/MSHADE-289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16585092#comment-16585092 ] ASF GitHub Bot commented on MSHADE-289: --- khmarbaise commented on issue #3: [MSHADE-

[jira] [Closed] (MSHADE-289) Maven Shade Plugin does not work under Java 10

[ https://issues.apache.org/jira/browse/MSHADE-289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise closed MSHADE-289. -- Resolution: Done > Maven Shade Plugin does not work under Java 10 > ---

[jira] [Commented] (MSHADE-289) Maven Shade Plugin does not work under Java 10

[ https://issues.apache.org/jira/browse/MSHADE-289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16585093#comment-16585093 ] ASF GitHub Bot commented on MSHADE-289: --- khmarbaise closed pull request #3: [MSHADE

[GitHub] khmarbaise commented on issue #3: [MSHADE-289] - Maven Shade Plugin does not work under Java 10

khmarbaise commented on issue #3: [MSHADE-289] - Maven Shade Plugin does not work under Java 10 URL: https://github.com/apache/maven-shade-plugin/pull/3#issuecomment-414114763 Based on the upgrade of JDependency we have to lift minimum JDK8+ for using minimizeJar=true otherwise you can use

[GitHub] khmarbaise closed pull request #3: [MSHADE-289] - Maven Shade Plugin does not work under Java 10

khmarbaise closed pull request #3: [MSHADE-289] - Maven Shade Plugin does not work under Java 10 URL: https://github.com/apache/maven-shade-plugin/pull/3 This is a PR merged from a forked repository. As GitHub hides the original diff on merge, it is displayed below for the sake of provena

[jira] [Commented] (WAGON-500) Re-enable ScmCvsExeWagonTest

[ https://issues.apache.org/jira/browse/WAGON-500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16585078#comment-16585078 ] ASF GitHub Bot commented on WAGON-500: -- basinilya commented on issue #44: [WAGON-500]

[GitHub] basinilya commented on issue #44: [WAGON-500] re-enable ScmCvsExeWagonTest

basinilya commented on issue #44: [WAGON-500] re-enable ScmCvsExeWagonTest URL: https://github.com/apache/maven-wagon/pull/44#issuecomment-414113884 Pushed. Please check. This is an automated message from the Apache Git Servic

[jira] [Commented] (WAGON-521) Maven cannot use system default proxies

[ https://issues.apache.org/jira/browse/WAGON-521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16585069#comment-16585069 ] Noel Grandin commented on WAGON-521: Yeah, that is my point, that java.net.useSystemPr

[jira] [Commented] (WAGON-500) Re-enable ScmCvsExeWagonTest

[ https://issues.apache.org/jira/browse/WAGON-500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16585067#comment-16585067 ] ASF GitHub Bot commented on WAGON-500: -- michael-o commented on issue #44: [WAGON-500]

[GitHub] michael-o commented on issue #44: [WAGON-500] re-enable ScmCvsExeWagonTest

michael-o commented on issue #44: [WAGON-500] re-enable ScmCvsExeWagonTest URL: https://github.com/apache/maven-wagon/pull/44#issuecomment-414112450 I take either. You decide what you want to provide. This is an automated mess

[jira] [Comment Edited] (WAGON-521) Maven cannot use system default proxies

[ https://issues.apache.org/jira/browse/WAGON-521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16585065#comment-16585065 ] Michael Osipov edited comment on WAGON-521 at 8/19/18 8:29 AM: -

[jira] [Commented] (WAGON-500) Re-enable ScmCvsExeWagonTest

[ https://issues.apache.org/jira/browse/WAGON-500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16585066#comment-16585066 ] ASF GitHub Bot commented on WAGON-500: -- basinilya commented on issue #44: [WAGON-500]

[GitHub] basinilya commented on issue #44: [WAGON-500] re-enable ScmCvsExeWagonTest

basinilya commented on issue #44: [WAGON-500] re-enable ScmCvsExeWagonTest URL: https://github.com/apache/maven-wagon/pull/44#issuecomment-414112397 There's a quick and a proper way. The quick way is to return from test methods when no cvs binary is found, just like maven-scm does. I can pu

[jira] [Commented] (WAGON-521) Maven cannot use system default proxies

[ https://issues.apache.org/jira/browse/WAGON-521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16585065#comment-16585065 ] Michael Osipov commented on WAGON-521: -- Wagon handles the transport passing to HttpCl