Re: Surefire Plugin: Tests failure on abstract class only shows the abstract class name
Hi Tison,
do you have access to the issue tracker?
https://issues.apache.org/jira/projects/SUREFIRE/issues
Am Mo., 16. Okt. 2023 um 07:51 Uhr schrieb tison :
>
> Bubble up. Or where I can file an issue to track if it's likely an
> improvement.
>
> Best,
> tison.
>
>
> tison 于2023年9月23日周六 09:48写道：
>
> > The "usePhrasedClassNameInRunning" property in
> > "JUnit5StatelessTestsetInfoReporter" helps a bit:
> >
> > @DisplayName("FsTest")
> > public class FsTest extends BehaviorTest {
> > // ...
> > }
> >
> > [INFO] Running FsTest AsyncWriteTest
> > [ERROR] Tests run: 4, Failures: 1, Errors: 0, Skipped: 0, Time elapsed:
> > 0.636 s <<< FAILURE! -- in FsTest AsyncWriteTest
> > [ERROR]
> > org.apache.opendal.behavior.BehaviorTest$AsyncWriteTest.testReadFull --
> > Time elapsed: 0.594 s <<< FAILURE!
> > java.lang.AssertionError:
> >
> > But not in the very end summary:
> >
> > [INFO] Results:
> > [INFO]
> > [ERROR] Failures:
> > [ERROR]
> > org.apache.opendal.behavior.BehaviorTest$AsyncWriteTest.testReadFull
> > [ERROR] Run 1: BehaviorTest$AsyncWriteTest.testReadFull:110
> >
> > You can clone https://github.com/apache/incubator-opendal/pull/3161 and
> > fail some tests case conditionally for debugging.
> >
> > Best,
> > tison.
> >
> >
> > tison 于2023年9月23日周六 01:17写道：
> >
> >> To demostrate the expected manner, I want:
> >>
> >> [ERROR] Tests run: 4, Failures: 1, Errors: 0, Skipped: 0, Time elapsed:
> >> 0.535 s <<< FAILURE! - in
> >> org.apache.opendal.behavior.BehaviorTest$AsyncWriteTest
> >> [ERROR]
> >> org.apache.opendal.behavior.BehaviorTest$AsyncWriteTest.testReadFull Time
> >> elapsed: 0.491 s <<< FAILURE!
> >> java.lang.AssertionError:
> >>
> >> to be:
> >>
> >> [ERROR] Tests run: 4, Failures: 1, Errors: 0, Skipped: 0, Time elapsed:
> >> 0.535 s <<< FAILURE! - in
> >> org.apache.opendal.behavior.BehaviorTest$AsyncWriteTest
> >> [ERROR]
> >> org.apache.opendal.behavior.FsTest>org.apache.opendal.behavior.BehaviorTest$AsyncWriteTest.testReadFull
> >> Time elapsed: 0.491 s <<< FAILURE!
> >> java.lang.AssertionError:
> >>
> >> Or other approach to specify the actual test class.
> >>
> >> Best,
> >> tison.
> >>
> >>
> >> tison 于2023年9月23日周六 01:11写道：
> >>
> >>> See https://github.com/junit-team/junit5/issues/3475 for details.
> >>>
> >>> Perhaps JUnit5ConsoleOutputReporter is related but I failed to located
> >>> the certain line constructing the test method name.
> >>>
> >>> Best,
> >>> tison.
> >>>
> >>
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Maven Javadoc Plugin version 3.6.2
+1 Am So., 5. Nov. 2023 um 20:32 Uhr schrieb Michael Osipov : > > Am 2023-11-03 um 21:42 schrieb Michael Osipov: > > Hi, > > > > We solved 7 issues: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317529=12353815 > > > > There are still a couple of issues left in JIRA: > > https://issues.apache.org/jira/projects/MJAVADOC/issues > > > > Staging repo: > > https://repository.apache.org/content/repositories/maven-2024/ > > https://repository.apache.org/content/repositories/maven-2024/org/apache/maven/plugins/maven-javadoc-plugin/3.6.2/maven-javadoc-plugin-3.6.2-source-release.zip > > > > Source release checksum(s): > > maven-javadoc-plugin-3.6.2-source-release.zip > > sha512: > > 9e6d0a8c9245bfee07b907e9a00390be60be50b9681ef0dcd6c85fc82ac9aeb3f35b9106d3d7e5e61b710be675f0654c0eace54787c02a37fafc314656f32781 > > > > Staging site: > > https://maven.apache.org/plugins-archives/maven-javadoc-plugin-LATEST/ > > > > Guide to testing staged releases: > > https://maven.apache.org/guides/development/guide-testing-releases.html > > > > Vote open for 72 hours. > > +1 > > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Maven Javadoc Plugin version 3.6.2
Am 2023-11-03 um 21:42 schrieb Michael Osipov: Hi, We solved 7 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317529=12353815 There are still a couple of issues left in JIRA: https://issues.apache.org/jira/projects/MJAVADOC/issues Staging repo: https://repository.apache.org/content/repositories/maven-2024/ https://repository.apache.org/content/repositories/maven-2024/org/apache/maven/plugins/maven-javadoc-plugin/3.6.2/maven-javadoc-plugin-3.6.2-source-release.zip Source release checksum(s): maven-javadoc-plugin-3.6.2-source-release.zip sha512: 9e6d0a8c9245bfee07b907e9a00390be60be50b9681ef0dcd6c85fc82ac9aeb3f35b9106d3d7e5e61b710be675f0654c0eace54787c02a37fafc314656f32781 Staging site: https://maven.apache.org/plugins-archives/maven-javadoc-plugin-LATEST/ Guide to testing staged releases: https://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72 hours. +1 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Maven 5 pom extension for agents
Le 2023-11-02 à 00 h 31, Tamás Cservenák a écrit : Here is where I am currently: https://cwiki.apache.org/confluence/display/MAVEN/Experiment+-+Explicit+JPMS+support It seems that I cannot add comment on that page, so below are my proposals: 1) Modify the explanation of the "jar" type. It currently said "same as today, added to classpath". It should be "same as today, automatic dispatching". The automatic dispatching may be based on the current heuristic rules (for compatibility reasons), or on new rules specified by a global configuration option, or on what the library producers declare (e.g. module in the POM of the dependencies?). 2) Add a new "classes" type with explanation "a non-JPMS artifact, added to class-path". 3) Add a column (or the information somewhere else) about mutually exclusive types. For example "jar", "classes" and "module" types are mutually exclusive. 4) Maybe omit "fatmodule" for now? That one may be difficult to do, because it would require to merge all module-info files in a single one. Even if we do so, the result will not be equivalent. In a JPMS world, there are other tools (jmod, jimage, jlink…) that we may want to explore before falling back on fatmodule. Thanks, Martin - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
