[GitHub] [maven-shade-plugin] dependabot[bot] opened a new pull request #99: Bump jdependency from 2.6.0 to 2.7.0

2021-06-02 Thread GitBox 


dependabot[bot] opened a new pull request #99:
URL: https://github.com/apache/maven-shade-plugin/pull/99


   Bumps [jdependency](https://github.com/tcurdt/jdependency) from 2.6.0 to 
2.7.0.
   
   Changelog
   Sourced from https://github.com/tcurdt/jdependency/blob/master/HISTORY.md;>jdependency's
 changelog.
   
   Version 2.7.0, release 02.06.2021
   
   Changed test with java 16
   Changed requires maven 3.6.0
   Added ASM9 Opcodes
   
   
   
   
   Commits
   
   https://github.com/tcurdt/jdependency/commit/027120183bb3cb31e7b451ae0378aebffdefb2ac;>0271201
 prepare for 2.7
   https://github.com/tcurdt/jdependency/commit/18f77f2fd2ffe4967685037858a9527021db8526;>18f77f2
 updated changelog
   https://github.com/tcurdt/jdependency/commit/fda3a00260044db21602ed5cd499058edf859d96;>fda3a00
 Bump commons-io from 2.8.0 to 2.9.0
   https://github.com/tcurdt/jdependency/commit/01868baaf33cee870617db267316ca8dc70c71a2;>01868ba
 Bump maven-javadoc-plugin from 3.2.0 to 3.3.0
   https://github.com/tcurdt/jdependency/commit/be6ec6da04f8ab62c7ea2811d04263730be6f127;>be6ec6d
 Use ASM9 Opcodes, add missing non-void overrides
   https://github.com/tcurdt/jdependency/commit/d5ef1e6e6f647ccf739dce10c1b1f75bda3b8ac9;>d5ef1e6
 workflow updates
   https://github.com/tcurdt/jdependency/commit/7b878873c4265d75c870208e4bd32130188f17f1;>7b87887
 Bump maven-gpg-plugin from 1.6 to 3.0.1
   https://github.com/tcurdt/jdependency/commit/c6577ae2f79317e6a77e389208f2916b70160884;>c6577ae
 Bump jacoco-maven-plugin from 0.8.6 to 0.8.7
   https://github.com/tcurdt/jdependency/commit/2631c3cd9265f70e5d3db1d015d4894bc2072fa5;>2631c3c
 Bump maven-project-info-reports-plugin from 3.1.1 to 3.1.2
   https://github.com/tcurdt/jdependency/commit/a9de5bbd2c5a6f97454b0f7291a4b91290560a51;>a9de5bb
 Bump maven-jxr-plugin from 3.0.0 to 3.1.1
   Additional commits viewable in https://github.com/tcurdt/jdependency/compare/jdependency-2.6.0...jdependency-2.7.0;>compare
 view
   
   
   
   
   
   [![Dependabot compatibility 
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=org.vafer:jdependency=maven=2.6.0=2.7.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)
   
   Dependabot will resolve any conflicts with this PR as long as you don't 
alter it yourself. You can also trigger a rebase manually by commenting 
`@dependabot rebase`.
   
   [//]: # (dependabot-automerge-start)
   [//]: # (dependabot-automerge-end)
   
   ---
   
   
   Dependabot commands and options
   
   
   You can trigger Dependabot actions by commenting on this PR:
   - `@dependabot rebase` will rebase this PR
   - `@dependabot recreate` will recreate this PR, overwriting any edits that 
have been made to it
   - `@dependabot merge` will merge this PR after your CI passes on it
   - `@dependabot squash and merge` will squash and merge this PR after your CI 
passes on it
   - `@dependabot cancel merge` will cancel a previously requested merge and 
block automerging
   - `@dependabot reopen` will reopen this PR if it is closed
   - `@dependabot close` will close this PR and stop Dependabot recreating it. 
You can achieve the same result by closing it manually
   - `@dependabot ignore this major version` will close this PR and stop 
Dependabot creating any more for this major version (unless you reopen the PR 
or upgrade to it yourself)
   - `@dependabot ignore this minor version` will close this PR and stop 
Dependabot creating any more for this minor version (unless you reopen the PR 
or upgrade to it yourself)
   - `@dependabot ignore this dependency` will close this PR and stop 
Dependabot creating any more for this dependency (unless you reopen the PR or 
upgrade to it yourself)
   
   
   


-- 
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.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[jira] [Commented] (SUREFIRE-1916) thread blocked freezing progress

2021-06-02 Thread Peter Firmstone (Jira) 


[ 
https://issues.apache.org/jira/browse/SUREFIRE-1916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17356094#comment-17356094
 ] 

Peter Firmstone commented on SUREFIRE-1916:
---

Some more info after killing process, unfortunately the temp files and core 
dump weren't there:

 

[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-surefire-plugin:2.22.2:test (default-test) on 
project jgdms-jeri: There are test failures.
[ERROR]
[ERROR] Please refer to dump files (if any exist) [date].dump, 
[date]-jvmRun[N].dump and [date].dumpstream.
[ERROR] The forked VM terminated without properly saying goodbye. VM crash or 
System.exit called?
[ERROR] Command was cmd.exe /X /C ""C:\Program Files\Zulu\zulu-8\jre\bin\java" 
-jar 
C:\Users\peter\AppData\Local\Temp\surefire8429026880123476667\surefirebooter3364058782169470640.jar
 C:\Users\peter\AppData\Local\Temp\surefire8429026880123476667 
2021-06-03T11-54-14_402-jvmRun1 surefire8868513778729657268tmp 
surefire_21062170392961684426tmp"
[ERROR] Process Exit Code: 0
[ERROR] org.apache.maven.surefire.booter.SurefireBooterForkException: The 
forked VM terminated without properly saying goodbye. VM crash or System.exit 
called?
[ERROR] Command was cmd.exe /X /C ""C:\Program Files\Zulu\zulu-8\jre\bin\java" 
-jar 
C:\Users\peter\AppData\Local\Temp\surefire8429026880123476667\surefirebooter3364058782169470640.jar
 C:\Users\peter\AppData\Local\Temp\surefire8429026880123476667 
2021-06-03T11-54-14_402-jvmRun1 surefire8868513778729657268tmp 
surefire_21062170392961684426tmp"
[ERROR] Process Exit Code: 0
[ERROR] at 
org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:669)
[ERROR] at 
org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:282)
[ERROR] at 
org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:245)
[ERROR] at 
org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider(AbstractSurefireMojo.java:1183)
[ERROR] at 
org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:1011)
[ERROR] at 
org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:857)
[ERROR] at 
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:137)
[ERROR] at 
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:210)
[ERROR] at 
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:156)
[ERROR] at 
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:148)
[ERROR] at 
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)
[ERROR] at 
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)
[ERROR] at 
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:56)
[ERROR] at 
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
[ERROR] at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:305)
[ERROR] at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:192)
[ERROR] at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:105)
[ERROR] at org.apache.maven.cli.MavenCli.execute(MavenCli.java:957)
[ERROR] at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:289)
[ERROR] at org.apache.maven.cli.MavenCli.main(MavenCli.java:193)
[ERROR] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[ERROR] at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
[ERROR] at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
[ERROR] at java.lang.reflect.Method.invoke(Method.java:498)
[ERROR] at 
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:282)
[ERROR] at 
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:225)
[ERROR] at 
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:406)
[ERROR] at 
org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:347)
[ERROR]
[ERROR] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please 
read the following articles:
[ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR] mvn  -rf :jgdms-jeri

> thread blocked freezing progress
> 
>
> Key: SUREFIRE-1916
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1916
> Project: Maven Surefire
>  Issue Type: Bug

[jira] [Created] (SUREFIRE-1916) thread blocked freezing progress

2021-06-02 Thread Peter Firmstone (Jira) 
Peter Firmstone created SUREFIRE-1916:
-

 Summary: thread blocked freezing progress
 Key: SUREFIRE-1916
 URL: https://issues.apache.org/jira/browse/SUREFIRE-1916
 Project: Maven Surefire
  Issue Type: Bug
  Components: Maven Surefire Plugin
Affects Versions: 2.22.2
 Environment: java -version
openjdk version "1.8.0_292"
OpenJDK Runtime Environment (Zulu 8.54.0.21-CA-win64) (build 1.8.0_292-b10)
OpenJDK 64-Bit Server VM (Zulu 8.54.0.21-CA-win64) (build 25.292-b10, mixed 
mode)
Reporter: Peter Firmstone


Thread live lock during reporting.  I'll update to a later release, this is 
very uncommon it's never happened before, just thought I'd report it here.

 


2021-06-03 12:16:36
Full thread dump OpenJDK 64-Bit Server VM (25.292-b10 mixed mode):

"ThreadedStreamConsumer" #40 daemon prio=5 os_prio=0 tid=0x3cd46800 
nid=0x56b8 runnable [0x4118e000]
 java.lang.Thread.State: RUNNABLE
 at java.io.FileOutputStream.writeBytes(Native Method)
 at java.io.FileOutputStream.write(FileOutputStream.java:326)
 at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:82)
 at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:140)
 - locked <0x0003f2a966e0> (a java.io.BufferedOutputStream)
 at java.io.PrintStream.write(PrintStream.java:482)
 - locked <0x0003f2a966c0> (a java.io.PrintStream)
 at sun.nio.cs.StreamEncoder.writeBytes(StreamEncoder.java:221)
 at sun.nio.cs.StreamEncoder.implFlushBuffer(StreamEncoder.java:291)
 at sun.nio.cs.StreamEncoder.flushBuffer(StreamEncoder.java:104)
 - locked <0x0003f2a96808> (a java.io.OutputStreamWriter)
 at java.io.OutputStreamWriter.flushBuffer(OutputStreamWriter.java:185)
 at java.io.PrintStream.write(PrintStream.java:527)
 - locked <0x0003f2a966c0> (a java.io.PrintStream)
 at java.io.PrintStream.print(PrintStream.java:583)
 at org.fusesource.jansi.FilterPrintStream.write(FilterPrintStream.java:99)
 at org.fusesource.jansi.FilterPrintStream.write(FilterPrintStream.java:107)
 at org.fusesource.jansi.FilterPrintStream.print(FilterPrintStream.java:156)
 at org.fusesource.jansi.FilterPrintStream.println(FilterPrintStream.java:231)
 - locked <0x0003f2a70188> (a org.fusesource.jansi.WindowsAnsiPrintStream)
 at org.slf4j.impl.SimpleLogger.write(SimpleLogger.java:318)
 at org.slf4j.impl.SimpleLogger.log(SimpleLogger.java:295)
 at org.slf4j.impl.SimpleLogger.info(SimpleLogger.java:480)
 at org.apache.maven.cli.logging.Slf4jLogger.info(Slf4jLogger.java:59)
 at 
org.apache.maven.plugin.surefire.log.PluginConsoleLogger.info(PluginConsoleLogger.java:77)
 at 
org.apache.maven.plugin.surefire.report.ConsoleReporter.println(ConsoleReporter.java:96)
 at 
org.apache.maven.plugin.surefire.report.ConsoleReporter.testSetCompleted(ConsoleReporter.java:74)
 at 
org.apache.maven.plugin.surefire.report.TestSetRunListener.testSetCompleted(TestSetRunListener.java:183)
 at 
org.apache.maven.plugin.surefire.booterclient.output.ForkClient.processLine(ForkClient.java:227)
 at 
org.apache.maven.plugin.surefire.booterclient.output.ForkClient.consumeLine(ForkClient.java:177)
 at 
org.apache.maven.plugin.surefire.booterclient.output.ThreadedStreamConsumer$Pumper.run(ThreadedStreamConsumer.java:88)
 at java.lang.Thread.run(Thread.java:748)

Locked ownable synchronizers:
 - None

"ping-timer-10s" #39 daemon prio=5 os_prio=0 tid=0x3cd49800 nid=0x5c54 
waiting on condition [0x40e8f000]
 java.lang.Thread.State: WAITING (parking)
 at sun.misc.Unsafe.park(Native Method)
 - parking to wait for <0x00067ff54578> (a 
java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject)
 at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)
 at 
java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2044)
 at 
java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:1081)
 at 
java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:809)
 at 
java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1074)
 at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1134)
 at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
 at java.lang.Thread.run(Thread.java:748)

Locked ownable synchronizers:
 - None

"timeout-check-timer" #37 daemon prio=5 os_prio=0 tid=0x3cd48800 
nid=0x67a4 runnable [0x40a6f000]
 java.lang.Thread.State: TIMED_WAITING (parking)
 at sun.misc.Unsafe.park(Native Method)
 - parking to wait for <0x00067ff585d0> (a 
java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject)
 at java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:215)
 at

[GitHub] [maven-apache-parent] michael-o commented on pull request #40: MPOM-244 upload SHA-512 only for source-release to staging repo

2021-06-02 Thread GitBox 


michael-o commented on pull request #40:
URL: 
https://github.com/apache/maven-apache-parent/pull/40#issuecomment-853395638


   > changed pom.xml version to 23 and ran the same `mvn -Papache-release 
deploy -Daether.checksums.algorithms="SHA-512,SHA-1,MD5"`
   > => perfect staging repository: 
https://repository.apache.org/content/repositories/orgapacheapache-1020/org/apache/apache/23/
   
   That is nice. One can manually delete the redundant files from staging.


-- 
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.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[jira] [Commented] (MSHADE-395) 3.3.0-SNAPSHOT not available in repository

2021-06-02 Thread Michael Osipov (Jira) 


[ 
https://issues.apache.org/jira/browse/MSHADE-395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17355959#comment-17355959
 ] 

Michael Osipov commented on MSHADE-395:
---

No one will make such guarantees.

> 3.3.0-SNAPSHOT not available in repository
> --
>
> Key: MSHADE-395
> URL: https://issues.apache.org/jira/browse/MSHADE-395
> Project: Maven Shade Plugin
>  Issue Type: Bug
>Affects Versions: 3.3.0
>Reporter: Gabriel Wolf
>Priority: Major
>  Labels: 16, 3.3.0, java, snapshot
>
> Hey, i am one of the developers from BetonQuest 
> [https://github.com/BetonQuest/BetonQuest] and we use the maven-shade-plugin.
>  Not we want/need to update to java 16.
> First i had the following issue: 
>  [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-shade-plugin:3.2.4:shade (default) on project 
> betonquest: Error creating shaded jar: Unsupported class file major version 
> 60 -> [Help 1]
> After a small research i found the following: 
> [https://www.reddit.com/r/Maven/comments/mw58hq/mavenshadeplugin_java_16/gvgg6hd/]
> So it seems that 3.3.0-SNAPSHOT 
> ([https://repository.apache.org/content/repositories/snapshots/]) solved my 
> problem, but i run into the same problem, that the snapshot can not be 
> downloaded.
> As a workaround, i tried to run mvn install by my own, and everything works 
> as wanted.
> But this is not working on my buildserver (github actions).
> Is the artifact broken in the repository or is there something else wrong?



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Assigned] (MSHARED-546) Change groupId from org.apache.maven to org.apache.maven.shared

2021-06-02 Thread Sylwester Lachiewicz (Jira) 


 [ 
https://issues.apache.org/jira/browse/MSHARED-546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sylwester Lachiewicz reassigned MSHARED-546:


Assignee: Sylwester Lachiewicz

> Change groupId from org.apache.maven to org.apache.maven.shared
> ---
>
> Key: MSHARED-546
> URL: https://issues.apache.org/jira/browse/MSHARED-546
> Project: Maven Shared Components
>  Issue Type: Improvement
>  Components: maven-archiver
>Affects Versions: maven-archiver-2.5
>Reporter: Karl Heinz Marbaise
>Assignee: Sylwester Lachiewicz
>Priority: Minor
> Fix For: maven-archiver-3.5.2
>
>
> Currently the maven-archiver is located in the groupId {{org.apache.maven}} 
> but it should be in {{org.apache.maven.shared.archiver}} as all other shared 
> components.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (MSHARED-955) Make MavenArchiver.parseOutputTimestamp static

2021-06-02 Thread Sylwester Lachiewicz (Jira) 


 [ 
https://issues.apache.org/jira/browse/MSHARED-955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sylwester Lachiewicz updated MSHARED-955:
-
Fix Version/s: maven-archiver-3.5.2

> Make MavenArchiver.parseOutputTimestamp static
> --
>
> Key: MSHARED-955
> URL: https://issues.apache.org/jira/browse/MSHARED-955
> Project: Maven Shared Components
>  Issue Type: Improvement
>  Components: maven-archiver
>Reporter: Elliotte Rusty Harold
>Assignee: Elliotte Rusty Harold
>Priority: Minor
> Fix For: maven-archiver-3.5.2
>
>
> see 
> [https://github.com/apache/maven-ear-plugin/pull/10#discussion_r481152669] 
> where a new MavenArchiver object is being created (incorrectly) simply to 
> call this method.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (MSHARED-991) Require Java 8

2021-06-02 Thread Sylwester Lachiewicz (Jira) 


 [ 
https://issues.apache.org/jira/browse/MSHARED-991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sylwester Lachiewicz updated MSHARED-991:
-
Fix Version/s: maven-archiver-3.5.2

> Require Java 8
> --
>
> Key: MSHARED-991
> URL: https://issues.apache.org/jira/browse/MSHARED-991
> Project: Maven Shared Components
>  Issue Type: Task
>  Components: maven-archiver
>Reporter: Sylwester Lachiewicz
>Priority: Major
> Fix For: maven-archiver-3.5.2
>
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (MSHARED-991) Require Java 8

2021-06-02 Thread Sylwester Lachiewicz (Jira) 


 [ 
https://issues.apache.org/jira/browse/MSHARED-991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sylwester Lachiewicz updated MSHARED-991:
-
Component/s: maven-archiver

> Require Java 8
> --
>
> Key: MSHARED-991
> URL: https://issues.apache.org/jira/browse/MSHARED-991
> Project: Maven Shared Components
>  Issue Type: Task
>  Components: maven-archiver
>Reporter: Sylwester Lachiewicz
>Priority: Major
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (MSHADE-395) 3.3.0-SNAPSHOT not available in repository

2021-06-02 Thread Gabriel Wolf (Jira) 


[ 
https://issues.apache.org/jira/browse/MSHADE-395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17355956#comment-17355956
 ] 

Gabriel Wolf commented on MSHADE-395:
-

I have no problem, that i use a snapshot. Anyway a snapshot should be available 
under a Snapshot repository.

> 3.3.0-SNAPSHOT not available in repository
> --
>
> Key: MSHADE-395
> URL: https://issues.apache.org/jira/browse/MSHADE-395
> Project: Maven Shade Plugin
>  Issue Type: Bug
>Affects Versions: 3.3.0
>Reporter: Gabriel Wolf
>Priority: Major
>  Labels: 16, 3.3.0, java, snapshot
>
> Hey, i am one of the developers from BetonQuest 
> [https://github.com/BetonQuest/BetonQuest] and we use the maven-shade-plugin.
>  Not we want/need to update to java 16.
> First i had the following issue: 
>  [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-shade-plugin:3.2.4:shade (default) on project 
> betonquest: Error creating shaded jar: Unsupported class file major version 
> 60 -> [Help 1]
> After a small research i found the following: 
> [https://www.reddit.com/r/Maven/comments/mw58hq/mavenshadeplugin_java_16/gvgg6hd/]
> So it seems that 3.3.0-SNAPSHOT 
> ([https://repository.apache.org/content/repositories/snapshots/]) solved my 
> problem, but i run into the same problem, that the snapshot can not be 
> downloaded.
> As a workaround, i tried to run mvn install by my own, and everything works 
> as wanted.
> But this is not working on my buildserver (github actions).
> Is the artifact broken in the repository or is there something else wrong?



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (MSHARED-546) Change groupId from org.apache.maven to org.apache.maven.shared

2021-06-02 Thread Sylwester Lachiewicz (Jira) 


 [ 
https://issues.apache.org/jira/browse/MSHARED-546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sylwester Lachiewicz updated MSHARED-546:
-
Fix Version/s: maven-archiver-3.5.2

> Change groupId from org.apache.maven to org.apache.maven.shared
> ---
>
> Key: MSHARED-546
> URL: https://issues.apache.org/jira/browse/MSHARED-546
> Project: Maven Shared Components
>  Issue Type: Improvement
>  Components: maven-archiver
>Affects Versions: maven-archiver-2.5
>Reporter: Karl Heinz Marbaise
>Priority: Minor
> Fix For: maven-archiver-3.5.2
>
>
> Currently the maven-archiver is located in the groupId {{org.apache.maven}} 
> but it should be in {{org.apache.maven.shared.archiver}} as all other shared 
> components.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (MSHARED-991) Require Java 8

2021-06-02 Thread Sylwester Lachiewicz (Jira) 
Sylwester Lachiewicz created MSHARED-991:


 Summary: Require Java 8
 Key: MSHARED-991
 URL: https://issues.apache.org/jira/browse/MSHARED-991
 Project: Maven Shared Components
  Issue Type: Task
Reporter: Sylwester Lachiewicz






--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[GitHub] [maven-apache-parent] hboutemy commented on pull request #40: MPOM-244 upload SHA-512 only for source-release to staging repo

2021-06-02 Thread GitBox 


hboutemy commented on pull request #40:
URL: 
https://github.com/apache/maven-apache-parent/pull/40#issuecomment-853358621


   changed pom.xml version to 23 and ran the same `mvn -Papache-release deploy 
-Daether.checksums.algorithms="SHA-512,SHA-1,MD5"`
   => perfect staging repository: 
https://repository.apache.org/content/repositories/orgapacheapache-1020/org/apache/apache/23/


-- 
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.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [maven-apache-parent] hboutemy commented on pull request #40: MPOM-244 upload SHA-512 only for source-release to staging repo

2021-06-02 Thread GitBox 


hboutemy commented on pull request #40:
URL: 
https://github.com/apache/maven-apache-parent/pull/40#issuecomment-853356689


   oh nice, I didn't know that content!
   I ran `mvn -Papache-release deploy 
-Daether.checksums.algorithms="SHA-512,SHA-1,MD5"` and got id 86 of 
https://repository.apache.org/content/repositories/snapshots/org/apache/apache/24-SNAPSHOT/
   no problem for now


-- 
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.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [maven-apache-parent] michael-o commented on pull request #40: MPOM-244 upload SHA-512 only for source-release to staging repo

2021-06-02 Thread GitBox 


michael-o commented on pull request #40:
URL: 
https://github.com/apache/maven-apache-parent/pull/40#issuecomment-853342953


   > 
   > 
   > > People can already configure it. I just want to avoid surprises for all 
Apache folks. E.g., Mark Thomas does this actively now.
   > 
   > can you show me, please? I don't know how to do that
   > 
   > notice: I mean using Maven, because that's the Maven ASF parent POM that 
we're tweaking...
   
   See https://maven.apache.org/resolver/configuration.html for 
`aether.checksums.algorithms=SHA-512`. Resolver should generate and update 
them. Please try in your setup.


-- 
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.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [maven-apache-parent] michael-o commented on pull request #40: MPOM-244 upload SHA-512 only for source-release to staging repo

2021-06-02 Thread GitBox 


michael-o commented on pull request #40:
URL: 
https://github.com/apache/maven-apache-parent/pull/40#issuecomment-853342182


   > 
   > 
   > FYI, I added some instructions to calculate sha512 in dist: 
[apache/maven-site@29bc21e](https://github.com/apache/maven-site/commit/29bc21e3dc9d2bb7ff61ce49cecf8a8600b9b5d1)
   > and while at it, I recalculated checksums for all our latest releases and 
found 6 fingerprints not exactly using the expected format (fixed in revision 
48099): this shows concrete example how people struggle to add the sha512 to 
dist area...
   
   I have done this massively in Core ITs: 
https://github.com/apache/maven-integration-testing/commit/672728a363c8b3503250589504efbfbea152e7e9


-- 
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.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [maven-apache-parent] hboutemy commented on pull request #40: MPOM-244 upload SHA-512 only for source-release to staging repo

2021-06-02 Thread GitBox 


hboutemy commented on pull request #40:
URL: 
https://github.com/apache/maven-apache-parent/pull/40#issuecomment-853339600


   > People can already configure it. I just want to avoid surprises for all 
Apache folks. E.g., Mark Thomas does this actively now.
   
   can you show me, please? I don't know how to do that
   
   notice: I mean using Maven, because that's the Maven ASF parent POM that 
we're tweaking...


-- 
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.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [maven-apache-parent] hboutemy commented on pull request #40: MPOM-244 upload SHA-512 only for source-release to staging repo

2021-06-02 Thread GitBox 


hboutemy commented on pull request #40:
URL: 
https://github.com/apache/maven-apache-parent/pull/40#issuecomment-853338590


   FYI, I added some instructions to calculate sha512 in dist: 
https://github.com/apache/maven-site/commit/29bc21e3dc9d2bb7ff61ce49cecf8a8600b9b5d1
   and while at it, I recalculated checksums for all our latest releases and 
found 6 fingerprints not exactly using the expected format (fixed in revision 
48099): this shows concrete example how people struggle to add the sha512 to 
dist area...


-- 
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.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [maven-apache-parent] michael-o commented on pull request #40: MPOM-244 upload SHA-512 only for source-release to staging repo

2021-06-02 Thread GitBox 


michael-o commented on pull request #40:
URL: 
https://github.com/apache/maven-apache-parent/pull/40#issuecomment-853336228


   See here: 
https://repo1.maven.org/maven2/org/apache/tomcat/tomcat-catalina/10.0.6/
   
   Produced by Resoler via Ant.


-- 
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.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [maven-apache-parent] michael-o commented on pull request #40: MPOM-244 upload SHA-512 only for source-release to staging repo

2021-06-02 Thread GitBox 


michael-o commented on pull request #40:
URL: 
https://github.com/apache/maven-apache-parent/pull/40#issuecomment-853335882


   > 
   > 
   > the day Maven Resolver will be configured to upload sha512, we'll remove 
this hack (because, yes, it's a hack to ease our release process)
   > When do you expect Maven Resolver to publish sha512 in addition to sha1 
and md5 in real world?
   
   People can already configure it. I just want to avoid surprises for all 
Apache folks. E.g., Mark Thomas does this actively now.


-- 
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.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [maven-apache-parent] hboutemy commented on pull request #40: MPOM-244 upload SHA-512 only for source-release to staging repo

2021-06-02 Thread GitBox 


hboutemy commented on pull request #40:
URL: 
https://github.com/apache/maven-apache-parent/pull/40#issuecomment-853335146


   the day Maven Resolver will be configured to upload sha512, we'll remove 
this hack (because, yes, it's a hack to ease our release process)
   When do you expect Maven Resolver to publish sha512 in addition to sha1 and 
md5 in real world?


-- 
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.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [maven-apache-parent] michael-o commented on pull request #40: MPOM-244 upload SHA-512 only for source-release to staging repo

2021-06-02 Thread GitBox 


michael-o commented on pull request #40:
URL: 
https://github.com/apache/maven-apache-parent/pull/40#issuecomment-853328882


   @hboutemy I wonder what will happen during a release: Maven Resolver uploads 
SHA-512, this change uploads it. Will Nexus staging reject it? This should be 
tested before merged.


-- 
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.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [maven-apache-parent] hboutemy edited a comment on pull request #40: MPOM-244 upload SHA-512 only for source-release to staging repo

2021-06-02 Thread GitBox 


hboutemy edited a comment on pull request #40:
URL: 
https://github.com/apache/maven-apache-parent/pull/40#issuecomment-853323824


   FYI, I tried `mvn -Papache-release deploy` with the sha512 attachments and 
got 
https://repository.apache.org/content/repositories/snapshots/org/apache/apache/24-SNAPSHOT/
   as expected, unwanted 
`apache-24-20210602.192221-85-source-release.zip.sha512.md5` and 
`apache-24-20210602.192221-85-source-release.zip.sha512.sha1` are there, but it 
works


-- 
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.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [maven-apache-parent] hboutemy commented on pull request #40: MPOM-244 upload SHA-512 only for source-release to staging repo

2021-06-02 Thread GitBox 


hboutemy commented on pull request #40:
URL: 
https://github.com/apache/maven-apache-parent/pull/40#issuecomment-853323824


   FYI, I tried `mvn -Papache-release deploy` with the sha512 attachments and 
got 
https://repository.apache.org/content/repositories/snapshots/org/apache/apache/24-SNAPSHOT/


-- 
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.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [maven-doxia-linkcheck] michael-o commented on pull request #7: remove dependency on Modello

2021-06-02 Thread GitBox 


michael-o commented on pull request #7:
URL: 
https://github.com/apache/maven-doxia-linkcheck/pull/7#issuecomment-853322238


   I don't understand who those two issues are related to Modello. For me, 
Modello works in Eclipse. I am against adding generated code. I would prefer to 
retire this component with the next release and recommend: 
https://validator.w3.org/checklink


-- 
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.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[jira] [Closed] (MDEP-747) analyze-only failed: Unsupported class file major version 61 (Java 17)

2021-06-02 Thread Herve Boutemy (Jira) 


 [ 
https://issues.apache.org/jira/browse/MDEP-747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Herve Boutemy closed MDEP-747.
--
Resolution: Fixed

thanks for the followup, [~namannigam12]

> analyze-only failed: Unsupported class file major version 61 (Java 17)
> --
>
> Key: MDEP-747
> URL: https://issues.apache.org/jira/browse/MDEP-747
> Project: Maven Dependency Plugin
>  Issue Type: Bug
>  Components: analyze
>Affects Versions: 3.1.2
> Environment: OpenJDK 17 on MacOS
>Reporter: Naman Nigam
>Assignee: Sylwester Lachiewicz
>Priority: Major
> Fix For: 3.2.0
>
>
> Goal org.apache.maven.plugins:maven-dependency-plugin:3.1.2:analyze-only does 
> not work with Java 17. ASM has to be updated to use [version 
> 9.1|https://asm.ow2.io/versions.html] or later.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Comment Edited] (MSHADE-395) 3.3.0-SNAPSHOT not available in repository

2021-06-02 Thread Michael Osipov (Jira) 


[ 
https://issues.apache.org/jira/browse/MSHADE-395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17355865#comment-17355865
 ] 

Michael Osipov edited comment on MSHADE-395 at 6/2/21, 5:06 PM:


11th commandment: Thou shalt not rely on snapshots.


was (Author: michael-o):
11th commandment: One shall not rely on snapshots.

> 3.3.0-SNAPSHOT not available in repository
> --
>
> Key: MSHADE-395
> URL: https://issues.apache.org/jira/browse/MSHADE-395
> Project: Maven Shade Plugin
>  Issue Type: Bug
>Affects Versions: 3.3.0
>Reporter: Gabriel Wolf
>Priority: Major
>  Labels: 16, 3.3.0, java, snapshot
>
> Hey, i am one of the developers from BetonQuest 
> [https://github.com/BetonQuest/BetonQuest] and we use the maven-shade-plugin.
>  Not we want/need to update to java 16.
> First i had the following issue: 
>  [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-shade-plugin:3.2.4:shade (default) on project 
> betonquest: Error creating shaded jar: Unsupported class file major version 
> 60 -> [Help 1]
> After a small research i found the following: 
> [https://www.reddit.com/r/Maven/comments/mw58hq/mavenshadeplugin_java_16/gvgg6hd/]
> So it seems that 3.3.0-SNAPSHOT 
> ([https://repository.apache.org/content/repositories/snapshots/]) solved my 
> problem, but i run into the same problem, that the snapshot can not be 
> downloaded.
> As a workaround, i tried to run mvn install by my own, and everything works 
> as wanted.
> But this is not working on my buildserver (github actions).
> Is the artifact broken in the repository or is there something else wrong?



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (MSHADE-395) 3.3.0-SNAPSHOT not available in repository

2021-06-02 Thread Michael Osipov (Jira) 


[ 
https://issues.apache.org/jira/browse/MSHADE-395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17355865#comment-17355865
 ] 

Michael Osipov commented on MSHADE-395:
---

11th commandment: One shall not rely on snapshots.

> 3.3.0-SNAPSHOT not available in repository
> --
>
> Key: MSHADE-395
> URL: https://issues.apache.org/jira/browse/MSHADE-395
> Project: Maven Shade Plugin
>  Issue Type: Bug
>Affects Versions: 3.3.0
>Reporter: Gabriel Wolf
>Priority: Major
>  Labels: 16, 3.3.0, java, snapshot
>
> Hey, i am one of the developers from BetonQuest 
> [https://github.com/BetonQuest/BetonQuest] and we use the maven-shade-plugin.
>  Not we want/need to update to java 16.
> First i had the following issue: 
>  [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-shade-plugin:3.2.4:shade (default) on project 
> betonquest: Error creating shaded jar: Unsupported class file major version 
> 60 -> [Help 1]
> After a small research i found the following: 
> [https://www.reddit.com/r/Maven/comments/mw58hq/mavenshadeplugin_java_16/gvgg6hd/]
> So it seems that 3.3.0-SNAPSHOT 
> ([https://repository.apache.org/content/repositories/snapshots/]) solved my 
> problem, but i run into the same problem, that the snapshot can not be 
> downloaded.
> As a workaround, i tried to run mvn install by my own, and everything works 
> as wanted.
> But this is not working on my buildserver (github actions).
> Is the artifact broken in the repository or is there something else wrong?



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[GitHub] [maven-shared-utils] elharo opened a new pull request #92: fix double typo

2021-06-02 Thread GitBox 


elharo opened a new pull request #92:
URL: https://github.com/apache/maven-shared-utils/pull/92


   @slachiewicz 


-- 
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.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [maven-shared-utils] kwin commented on a change in pull request #54: rework directory scanner to ensure it can enforce exclusions and it uses path

2021-06-02 Thread GitBox 


kwin commented on a change in pull request #54:
URL: https://github.com/apache/maven-shared-utils/pull/54#discussion_r644008249



##
File path: 
src/main/java/org/apache/maven/shared/utils/io/conductor/EnforceExcludesOverIncludes.java
##
@@ -0,0 +1,58 @@
+package org.apache.maven.shared.utils.io.conductor;
+
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one
+ * or more contributor license agreements.  See the NOTICE file
+ * distributed with this work for additional information
+ * regarding copyright ownership.  The ASF licenses this file
+ * to you under the Apache License, Version 2.0 (the
+ * "License"); you may not use this file except in compliance
+ * with the License.  You may obtain a copy of the License at
+ *
+ *  http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing,
+ * software distributed under the License is distributed on an
+ * "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ * KIND, either express or implied.  See the License for the
+ * specific language governing permissions and limitations
+ * under the License.
+ */
+
+import org.apache.maven.shared.utils.io.DirectoryScanner;
+import org.apache.maven.shared.utils.io.MatchPatterns;
+import org.apache.maven.shared.utils.io.ScanConductor;
+import org.apache.maven.shared.utils.io.ScannerAware;
+
+import java.io.File;
+
+/**
+ * If an exclude is defined on a folder it does not visit of the children
+ * even if some include can match children.
+ */
+public class EnforceExcludesOverIncludes implements ScanConductor, ScannerAware

Review comment:
   Wouldn't it make sense if this class would directly implement 
https://docs.oracle.com/javase/7/docs/api/java/nio/file/DirectoryStream.Filter.html
 instead? That way one could get rid of the ScanConductor interface...




-- 
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.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[jira] [Updated] (MCHANGES-399) change report: add further column: date

2021-06-02 Thread Michael Osipov (Jira) 


 [ 
https://issues.apache.org/jira/browse/MCHANGES-399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Osipov updated MCHANGES-399:

Fix Version/s: waiting-for-feedback

> change report: add further column: date 
> 
>
> Key: MCHANGES-399
> URL: https://issues.apache.org/jira/browse/MCHANGES-399
> Project: Maven Changes Plugin
>  Issue Type: New Feature
>Reporter: Ernst Reissner
>Priority: Major
> Fix For: waiting-for-feedback
>
>
> As an action in a changes file
> has the attributes dev, type, date and allows for description text,
> would be nice if for all of that there were a column in the changes report.
> Only the date is missing.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (MSHARED-989) Undeprecate DirectoryScanner and MatchPattern(s)

2021-06-02 Thread Romain Manni-Bucau (Jira) 


[ 
https://issues.apache.org/jira/browse/MSHARED-989?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17355768#comment-17355768
 ] 

Romain Manni-Bucau commented on MSHARED-989:


[~kwin] IIRC it was the idea yes

> Undeprecate DirectoryScanner and MatchPattern(s)
> 
>
> Key: MSHARED-989
> URL: https://issues.apache.org/jira/browse/MSHARED-989
> Project: Maven Shared Components
>  Issue Type: Improvement
>  Components: maven-shared-utils
>Reporter: Konrad Windszus
>Priority: Major
>
> In MSHARED-898 {{DirectoryScanner}} has been deprecated. Instead using the 
> {{java.nio.file.DirectoryStream}} is now recommended.
> The latter is often no replacement as the parametrization of DirectoryScanner 
> with Ant-style globs for includes/excludes is not supported. Also the 
> {{DEFAULTEXCLUDES}} are not part of Java NIO {{DirectoryStream}} either.
> The same applies to {{MatchPatterns}}, which is deprecated and now recommends 
> using {{java.nio.filejava.nio.file.DirectoryStream.Filter}}. Please 
> instead provide a Filter for Java NIO for those patterns (regex and ant) and 
> make {{DirectoryScanner}} use File NIO internally while keeping API 
> compatibility.
> Otherwise every consumer of DirectoryScanner needs to come up with a custom 
> implementation of pattern matching and a lot of glue code.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[GitHub] [maven-shared-utils] kwin commented on a change in pull request #54: rework directory scanner to ensure it can enforce exclusions and it uses path

2021-06-02 Thread GitBox 


kwin commented on a change in pull request #54:
URL: https://github.com/apache/maven-shared-utils/pull/54#discussion_r644008249



##
File path: 
src/main/java/org/apache/maven/shared/utils/io/conductor/EnforceExcludesOverIncludes.java
##
@@ -0,0 +1,58 @@
+package org.apache.maven.shared.utils.io.conductor;
+
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one
+ * or more contributor license agreements.  See the NOTICE file
+ * distributed with this work for additional information
+ * regarding copyright ownership.  The ASF licenses this file
+ * to you under the Apache License, Version 2.0 (the
+ * "License"); you may not use this file except in compliance
+ * with the License.  You may obtain a copy of the License at
+ *
+ *  http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing,
+ * software distributed under the License is distributed on an
+ * "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ * KIND, either express or implied.  See the License for the
+ * specific language governing permissions and limitations
+ * under the License.
+ */
+
+import org.apache.maven.shared.utils.io.DirectoryScanner;
+import org.apache.maven.shared.utils.io.MatchPatterns;
+import org.apache.maven.shared.utils.io.ScanConductor;
+import org.apache.maven.shared.utils.io.ScannerAware;
+
+import java.io.File;
+
+/**
+ * If an exclude is defined on a folder it does not visit of the children
+ * even if some include can match children.
+ */
+public class EnforceExcludesOverIncludes implements ScanConductor, ScannerAware

Review comment:
   Wouldn't it make class if this would directly implement 
https://docs.oracle.com/javase/7/docs/api/java/nio/file/DirectoryStream.Filter.html
 instead? That way one could get rid of the ScanConductor interface...




-- 
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.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [maven-shared-utils] kwin commented on pull request #54: rework directory scanner to ensure it can enforce exclusions and it uses path

2021-06-02 Thread GitBox 


kwin commented on pull request #54:
URL: https://github.com/apache/maven-shared-utils/pull/54#issuecomment-853062525


   IMHO this is relevant and would fix 
https://issues.apache.org/jira/browse/MSHARED-989.


-- 
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.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[jira] [Commented] (MSHARED-989) Undeprecate DirectoryScanner and MatchPattern(s)

2021-06-02 Thread Konrad Windszus (Jira) 


[ 
https://issues.apache.org/jira/browse/MSHARED-989?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17355754#comment-17355754
 ] 

Konrad Windszus commented on MSHARED-989:
-

I think this is mostly already provided in 
https://github.com/apache/maven-shared-utils/pull/54. [~romain.manni-bucau] Is 
my understanding correct?

> Undeprecate DirectoryScanner and MatchPattern(s)
> 
>
> Key: MSHARED-989
> URL: https://issues.apache.org/jira/browse/MSHARED-989
> Project: Maven Shared Components
>  Issue Type: Improvement
>  Components: maven-shared-utils
>Reporter: Konrad Windszus
>Priority: Major
>
> In MSHARED-898 {{DirectoryScanner}} has been deprecated. Instead using the 
> {{java.nio.file.DirectoryStream}} is now recommended.
> The latter is often no replacement as the parametrization of DirectoryScanner 
> with Ant-style globs for includes/excludes is not supported. Also the 
> {{DEFAULTEXCLUDES}} are not part of Java NIO {{DirectoryStream}} either.
> The same applies to {{MatchPatterns}}, which is deprecated and now recommends 
> using {{java.nio.filejava.nio.file.DirectoryStream.Filter}}. Please 
> instead provide a Filter for Java NIO for those patterns (regex and ant) and 
> make {{DirectoryScanner}} use File NIO internally while keeping API 
> compatibility.
> Otherwise every consumer of DirectoryScanner needs to come up with a custom 
> implementation of pattern matching and a lot of glue code.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (MCHANGES-399) change report: add further column: date

2021-06-02 Thread Michael Osipov (Jira) 


[ 
https://issues.apache.org/jira/browse/MCHANGES-399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17355726#comment-17355726
 ] 

Michael Osipov commented on MCHANGES-399:
-

Did you check 
https://maven.apache.org/plugins/maven-changes-plugin/changes-report-mojo.html#addActionDate?

> change report: add further column: date 
> 
>
> Key: MCHANGES-399
> URL: https://issues.apache.org/jira/browse/MCHANGES-399
> Project: Maven Changes Plugin
>  Issue Type: New Feature
>Reporter: Ernst Reissner
>Priority: Major
>
> As an action in a changes file
> has the attributes dev, type, date and allows for description text,
> would be nice if for all of that there were a column in the changes report.
> Only the date is missing.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (MSHADE-395) 3.3.0-SNAPSHOT not available in repository

2021-06-02 Thread Gabriel Wolf (Jira) 


 [ 
https://issues.apache.org/jira/browse/MSHADE-395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Gabriel Wolf updated MSHADE-395:

Description: 
Hey, i am one of the developers from BetonQuest 
[https://github.com/BetonQuest/BetonQuest] and we use the maven-shade-plugin.
 Not we want/need to update to java 16.

First i had the following issue: 
 [ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-shade-plugin:3.2.4:shade (default) on project 
betonquest: Error creating shaded jar: Unsupported class file major version 60 
-> [Help 1]

After a small research i found the following: 
[https://www.reddit.com/r/Maven/comments/mw58hq/mavenshadeplugin_java_16/gvgg6hd/]

So it seems that 3.3.0-SNAPSHOT 
([https://repository.apache.org/content/repositories/snapshots/]) solved my 
problem, but i run into the same problem, that the snapshot can not be 
downloaded.

As a workaround, i tried to run mvn install by my own, and everything works as 
wanted.

But this is not working on my buildserver (github actions).

Is the artifact broken in the repository or is there something else wrong?

  was:
Hey, i am one of the developers from BetonQuest 
[https://github.com/BetonQuest/BetonQuest] and we use the maven-shade-plugin.
Not we want/need to update to java 16.

First i had the following issue: 
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-shade-plugin:3.2.4:shade (default) on project 
betonquest: Error creating shaded jar: Unsupported class file major version 60 
-> [Help 1]

After a small research i found the following: 
[https://www.reddit.com/r/Maven/comments/mw58hq/mavenshadeplugin_java_16/gvgg6hd/]

So it seems that 3.3.0-SNAPSHOT solved my problem, but i run into the same 
problem, that the snapshot can not be downloaded.

As a workaround, i tried to run mvn install by my own, and everything works as 
wanted.

But this is not working on my buildserver (github actions).

Is the artifact broken in the repository or is there something else wrong?


> 3.3.0-SNAPSHOT not available in repository
> --
>
> Key: MSHADE-395
> URL: https://issues.apache.org/jira/browse/MSHADE-395
> Project: Maven Shade Plugin
>  Issue Type: Bug
>Affects Versions: 3.3.0
>Reporter: Gabriel Wolf
>Priority: Major
>  Labels: 16, 3.3.0, java, snapshot
>
> Hey, i am one of the developers from BetonQuest 
> [https://github.com/BetonQuest/BetonQuest] and we use the maven-shade-plugin.
>  Not we want/need to update to java 16.
> First i had the following issue: 
>  [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-shade-plugin:3.2.4:shade (default) on project 
> betonquest: Error creating shaded jar: Unsupported class file major version 
> 60 -> [Help 1]
> After a small research i found the following: 
> [https://www.reddit.com/r/Maven/comments/mw58hq/mavenshadeplugin_java_16/gvgg6hd/]
> So it seems that 3.3.0-SNAPSHOT 
> ([https://repository.apache.org/content/repositories/snapshots/]) solved my 
> problem, but i run into the same problem, that the snapshot can not be 
> downloaded.
> As a workaround, i tried to run mvn install by my own, and everything works 
> as wanted.
> But this is not working on my buildserver (github actions).
> Is the artifact broken in the repository or is there something else wrong?



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (MCHANGES-374) Allow OAuth authentication in Jira

2021-06-02 Thread Michael Osipov (Jira) 


[ 
https://issues.apache.org/jira/browse/MCHANGES-374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17355719#comment-17355719
 ] 

Michael Osipov commented on MCHANGES-374:
-

OAuth isn't authentication.

> Allow OAuth authentication in Jira
> --
>
> Key: MCHANGES-374
> URL: https://issues.apache.org/jira/browse/MCHANGES-374
> Project: Maven Changes Plugin
>  Issue Type: New Feature
>  Components: jira
>Reporter: Angel Cervera Claudio
>Priority: Major
>
> The only way to access to Jira is using User/Password.
> Usually, because security issues, is not an option in big companies so it is 
> necessary to use other authentication systems, like tokens or OAuth.
> Jira implements OAuth, so this would be the best option to avoid hard coded 
> passwords.
> Documentation: 
> https://developer.atlassian.com/jiradev/jira-apis/jira-rest-apis/jira-rest-api-tutorials/jira-rest-api-example-oauth-authentication



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (MSHADE-395) 3.3.0-SNAPSHOT not available in repository

2021-06-02 Thread Gabriel Wolf (Jira) 
Gabriel Wolf created MSHADE-395:
---

 Summary: 3.3.0-SNAPSHOT not available in repository
 Key: MSHADE-395
 URL: https://issues.apache.org/jira/browse/MSHADE-395
 Project: Maven Shade Plugin
  Issue Type: Bug
Affects Versions: 3.3.0
Reporter: Gabriel Wolf


Hey, i am one of the developers from BetonQuest 
[https://github.com/BetonQuest/BetonQuest] and we use the maven-shade-plugin.
Not we want/need to update to java 16.

First i had the following issue: 
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-shade-plugin:3.2.4:shade (default) on project 
betonquest: Error creating shaded jar: Unsupported class file major version 60 
-> [Help 1]

After a small research i found the following: 
[https://www.reddit.com/r/Maven/comments/mw58hq/mavenshadeplugin_java_16/gvgg6hd/]

So it seems that 3.3.0-SNAPSHOT solved my problem, but i run into the same 
problem, that the snapshot can not be downloaded.

As a workaround, i tried to run mvn install by my own, and everything works as 
wanted.

But this is not working on my buildserver (github actions).

Is the artifact broken in the repository or is there something else wrong?



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[GitHub] [maven-dependency-plugin] van-vliet commented on pull request #133: [MDEP-739] Dependency Plugin go-offline doesn't respect artifact classifier

2021-06-02 Thread GitBox 


van-vliet commented on pull request #133:
URL: 
https://github.com/apache/maven-dependency-plugin/pull/133#issuecomment-852882664


   @michael-o I am not sure how to describe the cruciality to you. I can 
describe the impact of not seeing this change released:
   
   My colleagues and I have a couple of projects that encounter this issue. 
Without an official release, we have the following options:
   1. Change our CI pipeline so it does not use go-offline
   1. Re-release dependencies that have a classifier with a new name and no 
classifier
   1. Release a forked version of the maven-dependency-plugin and use that in 
our CI pipeline.
   
   Option 1 is a huge task that will affect all of our builds and will require 
a lot of work.
   Option 2 is possible since we have only seen this issue with a single 
dependency so far. Version bumps and other dependencies with classifiers will 
make this option unsustainable in the long term. 
   Option 3 would fix the issue, but would require maintenance until we can 
switch back to an official release. We have no interest in maintaining a fork 
with just a single bugfix.
   
   Neither options are good for us. They all require a significant amount of 
effort to implement. Without an official release, we implement the least effort 
workaround, which is probably is option 3.
   
   
[MDEP-739](https://issues.apache.org/jira/projects/MDEP/issues/MDEP-739?filter=allopenissues)
 was reported by someone else, so at least one other person has encountered the 
issue and would benefit from the change.


-- 
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.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [maven] gnodet commented on pull request #413: [MNG-6843] Thread-safe artifacts in MavenProject

2021-06-02 Thread GitBox 


gnodet commented on pull request #413:
URL: https://github.com/apache/maven/pull/413#issuecomment-852829527


   @Tibor17 See https://github.com/apache/maven/pull/475


-- 
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.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [maven] gnodet commented on pull request #476: [MNG-7156] Parallel build can cause issues between clean and forked g…

2021-06-02 Thread GitBox 


gnodet commented on pull request #476:
URL: https://github.com/apache/maven/pull/476#issuecomment-852804630


   > Will this also resolve `-DdeployAtEnd=true`?
   
   I don't understand.  This only adds a locking mechanism to avoid conflicts 
caused by parallel execution between the normal lifecycle and forked 
lifecycles, which can cause the same project to be build twice concurrently.  
This has nothing to do with `deployAtEnd` afaik.


-- 
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.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[jira] [Commented] (MDEP-568) dependency:go-offline -DexcludeGroupIds=xxxx still try to resolve artifacts in the excluded group xxxx

2021-06-02 Thread Hudson (Jira) 


[ 
https://issues.apache.org/jira/browse/MDEP-568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17355526#comment-17355526
 ] 

Hudson commented on MDEP-568:
-

Build succeeded in Jenkins: Maven » Maven TLP » maven-dependency-plugin » 
MDEP-568_go-offline_filter #3

See 
https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven-dependency-plugin/job/MDEP-568_go-offline_filter/3/

> dependency:go-offline -DexcludeGroupIds= still try to resolve artifacts 
> in the excluded group 
> --
>
> Key: MDEP-568
> URL: https://issues.apache.org/jira/browse/MDEP-568
> Project: Maven Dependency Plugin
>  Issue Type: Bug
>  Components: go-offline, resolve
>Affects Versions: 2.3, 3.0.0
> Environment: windows / cygwin xp64 bit / bash / maven 3.0.3
>Reporter: Archimedes Trajano
>Priority: Major
> Attachments: MDEP-568-maven-dependency-plugin.patch, 
> go-offline_copy-dependencies_patch_sample.zip, test.tgz
>
>
> see thread: 
> http://mail-archives.apache.org/mod_mbox/maven-users/201109.mbox/%3c0B02C46601D44673A4A2DF4C4F907E9E@black%3e
> in attached sample pom structure:
> mvn org.apache.maven.plugins:maven-dependency-plugin:2.3:go-offline 
> -DexcludeGroupIds=us.pdinc.foo.maven.test
> fails



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[GitHub] [maven] bmarwell commented on pull request #476: [MNG-7156] Parallel build can cause issues between clean and forked g…

2021-06-02 Thread GitBox 


bmarwell commented on pull request #476:
URL: https://github.com/apache/maven/pull/476#issuecomment-852784225


   Will this also resolve `-DdeployAtEnd=true`?


-- 
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.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [maven] gnodet opened a new pull request #476: [MNG-7156] Parallel build can cause issues between clean and forked g…

2021-06-02 Thread GitBox 


gnodet opened a new pull request #476:
URL: https://github.com/apache/maven/pull/476


   …oals
   
   Following this checklist to help us incorporate your 
   contribution quickly and easily:
   
- [ ] Make sure there is a [JIRA 
issue](https://issues.apache.org/jira/browse/MNG) filed 
  for the change (usually before you start working on it).  Trivial 
changes like typos do not 
  require a JIRA issue.  Your pull request should address just this 
issue, without 
  pulling in other changes.
- [ ] Each commit in the pull request should have a meaningful subject line 
and body.
- [ ] Format the pull request title like `[MNG-XXX] - Fixes bug in 
ApproximateQuantiles`,
  where you replace `MNG-XXX` with the appropriate JIRA issue. Best 
practice
  is to use the JIRA issue title in the pull request title and in the 
first line of the 
  commit message.
- [ ] Write a pull request description that is detailed enough to 
understand what the pull request does, how, and why.
- [ ] Run `mvn clean verify` to make sure basic checks pass. A more 
thorough check will 
  be performed on your pull request automatically.
- [ ] You have run the [Core IT][core-its] successfully.
   
   If your pull request is about ~20 lines of code you don't need to sign an
   [Individual Contributor License 
Agreement](https://www.apache.org/licenses/icla.pdf) if you are unsure
   please ask on the developers list.
   
   To make clear that you license your contribution under 
   the [Apache License Version 2.0, January 
2004](http://www.apache.org/licenses/LICENSE-2.0)
   you have to acknowledge this by using the following check-box.
   
- [ ] I hereby declare this contribution to be licenced under the [Apache 
License Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0)
   
- [ ] In any other case, please file an [Apache Individual Contributor 
License Agreement](https://www.apache.org/licenses/icla.pdf).
   
   [core-its]: https://maven.apache.org/core-its/core-it-suite/
   


-- 
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.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [maven-dependency-plugin] michael-o commented on pull request #133: [MDEP-739] Dependency Plugin go-offline doesn't respect artifact classifier

2021-06-02 Thread GitBox 


michael-o commented on pull request #133:
URL: 
https://github.com/apache/maven-dependency-plugin/pull/133#issuecomment-852777381


   @van-vliet How crucial is is change for you?


-- 
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.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org