[GitHub] [maven-resolver] olamy merged pull request #27: document IllegalArgumentException thrown by CTR
olamy merged pull request #27: document IllegalArgumentException thrown by CTR URL: https://github.com/apache/maven-resolver/pull/27 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[jira] [Commented] (DOXIA-575) Add support for (X)HTML5
[ https://issues.apache.org/jira/browse/DOXIA-575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16785039#comment-16785039 ] Graham Leggett commented on DOXIA-575: -- > * Why have specialized items replaced with inline? What is the purpose? More on this - as I recall, doxia has very limited coverage of html4 - the vast majority of html4 tags are unsupported. Faced with a choice of spending soul destroying days trying to bend an html5 website into something that not only has to fit into html4, but also has to fit into doxia's subset of html4, we decided to just fix doxia instead. Taking the spec for html5.2, I added every single supported tag. The idea is someone writing docuemntation can just get on with writing the documentation, and not have to sit wondering why the formatting is all broken. The "styles" that were there previously are now proper tags in html5, and these have been expanded into the "inline" elements. > Add support for (X)HTML5 > > > Key: DOXIA-575 > URL: https://issues.apache.org/jira/browse/DOXIA-575 > Project: Maven Doxia > Issue Type: Improvement > Components: Core >Affects Versions: 1.8 >Reporter: Graham Leggett >Assignee: Michael Osipov >Priority: Major > Fix For: 1.9 > > Attachments: DOXIA-575.patch > > > Doxia currently generates XHTML v1.1, and does not support any of the new > HTML5 tags. > Update Doxia to support HTML5.2 as per https://www.w3.org/TR/html52/. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] [maven-shade-plugin] pes2009j commented on issue #10: [MSHADE-306] log all duplicates to not silently swallow a duplicate and an implicit selection
pes2009j commented on issue #10: [MSHADE-306] log all duplicates to not silently swallow a duplicate and an implicit selection URL: https://github.com/apache/maven-shade-plugin/pull/10#issuecomment-469848063 ipad This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[jira] [Commented] (MJAVADOC-583) javadoc: error - The code being documented uses modules but the packages defined in {URL} are in the unnamed module
[
https://issues.apache.org/jira/browse/MJAVADOC-583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16784878#comment-16784878
]
Sjoerd Talsma commented on MJAVADOC-583:
Could it be as simple as a Set having been replaced by a non-unique collection
somewhere in the plugin?
> javadoc: error - The code being documented uses modules but the packages
> defined in {URL} are in the unnamed module
> ---
>
> Key: MJAVADOC-583
> URL: https://issues.apache.org/jira/browse/MJAVADOC-583
> Project: Maven Javadoc Plugin
> Issue Type: Bug
> Components: jar
>Affects Versions: 3.1.0
> Environment: Travis CI, toolchain with openjdk 11.0.2
>Reporter: Sjoerd Talsma
>Priority: Major
> Attachments:
> context-propagation-dependabot-maven-org.apache.maven.plugins-maven-javadoc-plugin-3.1.0.zip,
> packages-3.0.1, packages-3.1.0
>
>
> My project build with toolchains, using both oracle JDK 8 and openjdk 11.0.2
> generating both 'jar' and 'aggregate-jar' documentation.
> This seems to inversely relate to MJAVADOC-555 somehow.
> The following error occurs:
> {quote}Exit code: 1 - javadoc: error - The code being documented uses modules
> but the packages defined in
> [https://javadoc.io/page/nl.talsmasoftware.context/context-propagation-root/1.0.6-SNAPSHOT/]
> are in the unnamed module
> {quote}
> _source:
> [https://travis-ci.org/talsma-ict/context-propagation/builds/501900168]_
> github:
> [https://github.com/talsma-ict/context-propagation/tree/dependabot/maven/org.apache.maven.plugins-maven-javadoc-plugin-3.1.0]
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MJAVADOC-583) javadoc: error - The code being documented uses modules but the packages defined in {URL} are in the unnamed module
[
https://issues.apache.org/jira/browse/MJAVADOC-583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16784876#comment-16784876
]
Sjoerd Talsma commented on MJAVADOC-583:
In the above project, the following is the `packages` file for `3.0.1`:
{quote}nl.talsmasoftware.context.clearable
nl.talsmasoftware.context
nl.talsmasoftware.context.threadlocal
nl.talsmasoftware.context.observer
nl.talsmasoftware.context.delegation
nl.talsmasoftware.context.timing
nl.talsmasoftware.context.executors
{quote}
The one for `3.1.0` is not so intuitive:
{quote}nl.talsmasoftware.context.clearable
nl.talsmasoftware.context.clearable
nl.talsmasoftware.context
nl.talsmasoftware.context.threadlocal
nl.talsmasoftware.context
nl.talsmasoftware.context.observer
nl.talsmasoftware.context.observer
nl.talsmasoftware.context.delegation
nl.talsmasoftware.context.delegation
nl.talsmasoftware.context.delegation
nl.talsmasoftware.context.delegation
nl.talsmasoftware.context.delegation
nl.talsmasoftware.context.delegation
nl.talsmasoftware.context.delegation
nl.talsmasoftware.context
nl.talsmasoftware.context.timing
nl.talsmasoftware.context.executors
nl.talsmasoftware.context
nl.talsmasoftware.context
nl.talsmasoftware.context
nl.talsmasoftware.context
nl.talsmasoftware.context
{quote}
Note the repetitions!
The error I get in my own machine, so not on travis is the following:
{quote}[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-javadoc-plugin:3.1.0:jar (generate-javadoc) on
project context-propagation: MavenReportException: Error while generating
Javadoc:
[ERROR] Exit code: 1 -
/Users/sjoerd/Documents/workspace/talsmasoftware/context-propagation/context-propagation-java5/src/main/java/nl/talsmasoftware/context/Timing.java:31:
error: class Timing clashes with package of same name
[ERROR] final class Timing {
{quote}
Please note there being a _class_ nl.talsmasoftware.context.Timing and a
_package_ nl.talsmasoftware.context.timing which was no problem for javac or
javadoc until plugin 3.1.0..
> javadoc: error - The code being documented uses modules but the packages
> defined in {URL} are in the unnamed module
> ---
>
> Key: MJAVADOC-583
> URL: https://issues.apache.org/jira/browse/MJAVADOC-583
> Project: Maven Javadoc Plugin
> Issue Type: Bug
> Components: jar
>Affects Versions: 3.1.0
> Environment: Travis CI, toolchain with openjdk 11.0.2
>Reporter: Sjoerd Talsma
>Priority: Major
> Attachments:
> context-propagation-dependabot-maven-org.apache.maven.plugins-maven-javadoc-plugin-3.1.0.zip,
> packages-3.0.1, packages-3.1.0
>
>
> My project build with toolchains, using both oracle JDK 8 and openjdk 11.0.2
> generating both 'jar' and 'aggregate-jar' documentation.
> This seems to inversely relate to MJAVADOC-555 somehow.
> The following error occurs:
> {quote}Exit code: 1 - javadoc: error - The code being documented uses modules
> but the packages defined in
> [https://javadoc.io/page/nl.talsmasoftware.context/context-propagation-root/1.0.6-SNAPSHOT/]
> are in the unnamed module
> {quote}
> _source:
> [https://travis-ci.org/talsma-ict/context-propagation/builds/501900168]_
> github:
> [https://github.com/talsma-ict/context-propagation/tree/dependabot/maven/org.apache.maven.plugins-maven-javadoc-plugin-3.1.0]
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (MJAVADOC-583) javadoc: error - The code being documented uses modules but the packages defined in {URL} are in the unnamed module
[
https://issues.apache.org/jira/browse/MJAVADOC-583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sjoerd Talsma updated MJAVADOC-583:
---
Attachment: packages-3.1.0
> javadoc: error - The code being documented uses modules but the packages
> defined in {URL} are in the unnamed module
> ---
>
> Key: MJAVADOC-583
> URL: https://issues.apache.org/jira/browse/MJAVADOC-583
> Project: Maven Javadoc Plugin
> Issue Type: Bug
> Components: jar
>Affects Versions: 3.1.0
> Environment: Travis CI, toolchain with openjdk 11.0.2
>Reporter: Sjoerd Talsma
>Priority: Major
> Attachments:
> context-propagation-dependabot-maven-org.apache.maven.plugins-maven-javadoc-plugin-3.1.0.zip,
> packages-3.0.1, packages-3.1.0
>
>
> My project build with toolchains, using both oracle JDK 8 and openjdk 11.0.2
> generating both 'jar' and 'aggregate-jar' documentation.
> This seems to inversely relate to MJAVADOC-555 somehow.
> The following error occurs:
> {quote}Exit code: 1 - javadoc: error - The code being documented uses modules
> but the packages defined in
> [https://javadoc.io/page/nl.talsmasoftware.context/context-propagation-root/1.0.6-SNAPSHOT/]
> are in the unnamed module
> {quote}
> _source:
> [https://travis-ci.org/talsma-ict/context-propagation/builds/501900168]_
> github:
> [https://github.com/talsma-ict/context-propagation/tree/dependabot/maven/org.apache.maven.plugins-maven-javadoc-plugin-3.1.0]
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (MJAVADOC-583) javadoc: error - The code being documented uses modules but the packages defined in {URL} are in the unnamed module
[
https://issues.apache.org/jira/browse/MJAVADOC-583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sjoerd Talsma updated MJAVADOC-583:
---
Attachment: packages-3.0.1
> javadoc: error - The code being documented uses modules but the packages
> defined in {URL} are in the unnamed module
> ---
>
> Key: MJAVADOC-583
> URL: https://issues.apache.org/jira/browse/MJAVADOC-583
> Project: Maven Javadoc Plugin
> Issue Type: Bug
> Components: jar
>Affects Versions: 3.1.0
> Environment: Travis CI, toolchain with openjdk 11.0.2
>Reporter: Sjoerd Talsma
>Priority: Major
> Attachments:
> context-propagation-dependabot-maven-org.apache.maven.plugins-maven-javadoc-plugin-3.1.0.zip,
> packages-3.0.1, packages-3.1.0
>
>
> My project build with toolchains, using both oracle JDK 8 and openjdk 11.0.2
> generating both 'jar' and 'aggregate-jar' documentation.
> This seems to inversely relate to MJAVADOC-555 somehow.
> The following error occurs:
> {quote}Exit code: 1 - javadoc: error - The code being documented uses modules
> but the packages defined in
> [https://javadoc.io/page/nl.talsmasoftware.context/context-propagation-root/1.0.6-SNAPSHOT/]
> are in the unnamed module
> {quote}
> _source:
> [https://travis-ci.org/talsma-ict/context-propagation/builds/501900168]_
> github:
> [https://github.com/talsma-ict/context-propagation/tree/dependabot/maven/org.apache.maven.plugins-maven-javadoc-plugin-3.1.0]
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[GitHub] [maven-shade-plugin] philipl commented on issue #16: [MSHADE-148] Don't attach exclusions that are already present
philipl commented on issue #16: [MSHADE-148] Don't attach exclusions that are already present URL: https://github.com/apache/maven-shade-plugin/pull/16#issuecomment-469834211 Note, that the fix in #15 looks like the fix for why exclusions get reevaluated. Even if that is merged, this fix should be taken too for correctness. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [maven-enforcer] Mazorius commented on issue #36: [MENFORCER-142] documentation - add example for checking rules via cli
Mazorius commented on issue #36: [MENFORCER-142] documentation - add example for checking rules via cli URL: https://github.com/apache/maven-enforcer/pull/36#issuecomment-469822449 @destebanm until 3.0.0-M3 release no CLI is possible with rules. In the master branch you can build the sources and use it till the release is done. I do the same. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[jira] [Commented] (SUREFIRE-1584) Rerun Failing Tests with JUnit 5
[
https://issues.apache.org/jira/browse/SUREFIRE-1584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16784795#comment-16784795
]
Tibor Digana commented on SUREFIRE-1584:
[~tictac.freshmint]
[~atmcarmo]
Can we close this ticket?
JUnit5 Pioneer has such ability with the annotation {{@RepeatFailedTest(3)}}.
https://www.swtestacademy.com/junit-5-how-to-repeat-failed-test/
> Rerun Failing Tests with JUnit 5
>
>
> Key: SUREFIRE-1584
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1584
> Project: Maven Surefire
> Issue Type: New Feature
> Components: JUnit 5.x support, Maven Surefire Report Plugin
>Affects Versions: 2.22.0
>Reporter: Tic Tac
>Priority: Major
> Labels: junit5
>
> The very useful feature for integration tests ¨[Rerun Failing
> Tests|https://maven.apache.org/surefire/maven-surefire-plugin/examples/rerun-failing-tests.html]¨
> is currently only supported for the very outdated JUnit 4.
> The documentation says: ¨This feature is supported only for JUnit 4.x.¨
> Can you please support this feature for JUnit 5.3 or later?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MJAVADOC-583) javadoc: error - The code being documented uses modules but the packages defined in {URL} are in the unnamed module
[
https://issues.apache.org/jira/browse/MJAVADOC-583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16784787#comment-16784787
]
Robert Scholte commented on MJAVADOC-583:
-
Running in debug mode will preserve these files.
> javadoc: error - The code being documented uses modules but the packages
> defined in {URL} are in the unnamed module
> ---
>
> Key: MJAVADOC-583
> URL: https://issues.apache.org/jira/browse/MJAVADOC-583
> Project: Maven Javadoc Plugin
> Issue Type: Bug
> Components: jar
>Affects Versions: 3.1.0
> Environment: Travis CI, toolchain with openjdk 11.0.2
>Reporter: Sjoerd Talsma
>Priority: Major
> Attachments:
> context-propagation-dependabot-maven-org.apache.maven.plugins-maven-javadoc-plugin-3.1.0.zip
>
>
> My project build with toolchains, using both oracle JDK 8 and openjdk 11.0.2
> generating both 'jar' and 'aggregate-jar' documentation.
> This seems to inversely relate to MJAVADOC-555 somehow.
> The following error occurs:
> {quote}Exit code: 1 - javadoc: error - The code being documented uses modules
> but the packages defined in
> [https://javadoc.io/page/nl.talsmasoftware.context/context-propagation-root/1.0.6-SNAPSHOT/]
> are in the unnamed module
> {quote}
> _source:
> [https://travis-ci.org/talsma-ict/context-propagation/builds/501900168]_
> github:
> [https://github.com/talsma-ict/context-propagation/tree/dependabot/maven/org.apache.maven.plugins-maven-javadoc-plugin-3.1.0]
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MJAVADOC-583) javadoc: error - The code being documented uses modules but the packages defined in {URL} are in the unnamed module
[
https://issues.apache.org/jira/browse/MJAVADOC-583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16784771#comment-16784771
]
Sjoerd Talsma commented on MJAVADOC-583:
{quote}Also compare the generated {{options}} and {{argument}} in the javadoc
rootfolder and try to figure out the effect of changed flags.
{quote}
I think I'll start there. Any tips on how I can _keep_ these around if the
plugin actually succeeds?
> javadoc: error - The code being documented uses modules but the packages
> defined in {URL} are in the unnamed module
> ---
>
> Key: MJAVADOC-583
> URL: https://issues.apache.org/jira/browse/MJAVADOC-583
> Project: Maven Javadoc Plugin
> Issue Type: Bug
> Components: jar
>Affects Versions: 3.1.0
> Environment: Travis CI, toolchain with openjdk 11.0.2
>Reporter: Sjoerd Talsma
>Priority: Major
> Attachments:
> context-propagation-dependabot-maven-org.apache.maven.plugins-maven-javadoc-plugin-3.1.0.zip
>
>
> My project build with toolchains, using both oracle JDK 8 and openjdk 11.0.2
> generating both 'jar' and 'aggregate-jar' documentation.
> This seems to inversely relate to MJAVADOC-555 somehow.
> The following error occurs:
> {quote}Exit code: 1 - javadoc: error - The code being documented uses modules
> but the packages defined in
> [https://javadoc.io/page/nl.talsmasoftware.context/context-propagation-root/1.0.6-SNAPSHOT/]
> are in the unnamed module
> {quote}
> _source:
> [https://travis-ci.org/talsma-ict/context-propagation/builds/501900168]_
> github:
> [https://github.com/talsma-ict/context-propagation/tree/dependabot/maven/org.apache.maven.plugins-maven-javadoc-plugin-3.1.0]
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MJAVADOC-583) javadoc: error - The code being documented uses modules but the packages defined in {URL} are in the unnamed module
[
https://issues.apache.org/jira/browse/MJAVADOC-583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16784731#comment-16784731
]
Robert Scholte commented on MJAVADOC-583:
-
In the spirit of Open Source, can you provide a minimal project (and not simply
your project) to reproduce the issue. Also compare the generated {{options}}
and {{argument}} in the javadoc rootfolder and try to figure out the effect of
changed flags.
> javadoc: error - The code being documented uses modules but the packages
> defined in {URL} are in the unnamed module
> ---
>
> Key: MJAVADOC-583
> URL: https://issues.apache.org/jira/browse/MJAVADOC-583
> Project: Maven Javadoc Plugin
> Issue Type: Bug
> Components: jar
>Affects Versions: 3.1.0
> Environment: Travis CI, toolchain with openjdk 11.0.2
>Reporter: Sjoerd Talsma
>Priority: Major
> Attachments:
> context-propagation-dependabot-maven-org.apache.maven.plugins-maven-javadoc-plugin-3.1.0.zip
>
>
> My project build with toolchains, using both oracle JDK 8 and openjdk 11.0.2
> generating both 'jar' and 'aggregate-jar' documentation.
> This seems to inversely relate to MJAVADOC-555 somehow.
> The following error occurs:
> {quote}Exit code: 1 - javadoc: error - The code being documented uses modules
> but the packages defined in
> [https://javadoc.io/page/nl.talsmasoftware.context/context-propagation-root/1.0.6-SNAPSHOT/]
> are in the unnamed module
> {quote}
> _source:
> [https://travis-ci.org/talsma-ict/context-propagation/builds/501900168]_
> github:
> [https://github.com/talsma-ict/context-propagation/tree/dependabot/maven/org.apache.maven.plugins-maven-javadoc-plugin-3.1.0]
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (DOXIA-575) Add support for (X)HTML5
[ https://issues.apache.org/jira/browse/DOXIA-575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16784707#comment-16784707 ] Graham Leggett commented on DOXIA-575: -- These are the comments: > * Why have specialized items replaced with inline? What is the purpose? They were all almost identical variations of what would otherwise have been the HTML "span" tag. As I recall (this patch was written 10 months ago) it extended an existing pattern in the code. > * Several `@since` tag value are wrong > * There is a merge conflict, please resolve Unfortunately this PR in github bit-rotted, the most recent patch is at https://jira.apache.org/jira/secure/attachment/12945908/DOXIA-575.patch > Add support for (X)HTML5 > > > Key: DOXIA-575 > URL: https://issues.apache.org/jira/browse/DOXIA-575 > Project: Maven Doxia > Issue Type: Improvement > Components: Core >Affects Versions: 1.8 >Reporter: Graham Leggett >Assignee: Michael Osipov >Priority: Major > Fix For: 1.9 > > Attachments: DOXIA-575.patch > > > Doxia currently generates XHTML v1.1, and does not support any of the new > HTML5 tags. > Update Doxia to support HTML5.2 as per https://www.w3.org/TR/html52/. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MSHADE-291) shadedPattern applied multiples times when relocating the contents of META-INF/services files
[
https://issues.apache.org/jira/browse/MSHADE-291?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16784684#comment-16784684
]
Robert Scholte commented on MSHADE-291:
---
[~larmitage] even though
[releasing|https://maven.apache.org/developers/release/maven-project-release-procedure.html]
isn't that hard, the [voting|https://www.apache.org/foundation/voting.html]
process will always claim time from several Maven PMC members. For that reason
I prefer not to do releases for a single issue.
However, if you manage to provide PRs for open issues of this plugin you
increase the chance of a release. (in other words, I don't have an ETA for you)
I expect using shadedPattern that doesn't contain the pattern is the workaround.
> shadedPattern applied multiples times when relocating the contents of
> META-INF/services files
> -
>
> Key: MSHADE-291
> URL: https://issues.apache.org/jira/browse/MSHADE-291
> Project: Maven Shade Plugin
> Issue Type: Bug
>Affects Versions: 3.1.1, 3.2.0, 3.2.1
>Reporter: Jan Luehe
>Assignee: Robert Scholte
>Priority: Major
> Labels: up-for-grabs
> Fix For: 3.2.2
>
>
> Steps to reproduce:
> 1. Modified the test case for
> https://issues.apache.org/jira/browse/MSHADE-190, as follows:
> {code:java}
> diff --git a/pom.xml b/pom.xml
> index 746b700..aea9abb 100644
> --- a/pom.xml
> +++ b/pom.xml
> @@ -68,12 +68,12 @@
>
> org.apache.maven.plugins
> maven-shade-plugin
> -2.4
> +3.1.1
>
>
>
> -org.eclipse.*
> -borg.eclipse.*
> +org.eclipse
> +org.eclipse1234
>
>
>
> {code}
> 2. mvn package
> 3. jar -xvf target/shade-meta-tc-1.0-SNAPSHOT.jar META-INF/services
> 4. cat META-INF/services/org.osgi.framework.launch.FrameworkFactory
> The shaded service implementation class looks as follows:
> {code:java}
> org.eclipse12341234.osgi.launch.EquinoxFactory
> {code}
> It appears that shadedPattern was applied twice.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[GitHub] [maven-surefire] Tibor17 commented on issue #222: Delay load testClass, but to use myown classLoader
Tibor17 commented on issue #222: Delay load testClass, but to use myown classLoader URL: https://github.com/apache/maven-surefire/pull/222#issuecomment-469771798 @cvictory No worries about TravisCI. It downloaded snapshot versions from ASF Nexus. I will create branch and run the Jenkins build. Meanwhile create issue in our Jira https://issues.apache.org/jira/projects/SUREFIRE and then the history of commits on how we name the commits (has name of Jira id in brackets, then title). This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[jira] [Created] (MRELEASE-1020) Cannot run release:prepare-with-pom
komlan created MRELEASE-1020: Summary: Cannot run release:prepare-with-pom Key: MRELEASE-1020 URL: https://issues.apache.org/jira/browse/MRELEASE-1020 Project: Maven Release Plugin Issue Type: Bug Affects Versions: 2.5.3 Reporter: komlan Attachments: maven.JPG -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNG-1388) Transitive Dependencies in a profile are not used
[
https://issues.apache.org/jira/browse/MNG-1388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16784624#comment-16784624
]
Igor Tykhyy commented on MNG-1388:
--
I'd also like to see this issue fixed (though I am not sure I could fix it
myself). I'd like profiles to apply to *not only dependencies*, but also
*child-modules* (specified under {{}}).
{{A}}
{{ - B (child-module)}}
{{ - C (child-module)}}
Doing
{code:java}
mvn clean install -Psome-profile
{code}
should apply the profile {{some-profile}} on *A* as well as on *B* and *C*,
running the profile in each module containing it.
At least for me it does not work - especially not if modules are stored in
profiles themselves (I only need some modules to be built in order to deploy
them; aggregator-project-packaging is set to _pom_).
> Transitive Dependencies in a profile are not used
> -
>
> Key: MNG-1388
> URL: https://issues.apache.org/jira/browse/MNG-1388
> Project: Maven
> Issue Type: Bug
> Components: Plugins and Lifecycle
>Affects Versions: 2.0
> Environment: Windows XP using Maven 2.0.
>Reporter: dbradicich
>Priority: Major
>
> I have a jar project file that defines a dependency inside a certain profile.
> If I then include that project inside of another war project, the
> dependencies defined in the jar project's profile isn't getting transferred
> over to the war.
> Ie we have this:
> A depends on SQL or Oracle depending on profile
> B depends on A.
> If sql profile is active, I would expect that when I build B, it pulls
> the transitive dependancy on sql from A.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (MNG-1388) Transitive Dependencies in a profile are not used
[
https://issues.apache.org/jira/browse/MNG-1388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16784624#comment-16784624
]
Igor Tykhyy edited comment on MNG-1388 at 3/5/19 4:29 PM:
--
I'd also like to see this issue fixed (though I am not sure I could fix it
myself). I'd like profiles to apply to *not only dependencies*, but also
*child-modules* (specified under {{}}).
{code:java}
A
- B (child-module)
- C (child-module){code}
Doing
{code:java}
mvn clean install -Psome-profile
{code}
should apply the profile {{some-profile}} on *A* as well as on *B* and *C*,
running the profile in each module containing it.
At least for me it does not work - especially not if modules are stored in
profiles themselves (I only need some modules to be built in order to deploy
them; aggregator-project-packaging is set to _pom_).
was (Author: divstar):
I'd also like to see this issue fixed (though I am not sure I could fix it
myself). I'd like profiles to apply to *not only dependencies*, but also
*child-modules* (specified under {{}}).
{{A}}
{{ - B (child-module)}}
{{ - C (child-module)}}
Doing
{code:java}
mvn clean install -Psome-profile
{code}
should apply the profile {{some-profile}} on *A* as well as on *B* and *C*,
running the profile in each module containing it.
At least for me it does not work - especially not if modules are stored in
profiles themselves (I only need some modules to be built in order to deploy
them; aggregator-project-packaging is set to _pom_).
> Transitive Dependencies in a profile are not used
> -
>
> Key: MNG-1388
> URL: https://issues.apache.org/jira/browse/MNG-1388
> Project: Maven
> Issue Type: Bug
> Components: Plugins and Lifecycle
>Affects Versions: 2.0
> Environment: Windows XP using Maven 2.0.
>Reporter: dbradicich
>Priority: Major
>
> I have a jar project file that defines a dependency inside a certain profile.
> If I then include that project inside of another war project, the
> dependencies defined in the jar project's profile isn't getting transferred
> over to the war.
> Ie we have this:
> A depends on SQL or Oracle depending on profile
> B depends on A.
> If sql profile is active, I would expect that when I build B, it pulls
> the transitive dependancy on sql from A.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (SUREFIRE-1644) Identify flaky tests in Surefire report
André Carmo created SUREFIRE-1644: - Summary: Identify flaky tests in Surefire report Key: SUREFIRE-1644 URL: https://issues.apache.org/jira/browse/SUREFIRE-1644 Project: Maven Surefire Issue Type: Improvement Components: Maven Surefire Report Plugin Reporter: André Carmo Hi all, There is a feature that allows to rerun failing tests: [https://maven.apache.org/surefire/maven-surefire-plugin/examples/rerun-failing-tests.html] This feature outputs to the surefire XML report some elements like flakyFailure, flakyError, and others. However, when generating the surefire report (invoking something like mvn surefire-report:report-only) those XML elements are not used and are not considered for the HTML report. That would be a great improvement. I can try to make a pull request for that, but please give me an overview first on where to look at to try to cut some time and some effort. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] [maven-enforcer] destebanm commented on issue #36: [MENFORCER-142] documentation - add example for checking rules via cli
destebanm commented on issue #36: [MENFORCER-142] documentation - add example for checking rules via cli URL: https://github.com/apache/maven-enforcer/pull/36#issuecomment-469718960 HI! I am using maven-enforcer-plugin:3.0.0-M2. I have this in my pom.xml and it is working fine when `mvn verify` ``` org.apache.maven.plugins maven-enforcer-plugin enforce-banned-dependencies enforce x.y:logger:(,10.93) x.y:soap-utils:(,10.93) x.y:correlation-id:(,10.93) true ``` Is there any way to get rid of pom.xml setup and get the same behaviour with the CLI? Thanks! This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[jira] [Created] (MRESOLVER-67) The Maven resolver API 1.3.2 JAR deployed on Maven central has been built with Java 11
Thomas Mortagne created MRESOLVER-67:
Summary: The Maven resolver API 1.3.2 JAR deployed on Maven
central has been built with Java 11
Key: MRESOLVER-67
URL: https://issues.apache.org/jira/browse/MRESOLVER-67
Project: Maven Resolver
Issue Type: Bug
Components: resolver
Affects Versions: 1.3.2
Reporter: Thomas Mortagne
bq. Build-Jdk: 11.0.1
Makes it unusable in Java 8. Example of problem:
{quote}
java.lang.NoSuchMethodError: java.nio.ByteBuffer.rewind()Ljava/nio/ByteBuffer;
at
org.eclipse.aether.spi.connector.transport.AbstractTransporter.copy(AbstractTransporter.java:254)
{quote}
See
https://mail-archives.apache.org/mod_mbox/maven-dev/201903.mbox/%3c64fbf6c9-0868-5da9-b42a-77500458b...@apache.org%3e
for more details.
I see 1.3.2 is not marked as released on Jira. Maybe it was not even supposed
to be on Maven central in the first place ?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (SUREFIRE-1584) Rerun Failing Tests with JUnit 5
[ https://issues.apache.org/jira/browse/SUREFIRE-1584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16784498#comment-16784498 ] André Carmo commented on SUREFIRE-1584: --- I second the need to have this feature. I mean it would be great to have this on JUnit 5 level. But the fact that Surefire puts it on the XML report is great and it goes towards the idea that, if you are rerunnig flakly tests, you better give visibility that they pass but they are still flaky. > Rerun Failing Tests with JUnit 5 > > > Key: SUREFIRE-1584 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1584 > Project: Maven Surefire > Issue Type: New Feature > Components: JUnit 5.x support, Maven Surefire Report Plugin >Affects Versions: 2.22.0 >Reporter: Tic Tac >Priority: Major > Labels: junit5 > > The very useful feature for integration tests ¨[Rerun Failing > Tests|https://maven.apache.org/surefire/maven-surefire-plugin/examples/rerun-failing-tests.html]¨ > is currently only supported for the very outdated JUnit 4. > The documentation says: ¨This feature is supported only for JUnit 4.x.¨ > Can you please support this feature for JUnit 5.3 or later? -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (MNG-6605) Unable to suppress download messages in interactive mode
Gunnar Wagenknecht created MNG-6605:
---
Summary: Unable to suppress download messages in interactive mode
Key: MNG-6605
URL: https://issues.apache.org/jira/browse/MNG-6605
Project: Maven
Issue Type: Improvement
Components: Command Line
Affects Versions: 3.6.0
Reporter: Gunnar Wagenknecht
When running Maven in batch mode (with option {{-B}}) it's possible to suppress
download messages using
"{{-Dorg.slf4j.simpleLogger.log.org.apache.maven.cli.transfer.Slf4jMavenTransferListener=warn}}"
Example:
{{mvn clean install -B
-Dorg.slf4j.simpleLogger.log.org.apache.maven.cli.transfer.Slf4jMavenTransferListener=warn}}
This does not work in non-batch mode.
*Example:*
{noformat}
export MAVEN_OPTS='-Xmx1g
-Dorg.slf4j.simpleLogger.log.org.apache.maven.cli.transfer.Slf4jMavenTransferListener=warn
-Dorg.slf4j.simpleLogger.showDateTime=true
-Dorg.slf4j.simpleLogger.dateTimeFormat=HH:mm:ss'
mvn clean install
{noformat}
Prints out time stamps as configured but does not suppress download progress
messages.
*Motivation:*
Because Travis CI supports colorized output in build logs I'd like to avoid
batch mode.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MSHADE-291) shadedPattern applied multiples times when relocating the contents of META-INF/services files
[
https://issues.apache.org/jira/browse/MSHADE-291?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16784326#comment-16784326
]
Lyndon Armitage commented on MSHADE-291:
What's the ETA on a release [~rfscholte]? And in the meantime what is the
workaround? I have spent a few days struggling with some shading issues
including this one and don't see why a patch level release hasn't been made yet.
> shadedPattern applied multiples times when relocating the contents of
> META-INF/services files
> -
>
> Key: MSHADE-291
> URL: https://issues.apache.org/jira/browse/MSHADE-291
> Project: Maven Shade Plugin
> Issue Type: Bug
>Affects Versions: 3.1.1, 3.2.0, 3.2.1
>Reporter: Jan Luehe
>Assignee: Robert Scholte
>Priority: Major
> Labels: up-for-grabs
> Fix For: 3.2.2
>
>
> Steps to reproduce:
> 1. Modified the test case for
> https://issues.apache.org/jira/browse/MSHADE-190, as follows:
> {code:java}
> diff --git a/pom.xml b/pom.xml
> index 746b700..aea9abb 100644
> --- a/pom.xml
> +++ b/pom.xml
> @@ -68,12 +68,12 @@
>
> org.apache.maven.plugins
> maven-shade-plugin
> -2.4
> +3.1.1
>
>
>
> -org.eclipse.*
> -borg.eclipse.*
> +org.eclipse
> +org.eclipse1234
>
>
>
> {code}
> 2. mvn package
> 3. jar -xvf target/shade-meta-tc-1.0-SNAPSHOT.jar META-INF/services
> 4. cat META-INF/services/org.osgi.framework.launch.FrameworkFactory
> The shaded service implementation class looks as follows:
> {code:java}
> org.eclipse12341234.osgi.launch.EquinoxFactory
> {code}
> It appears that shadedPattern was applied twice.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (MJAVADOC-583) javadoc: error - The code being documented uses modules but the packages defined in {URL} are in the unnamed module
[
https://issues.apache.org/jira/browse/MJAVADOC-583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sjoerd Talsma updated MJAVADOC-583:
---
Description:
My project build with toolchains, using both oracle JDK 8 and openjdk 11.0.2
generating both 'jar' and 'aggregate-jar' documentation.
This seems to inversely relate to MJAVADOC-555 somehow.
The following error occurs:
{quote}Exit code: 1 - javadoc: error - The code being documented uses modules
but the packages defined in
[https://javadoc.io/page/nl.talsmasoftware.context/context-propagation-root/1.0.6-SNAPSHOT/]
are in the unnamed module
{quote}
_source:
[https://travis-ci.org/talsma-ict/context-propagation/builds/501900168]_
github:
[https://github.com/talsma-ict/context-propagation/tree/dependabot/maven/org.apache.maven.plugins-maven-javadoc-plugin-3.1.0]
was:
My project build with toolchains, using both oracle JDK 8 and openjdk 11.0.2
generating both 'jar' and 'aggregate-jar' documentation.
This seems to inversely relate to MJAVADOC-555 somehow.
The following error occurs:
{quote}Exit code: 1 - javadoc: error - The code being documented uses modules
but the packages defined in
[https://javadoc.io/page/nl.talsmasoftware.context/context-propagation-root/1.0.6-SNAPSHOT/]
are in the unnamed module
{quote}
_source:
[https://travis-ci.org/talsma-ict/context-propagation/builds/501900168|https://travis-ci.org/talsma-ict/context-propagation/builds/501900168_]_
github:
[https://github.com/talsma-ict/context-propagation/tree/dependabot/maven/org.apache.maven.plugins-maven-javadoc-plugin-3.1.0]
> javadoc: error - The code being documented uses modules but the packages
> defined in {URL} are in the unnamed module
> ---
>
> Key: MJAVADOC-583
> URL: https://issues.apache.org/jira/browse/MJAVADOC-583
> Project: Maven Javadoc Plugin
> Issue Type: Bug
> Components: jar
>Affects Versions: 3.1.0
> Environment: Travis CI, toolchain with openjdk 11.0.2
>Reporter: Sjoerd Talsma
>Priority: Major
> Attachments:
> context-propagation-dependabot-maven-org.apache.maven.plugins-maven-javadoc-plugin-3.1.0.zip
>
>
> My project build with toolchains, using both oracle JDK 8 and openjdk 11.0.2
> generating both 'jar' and 'aggregate-jar' documentation.
> This seems to inversely relate to MJAVADOC-555 somehow.
> The following error occurs:
> {quote}Exit code: 1 - javadoc: error - The code being documented uses modules
> but the packages defined in
> [https://javadoc.io/page/nl.talsmasoftware.context/context-propagation-root/1.0.6-SNAPSHOT/]
> are in the unnamed module
> {quote}
> _source:
> [https://travis-ci.org/talsma-ict/context-propagation/builds/501900168]_
> github:
> [https://github.com/talsma-ict/context-propagation/tree/dependabot/maven/org.apache.maven.plugins-maven-javadoc-plugin-3.1.0]
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MJAVADOC-583) javadoc: error - The code being documented uses modules but the packages defined in {URL} are in the unnamed module
[
https://issues.apache.org/jira/browse/MJAVADOC-583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16784213#comment-16784213
]
Sjoerd Talsma commented on MJAVADOC-583:
This is most likely also related to
[https://bugs.openjdk.java.net/browse/JDK-8212233] but the funny thing is, the
project built fine with maven javadoc plugin `3.0.1` and only _broke_ with the
supposed fix `3.1.0`.
> javadoc: error - The code being documented uses modules but the packages
> defined in {URL} are in the unnamed module
> ---
>
> Key: MJAVADOC-583
> URL: https://issues.apache.org/jira/browse/MJAVADOC-583
> Project: Maven Javadoc Plugin
> Issue Type: Bug
> Components: jar
>Affects Versions: 3.1.0
> Environment: Travis CI, toolchain with openjdk 11.0.2
>Reporter: Sjoerd Talsma
>Priority: Major
> Attachments:
> context-propagation-dependabot-maven-org.apache.maven.plugins-maven-javadoc-plugin-3.1.0.zip
>
>
> My project build with toolchains, using both oracle JDK 8 and openjdk 11.0.2
> generating both 'jar' and 'aggregate-jar' documentation.
> This seems to inversely relate to MJAVADOC-555 somehow.
> The following error occurs:
> {quote}Exit code: 1 - javadoc: error - The code being documented uses modules
> but the packages defined in
> https://javadoc.io/page/nl.talsmasoftware.context/context-propagation-root/1.0.6-SNAPSHOT/
> are in the unnamed module
> {quote}
> _source:
> https://travis-ci.org/talsma-ict/context-propagation/builds/501900168_
> github:
> [https://github.com/talsma-ict/context-propagation/tree/dependabot/maven/org.apache.maven.plugins-maven-javadoc-plugin-3.1.0]
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (MJAVADOC-583) javadoc: error - The code being documented uses modules but the packages defined in {URL} are in the unnamed module
[
https://issues.apache.org/jira/browse/MJAVADOC-583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sjoerd Talsma updated MJAVADOC-583:
---
Description:
My project build with toolchains, using both oracle JDK 8 and openjdk 11.0.2
generating both 'jar' and 'aggregate-jar' documentation.
This seems to inversely relate to MJAVADOC-555 somehow.
The following error occurs:
{quote}Exit code: 1 - javadoc: error - The code being documented uses modules
but the packages defined in
[https://javadoc.io/page/nl.talsmasoftware.context/context-propagation-root/1.0.6-SNAPSHOT/]
are in the unnamed module
{quote}
_source:
[https://travis-ci.org/talsma-ict/context-propagation/builds/501900168|https://travis-ci.org/talsma-ict/context-propagation/builds/501900168_]_
github:
[https://github.com/talsma-ict/context-propagation/tree/dependabot/maven/org.apache.maven.plugins-maven-javadoc-plugin-3.1.0]
was:
My project build with toolchains, using both oracle JDK 8 and openjdk 11.0.2
generating both 'jar' and 'aggregate-jar' documentation.
This seems to inversely relate to MJAVADOC-555 somehow.
The following error occurs:
{quote}Exit code: 1 - javadoc: error - The code being documented uses modules
but the packages defined in
https://javadoc.io/page/nl.talsmasoftware.context/context-propagation-root/1.0.6-SNAPSHOT/
are in the unnamed module
{quote}
_source: https://travis-ci.org/talsma-ict/context-propagation/builds/501900168_
github:
[https://github.com/talsma-ict/context-propagation/tree/dependabot/maven/org.apache.maven.plugins-maven-javadoc-plugin-3.1.0]
> javadoc: error - The code being documented uses modules but the packages
> defined in {URL} are in the unnamed module
> ---
>
> Key: MJAVADOC-583
> URL: https://issues.apache.org/jira/browse/MJAVADOC-583
> Project: Maven Javadoc Plugin
> Issue Type: Bug
> Components: jar
>Affects Versions: 3.1.0
> Environment: Travis CI, toolchain with openjdk 11.0.2
>Reporter: Sjoerd Talsma
>Priority: Major
> Attachments:
> context-propagation-dependabot-maven-org.apache.maven.plugins-maven-javadoc-plugin-3.1.0.zip
>
>
> My project build with toolchains, using both oracle JDK 8 and openjdk 11.0.2
> generating both 'jar' and 'aggregate-jar' documentation.
> This seems to inversely relate to MJAVADOC-555 somehow.
> The following error occurs:
> {quote}Exit code: 1 - javadoc: error - The code being documented uses modules
> but the packages defined in
> [https://javadoc.io/page/nl.talsmasoftware.context/context-propagation-root/1.0.6-SNAPSHOT/]
> are in the unnamed module
> {quote}
> _source:
> [https://travis-ci.org/talsma-ict/context-propagation/builds/501900168|https://travis-ci.org/talsma-ict/context-propagation/builds/501900168_]_
> github:
> [https://github.com/talsma-ict/context-propagation/tree/dependabot/maven/org.apache.maven.plugins-maven-javadoc-plugin-3.1.0]
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (MJAVADOC-583) javadoc: error - The code being documented uses modules but the packages defined in {URL} are in the unnamed module
Sjoerd Talsma created MJAVADOC-583:
--
Summary: javadoc: error - The code being documented uses modules
but the packages defined in {URL} are in the unnamed module
Key: MJAVADOC-583
URL: https://issues.apache.org/jira/browse/MJAVADOC-583
Project: Maven Javadoc Plugin
Issue Type: Bug
Components: jar
Affects Versions: 3.1.0
Environment: Travis CI, toolchain with openjdk 11.0.2
Reporter: Sjoerd Talsma
Attachments:
context-propagation-dependabot-maven-org.apache.maven.plugins-maven-javadoc-plugin-3.1.0.zip
My project build with toolchains, using both oracle JDK 8 and openjdk 11.0.2
generating both 'jar' and 'aggregate-jar' documentation.
This seems to inversely relate to MJAVADOC-555 somehow.
The following error occurs:
{quote}Exit code: 1 - javadoc: error - The code being documented uses modules
but the packages defined in
https://javadoc.io/page/nl.talsmasoftware.context/context-propagation-root/1.0.6-SNAPSHOT/
are in the unnamed module
{quote}
_source: https://travis-ci.org/talsma-ict/context-propagation/builds/501900168_
github:
[https://github.com/talsma-ict/context-propagation/tree/dependabot/maven/org.apache.maven.plugins-maven-javadoc-plugin-3.1.0]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
