[GitHub] olamy commented on issue #197: SUREFIRE-1588 Patch (Java7)
olamy commented on issue #197: SUREFIRE-1588 Patch (Java7) URL: https://github.com/apache/maven-surefire/pull/197#issuecomment-434910977 +1 to have this released ASAP as it's really blocker. This is an automated message from the Apache Git Service. To respond to the message, please log on 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 With regards, Apache Git Services
[jira] [Commented] (SUREFIRE-1588) Surefire manifest jar classloading broken on latest Debian/Ubuntu Java8
[
https://issues.apache.org/jira/browse/SUREFIRE-1588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16671038#comment-16671038
]
ASF GitHub Bot commented on SUREFIRE-1588:
--
olamy commented on issue #197: SUREFIRE-1588 Patch (Java7)
URL: https://github.com/apache/maven-surefire/pull/197#issuecomment-434910977
+1 to have this released ASAP as it's really blocker.
This is an automated message from the Apache Git Service.
To respond to the message, please log on 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
> Surefire manifest jar classloading broken on latest Debian/Ubuntu Java8
> ---
>
> Key: SUREFIRE-1588
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1588
> Project: Maven Surefire
> Issue Type: Bug
>Affects Versions: 2.22.1
>Reporter: Cservenak, Tamas
>Priority: Major
>
> See issue [1], but in short: latest Java8 on Ubuntu/Debian/Mint family of
> Linuxes (am on Mint, Ubuntu derivative) contains this patch [3], and eforces
> Manifest class path entries to be relative, as defined in [2].
> Hence, surefire booter and rest of Maven classpath, that uses absolute URLs
> are simply discarded.
> Example error:
> {noformat}
> # Created at 2018-10-30T21:34:43.339
> Error: Could not find or load main class
> org.apache.maven.surefire.booter.ForkedBooter{noformat}
> using the new property
> {{-Djdk.net.URLClassPath.disableClassPathURLCheck=debug}} clearly shows that
> all the entries from the surefire JAR are simply ignored.
>
> [1] [https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911925]
> [2]
> https://docs.oracle.com/javase/8/docs/technotes/guides/jar/jar.html#classpath
> [3] [https://hg.openjdk.java.net/jdk/jdk/rev/27135de165ac]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (MANT-88) a scan is already progress
[ https://issues.apache.org/jira/browse/MANT-88?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wesval updated MANT-88: --- Description: in our apps we happened to get these error messages,click the scan button for the first time the phone just ask for the authority and while we give the promision,it doesn't answer.when we click the button second time it showed the error message:An error happened - A scan is already in progress > a scan is already progress > -- > > Key: MANT-88 > URL: https://issues.apache.org/jira/browse/MANT-88 > Project: Maven Ant Plugin > Issue Type: New Feature >Reporter: wesval >Priority: Major > > in our apps we happened to get these error messages,click the scan button for > the first time the phone just ask for the authority and while we give the > promision,it doesn't answer.when we click the button second time it showed > the error message:An error happened - A scan is already in progress -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (MANT-88) a scan is already progress
wesval created MANT-88: -- Summary: a scan is already progress Key: MANT-88 URL: https://issues.apache.org/jira/browse/MANT-88 Project: Maven Ant Plugin Issue Type: New Feature Reporter: wesval -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MSITE-828) Jdk 1.8 required / Upgrade Jetty Version 9.4.12
[ https://issues.apache.org/jira/browse/MSITE-828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16671021#comment-16671021 ] ASF GitHub Bot commented on MSITE-828: -- olamy commented on issue #3: [MSITE-828] Upgrade jetty to recent version. Update to java 1.8 (required for jetty) URL: https://github.com/apache/maven-site-plugin/pull/3#issuecomment-434906079 @rfscholte @hboutemy any objections? Dohh might be the first plugin being java8 required!! :) This is an automated message from the Apache Git Service. To respond to the message, please log on 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 > Jdk 1.8 required / Upgrade Jetty Version 9.4.12 > --- > > Key: MSITE-828 > URL: https://issues.apache.org/jira/browse/MSITE-828 > Project: Maven Site Plugin > Issue Type: Task >Reporter: Olivier Lamy (*$^¨%`£) >Assignee: Olivier Lamy (*$^¨%`£) >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MSHARED-362) Support removing default manifest entries with maven-archiver plugin
[ https://issues.apache.org/jira/browse/MSHARED-362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16670810#comment-16670810 ] Michael Osipov commented on MSHARED-362: I fully agree here. > Support removing default manifest entries with maven-archiver plugin > > > Key: MSHARED-362 > URL: https://issues.apache.org/jira/browse/MSHARED-362 > Project: Maven Shared Components > Issue Type: Improvement > Components: maven-archiver >Affects Versions: maven-archiver-2.4.2, maven-archiver-2.5 >Reporter: Richard Neish >Priority: Minor > Attachments: MSHARED-362-01.patch > > > As described in the StackOverflow question at > http://stackoverflow.com/q/25098307/274350 maven-archiver should allow the > user to remove the default manifest entries, such as "Built-By:" > Currently it is possible to set an empty value for these default entries, but > not to remove them from the manifest. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MSITE-828) Jdk 1.8 required / Upgrade Jetty Version 9.4.12
[ https://issues.apache.org/jira/browse/MSITE-828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16670685#comment-16670685 ] ASF GitHub Bot commented on MSITE-828: -- oflebbe commented on issue #3: [MSITE-828] Upgrade jetty to recent version. Update to java 1.8 (required for jetty) URL: https://github.com/apache/maven-site-plugin/pull/3#issuecomment-434836813 Fixed > mvn install org.apache.maven.plugins:maven-site-plugin:3.8-SNAPSHOT:run This is an automated message from the Apache Git Service. To respond to the message, please log on 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 > Jdk 1.8 required / Upgrade Jetty Version 9.4.12 > --- > > Key: MSITE-828 > URL: https://issues.apache.org/jira/browse/MSITE-828 > Project: Maven Site Plugin > Issue Type: Task >Reporter: Olivier Lamy (*$^¨%`£) >Assignee: Olivier Lamy (*$^¨%`£) >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MSHARED-362) Support removing default manifest entries with maven-archiver plugin
[
https://issues.apache.org/jira/browse/MSHARED-362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16670644#comment-16670644
]
Rostislav Krasny commented on MSHARED-362:
--
[~rfscholte], then let's just remove the:
*{{addManifestAttribute( m, entries, "Built-By", System.getProperty(
"user.name" ) );}}*
code line from the {{MavenArchiver.java}}. So by default the {{Built-By}} will
be disabled and people who want it in their manifests will define it in the
{{manifestEntries}} section of the {{maven-jar-plugin}} configuration, as in
your example.
> Support removing default manifest entries with maven-archiver plugin
>
>
> Key: MSHARED-362
> URL: https://issues.apache.org/jira/browse/MSHARED-362
> Project: Maven Shared Components
> Issue Type: Improvement
> Components: maven-archiver
>Affects Versions: maven-archiver-2.4.2, maven-archiver-2.5
>Reporter: Richard Neish
>Priority: Minor
> Attachments: MSHARED-362-01.patch
>
>
> As described in the StackOverflow question at
> http://stackoverflow.com/q/25098307/274350 maven-archiver should allow the
> user to remove the default manifest entries, such as "Built-By:"
> Currently it is possible to set an empty value for these default entries, but
> not to remove them from the manifest.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MSITE-828) Jdk 1.8 required / Upgrade Jetty Version 9.4.12
[ https://issues.apache.org/jira/browse/MSITE-828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16670486#comment-16670486 ] ASF GitHub Bot commented on MSITE-828: -- oflebbe commented on issue #3: [MSITE-828] Upgrade jetty to recent version. Update to java 1.8 (required for jetty) URL: https://github.com/apache/maven-site-plugin/pull/3#issuecomment-434794612 However I see a problem right now: `mvn site:run` fails with maven 3.5.4 but runs with maven 3.3.9 ?! Have to look into it This is an automated message from the Apache Git Service. To respond to the message, please log on 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 > Jdk 1.8 required / Upgrade Jetty Version 9.4.12 > --- > > Key: MSITE-828 > URL: https://issues.apache.org/jira/browse/MSITE-828 > Project: Maven Site Plugin > Issue Type: Task >Reporter: Olivier Lamy (*$^¨%`£) >Assignee: Olivier Lamy (*$^¨%`£) >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MSITE-828) Jdk 1.8 required / Upgrade Jetty Version 9.4.12
[ https://issues.apache.org/jira/browse/MSITE-828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16670483#comment-16670483 ] ASF GitHub Bot commented on MSITE-828: -- oflebbe commented on a change in pull request #3: [MSITE-828] Upgrade jetty to recent version. Update to java 1.8 (required for jetty) URL: https://github.com/apache/maven-site-plugin/pull/3#discussion_r22981 ## File path: pom.xml ## @@ -392,20 +394,34 @@ under the License. - org.mortbay.jetty - jetty - 6.1.25 + org.eclipse.jetty + jetty-server + 9.4.11.v20180605 Review comment: Introduced property and was wondering how I missed the most recent one. This is an automated message from the Apache Git Service. To respond to the message, please log on 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 > Jdk 1.8 required / Upgrade Jetty Version 9.4.12 > --- > > Key: MSITE-828 > URL: https://issues.apache.org/jira/browse/MSITE-828 > Project: Maven Site Plugin > Issue Type: Task >Reporter: Olivier Lamy (*$^¨%`£) >Assignee: Olivier Lamy (*$^¨%`£) >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (MNGSITE-356) Maven in 5 minutes - "mvn site" to be either elaborated or removed from intro page.
Perry Moen created MNGSITE-356: -- Summary: Maven in 5 minutes - "mvn site" to be either elaborated or removed from intro page. Key: MNGSITE-356 URL: https://issues.apache.org/jira/browse/MNGSITE-356 Project: Maven Project Web Site Issue Type: Improvement Environment: Windows Reporter: Perry Moen Hello, The documentation for the Maven in 5 minutes eludes that one would be able to simply run mvn site from the command line and have it work out of the box, if they've been following the demo. Unfortunately, with out the maven-site-plugin updated in the POM this does not work. My suggestion would be to either quickly show where/how to copy paste a plugin and update the POM, or briefly mention what mvn site does, and link to the official documentation. Otherwise, remove the mvn site altogether from the maven in 5 minutes tutorial. A new comer to programming and maven might find this intro frustrating if they cannot get the demo to work with a simple follow along. I am new to programming myself.. I would have found it useful to know. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (SUREFIRE-1588) Surefire manifest jar classloading broken on latest Debian/Ubuntu Java8
[
https://issues.apache.org/jira/browse/SUREFIRE-1588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16670432#comment-16670432
]
ASF GitHub Bot commented on SUREFIRE-1588:
--
Tibor17 commented on issue #197: SUREFIRE-1588 Patch (Java7)
URL: https://github.com/apache/maven-surefire/pull/197#issuecomment-434780362
@cstamas
I will try to do my bets today. Okay?
And then I will ask you to rebase this branch.
We can start release tomorrow.
This is an automated message from the Apache Git Service.
To respond to the message, please log on 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
> Surefire manifest jar classloading broken on latest Debian/Ubuntu Java8
> ---
>
> Key: SUREFIRE-1588
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1588
> Project: Maven Surefire
> Issue Type: Bug
>Affects Versions: 2.22.1
>Reporter: Cservenak, Tamas
>Priority: Major
>
> See issue [1], but in short: latest Java8 on Ubuntu/Debian/Mint family of
> Linuxes (am on Mint, Ubuntu derivative) contains this patch [3], and eforces
> Manifest class path entries to be relative, as defined in [2].
> Hence, surefire booter and rest of Maven classpath, that uses absolute URLs
> are simply discarded.
> Example error:
> {noformat}
> # Created at 2018-10-30T21:34:43.339
> Error: Could not find or load main class
> org.apache.maven.surefire.booter.ForkedBooter{noformat}
> using the new property
> {{-Djdk.net.URLClassPath.disableClassPathURLCheck=debug}} clearly shows that
> all the entries from the surefire JAR are simply ignored.
>
> [1] [https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911925]
> [2]
> https://docs.oracle.com/javase/8/docs/technotes/guides/jar/jar.html#classpath
> [3] [https://hg.openjdk.java.net/jdk/jdk/rev/27135de165ac]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[GitHub] Tibor17 commented on issue #197: SUREFIRE-1588 Patch (Java7)
Tibor17 commented on issue #197: SUREFIRE-1588 Patch (Java7) URL: https://github.com/apache/maven-surefire/pull/197#issuecomment-434780362 @cstamas I will try to do my bets today. Okay? And then I will ask you to rebase this branch. We can start release tomorrow. This is an automated message from the Apache Git Service. To respond to the message, please log on 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 With regards, Apache Git Services
[jira] [Commented] (SUREFIRE-1588) Surefire manifest jar classloading broken on latest Debian/Ubuntu Java8
[
https://issues.apache.org/jira/browse/SUREFIRE-1588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16670423#comment-16670423
]
ASF GitHub Bot commented on SUREFIRE-1588:
--
Tibor17 commented on issue #197: SUREFIRE-1588 Patch (Java7)
URL: https://github.com/apache/maven-surefire/pull/197#issuecomment-434777977
@cstamas
This will be a mess in project. As I said please wait a bit, I will fork the
issues of 3.0.0-M1 to multiple versions and we will make very frequent
releases. That's much better for us and one or two day plus minus is not a
difference.
This is an automated message from the Apache Git Service.
To respond to the message, please log on 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
> Surefire manifest jar classloading broken on latest Debian/Ubuntu Java8
> ---
>
> Key: SUREFIRE-1588
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1588
> Project: Maven Surefire
> Issue Type: Bug
>Affects Versions: 2.22.1
>Reporter: Cservenak, Tamas
>Priority: Major
>
> See issue [1], but in short: latest Java8 on Ubuntu/Debian/Mint family of
> Linuxes (am on Mint, Ubuntu derivative) contains this patch [3], and eforces
> Manifest class path entries to be relative, as defined in [2].
> Hence, surefire booter and rest of Maven classpath, that uses absolute URLs
> are simply discarded.
> Example error:
> {noformat}
> # Created at 2018-10-30T21:34:43.339
> Error: Could not find or load main class
> org.apache.maven.surefire.booter.ForkedBooter{noformat}
> using the new property
> {{-Djdk.net.URLClassPath.disableClassPathURLCheck=debug}} clearly shows that
> all the entries from the surefire JAR are simply ignored.
>
> [1] [https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911925]
> [2]
> https://docs.oracle.com/javase/8/docs/technotes/guides/jar/jar.html#classpath
> [3] [https://hg.openjdk.java.net/jdk/jdk/rev/27135de165ac]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[GitHub] Tibor17 commented on issue #197: SUREFIRE-1588 Patch (Java7)
Tibor17 commented on issue #197: SUREFIRE-1588 Patch (Java7) URL: https://github.com/apache/maven-surefire/pull/197#issuecomment-434777977 @cstamas This will be a mess in project. As I said please wait a bit, I will fork the issues of 3.0.0-M1 to multiple versions and we will make very frequent releases. That's much better for us and one or two day plus minus is not a difference. This is an automated message from the Apache Git Service. To respond to the message, please log on 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 With regards, Apache Git Services
[jira] [Commented] (MSHADE-303) Suppress module-info.class warning if the file if filtered
[ https://issues.apache.org/jira/browse/MSHADE-303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16670404#comment-16670404 ] Hudson commented on MSHADE-303: --- Build succeeded in Jenkins: Maven TLP » maven-shade-plugin » master #50 See https://builds.apache.org/job/maven-box/job/maven-shade-plugin/job/master/50/ > Suppress module-info.class warning if the file if filtered > -- > > Key: MSHADE-303 > URL: https://issues.apache.org/jira/browse/MSHADE-303 > Project: Maven Shade Plugin > Issue Type: Improvement >Affects Versions: 3.2.0 >Reporter: Danila >Assignee: Robert Scholte >Priority: Major > Fix For: 3.2.1 > > > Maven always shows “Discovered module-info.class. Shading will break its > strong encapsulation.” warning, even then the user has explicitly filtered > those files out. The same with “META-INF/INDEX.LIST” file. > I am going to issue a [pull > request|https://github.com/apache/maven-shade-plugin/pull/8] to fix this by > applying file filters BEFORE these built-in warning checkers. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] rfscholte closed pull request #6: Update site.xml spelling issue
rfscholte closed pull request #6: Update site.xml spelling issue URL: https://github.com/apache/maven-shade-plugin/pull/6 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), the diff is supplied below (as it won't show otherwise due to GitHub magic): diff --git a/src/site/site.xml b/src/site/site.xml index c602d8f..cba65de 100644 --- a/src/site/site.xml +++ b/src/site/site.xml @@ -64,7 +64,7 @@ under the License. - + This is an automated message from the Apache Git Service. To respond to the message, please log on 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 With regards, Apache Git Services
[jira] [Updated] (MDEP-631) purge-local-repository doesn't include dependencies with scope provided
[ https://issues.apache.org/jira/browse/MDEP-631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Donze updated MDEP-631: Description: When configuring a goal using purge-local-repository within a pom file the dependencies with of the module with scope provided are not purged from local repository. (was: When configuring a goal using purge-local-repository within a pom file. The dependencies with scope provided are not purged from local repository.) > purge-local-repository doesn't include dependencies with scope provided > --- > > Key: MDEP-631 > URL: https://issues.apache.org/jira/browse/MDEP-631 > Project: Maven Dependency Plugin > Issue Type: Bug > Components: purge-local-repository >Affects Versions: 3.1.1 >Reporter: Benjamin Donze >Priority: Major > > When configuring a goal using purge-local-repository within a pom file the > dependencies with of the module with scope provided are not purged from local > repository. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (MDEP-631) purge-local-repository doesn't include dependencies with scope provided
Benjamin Donze created MDEP-631: --- Summary: purge-local-repository doesn't include dependencies with scope provided Key: MDEP-631 URL: https://issues.apache.org/jira/browse/MDEP-631 Project: Maven Dependency Plugin Issue Type: Bug Components: purge-local-repository Affects Versions: 3.1.1 Reporter: Benjamin Donze When configuring a goal using purge-local-repository within a pom file. The dependencies with scope provided are not purged from local repository. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (MSHADE-303) Suppress module-info.class warning if the file if filtered
[ https://issues.apache.org/jira/browse/MSHADE-303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte closed MSHADE-303. - Resolution: Fixed Fix Version/s: 3.2.1 Fixed in [1f7f25d2ce4391741fab36d18b61a69637f46bc3|https://gitbox.apache.org/repos/asf?p=maven-shade-plugin.git;a=commit;h=1f7f25d2ce4391741fab36d18b61a69637f46bc3] Thanks for the patch! > Suppress module-info.class warning if the file if filtered > -- > > Key: MSHADE-303 > URL: https://issues.apache.org/jira/browse/MSHADE-303 > Project: Maven Shade Plugin > Issue Type: Improvement >Affects Versions: 3.2.0 >Reporter: Danila >Assignee: Robert Scholte >Priority: Major > Fix For: 3.2.1 > > > Maven always shows “Discovered module-info.class. Shading will break its > strong encapsulation.” warning, even then the user has explicitly filtered > those files out. The same with “META-INF/INDEX.LIST” file. > I am going to issue a [pull > request|https://github.com/apache/maven-shade-plugin/pull/8] to fix this by > applying file filters BEFORE these built-in warning checkers. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (SUREFIRE-1408) Surefire shows random tests failing with fork issue when one of the tests hangs
[
https://issues.apache.org/jira/browse/SUREFIRE-1408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16670370#comment-16670370
]
Nicola edited comment on SUREFIRE-1408 at 10/31/18 4:43 PM:
Hi All,
here I am on Ubuntu 18.04
{code:java}
mvn -version
Apache Maven 3.5.2
Maven home: /usr/share/maven
Java version: 10.0.2, vendor: Oracle Corporation
Java home: /usr/lib/jvm/java-11-openjdk-amd64
Default locale: en_IE, platform encoding: UTF-8
OS name: "linux", version: "4.15.0-38-lowlatency", arch: "amd64", family: "unix"
{code}
I created an example project with mvn archetype:generate and accept all the
default options.
{code:java}
maven-surefire-plugin
2.20.1
{code}
mvn compile is fine but if I run mvn package
{code:java}
[INFO] Scanning for projects...
[INFO]
[INFO]
[INFO] Building org.nick.helloworld 1.0
[INFO]
[INFO]
[INFO] --- maven-resources-plugin:3.0.2:resources (default-resources) @
org.nick.helloworld ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory
/home/nlunghiadm/tmp/java/test/test-project/org.nick.helloworld/src/main/resources
[INFO]
[INFO] --- maven-compiler-plugin:3.7.0:compile (default-compile) @
org.nick.helloworld ---
[INFO] Nothing to compile - all classes are up to date
[INFO]
[INFO] --- maven-resources-plugin:3.0.2:testResources (default-testResources) @
org.nick.helloworld ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory
/home/nlunghiadm/tmp/java/test/test-project/org.nick.helloworld/src/test/resources
[INFO]
[INFO] --- maven-compiler-plugin:3.7.0:testCompile (default-testCompile) @
org.nick.helloworld ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 1 source file to
/home/nlunghiadm/tmp/java/test/test-project/org.nick.helloworld/target/test-classes
[INFO]
[INFO] --- maven-surefire-plugin:2.20.1:test (default-test) @
org.nick.helloworld ---
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 2.129 s
[INFO] Finished at: 2018-10-31T16:38:23Z
[INFO] Final Memory: 12M/47M
[INFO]
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-surefire-plugin:2.20.1:test (default-test) on
project org.nick.helloworld: Execution default-test of goal
org.apache.maven.plugins:maven-surefire-plugin:2.20.1:test failed.:
NullPointerException -> [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/PluginExecutionException
{code}
I tried to switch to the 2.22.1 and it gets worst/better?
{code:java}
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by
com.google.inject.internal.cglib.core.$ReflectUtils$1
(file:/usr/share/maven/lib/guice.jar) to method
java.lang.ClassLoader.defineClass(java.lang.String,byte[],int,int,java.security.ProtectionDomain)
WARNING: Please consider reporting this to the maintainers of
com.google.inject.internal.cglib.core.$ReflectUtils$1
WARNING: Use --illegal-access=warn to enable warnings of further illegal
reflective access operations
WARNING: All illegal access operations will be denied in a future release
[INFO] Scanning for projects...
[INFO]
[INFO]
[INFO] Building org.nick.helloworld 1.0
[INFO]
[INFO]
[INFO] --- maven-resources-plugin:3.0.2:resources (default-resources) @
org.nick.helloworld ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory
/home/nlunghiadm/tmp/java/test/test-project/org.nick.helloworld/src/main/resources
[INFO]
[INFO] --- maven-compiler-plugin:3.7.0:compile (default-compile) @
org.nick.helloworld ---
[INFO] Nothing to compile - all classes are up to date
[INFO]
[INFO] --- maven-resources-plugin:3.0.2:testResources (default-testResources) @
org.nick.helloworld ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory
/home/nlunghiadm/tmp/java/test/test-project/org.nick.helloworld/src/test/resources
[INFO]
[INFO] --- maven-compiler-plugin:3.7.0:testCompile (default-testCompile) @
org.nick.helloworld ---
[INFO] Nothing to compile
[jira] [Commented] (SUREFIRE-1408) Surefire shows random tests failing with fork issue when one of the tests hangs
[
https://issues.apache.org/jira/browse/SUREFIRE-1408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16670370#comment-16670370
]
Nicola commented on SUREFIRE-1408:
--
Hi All,
here I am on Ubuntu 18.04
{code:java}
mvn -version
Apache Maven 3.5.2
Maven home: /usr/share/maven
Java version: 10.0.2, vendor: Oracle Corporation
Java home: /usr/lib/jvm/java-11-openjdk-amd64
Default locale: en_IE, platform encoding: UTF-8
OS name: "linux", version: "4.15.0-38-lowlatency", arch: "amd64", family: "unix"
{code}
I created an example project with mvn archetype:generate and accept all the
default options.
{code:java}
maven-surefire-plugin
2.20.1
{code}
mvn compile is fine but if I run mvn package
{code:java}
[INFO] Scanning for projects...
[INFO]
[INFO]
[INFO] Building org.nick.helloworld 1.0
[INFO]
[INFO]
[INFO] --- maven-resources-plugin:3.0.2:resources (default-resources) @
org.nick.helloworld ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory
/home/nlunghiadm/tmp/java/test/test-project/org.nick.helloworld/src/main/resources
[INFO]
[INFO] --- maven-compiler-plugin:3.7.0:compile (default-compile) @
org.nick.helloworld ---
[INFO] Nothing to compile - all classes are up to date
[INFO]
[INFO] --- maven-resources-plugin:3.0.2:testResources (default-testResources) @
org.nick.helloworld ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory
/home/nlunghiadm/tmp/java/test/test-project/org.nick.helloworld/src/test/resources
[INFO]
[INFO] --- maven-compiler-plugin:3.7.0:testCompile (default-testCompile) @
org.nick.helloworld ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 1 source file to
/home/nlunghiadm/tmp/java/test/test-project/org.nick.helloworld/target/test-classes
[INFO]
[INFO] --- maven-surefire-plugin:2.20.1:test (default-test) @
org.nick.helloworld ---
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 2.129 s
[INFO] Finished at: 2018-10-31T16:38:23Z
[INFO] Final Memory: 12M/47M
[INFO]
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-surefire-plugin:2.20.1:test (default-test) on
project org.nick.helloworld: Execution default-test of goal
org.apache.maven.plugins:maven-surefire-plugin:2.20.1:test failed.:
NullPointerException -> [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/PluginExecutionException
{code}
I tried to switch to the 2.22.1 and it gets worst/better?
{code:java}
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by
com.google.inject.internal.cglib.core.$ReflectUtils$1
(file:/usr/share/maven/lib/guice.jar) to method
java.lang.ClassLoader.defineClass(java.lang.String,byte[],int,int,java.security.ProtectionDomain)
WARNING: Please consider reporting this to the maintainers of
com.google.inject.internal.cglib.core.$ReflectUtils$1
WARNING: Use --illegal-access=warn to enable warnings of further illegal
reflective access operations
WARNING: All illegal access operations will be denied in a future release
[INFO] Scanning for projects...
[INFO]
[INFO]
[INFO] Building org.nick.helloworld 1.0
[INFO]
[INFO]
[INFO] --- maven-resources-plugin:3.0.2:resources (default-resources) @
org.nick.helloworld ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory
/home/nlunghiadm/tmp/java/test/test-project/org.nick.helloworld/src/main/resources
[INFO]
[INFO] --- maven-compiler-plugin:3.7.0:compile (default-compile) @
org.nick.helloworld ---
[INFO] Nothing to compile - all classes are up to date
[INFO]
[INFO] --- maven-resources-plugin:3.0.2:testResources (default-testResources) @
org.nick.helloworld ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory
/home/nlunghiadm/tmp/java/test/test-project/org.nick.helloworld/src/test/resources
[INFO]
[INFO] --- maven-compiler-plugin:3.7.0:testCompile (default-testCompile) @
org.nick.helloworld ---
[INFO] Nothing to compile - all classes are up to date
[INFO]
[INFO] ---
[jira] [Commented] (MSHARED-362) Support removing default manifest entries with maven-archiver plugin
[
https://issues.apache.org/jira/browse/MSHARED-362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16670367#comment-16670367
]
Robert Scholte commented on MSHARED-362:
*_IF_* we want to have By-Built empty by default, just make it {{null}}.
Document that if you want to original value, you must add the following entry
{code:xml}
${user.name}
{code}
So only 1 entry to control this key, not multiple (which implies some kind of
redundency to me)
> Support removing default manifest entries with maven-archiver plugin
>
>
> Key: MSHARED-362
> URL: https://issues.apache.org/jira/browse/MSHARED-362
> Project: Maven Shared Components
> Issue Type: Improvement
> Components: maven-archiver
>Affects Versions: maven-archiver-2.4.2, maven-archiver-2.5
>Reporter: Richard Neish
>Priority: Minor
> Attachments: MSHARED-362-01.patch
>
>
> As described in the StackOverflow question at
> http://stackoverflow.com/q/25098307/274350 maven-archiver should allow the
> user to remove the default manifest entries, such as "Built-By:"
> Currently it is possible to set an empty value for these default entries, but
> not to remove them from the manifest.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MDEPLOY-131) use default repository when no url specified
[ https://issues.apache.org/jira/browse/MDEPLOY-131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16670349#comment-16670349 ] T Vorschuetz commented on MDEPLOY-131: -- I completely agree with Richard. Where is the problem to implement the few lines of code to increase the usability of this plugin a lot? Why is the ticket not processed for years, even if meaning is clearly defined and the code is already there? > use default repository when no url specified > > > Key: MDEPLOY-131 > URL: https://issues.apache.org/jira/browse/MDEPLOY-131 > Project: Maven Deploy Plugin > Issue Type: Improvement > Components: deploy:deploy-file >Reporter: raymond domingo >Priority: Major > Labels: contributers-welcome > Attachments: DeployFileMojo.java, > maven-deploy-useProjectRepo-20170319.patch, patch_deploy_file_mojo.diff > > > When using the deploy goal there is no need to specify the url of the > repository. > When using deploy-file you DO need to specify the url. This is a problem, > because during development I like to deploy to snapshot repository and when > releasing i deploy to release repository and I can't add this logic to the > pom. > Thas is why I like the url paramter to become optional (backwards compatible) > and add default behaviour when it is null. It should just like the deploy > plugin use the default repository. Snapshot for snapshots and release for > none snapshot versions. > I added a patch file fixing this. > I also added complete source of patched Mojo -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (MCOMPILER-320) Allow additional class path items to be given during compilation
[
https://issues.apache.org/jira/browse/MCOMPILER-320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte updated MCOMPILER-320:
-
Fix Version/s: (was: 3.8.1)
> Allow additional class path items to be given during compilation
>
>
> Key: MCOMPILER-320
> URL: https://issues.apache.org/jira/browse/MCOMPILER-320
> Project: Maven Compiler Plugin
> Issue Type: New Feature
>Reporter: David M. Lloyd
>Priority: Major
>
> At present it is very difficult to include additional class path items during
> compilation that are not dependencies. But this is a very useful capability,
> especially when doing partial builds, MR JARs, JDK API stubbing, including
> dependency items that cannot be included in any other build phase or
> execution, etc.
> This enhancement and pull request are to request the addition of a
> {{additionalCompilePathItems}} property in CompilerMojo or
> AbstractCompilerMojo which includes additional filesystem paths in the
> compilation class path.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MSHADE-303) Suppress module-info.class warning if the file if filtered
[ https://issues.apache.org/jira/browse/MSHADE-303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16670337#comment-16670337 ] ASF GitHub Bot commented on MSHADE-303: --- rfscholte closed pull request #8: [MSHADE-303] Suppress module-info.class warning if the file if filtered URL: https://github.com/apache/maven-shade-plugin/pull/8 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), the diff is supplied below (as it won't show otherwise due to GitHub magic): diff --git a/src/main/java/org/apache/maven/plugins/shade/DefaultShader.java b/src/main/java/org/apache/maven/plugins/shade/DefaultShader.java index ee633f8..825ed68 100644 --- a/src/main/java/org/apache/maven/plugins/shade/DefaultShader.java +++ b/src/main/java/org/apache/maven/plugins/shade/DefaultShader.java @@ -169,6 +169,12 @@ private void shadeJars( ShadeRequest shadeRequest, Set resources, List resources, List Suppress module-info.class warning if the file if filtered > -- > > Key: MSHADE-303 > URL: https://issues.apache.org/jira/browse/MSHADE-303 > Project: Maven Shade Plugin > Issue Type: Improvement >Affects Versions: 3.2.0 >Reporter: Danila >Assignee: Robert Scholte >Priority: Major > > Maven always shows “Discovered module-info.class. Shading will break its > strong encapsulation.” warning, even then the user has explicitly filtered > those files out. The same with “META-INF/INDEX.LIST” file. > I am going to issue a [pull > request|https://github.com/apache/maven-shade-plugin/pull/8] to fix this by > applying file filters BEFORE these built-in warning checkers. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] rfscholte closed pull request #8: [MSHADE-303] Suppress module-info.class warning if the file if filtered
rfscholte closed pull request #8: [MSHADE-303] Suppress module-info.class warning if the file if filtered URL: https://github.com/apache/maven-shade-plugin/pull/8 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), the diff is supplied below (as it won't show otherwise due to GitHub magic): diff --git a/src/main/java/org/apache/maven/plugins/shade/DefaultShader.java b/src/main/java/org/apache/maven/plugins/shade/DefaultShader.java index ee633f8..825ed68 100644 --- a/src/main/java/org/apache/maven/plugins/shade/DefaultShader.java +++ b/src/main/java/org/apache/maven/plugins/shade/DefaultShader.java @@ -169,6 +169,12 @@ private void shadeJars( ShadeRequest shadeRequest, Set resources, List resources, List
[jira] [Commented] (SUREFIRE-1588) Surefire manifest jar classloading broken on latest Debian/Ubuntu Java8
[
https://issues.apache.org/jira/browse/SUREFIRE-1588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16670325#comment-16670325
]
Thorsten Glaser commented on SUREFIRE-1588:
---
Erm, can’t you please release a 2.x with the fix, as this is really important
{color:#FF}RIGHT NOW{color}?
We can upgrade to an incompatible 3.x later, but we’ll not use a -Mxxx
milestone snapshot in production, and who knows what other incompatibilities
3.x will have.
(As for making it Java 7+ that’s no problem, we got even the slowest and most
conservative of customers to upgrade to Java 7 years ago, and almost all to
Java 8 even, years ago even.)
> Surefire manifest jar classloading broken on latest Debian/Ubuntu Java8
> ---
>
> Key: SUREFIRE-1588
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1588
> Project: Maven Surefire
> Issue Type: Bug
>Affects Versions: 2.22.1
>Reporter: Cservenak, Tamas
>Priority: Major
>
> See issue [1], but in short: latest Java8 on Ubuntu/Debian/Mint family of
> Linuxes (am on Mint, Ubuntu derivative) contains this patch [3], and eforces
> Manifest class path entries to be relative, as defined in [2].
> Hence, surefire booter and rest of Maven classpath, that uses absolute URLs
> are simply discarded.
> Example error:
> {noformat}
> # Created at 2018-10-30T21:34:43.339
> Error: Could not find or load main class
> org.apache.maven.surefire.booter.ForkedBooter{noformat}
> using the new property
> {{-Djdk.net.URLClassPath.disableClassPathURLCheck=debug}} clearly shows that
> all the entries from the surefire JAR are simply ignored.
>
> [1] [https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911925]
> [2]
> https://docs.oracle.com/javase/8/docs/technotes/guides/jar/jar.html#classpath
> [3] [https://hg.openjdk.java.net/jdk/jdk/rev/27135de165ac]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (SUREFIRE-1588) Surefire manifest jar classloading broken on latest Debian/Ubuntu Java8
[
https://issues.apache.org/jira/browse/SUREFIRE-1588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16670286#comment-16670286
]
ASF GitHub Bot commented on SUREFIRE-1588:
--
Github user asfgit closed the pull request at:
https://github.com/apache/brooklyn-client/pull/71
> Surefire manifest jar classloading broken on latest Debian/Ubuntu Java8
> ---
>
> Key: SUREFIRE-1588
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1588
> Project: Maven Surefire
> Issue Type: Bug
>Affects Versions: 2.22.1
>Reporter: Cservenak, Tamas
>Priority: Major
>
> See issue [1], but in short: latest Java8 on Ubuntu/Debian/Mint family of
> Linuxes (am on Mint, Ubuntu derivative) contains this patch [3], and eforces
> Manifest class path entries to be relative, as defined in [2].
> Hence, surefire booter and rest of Maven classpath, that uses absolute URLs
> are simply discarded.
> Example error:
> {noformat}
> # Created at 2018-10-30T21:34:43.339
> Error: Could not find or load main class
> org.apache.maven.surefire.booter.ForkedBooter{noformat}
> using the new property
> {{-Djdk.net.URLClassPath.disableClassPathURLCheck=debug}} clearly shows that
> all the entries from the surefire JAR are simply ignored.
>
> [1] [https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911925]
> [2]
> https://docs.oracle.com/javase/8/docs/technotes/guides/jar/jar.html#classpath
> [3] [https://hg.openjdk.java.net/jdk/jdk/rev/27135de165ac]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MSITE-822) JDK 10: Null Pointer Exception
[
https://issues.apache.org/jira/browse/MSITE-822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16670271#comment-16670271
]
Hervé Boutemy commented on MSITE-822:
-
yes, what I see here is that this type of exception during a report execution
deserve an additional Exception to know which report plugin is the cause...
> JDK 10: Null Pointer Exception
> --
>
> Key: MSITE-822
> URL: https://issues.apache.org/jira/browse/MSITE-822
> Project: Maven Site Plugin
> Issue Type: Bug
>Affects Versions: 3.7
>Reporter: Karl Heinz Marbaise
>Priority: Blocker
>
> Currently facing the following NPE while using JDK 10:
> {code}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-site-plugin:3.7:site (default-site) on project
> maven-acr-plugin: Execution default-site of goal
> org.apache.maven.plugins:maven-site-plugin:3.7:site failed.:
> NullPointerException -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-site-plugin:3.7:site (default-site) on
> project maven-acr-plugin: Execution default-site of goal
> org.apache.maven.plugins:maven-site-plugin:3.7:site failed.
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:213)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:154)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:146)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:117)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:81)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
> (SingleThreadedBuilder.java:56)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
> (LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
> at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
> at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956)
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:290)
> at org.apache.maven.cli.MavenCli.main (MavenCli.java:194)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke
> (NativeMethodAccessorImpl.java:62)
> at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke
> (DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke (Method.java:564)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
> (Launcher.java:289)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch
> (Launcher.java:229)
> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
> (Launcher.java:415)
> at org.codehaus.plexus.classworlds.launcher.Launcher.main
> (Launcher.java:356)
> Caused by: org.apache.maven.plugin.PluginExecutionException: Execution
> default-site of goal org.apache.maven.plugins:maven-site-plugin:3.7:site
> failed.
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:148)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:208)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:154)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:146)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:117)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:81)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
> (SingleThreadedBuilder.java:56)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
> (LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
> at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
> at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956)
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:290)
> at org.apache.maven.cli.MavenCli.main (MavenCli.java:194)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke
> (NativeMethodAccessorImpl.java:62)
> at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke
> (DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke
[jira] [Updated] (MSITE-822) JDK 10: Null Pointer Exception
[
https://issues.apache.org/jira/browse/MSITE-822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hervé Boutemy updated MSITE-822:
Fix Version/s: (was: 3.7)
> JDK 10: Null Pointer Exception
> --
>
> Key: MSITE-822
> URL: https://issues.apache.org/jira/browse/MSITE-822
> Project: Maven Site Plugin
> Issue Type: Bug
>Affects Versions: 3.7
>Reporter: Karl Heinz Marbaise
>Priority: Blocker
>
> Currently facing the following NPE while using JDK 10:
> {code}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-site-plugin:3.7:site (default-site) on project
> maven-acr-plugin: Execution default-site of goal
> org.apache.maven.plugins:maven-site-plugin:3.7:site failed.:
> NullPointerException -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-site-plugin:3.7:site (default-site) on
> project maven-acr-plugin: Execution default-site of goal
> org.apache.maven.plugins:maven-site-plugin:3.7:site failed.
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:213)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:154)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:146)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:117)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:81)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
> (SingleThreadedBuilder.java:56)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
> (LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
> at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
> at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956)
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:290)
> at org.apache.maven.cli.MavenCli.main (MavenCli.java:194)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke
> (NativeMethodAccessorImpl.java:62)
> at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke
> (DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke (Method.java:564)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
> (Launcher.java:289)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch
> (Launcher.java:229)
> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
> (Launcher.java:415)
> at org.codehaus.plexus.classworlds.launcher.Launcher.main
> (Launcher.java:356)
> Caused by: org.apache.maven.plugin.PluginExecutionException: Execution
> default-site of goal org.apache.maven.plugins:maven-site-plugin:3.7:site
> failed.
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:148)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:208)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:154)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:146)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:117)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:81)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
> (SingleThreadedBuilder.java:56)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
> (LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
> at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
> at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956)
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:290)
> at org.apache.maven.cli.MavenCli.main (MavenCli.java:194)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke
> (NativeMethodAccessorImpl.java:62)
> at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke
> (DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke (Method.java:564)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
> (Launcher.java:289)
> at
[jira] [Created] (MNG-6502) More performant AbstractZipArchiver
Hoa Phan created MNG-6502: - Summary: More performant AbstractZipArchiver Key: MNG-6502 URL: https://issues.apache.org/jira/browse/MNG-6502 Project: Maven Issue Type: Improvement Reporter: Hoa Phan Attachments: Screen Shot 2018-11-01 at 2.22.42 am.png, Screen Shot 2018-11-01 at 2.25.22 am.png Consider process resources in parallel !Screen Shot 2018-11-01 at 2.22.42 am.png! Consider flexible/adjustable buffer size for IOUtil.copy !Screen Shot 2018-11-01 at 2.25.22 am.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (SUREFIRE-1588) Surefire manifest jar classloading broken on latest Debian/Ubuntu Java8
[
https://issues.apache.org/jira/browse/SUREFIRE-1588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16670234#comment-16670234
]
ASF GitHub Bot commented on SUREFIRE-1588:
--
cstamas commented on issue #197: SUREFIRE-1588 Patch (Java7)
URL: https://github.com/apache/maven-surefire/pull/197#issuecomment-434728533
@Tibor17 Hi there! It might become necessary to make 2.22.2 bugfix release,
as this seems to affect a LOT of people out there (seems this check is also in
Oracle Java 1.8.0_191?)
Will try to backport to java6 code then the fix, to not perform java
language version change in a bugfix release. (or anyone out there is welcome to
do the same)
This is an automated message from the Apache Git Service.
To respond to the message, please log on 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
> Surefire manifest jar classloading broken on latest Debian/Ubuntu Java8
> ---
>
> Key: SUREFIRE-1588
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1588
> Project: Maven Surefire
> Issue Type: Bug
>Affects Versions: 2.22.1
>Reporter: Cservenak, Tamas
>Priority: Major
>
> See issue [1], but in short: latest Java8 on Ubuntu/Debian/Mint family of
> Linuxes (am on Mint, Ubuntu derivative) contains this patch [3], and eforces
> Manifest class path entries to be relative, as defined in [2].
> Hence, surefire booter and rest of Maven classpath, that uses absolute URLs
> are simply discarded.
> Example error:
> {noformat}
> # Created at 2018-10-30T21:34:43.339
> Error: Could not find or load main class
> org.apache.maven.surefire.booter.ForkedBooter{noformat}
> using the new property
> {{-Djdk.net.URLClassPath.disableClassPathURLCheck=debug}} clearly shows that
> all the entries from the surefire JAR are simply ignored.
>
> [1] [https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911925]
> [2]
> https://docs.oracle.com/javase/8/docs/technotes/guides/jar/jar.html#classpath
> [3] [https://hg.openjdk.java.net/jdk/jdk/rev/27135de165ac]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (MARCHETYPES-62) generated pom.xml contains a value instead of ${basedir}
[
https://issues.apache.org/jira/browse/MARCHETYPES-62?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hervé Boutemy closed MARCHETYPES-62.
Resolution: Fixed
fixed in
[02014505902ed24288673ef949072f40c999f65e|https://gitbox.apache.org/repos/asf?p=maven-archetypes.git;a=commit;h=02014505902ed24288673ef949072f40c999f65e]
during [Paris Hackergarten
session|https://www.meetup.com/fr-FR/Paris-Hackergarten/events/tvdrwpyxnbnc/]
> generated pom.xml contains a value instead of ${basedir}
>
>
> Key: MARCHETYPES-62
> URL: https://issues.apache.org/jira/browse/MARCHETYPES-62
> Project: Maven Archetype Bundles
> Issue Type: Bug
> Components: Maven Skin Archetype
>Affects Versions: 1.3
>Reporter: Hervé Boutemy
>Assignee: Hervé Boutemy
>Priority: Major
> Fix For: 1.4
>
>
> when generating a site skin from archetype, pom.xml contains:
> {code:xml}
>
>
> /home/herve/projets/maven/git/aggregator/archetypes/target/checkout/maven-archetype-site-skin/src/main/resources
>
> css/print.css
>
>
> {code}
> when it should contain
> {code:xml}
>
> ${basedir}/src/main/resources
>
> css/print.css
>
>
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[GitHub] cstamas commented on issue #197: SUREFIRE-1588 Patch (Java7)
cstamas commented on issue #197: SUREFIRE-1588 Patch (Java7) URL: https://github.com/apache/maven-surefire/pull/197#issuecomment-434728533 @Tibor17 Hi there! It might become necessary to make 2.22.2 bugfix release, as this seems to affect a LOT of people out there (seems this check is also in Oracle Java 1.8.0_191?) Will try to backport to java6 code then the fix, to not perform java language version change in a bugfix release. (or anyone out there is welcome to do the same) This is an automated message from the Apache Git Service. To respond to the message, please log on 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 With regards, Apache Git Services
[jira] [Commented] (SUREFIRE-1588) Surefire manifest jar classloading broken on latest Debian/Ubuntu Java8
[
https://issues.apache.org/jira/browse/SUREFIRE-1588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16670228#comment-16670228
]
ASF GitHub Bot commented on SUREFIRE-1588:
--
GitHub user kemitix opened a pull request:
https://github.com/apache/brooklyn-client/pull/71
Fix for SUREFIRE-1588
Latest version of Java 1.8.0_191 enforces that Manifest classpath entries be
relative.
https://issues.apache.org/jira/browse/SUREFIRE-1588
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/kemitix/brooklyn-client fix-for-SUREFIRE-1588
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/brooklyn-client/pull/71.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #71
commit 82413a4dce2b4221fab28b8b0f167f01ffe2eed4
Author: Paul Campbell
Date: 2018-10-31T15:11:52Z
Fix for SUREFIRE-1588
Latest version of Java 1.8.0_191 enforces that Manifest classpath entries be
relative.
https://issues.apache.org/jira/browse/SUREFIRE-1588
> Surefire manifest jar classloading broken on latest Debian/Ubuntu Java8
> ---
>
> Key: SUREFIRE-1588
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1588
> Project: Maven Surefire
> Issue Type: Bug
>Affects Versions: 2.22.1
>Reporter: Cservenak, Tamas
>Priority: Major
>
> See issue [1], but in short: latest Java8 on Ubuntu/Debian/Mint family of
> Linuxes (am on Mint, Ubuntu derivative) contains this patch [3], and eforces
> Manifest class path entries to be relative, as defined in [2].
> Hence, surefire booter and rest of Maven classpath, that uses absolute URLs
> are simply discarded.
> Example error:
> {noformat}
> # Created at 2018-10-30T21:34:43.339
> Error: Could not find or load main class
> org.apache.maven.surefire.booter.ForkedBooter{noformat}
> using the new property
> {{-Djdk.net.URLClassPath.disableClassPathURLCheck=debug}} clearly shows that
> all the entries from the surefire JAR are simply ignored.
>
> [1] [https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911925]
> [2]
> https://docs.oracle.com/javase/8/docs/technotes/guides/jar/jar.html#classpath
> [3] [https://hg.openjdk.java.net/jdk/jdk/rev/27135de165ac]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[GitHub] hboutemy commented on issue #2: Add \ to print.css ${basedir} to correct generate path
hboutemy commented on issue #2: Add \ to print.css ${basedir} to correct
generate path
URL: https://github.com/apache/maven-archetypes/pull/2#issuecomment-434727134
the first contribution is an important moment: this prepares the next one :)
FYI, I created a Jira issue to track the fix on the next archetypes release:
see https://issues.apache.org/jira/browse/MARCHETYPES-62
in general, creating such a Jira issue is a good practice and having its id
(here MARCHETYPES-62) in the commit message
This is an automated message from the Apache Git Service.
To respond to the message, please log on 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
With regards,
Apache Git Services
[jira] [Created] (MARCHETYPES-62) generated pom.xml contains a value instead of ${basedir}
Hervé Boutemy created MARCHETYPES-62:
Summary: generated pom.xml contains a value instead of ${basedir}
Key: MARCHETYPES-62
URL: https://issues.apache.org/jira/browse/MARCHETYPES-62
Project: Maven Archetype Bundles
Issue Type: Bug
Components: Maven Skin Archetype
Affects Versions: 1.3
Reporter: Hervé Boutemy
Assignee: Hervé Boutemy
Fix For: 1.4
when generating a site skin from archetype, pom.xml contains:
{code:xml}
/home/herve/projets/maven/git/aggregator/archetypes/target/checkout/maven-archetype-site-skin/src/main/resources
css/print.css
{code}
when it should contain
{code:xml}
${basedir}/src/main/resources
css/print.css
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (SUREFIRE-1588) Surefire manifest jar classloading broken on latest Debian/Ubuntu Java8
[
https://issues.apache.org/jira/browse/SUREFIRE-1588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16670212#comment-16670212
]
ASF GitHub Bot commented on SUREFIRE-1588:
--
Tibor17 edited a comment on issue #197: SUREFIRE-1588 Patch (Java7)
URL: https://github.com/apache/maven-surefire/pull/197#issuecomment-434721855
Hi @cstamas
Thx for the fix. We will release version 3.0.0-M1 and we discontinued
versions 2.x.
The only issue is that we develop new version in branch `3.0.0-M1` and there
are last things to finish support of Maven Plugin API 3.0 as for instance we
want to use `scope=provided` on Maven api dependencies. It should be finished
these days. Next problem is unstable ASF Jenkins. I hope the INFRA team will
fix it soon. Then I plan to have Java 1.7, see
https://issues.apache.org/jira/browse/SUREFIRE-1474, on the top of the branch
`3.0.0-M1` which includes your change with JavaVersion property and Java code
in I/O. But I would rather wait with this PR few days and rebase it after
`SUREFIRE-1474` has been finished too.
This is an automated message from the Apache Git Service.
To respond to the message, please log on 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
> Surefire manifest jar classloading broken on latest Debian/Ubuntu Java8
> ---
>
> Key: SUREFIRE-1588
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1588
> Project: Maven Surefire
> Issue Type: Bug
>Affects Versions: 2.22.1
>Reporter: Cservenak, Tamas
>Priority: Major
>
> See issue [1], but in short: latest Java8 on Ubuntu/Debian/Mint family of
> Linuxes (am on Mint, Ubuntu derivative) contains this patch [3], and eforces
> Manifest class path entries to be relative, as defined in [2].
> Hence, surefire booter and rest of Maven classpath, that uses absolute URLs
> are simply discarded.
> Example error:
> {noformat}
> # Created at 2018-10-30T21:34:43.339
> Error: Could not find or load main class
> org.apache.maven.surefire.booter.ForkedBooter{noformat}
> using the new property
> {{-Djdk.net.URLClassPath.disableClassPathURLCheck=debug}} clearly shows that
> all the entries from the surefire JAR are simply ignored.
>
> [1] [https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911925]
> [2]
> https://docs.oracle.com/javase/8/docs/technotes/guides/jar/jar.html#classpath
> [3] [https://hg.openjdk.java.net/jdk/jdk/rev/27135de165ac]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[GitHub] Tibor17 edited a comment on issue #197: SUREFIRE-1588 Patch (Java7)
Tibor17 edited a comment on issue #197: SUREFIRE-1588 Patch (Java7) URL: https://github.com/apache/maven-surefire/pull/197#issuecomment-434721855 Hi @cstamas Thx for the fix. We will release version 3.0.0-M1 and we discontinued versions 2.x. The only issue is that we develop new version in branch `3.0.0-M1` and there are last things to finish support of Maven Plugin API 3.0 as for instance we want to use `scope=provided` on Maven api dependencies. It should be finished these days. Next problem is unstable ASF Jenkins. I hope the INFRA team will fix it soon. Then I plan to have Java 1.7, see https://issues.apache.org/jira/browse/SUREFIRE-1474, on the top of the branch `3.0.0-M1` which includes your change with JavaVersion property and Java code in I/O. But I would rather wait with this PR few days and rebase it after `SUREFIRE-1474` has been finished too. This is an automated message from the Apache Git Service. To respond to the message, please log on 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 With regards, Apache Git Services
[jira] [Commented] (SUREFIRE-1588) Surefire manifest jar classloading broken on latest Debian/Ubuntu Java8
[
https://issues.apache.org/jira/browse/SUREFIRE-1588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16670209#comment-16670209
]
Cservenak, Tamas commented on SUREFIRE-1588:
A maven-surefire 2.22.1 patch that "works for me":
[https://github.com/apache/maven-surefire/pull/197]
But word of warnings: if you build the PR as-is, you a) will *make surefire
plugin java7* (is java6 currently), and b) will *replace official surefire
plugin 2.22.1 in your local repo* (something you really don't want unless you
know what are you doing)
> Surefire manifest jar classloading broken on latest Debian/Ubuntu Java8
> ---
>
> Key: SUREFIRE-1588
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1588
> Project: Maven Surefire
> Issue Type: Bug
>Affects Versions: 2.22.1
>Reporter: Cservenak, Tamas
>Priority: Major
>
> See issue [1], but in short: latest Java8 on Ubuntu/Debian/Mint family of
> Linuxes (am on Mint, Ubuntu derivative) contains this patch [3], and eforces
> Manifest class path entries to be relative, as defined in [2].
> Hence, surefire booter and rest of Maven classpath, that uses absolute URLs
> are simply discarded.
> Example error:
> {noformat}
> # Created at 2018-10-30T21:34:43.339
> Error: Could not find or load main class
> org.apache.maven.surefire.booter.ForkedBooter{noformat}
> using the new property
> {{-Djdk.net.URLClassPath.disableClassPathURLCheck=debug}} clearly shows that
> all the entries from the surefire JAR are simply ignored.
>
> [1] [https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911925]
> [2]
> https://docs.oracle.com/javase/8/docs/technotes/guides/jar/jar.html#classpath
> [3] [https://hg.openjdk.java.net/jdk/jdk/rev/27135de165ac]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (SUREFIRE-1588) Surefire manifest jar classloading broken on latest Debian/Ubuntu Java8
[
https://issues.apache.org/jira/browse/SUREFIRE-1588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16670208#comment-16670208
]
ASF GitHub Bot commented on SUREFIRE-1588:
--
Tibor17 commented on issue #197: SUREFIRE-1588 Patch (Java7)
URL: https://github.com/apache/maven-surefire/pull/197#issuecomment-434721855
Hi @cstamas
Thx for the fix. We will release version 3.0.0-M1 nd we discontinued
versions 2.x.
The only issue is that we develop new version in branch `3.0.0-M1` and there
are last things to finish support of Maven Plugin API 3.0 as for instance we
want to use `scope=provided` on Maven api dependencies. It should be finished
these days. Next problem is unstable ASF Jenkins. I hope the INFRA team will
fix it soon. Then I plan is to have Java 1.7, see
https://issues.apache.org/jira/browse/SUREFIRE-1474, on the top of the branch
`3.0.0-M1` which includes your change with JavaVersion property and Java code
in I/O. But I would rather wait with this PR few days and rebase it after
`SUREFIRE-1474` has been finished too.
This is an automated message from the Apache Git Service.
To respond to the message, please log on 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
> Surefire manifest jar classloading broken on latest Debian/Ubuntu Java8
> ---
>
> Key: SUREFIRE-1588
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1588
> Project: Maven Surefire
> Issue Type: Bug
>Affects Versions: 2.22.1
>Reporter: Cservenak, Tamas
>Priority: Major
>
> See issue [1], but in short: latest Java8 on Ubuntu/Debian/Mint family of
> Linuxes (am on Mint, Ubuntu derivative) contains this patch [3], and eforces
> Manifest class path entries to be relative, as defined in [2].
> Hence, surefire booter and rest of Maven classpath, that uses absolute URLs
> are simply discarded.
> Example error:
> {noformat}
> # Created at 2018-10-30T21:34:43.339
> Error: Could not find or load main class
> org.apache.maven.surefire.booter.ForkedBooter{noformat}
> using the new property
> {{-Djdk.net.URLClassPath.disableClassPathURLCheck=debug}} clearly shows that
> all the entries from the surefire JAR are simply ignored.
>
> [1] [https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911925]
> [2]
> https://docs.oracle.com/javase/8/docs/technotes/guides/jar/jar.html#classpath
> [3] [https://hg.openjdk.java.net/jdk/jdk/rev/27135de165ac]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[GitHub] Tibor17 commented on issue #197: SUREFIRE-1588 Patch (Java7)
Tibor17 commented on issue #197: SUREFIRE-1588 Patch (Java7) URL: https://github.com/apache/maven-surefire/pull/197#issuecomment-434721855 Hi @cstamas Thx for the fix. We will release version 3.0.0-M1 nd we discontinued versions 2.x. The only issue is that we develop new version in branch `3.0.0-M1` and there are last things to finish support of Maven Plugin API 3.0 as for instance we want to use `scope=provided` on Maven api dependencies. It should be finished these days. Next problem is unstable ASF Jenkins. I hope the INFRA team will fix it soon. Then I plan is to have Java 1.7, see https://issues.apache.org/jira/browse/SUREFIRE-1474, on the top of the branch `3.0.0-M1` which includes your change with JavaVersion property and Java code in I/O. But I would rather wait with this PR few days and rebase it after `SUREFIRE-1474` has been finished too. This is an automated message from the Apache Git Service. To respond to the message, please log on 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 With regards, Apache Git Services
[jira] [Commented] (MNG-6501) Maven always picks the JRE path as java.home
[
https://issues.apache.org/jira/browse/MNG-6501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16670182#comment-16670182
]
Joseph commented on MNG-6501:
-
Even in my local environment also it works in the same fashion (attached the
image)
> Maven always picks the JRE path as java.home
>
>
> Key: MNG-6501
> URL: https://issues.apache.org/jira/browse/MNG-6501
> Project: Maven
> Issue Type: Bug
> Components: core
>Affects Versions: 3.2.3
>Reporter: Joseph
>Priority: Blocker
> Attachments: maven_jdk.png
>
>
> we set the proper JDK directory as JAVA_HOME in the environment variable. but
> the maven is forcefully picking up JRE_HOME.
> Even though the JAVA_HOME is pointing to the proper JDK path.
>
> $ echo $JAVA_HOME
> */apps/dftjenkins/local/java/jdk1.8.0_102*
> $ ls -lrt ${JAVA_HOME}/bin/javac
> -rwxr-xr-x. 1 dftjenkins cisco 7941 Jun 22 2016
> */apps/dftjenkins/local/java/jdk1.8.0_102/bin/javac*
> $ echo $M2_HOME
> /apps/dftjenkins/local/apache-maven/apache-maven-3.2.3
>
> Maven is picking the JRE path as java.home
>
> $ mvn -v
> Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m;
> support was removed in 8.0
> Picked up _JAVA_OPTIONS: -Djava.io.tmpdir=/apps/dftjenkins/jenkins_node/tmp
> Apache Maven 3.2.3 (33f8c3e1027c3ddde99d3cdebad2656a31e8fdf4;
> 2014-08-11T13:58:10-07:00)
> Maven home: /apps/dftjenkins/local/apache-maven/current
> Java version: 1.8.0_102, vendor: Oracle Corporation
> *Java home: /apps/dftjenkins/local/java/jdk1.8.0_102/jre*
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux", version: "3.10.0-693.11.6.el7.x86_64", arch: "amd64",
> family: "unix"
> This issue impact the ant call from maven execution . because java.home is
> pointing to JRE_HOME and the ant compilation fails with
>
> [ERROR] Perhaps JAVA_HOME does not point to the JDK.
> [ERROR] It is currently set to "/apps/dftjenkins/local/java/jdk1.8.0_102/jre"
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (MNG-6501) Maven always picks the JRE path as java.home
[
https://issues.apache.org/jira/browse/MNG-6501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joseph updated MNG-6501:
Attachment: maven_jdk.png
> Maven always picks the JRE path as java.home
>
>
> Key: MNG-6501
> URL: https://issues.apache.org/jira/browse/MNG-6501
> Project: Maven
> Issue Type: Bug
> Components: core
>Affects Versions: 3.2.3
>Reporter: Joseph
>Priority: Blocker
> Attachments: maven_jdk.png
>
>
> we set the proper JDK directory as JAVA_HOME in the environment variable. but
> the maven is forcefully picking up JRE_HOME.
> Even though the JAVA_HOME is pointing to the proper JDK path.
>
> $ echo $JAVA_HOME
> */apps/dftjenkins/local/java/jdk1.8.0_102*
> $ ls -lrt ${JAVA_HOME}/bin/javac
> -rwxr-xr-x. 1 dftjenkins cisco 7941 Jun 22 2016
> */apps/dftjenkins/local/java/jdk1.8.0_102/bin/javac*
> $ echo $M2_HOME
> /apps/dftjenkins/local/apache-maven/apache-maven-3.2.3
>
> Maven is picking the JRE path as java.home
>
> $ mvn -v
> Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m;
> support was removed in 8.0
> Picked up _JAVA_OPTIONS: -Djava.io.tmpdir=/apps/dftjenkins/jenkins_node/tmp
> Apache Maven 3.2.3 (33f8c3e1027c3ddde99d3cdebad2656a31e8fdf4;
> 2014-08-11T13:58:10-07:00)
> Maven home: /apps/dftjenkins/local/apache-maven/current
> Java version: 1.8.0_102, vendor: Oracle Corporation
> *Java home: /apps/dftjenkins/local/java/jdk1.8.0_102/jre*
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux", version: "3.10.0-693.11.6.el7.x86_64", arch: "amd64",
> family: "unix"
> This issue impact the ant call from maven execution . because java.home is
> pointing to JRE_HOME and the ant compilation fails with
>
> [ERROR] Perhaps JAVA_HOME does not point to the JDK.
> [ERROR] It is currently set to "/apps/dftjenkins/local/java/jdk1.8.0_102/jre"
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (SUREFIRE-1588) Surefire manifest jar classloading broken on latest Debian/Ubuntu Java8
[
https://issues.apache.org/jira/browse/SUREFIRE-1588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16670138#comment-16670138
]
Girish Kamath commented on SUREFIRE-1588:
-
I got it working by setting forkCount to 0 in the surefire plugin configuration
{code:java}
org.apache.maven.plugins
maven-surefire-plugin
2.21.0
0
-Xmx1024m -XX:MaxPermSize=256m
{code}
> Surefire manifest jar classloading broken on latest Debian/Ubuntu Java8
> ---
>
> Key: SUREFIRE-1588
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1588
> Project: Maven Surefire
> Issue Type: Bug
>Affects Versions: 2.22.1
>Reporter: Cservenak, Tamas
>Priority: Major
>
> See issue [1], but in short: latest Java8 on Ubuntu/Debian/Mint family of
> Linuxes (am on Mint, Ubuntu derivative) contains this patch [3], and eforces
> Manifest class path entries to be relative, as defined in [2].
> Hence, surefire booter and rest of Maven classpath, that uses absolute URLs
> are simply discarded.
> Example error:
> {noformat}
> # Created at 2018-10-30T21:34:43.339
> Error: Could not find or load main class
> org.apache.maven.surefire.booter.ForkedBooter{noformat}
> using the new property
> {{-Djdk.net.URLClassPath.disableClassPathURLCheck=debug}} clearly shows that
> all the entries from the surefire JAR are simply ignored.
>
> [1] [https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911925]
> [2]
> https://docs.oracle.com/javase/8/docs/technotes/guides/jar/jar.html#classpath
> [3] [https://hg.openjdk.java.net/jdk/jdk/rev/27135de165ac]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (SUREFIRE-1588) Surefire manifest jar classloading broken on latest Debian/Ubuntu Java8
[
https://issues.apache.org/jira/browse/SUREFIRE-1588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cservenak, Tamas updated SUREFIRE-1588:
---
Summary: Surefire manifest jar classloading broken on latest Debian/Ubuntu
Java8 (was: Surefire 2.22.1 (and maybe other versions too) are broken on
latest Ubuntu Java8)
> Surefire manifest jar classloading broken on latest Debian/Ubuntu Java8
> ---
>
> Key: SUREFIRE-1588
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1588
> Project: Maven Surefire
> Issue Type: Bug
>Affects Versions: 2.22.1
>Reporter: Cservenak, Tamas
>Priority: Major
>
> See issue [1], but in short: latest Java8 on Ubuntu/Debian/Mint family of
> Linuxes (am on Mint, Ubuntu derivative) contains this patch [3], and eforces
> Manifest class path entries to be relative, as defined in [2].
> Hence, surefire booter and rest of Maven classpath, that uses absolute URLs
> are simply discarded.
> Example error:
> {noformat}
> # Created at 2018-10-30T21:34:43.339
> Error: Could not find or load main class
> org.apache.maven.surefire.booter.ForkedBooter{noformat}
> using the new property
> {{-Djdk.net.URLClassPath.disableClassPathURLCheck=debug}} clearly shows that
> all the entries from the surefire JAR are simply ignored.
>
> [1] [https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911925]
> [2]
> https://docs.oracle.com/javase/8/docs/technotes/guides/jar/jar.html#classpath
> [3] [https://hg.openjdk.java.net/jdk/jdk/rev/27135de165ac]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (SUREFIRE-1588) Surefire 2.22.1 (and maybe other versions too) are broken on latest Ubuntu Java8
[
https://issues.apache.org/jira/browse/SUREFIRE-1588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16670105#comment-16670105
]
tibi edited comment on SUREFIRE-1588 at 10/31/18 1:31 PM:
--
i can confirm it also happens on 2.22.0
i updated my pom.xml and added this line:
{code:xml}
false{code}
like this:
{code:xml}
org.apache.maven.plugins
maven-surefire-plugin
2.22.1
false
{code}
which did help
or for now skip test using -DskipTests
was (Author: tibi):
i can confirm it also happens on 2.22.0
i updated my pom.xml and added this line:
{code:xml}
false{code}
like this:
{code:xml}
org.apache.maven.plugins
maven-surefire-plugin
2.22.1
false
{code}
which did not help
for now i skip test using -DskipTests
> Surefire 2.22.1 (and maybe other versions too) are broken on latest Ubuntu
> Java8
>
>
> Key: SUREFIRE-1588
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1588
> Project: Maven Surefire
> Issue Type: Bug
>Affects Versions: 2.22.1
>Reporter: Cservenak, Tamas
>Priority: Major
>
> See issue [1], but in short: latest Java8 on Ubuntu/Debian/Mint family of
> Linuxes (am on Mint, Ubuntu derivative) contains this patch [3], and eforces
> Manifest class path entries to be relative, as defined in [2].
> Hence, surefire booter and rest of Maven classpath, that uses absolute URLs
> are simply discarded.
> Example error:
> {noformat}
> # Created at 2018-10-30T21:34:43.339
> Error: Could not find or load main class
> org.apache.maven.surefire.booter.ForkedBooter{noformat}
> using the new property
> {{-Djdk.net.URLClassPath.disableClassPathURLCheck=debug}} clearly shows that
> all the entries from the surefire JAR are simply ignored.
>
> [1] [https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911925]
> [2]
> https://docs.oracle.com/javase/8/docs/technotes/guides/jar/jar.html#classpath
> [3] [https://hg.openjdk.java.net/jdk/jdk/rev/27135de165ac]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (SUREFIRE-1588) Surefire 2.22.1 (and maybe other versions too) are broken on latest Ubuntu Java8
[
https://issues.apache.org/jira/browse/SUREFIRE-1588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16670107#comment-16670107
]
Cservenak, Tamas commented on SUREFIRE-1588:
Re fix:
[https://github.com/apache/maven-surefire/blob/7149edc6f24fa8bff06372e24a177e86d4960d8c/maven-surefire-common/src/main/java/org/apache/maven/plugin/surefire/booterclient/JarManifestForkConfiguration.java#L110]
As the manifest should contain relative paths only (unlike absolute as now),
and generated "manifest jar" is not meant to be relocated, it could easily
calculated the relative paths of the classpath entries, and use them instead?
> Surefire 2.22.1 (and maybe other versions too) are broken on latest Ubuntu
> Java8
>
>
> Key: SUREFIRE-1588
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1588
> Project: Maven Surefire
> Issue Type: Bug
>Affects Versions: 2.22.1
>Reporter: Cservenak, Tamas
>Priority: Major
>
> See issue [1], but in short: latest Java8 on Ubuntu/Debian/Mint family of
> Linuxes (am on Mint, Ubuntu derivative) contains this patch [3], and eforces
> Manifest class path entries to be relative, as defined in [2].
> Hence, surefire booter and rest of Maven classpath, that uses absolute URLs
> are simply discarded.
> Example error:
> {noformat}
> # Created at 2018-10-30T21:34:43.339
> Error: Could not find or load main class
> org.apache.maven.surefire.booter.ForkedBooter{noformat}
> using the new property
> {{-Djdk.net.URLClassPath.disableClassPathURLCheck=debug}} clearly shows that
> all the entries from the surefire JAR are simply ignored.
>
> [1] [https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911925]
> [2]
> https://docs.oracle.com/javase/8/docs/technotes/guides/jar/jar.html#classpath
> [3] [https://hg.openjdk.java.net/jdk/jdk/rev/27135de165ac]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (SUREFIRE-1588) Surefire 2.22.1 (and maybe other versions too) are broken on latest Ubuntu Java8
[
https://issues.apache.org/jira/browse/SUREFIRE-1588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16670105#comment-16670105
]
tibi commented on SUREFIRE-1588:
i can confirm it also happens on 2.22.0
i updated my pom.xml and added this line:
{code:xml}
false{code}
like this:
{code:xml}
org.apache.maven.plugins
maven-surefire-plugin
2.22.1
false
{code}
which did not help
for now i skip test using -DskipTests
> Surefire 2.22.1 (and maybe other versions too) are broken on latest Ubuntu
> Java8
>
>
> Key: SUREFIRE-1588
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1588
> Project: Maven Surefire
> Issue Type: Bug
>Affects Versions: 2.22.1
>Reporter: Cservenak, Tamas
>Priority: Major
>
> See issue [1], but in short: latest Java8 on Ubuntu/Debian/Mint family of
> Linuxes (am on Mint, Ubuntu derivative) contains this patch [3], and eforces
> Manifest class path entries to be relative, as defined in [2].
> Hence, surefire booter and rest of Maven classpath, that uses absolute URLs
> are simply discarded.
> Example error:
> {noformat}
> # Created at 2018-10-30T21:34:43.339
> Error: Could not find or load main class
> org.apache.maven.surefire.booter.ForkedBooter{noformat}
> using the new property
> {{-Djdk.net.URLClassPath.disableClassPathURLCheck=debug}} clearly shows that
> all the entries from the surefire JAR are simply ignored.
>
> [1] [https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911925]
> [2]
> https://docs.oracle.com/javase/8/docs/technotes/guides/jar/jar.html#classpath
> [3] [https://hg.openjdk.java.net/jdk/jdk/rev/27135de165ac]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (SUREFIRE-1589) mvn test does not run any test error: Could not find or load main class org.apache.maven.surefire.booter.ForkedBooter
[ https://issues.apache.org/jira/browse/SUREFIRE-1589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cservenak, Tamas resolved SUREFIRE-1589. Resolution: Duplicate > mvn test does not run any test error: Could not find or load main class > org.apache.maven.surefire.booter.ForkedBooter > - > > Key: SUREFIRE-1589 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1589 > Project: Maven Surefire > Issue Type: Bug >Affects Versions: 2.22.1 >Reporter: tibi >Priority: Major > > when running mvn test on a fresh jhipster* project i get the following error: > > Error: Could not find or load main class > org.apache.maven.surefire.booter.ForkedBooter > this is the output on console: > [INFO] Results: > [INFO] > [INFO] Tests run: 0, Failures: 0, Errors: 0, Skipped: 0 > [INFO] > [INFO] > > [INFO] BUILD FAILURE > [INFO] > > [INFO] Total time: 47.236 s > [INFO] Finished at: 2018-10-31T13:54:49+01:00 > [INFO] > > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-surefire-plugin:2.22.0:test (default-test) on > project stand-bystand: There are test failures. > [ERROR] > [ERROR] Please refer to /home/tibi/git/mvntest/target/surefire-reports for > the individual test results. > [ERROR] Please refer to dump files (if any exist) [date]-jvmRun[N].dump, > [date].dumpstream and [date]-jvmRun[N].dumpstream. > [ERROR] The forked VM terminated without properly saying goodbye. VM crash or > System.exit called? > [ERROR] Command was /bin/sh -c cd /home/tibi/git/mvntest && > /usr/lib/jvm/java-8-openjdk-amd64/jre/bin/java > -javaagent:/home/tibi/.m2/repository/org/jacoco/org.jacoco.agent/0.8.2/org.jacoco.agent-0.8.2-runtime.jar=destfile=/home/tibi/git/mvntest/target/test-results/coverage/jacoco/jacoco.exec > -Djava.security.egd=file:/dev/./urandom -Xmx256m -jar > /home/tibi/git/mvntest/target/surefire/surefirebooter9169551205789441059.jar > /home/tibi/git/mvntest/target/surefire 2018-10-31T13-54-48_997-jvmRun1 > surefire4367139397955700461tmp surefire_09091753917082460771tmp > [ERROR] Error occurred in starting fork, check output in log > > > *jhipster is a java angular project generator. i use it for a year and mvn > test worked fine up to today. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (SUREFIRE-1588) Surefire 2.22.1 (and maybe other versions too) are broken on latest Ubuntu Java8
[
https://issues.apache.org/jira/browse/SUREFIRE-1588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16670087#comment-16670087
]
Cservenak, Tamas commented on SUREFIRE-1588:
Currently several workarounds exists, none of them are w/o problems:
# Set {{useSystemClassLoader}} = false in POM (this may work if your app is
"well behaved", see
[https://maven.apache.org/surefire/maven-surefire-plugin/examples/class-loading.html]
# Set {{jdk.net.URLClassPath.disableClassPathURLCheck=true}} system property
on forked JVM (see {{argLine}} configuration)
On my setup (again, this is project dependant, see 1. bullet), both works ok.
> Surefire 2.22.1 (and maybe other versions too) are broken on latest Ubuntu
> Java8
>
>
> Key: SUREFIRE-1588
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1588
> Project: Maven Surefire
> Issue Type: Bug
>Affects Versions: 2.22.1
>Reporter: Cservenak, Tamas
>Priority: Major
>
> See issue [1], but in short: latest Java8 on Ubuntu/Debian/Mint family of
> Linuxes (am on Mint, Ubuntu derivative) contains this patch [3], and eforces
> Manifest class path entries to be relative, as defined in [2].
> Hence, surefire booter and rest of Maven classpath, that uses absolute URLs
> are simply discarded.
> Example error:
> {noformat}
> # Created at 2018-10-30T21:34:43.339
> Error: Could not find or load main class
> org.apache.maven.surefire.booter.ForkedBooter{noformat}
> using the new property
> {{-Djdk.net.URLClassPath.disableClassPathURLCheck=debug}} clearly shows that
> all the entries from the surefire JAR are simply ignored.
>
> [1] [https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911925]
> [2]
> https://docs.oracle.com/javase/8/docs/technotes/guides/jar/jar.html#classpath
> [3] [https://hg.openjdk.java.net/jdk/jdk/rev/27135de165ac]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (SUREFIRE-1588) Surefire 2.22.1 (and maybe other versions too) are broken on latest Ubuntu Java8
[
https://issues.apache.org/jira/browse/SUREFIRE-1588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16670083#comment-16670083
]
Thorsten Glaser commented on SUREFIRE-1588:
---
This is apparently a bug in the Debian package, in that they did not backport
the patch that disables these new stricter checks by default:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911925#38
There’s a workaround, but that involves either touching the POM of *every*
project one develops with manually to set useSystemClassLoader=false for
Surefire (and I’m not sure what other implications this has)
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911925#10 or, worse, setting
a JVM property (I’m not sure where to even begin doing so, considering java is
invoked indirectly under a bazillion layers, from Jenkins over Maven to its
plugins…) https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911925#29
Considering this is supposed to be a new stricter check for something, is there
a way we can get a new Surefire release that adheres to these stricter
standards? The Canonical/Debian people are, unfortunately, unwilling to
consider a full development showstopper as bug and consider it a “security
feature” and an “intentional upstream change” instead:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912333#53
For now, general advice is to downgrade to the last working OpenJDK version in
a development environment (and yes, thus not getting the latest security fixes,
which is extremely unfortunate) until the OpenJDK, Canonical/Debian, and
Maven/Surefire people “fight” this out among themselves. (And who knows what
*else* will break due to this change… there’s not even a warning output!)
> Surefire 2.22.1 (and maybe other versions too) are broken on latest Ubuntu
> Java8
>
>
> Key: SUREFIRE-1588
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1588
> Project: Maven Surefire
> Issue Type: Bug
>Affects Versions: 2.22.1
>Reporter: Cservenak, Tamas
>Priority: Major
>
> See issue [1], but in short: latest Java8 on Ubuntu/Debian/Mint family of
> Linuxes (am on Mint, Ubuntu derivative) contains this patch [3], and eforces
> Manifest class path entries to be relative, as defined in [2].
> Hence, surefire booter and rest of Maven classpath, that uses absolute URLs
> are simply discarded.
> Example error:
> {noformat}
> # Created at 2018-10-30T21:34:43.339
> Error: Could not find or load main class
> org.apache.maven.surefire.booter.ForkedBooter{noformat}
> using the new property
> {{-Djdk.net.URLClassPath.disableClassPathURLCheck=debug}} clearly shows that
> all the entries from the surefire JAR are simply ignored.
>
> [1] [https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911925]
> [2]
> https://docs.oracle.com/javase/8/docs/technotes/guides/jar/jar.html#classpath
> [3] [https://hg.openjdk.java.net/jdk/jdk/rev/27135de165ac]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (SUREFIRE-1589) mvn test does not run any test error: Could not find or load main class org.apache.maven.surefire.booter.ForkedBooter
[ https://issues.apache.org/jira/browse/SUREFIRE-1589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16670080#comment-16670080 ] tibi commented on SUREFIRE-1589: yes on ubuntu check then this is a duplicate! > mvn test does not run any test error: Could not find or load main class > org.apache.maven.surefire.booter.ForkedBooter > - > > Key: SUREFIRE-1589 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1589 > Project: Maven Surefire > Issue Type: Bug >Affects Versions: 2.22.1 >Reporter: tibi >Priority: Major > > when running mvn test on a fresh jhipster* project i get the following error: > > Error: Could not find or load main class > org.apache.maven.surefire.booter.ForkedBooter > this is the output on console: > [INFO] Results: > [INFO] > [INFO] Tests run: 0, Failures: 0, Errors: 0, Skipped: 0 > [INFO] > [INFO] > > [INFO] BUILD FAILURE > [INFO] > > [INFO] Total time: 47.236 s > [INFO] Finished at: 2018-10-31T13:54:49+01:00 > [INFO] > > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-surefire-plugin:2.22.0:test (default-test) on > project stand-bystand: There are test failures. > [ERROR] > [ERROR] Please refer to /home/tibi/git/mvntest/target/surefire-reports for > the individual test results. > [ERROR] Please refer to dump files (if any exist) [date]-jvmRun[N].dump, > [date].dumpstream and [date]-jvmRun[N].dumpstream. > [ERROR] The forked VM terminated without properly saying goodbye. VM crash or > System.exit called? > [ERROR] Command was /bin/sh -c cd /home/tibi/git/mvntest && > /usr/lib/jvm/java-8-openjdk-amd64/jre/bin/java > -javaagent:/home/tibi/.m2/repository/org/jacoco/org.jacoco.agent/0.8.2/org.jacoco.agent-0.8.2-runtime.jar=destfile=/home/tibi/git/mvntest/target/test-results/coverage/jacoco/jacoco.exec > -Djava.security.egd=file:/dev/./urandom -Xmx256m -jar > /home/tibi/git/mvntest/target/surefire/surefirebooter9169551205789441059.jar > /home/tibi/git/mvntest/target/surefire 2018-10-31T13-54-48_997-jvmRun1 > surefire4367139397955700461tmp surefire_09091753917082460771tmp > [ERROR] Error occurred in starting fork, check output in log > > > *jhipster is a java angular project generator. i use it for a year and mvn > test worked fine up to today. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (SUREFIRE-1589) mvn test does not run any test error: Could not find or load main class org.apache.maven.surefire.booter.ForkedBooter
[ https://issues.apache.org/jira/browse/SUREFIRE-1589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16670076#comment-16670076 ] Cservenak, Tamas commented on SUREFIRE-1589: "and mvn test worked fine up to today."... what OS are you on? If Ubuntu/Debian/Mint (or some derivative), Java updates were sent out yesterday. See SUREFIRE-1588 in that case. > mvn test does not run any test error: Could not find or load main class > org.apache.maven.surefire.booter.ForkedBooter > - > > Key: SUREFIRE-1589 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1589 > Project: Maven Surefire > Issue Type: Bug >Affects Versions: 2.22.1 >Reporter: tibi >Priority: Major > > when running mvn test on a fresh jhipster* project i get the following error: > > Error: Could not find or load main class > org.apache.maven.surefire.booter.ForkedBooter > this is the output on console: > [INFO] Results: > [INFO] > [INFO] Tests run: 0, Failures: 0, Errors: 0, Skipped: 0 > [INFO] > [INFO] > > [INFO] BUILD FAILURE > [INFO] > > [INFO] Total time: 47.236 s > [INFO] Finished at: 2018-10-31T13:54:49+01:00 > [INFO] > > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-surefire-plugin:2.22.0:test (default-test) on > project stand-bystand: There are test failures. > [ERROR] > [ERROR] Please refer to /home/tibi/git/mvntest/target/surefire-reports for > the individual test results. > [ERROR] Please refer to dump files (if any exist) [date]-jvmRun[N].dump, > [date].dumpstream and [date]-jvmRun[N].dumpstream. > [ERROR] The forked VM terminated without properly saying goodbye. VM crash or > System.exit called? > [ERROR] Command was /bin/sh -c cd /home/tibi/git/mvntest && > /usr/lib/jvm/java-8-openjdk-amd64/jre/bin/java > -javaagent:/home/tibi/.m2/repository/org/jacoco/org.jacoco.agent/0.8.2/org.jacoco.agent-0.8.2-runtime.jar=destfile=/home/tibi/git/mvntest/target/test-results/coverage/jacoco/jacoco.exec > -Djava.security.egd=file:/dev/./urandom -Xmx256m -jar > /home/tibi/git/mvntest/target/surefire/surefirebooter9169551205789441059.jar > /home/tibi/git/mvntest/target/surefire 2018-10-31T13-54-48_997-jvmRun1 > surefire4367139397955700461tmp surefire_09091753917082460771tmp > [ERROR] Error occurred in starting fork, check output in log > > > *jhipster is a java angular project generator. i use it for a year and mvn > test worked fine up to today. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (SUREFIRE-1589) mvn test does not run any test error: Could not find or load main class org.apache.maven.surefire.booter.ForkedBooter
tibi created SUREFIRE-1589: -- Summary: mvn test does not run any test error: Could not find or load main class org.apache.maven.surefire.booter.ForkedBooter Key: SUREFIRE-1589 URL: https://issues.apache.org/jira/browse/SUREFIRE-1589 Project: Maven Surefire Issue Type: Bug Affects Versions: 2.22.1 Reporter: tibi when running mvn test on a fresh jhipster* project i get the following error: Error: Could not find or load main class org.apache.maven.surefire.booter.ForkedBooter this is the output on console: [INFO] Results: [INFO] [INFO] Tests run: 0, Failures: 0, Errors: 0, Skipped: 0 [INFO] [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 47.236 s [INFO] Finished at: 2018-10-31T13:54:49+01:00 [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.22.0:test (default-test) on project stand-bystand: There are test failures. [ERROR] [ERROR] Please refer to /home/tibi/git/mvntest/target/surefire-reports for the individual test results. [ERROR] Please refer to dump files (if any exist) [date]-jvmRun[N].dump, [date].dumpstream and [date]-jvmRun[N].dumpstream. [ERROR] The forked VM terminated without properly saying goodbye. VM crash or System.exit called? [ERROR] Command was /bin/sh -c cd /home/tibi/git/mvntest && /usr/lib/jvm/java-8-openjdk-amd64/jre/bin/java -javaagent:/home/tibi/.m2/repository/org/jacoco/org.jacoco.agent/0.8.2/org.jacoco.agent-0.8.2-runtime.jar=destfile=/home/tibi/git/mvntest/target/test-results/coverage/jacoco/jacoco.exec -Djava.security.egd=file:/dev/./urandom -Xmx256m -jar /home/tibi/git/mvntest/target/surefire/surefirebooter9169551205789441059.jar /home/tibi/git/mvntest/target/surefire 2018-10-31T13-54-48_997-jvmRun1 surefire4367139397955700461tmp surefire_09091753917082460771tmp [ERROR] Error occurred in starting fork, check output in log *jhipster is a java angular project generator. i use it for a year and mvn test worked fine up to today. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (MNG-6501) Maven always picks the JRE path as java.home
Joseph created MNG-6501:
---
Summary: Maven always picks the JRE path as java.home
Key: MNG-6501
URL: https://issues.apache.org/jira/browse/MNG-6501
Project: Maven
Issue Type: Bug
Components: core
Affects Versions: 3.2.3
Reporter: Joseph
we set the proper JDK directory as JAVA_HOME in the environment variable. but
the maven is forcefully picking up JRE_HOME.
Even though the JAVA_HOME is pointing to the proper JDK path.
$ echo $JAVA_HOME
*/apps/dftjenkins/local/java/jdk1.8.0_102*
$ ls -lrt ${JAVA_HOME}/bin/javac
-rwxr-xr-x. 1 dftjenkins cisco 7941 Jun 22 2016
*/apps/dftjenkins/local/java/jdk1.8.0_102/bin/javac*
$ echo $M2_HOME
/apps/dftjenkins/local/apache-maven/apache-maven-3.2.3
Maven is picking the JRE path as java.home
$ mvn -v
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m;
support was removed in 8.0
Picked up _JAVA_OPTIONS: -Djava.io.tmpdir=/apps/dftjenkins/jenkins_node/tmp
Apache Maven 3.2.3 (33f8c3e1027c3ddde99d3cdebad2656a31e8fdf4;
2014-08-11T13:58:10-07:00)
Maven home: /apps/dftjenkins/local/apache-maven/current
Java version: 1.8.0_102, vendor: Oracle Corporation
*Java home: /apps/dftjenkins/local/java/jdk1.8.0_102/jre*
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "3.10.0-693.11.6.el7.x86_64", arch: "amd64", family:
"unix"
This issue impact the ant call from maven execution . because java.home is
pointing to JRE_HOME and the ant compilation fails with
[ERROR] Perhaps JAVA_HOME does not point to the JDK.
[ERROR] It is currently set to "/apps/dftjenkins/local/java/jdk1.8.0_102/jre"
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (SUREFIRE-1588) Surefire 2.22.1 (and maybe other versions too) are broken on latest Ubuntu Java8
[
https://issues.apache.org/jira/browse/SUREFIRE-1588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cservenak, Tamas updated SUREFIRE-1588:
---
Description:
See issue [1], but in short: latest Java8 on Ubuntu/Debian/Mint family of
Linuxes (am on Mint, Ubuntu derivative) contains this patch [3], and eforces
Manifest class path entries to be relative, as defined in [2].
Hence, surefire booter and rest of Maven classpath, that uses absolute URLs are
simply discarded.
Example error:
{noformat}
# Created at 2018-10-30T21:34:43.339
Error: Could not find or load main class
org.apache.maven.surefire.booter.ForkedBooter{noformat}
using the new property
{{-Djdk.net.URLClassPath.disableClassPathURLCheck=debug}} clearly shows that
all the entries from the surefire JAR are simply ignored.
[1] [https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911925]
[2]
https://docs.oracle.com/javase/8/docs/technotes/guides/jar/jar.html#classpath
[3] [https://hg.openjdk.java.net/jdk/jdk/rev/27135de165ac]
was:
See issue [1], but in short: latest Java8 on Ubuntu family of Linuxes (am on
Mint, Ubuntu derivative) contains this patch [3], and eforces Manifest class
path entries to be relative, as defined in [2].
Hence, surefire booter and rest of Maven classpath, that uses absolute URLs are
simply discarded.
Example error:
{noformat}
# Created at 2018-10-30T21:34:43.339
Error: Could not find or load main class
org.apache.maven.surefire.booter.ForkedBooter{noformat}
using the new property
{{-Djdk.net.URLClassPath.disableClassPathURLCheck=debug}} clearly shows that
all the entries from the surefire JAR are simply ignored.
[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911925
[2]
[https://docs.oracle.com/javase/8/docs/technotes/guides/jar/jar.html#classpath|https://docs.oracle.com/javase/8/docs/technotes/guides/jar/jar.html#classpath[1]
[3] [https://hg.openjdk.java.net/jdk/jdk/rev/27135de165ac]
> Surefire 2.22.1 (and maybe other versions too) are broken on latest Ubuntu
> Java8
>
>
> Key: SUREFIRE-1588
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1588
> Project: Maven Surefire
> Issue Type: Bug
>Affects Versions: 2.22.1
>Reporter: Cservenak, Tamas
>Priority: Major
>
> See issue [1], but in short: latest Java8 on Ubuntu/Debian/Mint family of
> Linuxes (am on Mint, Ubuntu derivative) contains this patch [3], and eforces
> Manifest class path entries to be relative, as defined in [2].
> Hence, surefire booter and rest of Maven classpath, that uses absolute URLs
> are simply discarded.
> Example error:
> {noformat}
> # Created at 2018-10-30T21:34:43.339
> Error: Could not find or load main class
> org.apache.maven.surefire.booter.ForkedBooter{noformat}
> using the new property
> {{-Djdk.net.URLClassPath.disableClassPathURLCheck=debug}} clearly shows that
> all the entries from the surefire JAR are simply ignored.
>
> [1] [https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911925]
> [2]
> https://docs.oracle.com/javase/8/docs/technotes/guides/jar/jar.html#classpath
> [3] [https://hg.openjdk.java.net/jdk/jdk/rev/27135de165ac]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (SUREFIRE-1588) Surefire 2.22.1 (and maybe other versions too) are broken on latest Ubuntu Java8
[
https://issues.apache.org/jira/browse/SUREFIRE-1588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16669907#comment-16669907
]
Lasse Westh-Nielsen commented on SUREFIRE-1588:
---
This is a complete production halt for us, please fix soon, thanks!
> Surefire 2.22.1 (and maybe other versions too) are broken on latest Ubuntu
> Java8
>
>
> Key: SUREFIRE-1588
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1588
> Project: Maven Surefire
> Issue Type: Bug
>Affects Versions: 2.22.1
>Reporter: Cservenak, Tamas
>Priority: Major
>
> See issue [1], but in short: latest Java8 on Ubuntu family of Linuxes (am on
> Mint, Ubuntu derivative) contains this patch [3], and eforces Manifest class
> path entries to be relative, as defined in [2].
> Hence, surefire booter and rest of Maven classpath, that uses absolute URLs
> are simply discarded.
> Example error:
> {noformat}
> # Created at 2018-10-30T21:34:43.339
> Error: Could not find or load main class
> org.apache.maven.surefire.booter.ForkedBooter{noformat}
> using the new property
> {{-Djdk.net.URLClassPath.disableClassPathURLCheck=debug}} clearly shows that
> all the entries from the surefire JAR are simply ignored.
>
> [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911925
> [2]
> [https://docs.oracle.com/javase/8/docs/technotes/guides/jar/jar.html#classpath|https://docs.oracle.com/javase/8/docs/technotes/guides/jar/jar.html#classpath[1]
> [3] [https://hg.openjdk.java.net/jdk/jdk/rev/27135de165ac]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MRESOLVER-55) Artifact download failures
[ https://issues.apache.org/jira/browse/MRESOLVER-55?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16669885#comment-16669885 ] Michael Osipov commented on MRESOLVER-55: - That's really really confusing, the connection timeout should cause an exception. Can you isolate the issue w/o the CI system? At best, with a Wireshark dump. The TCP packets should show us the issue, hopefully. > Artifact download failures > -- > > Key: MRESOLVER-55 > URL: https://issues.apache.org/jira/browse/MRESOLVER-55 > Project: Maven Resolver > Issue Type: Bug > Components: resolver >Affects Versions: Maven Artifact Resolver 1.1.1 > Environment: Windows, Ubuntu >Reporter: Lasse Westh-Nielsen >Priority: Major > Fix For: waiting-for-feedback > > > Hey, > We often run Maven builds of [https://github.com/neo4j/neo4j] on machines > with cold caches/ empty ~/.m2/repository folders. > There are rather a lot of dependencies to download, so even though the > failure rate of individual artifact downloads is small, at our scale it > causes significant build failures. > I am working on seeding caches. Separately though it would be great to be > able to configure retries and timeouts for dependency downloads - optimise > for build throughput rather than latency as it were. > How do I do that? I can't find it documented anywhere, and trying to browse > "wagon" source code got me nowhere. > Regards, > Lasse > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (MRESOLVER-55) Artifact download failures
[
https://issues.apache.org/jira/browse/MRESOLVER-55?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16668644#comment-16668644
]
Michael Osipov edited comment on MRESOLVER-55 at 10/31/18 10:15 AM:
[~michael-o] There are no errors in our artifactory.log and there is nothing in
our artifactory request log except for lines with 200(OK) so I don't think the
artifactory is even seeing the request that fails. The errors happen on our CI
system when multiple builds are going on so I think it is due to network
congestion. Sorry, but I am not sure what you mean by "fully on your side".
In the build log just before the connect timeout occurs there is this info:
{noformat}
[12:09:36]W: [:] FINE: http-outgoing-6 <<
Content-Length: 40
[12:09:36]W: [:] Oct 30, 2018 12:09:36 PM
org.apache.maven.wagon.providers.http.httpclient.headers onResponseReceived
[12:09:36]W: [:] FINE: http-outgoing-6 << Date:
Tue, 30 Oct 2018 12:08:42 GMT
[12:09:36]W: [:] Oct 30, 2018 12:09:36 PM
org.apache.maven.wagon.providers.http.httpclient.impl.execchain.MainClientExec
execute
[12:09:36]W: [:] FINE: Connection can be kept
alive indefinitely
[12:09:36]W: [:] Oct 30, 2018 12:09:36 PM
org.apache.maven.wagon.providers.http.httpclient.impl.conn.PoolingHttpClientConnectionManager
releaseConnection
[12:09:36]W: [:] FINE: Connection [id: 6][route:
\{s}->https://: can be kept alive indefinitely
[12:09:36]W: [:] Oct 30, 2018 12:09:36 PM
org.apache.maven.wagon.providers.http.httpclient.impl.conn.PoolingHttpClientConnectionManager
releaseConnection
[12:09:36]W: [:] FINE: Connection released: [id:
6][route: \{s}->https://:][total kept alive: 3; route
allocated: 4 of 20; total allocated: 4 of 40]
[12:09:36] : [Step 2/8] [INFO] Downloaded:
https://:/.jar (3806 KB
at 116.0 KB/sec)
[12:10:03]W: [:] Oct 30, 2018 12:10:03 PM
org.apache.maven.wagon.providers.http.httpclient.impl.conn.DefaultManagedHttpClientConnection
shutdown
[12:10:03]W: [:] FINE: http-outgoing-8: Shutdown
connection
[12:10:03]W: [:] Oct 30, 2018 12:10:03 PM
org.apache.maven.wagon.providers.http.httpclient.impl.execchain.MainClientExec
abortConnection
[12:10:03]W: [:] FINE: Connection discarded
[12:10:03]W: [:] Oct 30, 2018 12:10:03 PM
org.apache.maven.wagon.providers.http.httpclient.impl.conn.DefaultManagedHttpClientConnection
close
[12:10:03]W: [:] FINE: http-outgoing-8: Close
connection
[12:10:03]W: [:] Oct 30, 2018 12:10:03 PM
org.apache.maven.wagon.providers.http.httpclient.impl.conn.PoolingHttpClientConnectionManager
releaseConnection
[12:10:03]W: [:] FINE: Connection released: [id:
8][route: \{s}->https://:][total kept alive: 3; route
allocated: 3 of 20; total allocated: 3 of 40]
[12:10:11] : [Step 2/8] [Maven Watcher]
[12:10:11]E: [Step 2/8] Failed to execute goal on project :
Could not resolve dependencies for project
::pom:: Could not transfer artifact
::jar: from/to
(https://:/): Connect to
: [/] failed: connect timed out
{noformat}
The settings.xml contains the following:
{code:xml}
6
6
true
{code}
I dont see anything in the build log showing +any+ retries for connect.
was (Author: gordon.c...@zafin.com):
[~michael-o] There are no errors in our artifactory.log and there is nothing in
our artifactory request log except for lines with 200(OK) so I don't think the
artifactory is even seeing the request that fails. The errors happen on our CI
system when multiple builds are going on so I think it is due to network
congestion. Sorry, but I am not sure what you mean by "fully on your side".
In the build log just before the connect timeout occurs there is this info:
[12:09:36]W: [:] FINE: http-outgoing-6 <<
Content-Length: 40
[12:09:36]W: [:] Oct 30, 2018 12:09:36 PM
org.apache.maven.wagon.providers.http.httpclient.headers onResponseReceived
[12:09:36]W: [:] FINE: http-outgoing-6 << Date:
Tue, 30 Oct 2018 12:08:42 GMT
[12:09:36]W: [:] Oct 30, 2018 12:09:36 PM
org.apache.maven.wagon.providers.http.httpclient.impl.execchain.MainClientExec
execute
[12:09:36]W: [:] FINE: Connection can be kept
alive indefinitely
[12:09:36]W: [:] Oct 30, 2018 12:09:36 PM
org.apache.maven.wagon.providers.http.httpclient.impl.conn.PoolingHttpClientConnectionManager
releaseConnection
[12:09:36]W: [:] FINE: Connection [id: 6][route:
\{s}->https://: can be kept alive indefinitely
[12:09:36]W: [:] Oct 30, 2018 12:09:36 PM
org.apache.maven.wagon.providers.http.httpclient.impl.conn.PoolingHttpClientConnectionManager
releaseConnection
[12:09:36]W: [:] FINE: Connection released: [id:
6][route: \{s}->https://:][total kept alive: 3; route
allocated: 4 of 20;
[jira] [Closed] (MPMD-275) Upgrade to PMD 6.9.0
[ https://issues.apache.org/jira/browse/MPMD-275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Dangel closed MPMD-275. --- > Upgrade to PMD 6.9.0 > > > Key: MPMD-275 > URL: https://issues.apache.org/jira/browse/MPMD-275 > Project: Maven PMD Plugin > Issue Type: Dependency upgrade > Components: CPD, PMD >Reporter: Andreas Dangel >Assignee: Andreas Dangel >Priority: Major > Fix For: 3.12.0 > > > See PR [https://github.com/apache/maven-pmd-plugin/pull/5/files] > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (MPMD-275) Upgrade to PMD 6.9.0
[ https://issues.apache.org/jira/browse/MPMD-275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Dangel updated MPMD-275: Fix Version/s: 3.12.0 > Upgrade to PMD 6.9.0 > > > Key: MPMD-275 > URL: https://issues.apache.org/jira/browse/MPMD-275 > Project: Maven PMD Plugin > Issue Type: Dependency upgrade > Components: CPD, PMD >Reporter: Andreas Dangel >Assignee: Andreas Dangel >Priority: Major > Fix For: 3.12.0 > > > See PR [https://github.com/apache/maven-pmd-plugin/pull/5/files] > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MSITE-828) Jdk 1.8 required / Upgrade Jetty Version 9.4.12
[ https://issues.apache.org/jira/browse/MSITE-828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16669674#comment-16669674 ] ASF GitHub Bot commented on MSITE-828: -- olamy commented on a change in pull request #3: [MSITE-828] Upgrade jetty to recent version. Update to java 1.8 (required for jetty) URL: https://github.com/apache/maven-site-plugin/pull/3#discussion_r229574062 ## File path: pom.xml ## @@ -392,20 +394,34 @@ under the License. - org.mortbay.jetty - jetty - 6.1.25 + org.eclipse.jetty + jetty-server + 9.4.11.v20180605 Review comment: the last version is `9.4.12.v20180830` and I would prefer having this version in a property instead of few repeats. This is an automated message from the Apache Git Service. To respond to the message, please log on 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 > Jdk 1.8 required / Upgrade Jetty Version 9.4.12 > --- > > Key: MSITE-828 > URL: https://issues.apache.org/jira/browse/MSITE-828 > Project: Maven Site Plugin > Issue Type: Task >Reporter: Olivier Lamy (*$^¨%`£) >Assignee: Olivier Lamy (*$^¨%`£) >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MSITE-828) Jdk 1.8 required / Upgrade Jetty Version 9.4.12
[ https://issues.apache.org/jira/browse/MSITE-828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16669667#comment-16669667 ] ASF GitHub Bot commented on MSITE-828: -- olamy commented on a change in pull request #3: [MSITE-828] Upgrade jetty to recent version. Update to java 1.8 (required for jetty) URL: https://github.com/apache/maven-site-plugin/pull/3#discussion_r229574062 ## File path: pom.xml ## @@ -392,20 +394,34 @@ under the License. - org.mortbay.jetty - jetty - 6.1.25 + org.eclipse.jetty + jetty-server + 9.4.11.v20180605 Review comment: the last version is `9.4.12.v20180830` and would prefer having this version in a property. This is an automated message from the Apache Git Service. To respond to the message, please log on 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 > Jdk 1.8 required / Upgrade Jetty Version 9.4.12 > --- > > Key: MSITE-828 > URL: https://issues.apache.org/jira/browse/MSITE-828 > Project: Maven Site Plugin > Issue Type: Task >Reporter: Olivier Lamy (*$^¨%`£) >Assignee: Olivier Lamy (*$^¨%`£) >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
