[jira] [Commented] (MSHARED-1411) Allow to access the root content entries if it is a multi-release JAR file
[
https://issues.apache.org/jira/browse/MSHARED-1411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17854273#comment-17854273
]
Michael Osipov commented on MSHARED-1411:
-
{{JarData::getRootEntries()}} would be good...
> Allow to access the root content entries if it is a multi-release JAR file
> ---
>
> Key: MSHARED-1411
> URL: https://issues.apache.org/jira/browse/MSHARED-1411
> Project: Maven Shared Components
> Issue Type: Bug
> Components: maven-shared-jar
>Affects Versions: maven-shared-jar-3.1.0
>Reporter: Gabriel Belingueres
>Priority: Major
>
> The method JarData::getEntries return all JAR entries in the file, while the
> JarVersionedRuntime::getEntries return the JAR entries inside a particular
> META-INF/versions/NN entry.
> However, there is no way to get only the entries belonging to the root
> content of the JAR file.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (SUREFIRE-2232) [REGRESSION] StatelessXmlReporter fails to process failed result without a throwable
[
https://issues.apache.org/jira/browse/SUREFIRE-2232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed SUREFIRE-2232.
Resolution: Fixed
Fixed with
[e6287ddbda7bf89ba370759af6164cbf925eebd1|https://gitbox.apache.org/repos/asf?p=maven-surefire.git;a=commit;h=e6287ddbda7bf89ba370759af6164cbf925eebd1].
> [REGRESSION] StatelessXmlReporter fails to process failed result without a
> throwable
>
>
> Key: SUREFIRE-2232
> URL: https://issues.apache.org/jira/browse/SUREFIRE-2232
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
>Affects Versions: 3.0.0-M6, 3.2.3, 3.2.5
>Reporter: Artem Yak
>Assignee: Michael Osipov
>Priority: Minor
> Fix For: 3.3.0
>
>
>
> A regression bug appeared in 3.0.0-M6:
> A testNG test class has a listener which updates results from SUCCESS to
> FAILURE:
>
> {noformat}
> @Override
> public void onTestSuccess(ITestResult result) {
> result.setStatus(ITestResult.FAILURE);
> result.getTestContext().getPassedTests().removeResult(result);
> result.getTestContext().getFailedTests().addResult(result);
> }{noformat}
>
> Surefire fails to process a failed test result without a throwable and
> reports 0 total tests.
> {code:java}
> ForkStarter IOException: java.util.NoSuchElementException.
> org.apache.maven.plugin.surefire.booterclient.output.MultipleFailureException:
> java.util.NoSuchElementException
> at
> org.apache.maven.plugin.surefire.booterclient.output.ThreadedStreamConsumer$Pumper.(ThreadedStreamConsumer.java:59)
> at
> org.apache.maven.plugin.surefire.booterclient.output.ThreadedStreamConsumer.(ThreadedStreamConsumer.java:107)
> at
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:546)
> at
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:285)
> at
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:250)
> {code}
>
> Reproducible unit test.
> {code:java}
> package org.apache.maven.plugin.surefire.report;
> import java.io.File;
> import java.util.HashMap;
> import java.util.concurrent.atomic.AtomicInteger;
> import junit.framework.TestCase;
> import
> org.apache.maven.plugin.surefire.booterclient.output.DeserializedStacktraceWriter;
> import org.apache.maven.surefire.api.report.SimpleReportEntry;
> import org.apache.maven.surefire.api.report.StackTraceWriter;
> import static org.apache.maven.plugin.surefire.report.ReportEntryType.ERROR;
> import static org.apache.maven.surefire.api.report.RunMode.NORMAL_RUN;
> @SuppressWarnings({"ResultOfMethodCallIgnored", "checkstyle:magicnumber"})
> public class StatelessXmlReporter2Test extends TestCase {
> private static final String XSD =
>
> "https://maven.apache.org/surefire/maven-surefire-plugin/xsd/surefire-test-report-3.0.xsd;;
> private static final AtomicInteger FOLDER_POSTFIX = new AtomicInteger();
> private File reportDir;
> @Override
> protected void setUp() throws Exception {
> File basedir = new File(".");
> File target = new File(basedir.getCanonicalFile(), "target");
> target.mkdir();
> String reportRelDir = getClass().getSimpleName() + "-" +
> FOLDER_POSTFIX.incrementAndGet();
> reportDir = new File(target, reportRelDir);
> reportDir.mkdir();
> }
> @Override
> protected void tearDown() {
> }
> public void testOutputFailedTestWithoutThrowable() {
> StackTraceWriter stackTraceWriterOne = new
> DeserializedStacktraceWriter(null, null, "");
> WrappedReportEntry testReport = new WrappedReportEntry(
> new SimpleReportEntry(
> NORMAL_RUN, 1L, getClass().getName(), null, "a test name",
> null, stackTraceWriterOne, 5),
> ERROR,
> 5,
> null,
> null);
> TestSetStats testSetStats = new TestSetStats(false, false);
> testSetStats.testError(testReport);
> StatelessXmlReporter reporter = new StatelessXmlReporter(
> reportDir, null, false, 1, new HashMap<>(), XSD, "3.0", false,
> false, false, false);
> reporter.testSetCompleted(testReport, testSetStats);
> }
> } {code}
>
>
>
> {code:java}
> java.util.NoSuchElementException
> at java.base/java.util.StringTokenizer.nextToken(StringTokenizer.java:349)
> at
> org.apache.maven.plugin.surefire.report.StatelessXmlReporter.getTestProblems(StatelessXmlReporter.java:454)
> at
> org.apache.maven.plugin.surefire.report.StatelessXmlReporter.serializeTestClassWithRerun(StatelessXmlReporter.java:256)
> at
>
[jira] [Assigned] (MSITE-988) Documentation
[ https://issues.apache.org/jira/browse/MSITE-988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov reassigned MSITE-988: Assignee: (was: Michael Osipov) > Documentation > - > > Key: MSITE-988 > URL: https://issues.apache.org/jira/browse/MSITE-988 > Project: Maven Site Plugin > Issue Type: Bug > Components: documentation >Affects Versions: 4.0.0-M9 >Reporter: Ernst Reissner >Priority: Major > > Create old pre-version 2.0.0 model. > If using newer versions, 4.0.0-M9 to the current M11, > then an error occurs: > ``` > Site model of > 'eu.simuline.m2latex:latex-maven-plugin:maven-plugin:2.0-SNAPSHOT' > for locale 'en' is still using the old pre-version 2.0.0 model. > You MUST migrate to the new model as soon as possible > otherwise your build will break in the future! > ``` > This is due to an old form of `site.xml` > The first problem is the documentation, > `https://maven.apache.org/plugins/maven-site-plugin/examples/sitedescriptor.html` > > which describes the old form and refers to the new one only in a link. > What would be needed is a clear statement on the mapping of the version to > the form. > Also the new form is not completely supported: > ``` >xmlns="http://maven.apache.org/SITE/2.0.0; > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; > xsi:schemaLocation="http://maven.apache.org/SITE/2.0.0 > https://maven.apache.org/xsd/site-2.0.0.xsd;> > ... > > ``` > well, the link `https://maven.apache.org/xsd/site-2.0.0.xsd` does not exist, > resulting in a warning in my IDE. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MPMD-399) Incorrect warning: The project X does not seem to be compiled. PMD results might be inaccurate.
[
https://issues.apache.org/jira/browse/MPMD-399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17854136#comment-17854136
]
Michael Osipov commented on MPMD-399:
-
...and it does. I verified by debugging it. The comment for the param is just
confusing.
> Incorrect warning: The project X does not seem to be compiled. PMD results
> might be inaccurate.
> ---
>
> Key: MPMD-399
> URL: https://issues.apache.org/jira/browse/MPMD-399
> Project: Maven PMD Plugin
> Issue Type: Bug
> Components: PMD
>Affects Versions: 3.22.0
>Reporter: AB-xdev
>Priority: Major
>
> PMD plugin is reporting the following warnings on in a multi-maven project:
> "The project X does not seem to be compiled. PMD results might be inaccurate."
> This is caused by the fact that not all modules have a
> * {{src/main/java}} or
> * {{src/test/java}} folder
> and therefore no {{target/classes}} or {{target/test-classes}} folders are
> generated.
> The affected code that causes the problem can be found here:
> [https://github.com/apache/maven-pmd-plugin/blob/1961d771ea585e9344c25dfde194ee64a1b9040b/src/main/java/org/apache/maven/plugins/pmd/PmdReport.java#L516-L532]
> h3. Reproduction example
> * Create a maven multi-module project
> * Leave {{src/main/java}} of one module empty
> * Execute {{pmd:aggregate-pmd}} or {{test pmd:aggregate-pmd-no-fork
> -DskipTests}}
> → (x) Warning is reported
> h3. Possible fixes
> * Make it possible to ignore this warning
> * Do not warn when at least {{target/classes}} or {{target/test-classes}} is
> present
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MPMD-399) Incorrect warning: The project X does not seem to be compiled. PMD results might be inaccurate.
[
https://issues.apache.org/jira/browse/MPMD-399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17853706#comment-17853706
]
Michael Osipov commented on MPMD-399:
-
Have a look at the PR.
> Incorrect warning: The project X does not seem to be compiled. PMD results
> might be inaccurate.
> ---
>
> Key: MPMD-399
> URL: https://issues.apache.org/jira/browse/MPMD-399
> Project: Maven PMD Plugin
> Issue Type: Bug
> Components: PMD
>Affects Versions: 3.22.0
>Reporter: AB-xdev
>Priority: Major
>
> PMD plugin is reporting the following warnings on in a multi-maven project:
> "The project X does not seem to be compiled. PMD results might be inaccurate."
> This is caused by the fact that not all modules have a
> * {{src/main/java}} or
> * {{src/test/java}} folder
> and therefore no {{target/classes}} or {{target/test-classes}} folders are
> generated.
> The affected code that causes the problem can be found here:
> [https://github.com/apache/maven-pmd-plugin/blob/1961d771ea585e9344c25dfde194ee64a1b9040b/src/main/java/org/apache/maven/plugins/pmd/PmdReport.java#L516-L532]
> h3. Reproduction example
> * Create a maven multi-module project
> * Leave {{src/main/java}} of one module empty
> * Execute {{pmd:aggregate-pmd}} or {{test pmd:aggregate-pmd-no-fork
> -DskipTests}}
> → (x) Warning is reported
> h3. Possible fixes
> * Make it possible to ignore this warning
> * Do not warn when at least {{target/classes}} or {{target/test-classes}} is
> present
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MPMD-399) Incorrect warning: The project X does not seem to be compiled. PMD results might be inaccurate.
[
https://issues.apache.org/jira/browse/MPMD-399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17853702#comment-17853702
]
Michael Osipov commented on MPMD-399:
-
Forget my previous questions because
{{localProject.getTestClasspathElements()}} is cumulative. Ony the
documentation needs to be updated. [~AB-xdev], we can get back to the actual
problem.
> Incorrect warning: The project X does not seem to be compiled. PMD results
> might be inaccurate.
> ---
>
> Key: MPMD-399
> URL: https://issues.apache.org/jira/browse/MPMD-399
> Project: Maven PMD Plugin
> Issue Type: Bug
> Components: PMD
>Affects Versions: 3.22.0
>Reporter: AB-xdev
>Priority: Major
>
> PMD plugin is reporting the following warnings on in a multi-maven project:
> "The project X does not seem to be compiled. PMD results might be inaccurate."
> This is caused by the fact that not all modules have a
> * {{src/main/java}} or
> * {{src/test/java}} folder
> and therefore no {{target/classes}} or {{target/test-classes}} folders are
> generated.
> The affected code that causes the problem can be found here:
> [https://github.com/apache/maven-pmd-plugin/blob/1961d771ea585e9344c25dfde194ee64a1b9040b/src/main/java/org/apache/maven/plugins/pmd/PmdReport.java#L516-L532]
> h3. Reproduction example
> * Create a maven multi-module project
> * Leave {{src/main/java}} of one module empty
> * Execute {{pmd:aggregate-pmd}} or {{test pmd:aggregate-pmd-no-fork
> -DskipTests}}
> → (x) Warning is reported
> h3. Possible fixes
> * Make it possible to ignore this warning
> * Do not warn when at least {{target/classes}} or {{target/test-classes}} is
> present
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MPMD-399) Incorrect warning: The project X does not seem to be compiled. PMD results might be inaccurate.
[
https://issues.apache.org/jira/browse/MPMD-399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17853699#comment-17853699
]
Michael Osipov commented on MPMD-399:
-
I am also confused why the single project case does not include the deps...
> Incorrect warning: The project X does not seem to be compiled. PMD results
> might be inaccurate.
> ---
>
> Key: MPMD-399
> URL: https://issues.apache.org/jira/browse/MPMD-399
> Project: Maven PMD Plugin
> Issue Type: Bug
> Components: PMD
>Affects Versions: 3.22.0
>Reporter: AB-xdev
>Priority: Major
>
> PMD plugin is reporting the following warnings on in a multi-maven project:
> "The project X does not seem to be compiled. PMD results might be inaccurate."
> This is caused by the fact that not all modules have a
> * {{src/main/java}} or
> * {{src/test/java}} folder
> and therefore no {{target/classes}} or {{target/test-classes}} folders are
> generated.
> The affected code that causes the problem can be found here:
> [https://github.com/apache/maven-pmd-plugin/blob/1961d771ea585e9344c25dfde194ee64a1b9040b/src/main/java/org/apache/maven/plugins/pmd/PmdReport.java#L516-L532]
> h3. Reproduction example
> * Create a maven multi-module project
> * Leave {{src/main/java}} of one module empty
> * Execute {{pmd:aggregate-pmd}} or {{test pmd:aggregate-pmd-no-fork
> -DskipTests}}
> → (x) Warning is reported
> h3. Possible fixes
> * Make it possible to ignore this warning
> * Do not warn when at least {{target/classes}} or {{target/test-classes}} is
> present
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MPMD-399) Incorrect warning: The project X does not seem to be compiled. PMD results might be inaccurate.
[
https://issues.apache.org/jira/browse/MPMD-399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17853698#comment-17853698
]
Michael Osipov commented on MPMD-399:
-
I have a slight problem with {{includeTests}}: It documentation says "Run PMD
on the tests.". Looking at
https://github.com/apache/maven-pmd-plugin/blob/1961d771ea585e9344c25dfde194ee64a1b9040b/src/main/java/org/apache/maven/plugins/pmd/AbstractPmdReport.java#L351-L384.
The operation is additive/inclusive. The description is wrong. But here, it is
exclusive:
https://github.com/apache/maven-pmd-plugin/blob/1961d771ea585e9344c25dfde194ee64a1b9040b/src/main/java/org/apache/maven/plugins/pmd/PmdReport.java#L516-L518
[~adangel], shouldn't {{auxClasspath}} include main classpath as well when
tests should be included? Since dependencies are inclusive as well:
https://github.com/apache/maven-pmd-plugin/blob/1961d771ea585e9344c25dfde194ee64a1b9040b/src/main/java/org/apache/maven/plugins/pmd/PmdReport.java#L493-L497
It does not compute fo me.
[~AB-xdev], sorry to deviate, but that needs to clarified first.
> Incorrect warning: The project X does not seem to be compiled. PMD results
> might be inaccurate.
> ---
>
> Key: MPMD-399
> URL: https://issues.apache.org/jira/browse/MPMD-399
> Project: Maven PMD Plugin
> Issue Type: Bug
> Components: PMD
>Affects Versions: 3.22.0
>Reporter: AB-xdev
>Priority: Major
>
> PMD plugin is reporting the following warnings on in a multi-maven project:
> "The project X does not seem to be compiled. PMD results might be inaccurate."
> This is caused by the fact that not all modules have a
> * {{src/main/java}} or
> * {{src/test/java}} folder
> and therefore no {{target/classes}} or {{target/test-classes}} folders are
> generated.
> The affected code that causes the problem can be found here:
> [https://github.com/apache/maven-pmd-plugin/blob/1961d771ea585e9344c25dfde194ee64a1b9040b/src/main/java/org/apache/maven/plugins/pmd/PmdReport.java#L516-L532]
> h3. Reproduction example
> * Create a maven multi-module project
> * Leave {{src/main/java}} of one module empty
> * Execute {{pmd:aggregate-pmd}} or {{test pmd:aggregate-pmd-no-fork
> -DskipTests}}
> → (x) Warning is reported
> h3. Possible fixes
> * Make it possible to ignore this warning
> * Do not warn when at least {{target/classes}} or {{target/test-classes}} is
> present
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MPMD-399) Incorrect warning: The project X does not seem to be compiled. PMD results might be inaccurate.
[
https://issues.apache.org/jira/browse/MPMD-399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17853692#comment-17853692
]
Michael Osipov commented on MPMD-399:
-
Hold on, that confuses me. In the default case if src/main is there there
should be not warning, only if src/tests are there and {{includeTests}} is
{{false}} and the other way around: {{true}} and only {{src/main}}. The first
case I do not understand, but the latter makes sense. You should see the
warning. Can you confirm?
> Incorrect warning: The project X does not seem to be compiled. PMD results
> might be inaccurate.
> ---
>
> Key: MPMD-399
> URL: https://issues.apache.org/jira/browse/MPMD-399
> Project: Maven PMD Plugin
> Issue Type: Bug
> Components: PMD
>Affects Versions: 3.22.0
>Reporter: AB-xdev
>Priority: Major
>
> PMD plugin is reporting the following warnings on in a multi-maven project:
> "The project X does not seem to be compiled. PMD results might be inaccurate."
> This is caused by the fact that not all modules have a
> * {{src/main/java}} or
> * {{src/test/java}} folder
> and therefore no {{target/classes}} or {{target/test-classes}} folders are
> generated.
> The affected code that causes the problem can be found here:
> [https://github.com/apache/maven-pmd-plugin/blob/1961d771ea585e9344c25dfde194ee64a1b9040b/src/main/java/org/apache/maven/plugins/pmd/PmdReport.java#L516-L532]
> h3. Reproduction example
> * Create a maven multi-module project
> * Leave {{src/main/java}} of one module empty
> * Execute {{pmd:aggregate-pmd}} or {{test pmd:aggregate-pmd-no-fork
> -DskipTests}}
> → (x) Warning is reported
> h3. Possible fixes
> * Make it possible to ignore this warning
> * Do not warn when at least {{target/classes}} or {{target/test-classes}} is
> present
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MPMD-399) Incorrect warning: The project X does not seem to be compiled. PMD results might be inaccurate.
[
https://issues.apache.org/jira/browse/MPMD-399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17853670#comment-17853670
]
Michael Osipov commented on MPMD-399:
-
The method is deprecated, but the information is still required and needs to be
obtained elsewhere. That is different discussion. I would take care of the
message.
Why do you have a JAR project w/o source code in the first place?
> Incorrect warning: The project X does not seem to be compiled. PMD results
> might be inaccurate.
> ---
>
> Key: MPMD-399
> URL: https://issues.apache.org/jira/browse/MPMD-399
> Project: Maven PMD Plugin
> Issue Type: Bug
> Components: PMD
>Affects Versions: 3.22.0
>Reporter: AB-xdev
>Priority: Major
>
> PMD plugin is reporting the following warnings on in a multi-maven project:
> "The project X does not seem to be compiled. PMD results might be inaccurate."
> This is caused by the fact that not all modules have a
> * {{src/main/java}} or
> * {{src/test/java}} folder
> and therefore no {{target/classes}} or {{target/test-classes}} folders are
> generated.
> The affected code that causes the problem can be found here:
> [https://github.com/apache/maven-pmd-plugin/blob/1961d771ea585e9344c25dfde194ee64a1b9040b/src/main/java/org/apache/maven/plugins/pmd/PmdReport.java#L516-L532]
> h3. Reproduction example
> * Create a maven multi-module project
> * Leave {{src/main/java}} of one module empty
> * Execute {{pmd:aggregate-pmd}} or {{test pmd:aggregate-pmd-no-fork
> -DskipTests}}
> → (x) Warning is reported
> h3. Possible fixes
> * Make it possible to ignore this warning
> * Do not warn when at least {{target/classes}} or {{target/test-classes}} is
> present
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MPMD-399) Incorrect warning: The project X does not seem to be compiled. PMD results might be inaccurate.
[
https://issues.apache.org/jira/browse/MPMD-399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17853660#comment-17853660
]
Michael Osipov commented on MPMD-399:
-
I am inclined to delete this entire block
https://github.com/apache/maven-pmd-plugin/blob/1961d771ea585e9344c25dfde194ee64a1b9040b/src/main/java/org/apache/maven/plugins/pmd/PmdReport.java#L522-L532
because in a single module there is not such message, but would make sense to
be consistent:
https://github.com/apache/maven-pmd-plugin/blob/1961d771ea585e9344c25dfde194ee64a1b9040b/src/main/java/org/apache/maven/plugins/pmd/PmdReport.java#L539-L541
Either both or none, WDYT?
> Incorrect warning: The project X does not seem to be compiled. PMD results
> might be inaccurate.
> ---
>
> Key: MPMD-399
> URL: https://issues.apache.org/jira/browse/MPMD-399
> Project: Maven PMD Plugin
> Issue Type: Bug
> Components: PMD
>Affects Versions: 3.22.0
>Reporter: AB-xdev
>Priority: Major
>
> PMD plugin is reporting the following warnings on in a multi-maven project:
> "The project X does not seem to be compiled. PMD results might be inaccurate."
> This is caused by the fact that not all modules have a
> * {{src/main/java}} or
> * {{src/test/java}} folder
> and therefore no {{target/classes}} or {{target/test-classes}} folders are
> generated.
> The affected code that causes the problem can be found here:
> [https://github.com/apache/maven-pmd-plugin/blob/1961d771ea585e9344c25dfde194ee64a1b9040b/src/main/java/org/apache/maven/plugins/pmd/PmdReport.java#L516-L532]
> h3. Reproduction example
> * Create a maven multi-module project
> * Leave {{src/main/java}} of one module empty
> * Execute {{pmd:aggregate-pmd}} or {{test pmd:aggregate-pmd-no-fork
> -DskipTests}}
> → (x) Warning is reported
> h3. Possible fixes
> * Make it possible to ignore this warning
> * Do not warn when at least {{target/classes}} or {{target/test-classes}} is
> present
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MPMD-399) Incorrect warning: The project X does not seem to be compiled. PMD results might be inaccurate.
[
https://issues.apache.org/jira/browse/MPMD-399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17853652#comment-17853652
]
Michael Osipov commented on MPMD-399:
-
Does it work for your with {{-Dpmd.typeResolution=false}}?
> Incorrect warning: The project X does not seem to be compiled. PMD results
> might be inaccurate.
> ---
>
> Key: MPMD-399
> URL: https://issues.apache.org/jira/browse/MPMD-399
> Project: Maven PMD Plugin
> Issue Type: Bug
> Components: PMD
>Affects Versions: 3.22.0
>Reporter: AB-xdev
>Priority: Major
>
> PMD plugin is reporting the following warnings on in a multi-maven project:
> "The project X does not seem to be compiled. PMD results might be inaccurate."
> This is caused by the fact that not all modules have a
> * {{src/main/java}} or
> * {{src/test/java}} folder
> and therefore no {{target/classes}} or {{target/test-classes}} folders are
> generated.
> The affected code that causes the problem can be found here:
> [https://github.com/apache/maven-pmd-plugin/blob/1961d771ea585e9344c25dfde194ee64a1b9040b/src/main/java/org/apache/maven/plugins/pmd/PmdReport.java#L516-L532]
> h3. Reproduction example
> * Create a maven multi-module project
> * Leave {{src/main/java}} of one module empty
> * Execute {{pmd:aggregate-pmd}} or {{test pmd:aggregate-pmd-no-fork
> -DskipTests}}
> → (x) Warning is reported
> h3. Possible fixes
> * Make it possible to ignore this warning
> * Do not warn when at least {{target/classes}} or {{target/test-classes}} is
> present
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MPMD-399) Incorrect warning: The project X does not seem to be compiled. PMD results might be inaccurate.
[
https://issues.apache.org/jira/browse/MPMD-399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17853645#comment-17853645
]
Michael Osipov commented on MPMD-399:
-
What packaging type is the project in question?
> Incorrect warning: The project X does not seem to be compiled. PMD results
> might be inaccurate.
> ---
>
> Key: MPMD-399
> URL: https://issues.apache.org/jira/browse/MPMD-399
> Project: Maven PMD Plugin
> Issue Type: Bug
> Components: PMD
>Affects Versions: 3.22.0
>Reporter: AB-xdev
>Priority: Major
>
> PMD plugin is reporting the following warnings on in a multi-maven project:
> "The project X does not seem to be compiled. PMD results might be inaccurate."
> This is caused by the fact that not all modules have a
> * {{src/main/java}} or
> * {{src/test/java}} folder
> and therefore no {{target/classes}} or {{target/test-classes}} folders are
> generated.
> The affected code that causes the problem can be found here:
> [https://github.com/apache/maven-pmd-plugin/blob/1961d771ea585e9344c25dfde194ee64a1b9040b/src/main/java/org/apache/maven/plugins/pmd/PmdReport.java#L516-L532]
> h3. Reproduction example
> * Create a maven multi-module project
> * Leave {{src/main/java}} of one module empty
> * Execute {{pmd:aggregate-pmd}} or {{test pmd:aggregate-pmd-no-fork
> -DskipTests}}
> → (x) Warning is reported
> h3. Possible fixes
> * Make it possible to ignore this warning
> * Do not warn when at least {{target/classes}} or {{target/test-classes}} is
> present
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MSITE-1010) site-deployment for POM projects does not create project folders in site-repository
[
https://issues.apache.org/jira/browse/MSITE-1010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17853632#comment-17853632
]
Michael Osipov commented on MSITE-1010:
---
The bug might just be in the WebDAV provider.
> site-deployment for POM projects does not create project folders in
> site-repository
> ---
>
> Key: MSITE-1010
> URL: https://issues.apache.org/jira/browse/MSITE-1010
> Project: Maven Site Plugin
> Issue Type: Bug
> Components: site:deploy
>Affects Versions: 3.12.0, 4.0.0-M14
> Environment: Nexus, since at least Maven 3.6.3 (not tested with 3.9.7
> or 4.0.0-beta)
>Reporter: Matthias Bünger
>Priority: Minor
> Fix For: waiting-for-feedback
>
> Attachments: pom.xml, webdav.txt
>
>
> I noticed the following issue while updating the plugins in our teams
> META-POM and could backtrack it at least until 3.12 but might be an even
> older issue. Havn't checked 4.0.0-M15 but from the releases notes I doubt it
> is fixed.
> When you do "site-deploy" for a single module or multi module project the
> site files (.html, css-folders, etc.) are stored in the site-repository (we
> have current Nexus version) within a subfolder with the name of the project,
> e.g
> {code}
> / (root of site-repository)
> /- project-A
>/css
>report.html
> /- project-B
>/css
>report.html
> /project-C
> {code}
> If you do the same for a "POM" project (e.g. a META-POM or BOM) the site
> files are all stored at root level (instead of creating a project folder) and
> ofc overwriting the ones from other POM-projects:
> {code}
> / (root of site-repository)
> /css
> /project-A
> /project-B
> /project-C
> report.html
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MSITE-1010) site-deployment for POM projects does not create project folders in site-repository
[
https://issues.apache.org/jira/browse/MSITE-1010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17853631#comment-17853631
]
Michael Osipov commented on MSITE-1010:
---
It does not answer my question. Can you try test setup which just deploys
locally with {{file://}} and check whether the structure is the way you expect?
> site-deployment for POM projects does not create project folders in
> site-repository
> ---
>
> Key: MSITE-1010
> URL: https://issues.apache.org/jira/browse/MSITE-1010
> Project: Maven Site Plugin
> Issue Type: Bug
> Components: site:deploy
>Affects Versions: 3.12.0, 4.0.0-M14
> Environment: Nexus, since at least Maven 3.6.3 (not tested with 3.9.7
> or 4.0.0-beta)
>Reporter: Matthias Bünger
>Priority: Minor
> Fix For: waiting-for-feedback
>
> Attachments: pom.xml, webdav.txt
>
>
> I noticed the following issue while updating the plugins in our teams
> META-POM and could backtrack it at least until 3.12 but might be an even
> older issue. Havn't checked 4.0.0-M15 but from the releases notes I doubt it
> is fixed.
> When you do "site-deploy" for a single module or multi module project the
> site files (.html, css-folders, etc.) are stored in the site-repository (we
> have current Nexus version) within a subfolder with the name of the project,
> e.g
> {code}
> / (root of site-repository)
> /- project-A
>/css
>report.html
> /- project-B
>/css
>report.html
> /project-C
> {code}
> If you do the same for a "POM" project (e.g. a META-POM or BOM) the site
> files are all stored at root level (instead of creating a project folder) and
> ofc overwriting the ones from other POM-projects:
> {code}
> / (root of site-repository)
> /css
> /project-A
> /project-B
> /project-C
> report.html
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MSITE-1010) site-deployment for POM projects does not create project folders in site-repository
[
https://issues.apache.org/jira/browse/MSITE-1010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17853620#comment-17853620
]
Michael Osipov commented on MSITE-1010:
---
I see you deploy through WebDAV. Please see whether file-based deployment makes
a difference. Maybe the DAV module is faulty.
> site-deployment for POM projects does not create project folders in
> site-repository
> ---
>
> Key: MSITE-1010
> URL: https://issues.apache.org/jira/browse/MSITE-1010
> Project: Maven Site Plugin
> Issue Type: Bug
> Components: site:deploy
>Affects Versions: 3.12.0, 4.0.0-M14
> Environment: Nexus, since at least Maven 3.6.3 (not tested with 3.9.7
> or 4.0.0-beta)
>Reporter: Matthias Bünger
>Priority: Minor
> Fix For: waiting-for-feedback
>
> Attachments: pom.xml
>
>
> I noticed the following issue while updating the plugins in our teams
> META-POM and could backtrack it at least until 3.12 but might be an even
> older issue. Havn't checked 4.0.0-M15 but from the releases notes I doubt it
> is fixed.
> When you do "site-deploy" for a single module or multi module project the
> site files (.html, css-folders, etc.) are stored in the site-repository (we
> have current Nexus version) within a subfolder with the name of the project,
> e.g
> {code}
> / (root of site-repository)
> /- project-A
>/css
>report.html
> /- project-B
>/css
>report.html
> /project-C
> {code}
> If you do the same for a "POM" project (e.g. a META-POM or BOM) the site
> files are all stored at root level (instead of creating a project folder) and
> ofc overwriting the ones from other POM-projects:
> {code}
> / (root of site-repository)
> /css
> /project-A
> /project-B
> /project-C
> report.html
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (MRELEASE-1144) Upgrade to Parent 42
[ https://issues.apache.org/jira/browse/MRELEASE-1144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed MRELEASE-1144. Resolution: Fixed Fixed with [2142c9e00ee4b1e55ba18a6126f00afcd58ddde0|https://gitbox.apache.org/repos/asf?p=maven-release.git;a=commit;h=2142c9e00ee4b1e55ba18a6126f00afcd58ddde0]. > Upgrade to Parent 42 > > > Key: MRELEASE-1144 > URL: https://issues.apache.org/jira/browse/MRELEASE-1144 > Project: Maven Release Plugin > Issue Type: Dependency upgrade >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: 3.1.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MRELEASE-1146) maven-release-plugin tests do not properly check for existence of svn command
[
https://issues.apache.org/jira/browse/MRELEASE-1146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed MRELEASE-1146.
Resolution: Fixed
Fixed with
[869ad977d7f5ef43d40494ebc94294be539b2654|https://gitbox.apache.org/repos/asf?p=maven-release.git;a=commit;h=869ad977d7f5ef43d40494ebc94294be539b2654].
> maven-release-plugin tests do not properly check for existence of svn command
> -
>
> Key: MRELEASE-1146
> URL: https://issues.apache.org/jira/browse/MRELEASE-1146
> Project: Maven Release Plugin
> Issue Type: Bug
>Affects Versions: 3.0.1
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 3.0.2
>
>
> Remove svn from PATH and see:
> {noformat}
> [ERROR] The following builds failed:
> [ERROR] * projects\prepare\flat-multi-module\parent-project\pom.xml
> [ERROR] * projects\prepare\MRELEASE-1053\pom.xml
> [ERROR] * projects\prepare\MRELEASE-128\pom.xml
> [ERROR] * projects\prepare\regular-multi-module\pom.xml
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (MRELEASE-1146) maven-release-plugin tests do not properly check for existence of svn command
Michael Osipov created MRELEASE-1146:
Summary: maven-release-plugin tests do not properly check for
existence of svn command
Key: MRELEASE-1146
URL: https://issues.apache.org/jira/browse/MRELEASE-1146
Project: Maven Release Plugin
Issue Type: Bug
Affects Versions: 3.0.1
Reporter: Michael Osipov
Assignee: Michael Osipov
Fix For: 3.0.2
Remove svn from PATH and see:
{noformat}
[ERROR] The following builds failed:
[ERROR] * projects\prepare\flat-multi-module\parent-project\pom.xml
[ERROR] * projects\prepare\MRELEASE-1053\pom.xml
[ERROR] * projects\prepare\MRELEASE-128\pom.xml
[ERROR] * projects\prepare\regular-multi-module\pom.xml
{noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MDEP-942) Deprecate the get goal
[
https://issues.apache.org/jira/browse/MDEP-942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17853507#comment-17853507
]
Michael Osipov commented on MDEP-942:
-
Should I cancel the vote for 3.7.1 with this issue?
> Deprecate the get goal
> --
>
> Key: MDEP-942
> URL: https://issues.apache.org/jira/browse/MDEP-942
> Project: Maven Dependency Plugin
> Issue Type: Improvement
>Reporter: Slawomir Jaranowski
>Priority: Major
>
> It looks like goal {{get}} is not usable or can be misunderstood
> - there is no {{destination}} parameter MDEP-395, MDEP-495
> But mentioned goal {{copy}}
> - doesn't have a possibility to copy transitive dependencies
> - doesn't support additional remote repositories
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (MRELEASE-1145) Upgrade to Maven 3.6.3
Michael Osipov created MRELEASE-1145: Summary: Upgrade to Maven 3.6.3 Key: MRELEASE-1145 URL: https://issues.apache.org/jira/browse/MRELEASE-1145 Project: Maven Release Plugin Issue Type: Dependency upgrade Reporter: Michael Osipov Assignee: Michael Osipov Fix For: next-release -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MRELEASE-1144) Upgrade to Parent 42
[ https://issues.apache.org/jira/browse/MRELEASE-1144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MRELEASE-1144: - Summary: Upgrade to Parent 42 (was: Upgrade to Parent 42 and Maven 3.6.3) > Upgrade to Parent 42 > > > Key: MRELEASE-1144 > URL: https://issues.apache.org/jira/browse/MRELEASE-1144 > Project: Maven Release Plugin > Issue Type: Dependency upgrade >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: next-release > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MDEP-903) Upgrade to Doxia 2.0.0 Milestone Stack
[ https://issues.apache.org/jira/browse/MDEP-903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MDEP-903: Fix Version/s: (was: Backlog) > Upgrade to Doxia 2.0.0 Milestone Stack > -- > > Key: MDEP-903 > URL: https://issues.apache.org/jira/browse/MDEP-903 > Project: Maven Dependency Plugin > Issue Type: Dependency upgrade >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > > * Ugprade to Doxia 2.0.0-M8 > * Upgrade to Maven Reporting API 4.0.0-M9 > * Upgrade to Maven Reporting Impl 4.0.0-M13 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MDEP-941) Deprecate dependency:sources in favor of dependency:resolve-sources
[
https://issues.apache.org/jira/browse/MDEP-941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed MDEP-941.
---
Resolution: Fixed
Fixed with
[dbdda0ccba8bebb98c0f2390e000b0561bfc5f4b|https://gitbox.apache.org/repos/asf?p=maven-dependency-plugin.git;a=commit;h=dbdda0ccba8bebb98c0f2390e000b0561bfc5f4b].
> Deprecate dependency:sources in favor of dependency:resolve-sources
> ---
>
> Key: MDEP-941
> URL: https://issues.apache.org/jira/browse/MDEP-941
> Project: Maven Dependency Plugin
> Issue Type: Task
> Components: sources
>Affects Versions: 3.6.1
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 3.7.0
>
>
> Unfortunately, the goal name does not really depict what the goal is doing,
> it fact it causes confusion as in MDEP-895. The name should clearly say that
> it *resolves* sources and does not collect (semantics is imporant). The new
> goal {{resolve-sources}} is functionally equivalent, but is just more
> expressive.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MDEP-838) "Artifact has not been packaged yet" error message is not very helpful
[ https://issues.apache.org/jira/browse/MDEP-838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MDEP-838: Affects Version/s: 3.6.1 > "Artifact has not been packaged yet" error message is not very helpful > -- > > Key: MDEP-838 > URL: https://issues.apache.org/jira/browse/MDEP-838 > Project: Maven Dependency Plugin > Issue Type: Bug >Affects Versions: 3.6.1 >Reporter: Christoph Läubrich >Assignee: Michael Osipov >Priority: Major > Fix For: 3.7.0 > > > Today in a build i get the error > > Artifact has not been packaged yet. When used on reactor artifact, copy > > should be executed after packaging: see MDEP-187 > So I know something is wrong but ... > The error message should at best include > # The "not packed artifact" > # The possible location / reactor project > # Probably *why* it is not considered as packed (e.g does it has no artifact > file? Is it a directory? Something else?) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MDEP-838) "Artifact has not been packaged yet" error message is not very helpful
[ https://issues.apache.org/jira/browse/MDEP-838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed MDEP-838. --- Resolution: Fixed Fixed with [f090b5efdeff0b2f2ebcc88a40f4b02dc4a6f408|https://gitbox.apache.org/repos/asf?p=maven-dependency-plugin.git;a=commit;h=f090b5efdeff0b2f2ebcc88a40f4b02dc4a6f408]. > "Artifact has not been packaged yet" error message is not very helpful > -- > > Key: MDEP-838 > URL: https://issues.apache.org/jira/browse/MDEP-838 > Project: Maven Dependency Plugin > Issue Type: Bug >Reporter: Christoph Läubrich >Assignee: Michael Osipov >Priority: Major > Fix For: 3.7.0 > > > Today in a build i get the error > > Artifact has not been packaged yet. When used on reactor artifact, copy > > should be executed after packaging: see MDEP-187 > So I know something is wrong but ... > The error message should at best include > # The "not packed artifact" > # The possible location / reactor project > # Probably *why* it is not considered as packed (e.g does it has no artifact > file? Is it a directory? Something else?) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MPLUGIN-528) Tone done report plugin console output
[
https://issues.apache.org/jira/browse/MPLUGIN-528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17853469#comment-17853469
]
Michael Osipov commented on MPLUGIN-528:
Yes, the first line is totally fine.
> Tone done report plugin console output
> --
>
> Key: MPLUGIN-528
> URL: https://issues.apache.org/jira/browse/MPLUGIN-528
> Project: Maven Plugin Tools
> Issue Type: Task
> Components: Plugin Reporting Plugin
>Affects Versions: 3.12.0, 3.13.1
>Reporter: Michael Osipov
>Priority: Major
>
> The report plugin writes too much at {{INFO}} level:
> {noformat}
> [WARNING] ^
> [INFO] Generating "Plugin Documentation" report ---
> maven-plugin-report-plugin:3.12.0:report
> Downloading from central:
> https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-pmd-plugin/maven-metadata.xml
> Downloading from apache.snapshots:
> https://repository.apache.org/snapshots/org/apache/maven/plugins/maven-pmd-plugin/maven-metadata.xml
> Downloaded from central:
> https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-pmd-plugin/maven-metadata.xml
> (1.4 kB at 20 kB/s)
> Downloaded from apache.snapshots:
> https://repository.apache.org/snapshots/org/apache/maven/plugins/maven-pmd-plugin/maven-metadata.xml
> (862 B at 3.4 kB/s)
> [INFO] Detecting plugin requirements history for range [0,): 36 releases,
> from 2.0-alpha-2 to 3.22.0
> [INFO] - RequirementsHistory{version='3.22.0', maven='3.2.5', jdk='8'}
> [INFO] - RequirementsHistory{version='3.21.2', maven='3.2.5', jdk='8'}
> [INFO] - RequirementsHistory{version='3.21.0', maven='3.2.5', jdk='8'}
> Downloading from central:
> https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-pmd-plugin/3.20.0/maven-pmd-plugin-3.20.0.pom
> Downloaded from central:
> https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-pmd-plugin/3.20.0/maven-pmd-plugin-3.20.0.pom
> (15 kB at 363 kB/s)
> [INFO] - RequirementsHistory{version='3.20.0', maven='3.2.5', jdk='8'}
> [INFO] - RequirementsHistory{version='3.19.0', maven='3.2.5', jdk='8'}
> Downloading from central:
> https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-pmd-plugin/3.18.0/maven-pmd-plugin-3.18.0.pom
> Downloaded from central:
> https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-pmd-plugin/3.18.0/maven-pmd-plugin-3.18.0.pom
> (15 kB at 392 kB/s)
> [INFO] - RequirementsHistory{version='3.18.0', maven='3.2.5', jdk='8'}
> [INFO] - RequirementsHistory{version='3.17.0', maven='3.2.5', jdk='8'}
> [INFO] - RequirementsHistory{version='3.16.0', maven='3.1.1', jdk='8'}
> Downloading from central:
> https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-pmd-plugin/3.15.0/maven-pmd-plugin-3.15.0.pom
> Downloaded from central:
> https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-pmd-plugin/3.15.0/maven-pmd-plugin-3.15.0.pom
> (14 kB at 313 kB/s)
> [INFO] - RequirementsHistory{version='3.15.0', maven='3.1.0', jdk='8'}
> Downloading from central:
> https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-pmd-plugin/3.14.0/maven-pmd-plugin-3.14.0.pom
> Downloaded from central:
> https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-pmd-plugin/3.14.0/maven-pmd-plugin-3.14.0.pom
> (13 kB at 371 kB/s)
> [INFO] - RequirementsHistory{version='3.14.0', maven='3.0', jdk='7'}
> Downloading from central:
> https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-pmd-plugin/3.13.0/maven-pmd-plugin-3.13.0.pom
> Downloaded from central:
> https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-pmd-plugin/3.13.0/maven-pmd-plugin-3.13.0.pom
> (12 kB at 213 kB/s)
> [INFO] - RequirementsHistory{version='3.13.0', maven='3.0', jdk='7'}
> Downloading from central:
> https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-pmd-plugin/3.12.0/maven-pmd-plugin-3.12.0.pom
> Downloaded from central:
> https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-pmd-plugin/3.12.0/maven-pmd-plugin-3.12.0.pom
> (12 kB at 374 kB/s)
> [INFO] - RequirementsHistory{version='3.12.0', maven='3.0', jdk='7'}
> Downloading from central:
> https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-pmd-plugin/3.11.0/maven-pmd-plugin-3.11.0.pom
> Downloaded from central:
> https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-pmd-plugin/3.11.0/maven-pmd-plugin-3.11.0.pom
> (13 kB at 341 kB/s)
> [INFO] - RequirementsHistory{version='3.11.0', maven='3.0', jdk='7'}
> Downloading from central:
> https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-pmd-plugin/3.10.0/maven-pmd-plugin-3.10.0.pom
> Downloaded from central:
>
[jira] [Created] (MRELEASE-1144) Upgrade to Parent 42 and Maven 3.6.3
Michael Osipov created MRELEASE-1144: Summary: Upgrade to Parent 42 and Maven 3.6.3 Key: MRELEASE-1144 URL: https://issues.apache.org/jira/browse/MRELEASE-1144 Project: Maven Release Plugin Issue Type: Dependency upgrade Reporter: Michael Osipov Assignee: Michael Osipov Fix For: next-release -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MDEP-838) "Artifact has not been packaged yet" error message is not very helpful
[ https://issues.apache.org/jira/browse/MDEP-838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MDEP-838: Fix Version/s: 3.7.0 > "Artifact has not been packaged yet" error message is not very helpful > -- > > Key: MDEP-838 > URL: https://issues.apache.org/jira/browse/MDEP-838 > Project: Maven Dependency Plugin > Issue Type: Bug >Reporter: Christoph Läubrich >Priority: Major > Fix For: 3.7.0 > > > Today in a build i get the error > > Artifact has not been packaged yet. When used on reactor artifact, copy > > should be executed after packaging: see MDEP-187 > So I know something is wrong but ... > The error message should at best include > # The "not packed artifact" > # The possible location / reactor project > # Probably *why* it is not considered as packed (e.g does it has no artifact > file? Is it a directory? Something else?) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MDEP-838) "Artifact has not been packaged yet" error message is not very helpful
[ https://issues.apache.org/jira/browse/MDEP-838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MDEP-838: Summary: "Artifact has not been packaged yet" error message is not very helpful (was: "Artifact has not been packaged yet" error message is not very helpful.) > "Artifact has not been packaged yet" error message is not very helpful > -- > > Key: MDEP-838 > URL: https://issues.apache.org/jira/browse/MDEP-838 > Project: Maven Dependency Plugin > Issue Type: Bug >Reporter: Christoph Läubrich >Priority: Major > > Today in a build i get the error > > Artifact has not been packaged yet. When used on reactor artifact, copy > > should be executed after packaging: see MDEP-187 > So I know something is wrong but ... > The error message should at best include > # The "not packed artifact" > # The possible location / reactor project > # Probably *why* it is not considered as packed (e.g does it has no artifact > file? Is it a directory? Something else?) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (MDEP-838) "Artifact has not been packaged yet" error message is not very helpful
[ https://issues.apache.org/jira/browse/MDEP-838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov reassigned MDEP-838: --- Assignee: Michael Osipov > "Artifact has not been packaged yet" error message is not very helpful > -- > > Key: MDEP-838 > URL: https://issues.apache.org/jira/browse/MDEP-838 > Project: Maven Dependency Plugin > Issue Type: Bug >Reporter: Christoph Läubrich >Assignee: Michael Osipov >Priority: Major > Fix For: 3.7.0 > > > Today in a build i get the error > > Artifact has not been packaged yet. When used on reactor artifact, copy > > should be executed after packaging: see MDEP-187 > So I know something is wrong but ... > The error message should at best include > # The "not packed artifact" > # The possible location / reactor project > # Probably *why* it is not considered as packed (e.g does it has no artifact > file? Is it a directory? Something else?) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MDEP-669) Optimize the documentation of of build-classpath-mojo
[ https://issues.apache.org/jira/browse/MDEP-669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed MDEP-669. --- Resolution: Fixed Fixed with [1d79937b583a9ef5450c39b0e369f26ea75bb361|https://gitbox.apache.org/repos/asf?p=maven-dependency-plugin.git;a=commit;h=1d79937b583a9ef5450c39b0e369f26ea75bb361]. > Optimize the documentation of of build-classpath-mojo > -- > > Key: MDEP-669 > URL: https://issues.apache.org/jira/browse/MDEP-669 > Project: Maven Dependency Plugin > Issue Type: Improvement > Components: build-classpath >Reporter: Xinrong Meng >Assignee: Michael Osipov >Priority: Major > Labels: up-for-grabs > Fix For: 3.7.0 > > > The documentation in > [https://maven.apache.org/plugins/maven-dependency-plugin/build-classpath-mojo.html#outputProperty] > is relatively confusing. > > `A property to set to the content of the classpath string.` would give users > illusions that they can use this parameter to modify the content of the > classpath string, rather than set the content of the classpath string to some > property. > > As far as I'm concerned, I wanted to embed classifier information in the > displayed classpath string, and I misunderstood this parameter until I > checked the source code of how it is defined. > > All in all, it would be great we could explicitly point it out that this > parameter sets the content of the classpath string to some property. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MDEP-669) Optimize the documentation of of build-classpath-mojo
[ https://issues.apache.org/jira/browse/MDEP-669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MDEP-669: Fix Version/s: 3.7.0 > Optimize the documentation of of build-classpath-mojo > -- > > Key: MDEP-669 > URL: https://issues.apache.org/jira/browse/MDEP-669 > Project: Maven Dependency Plugin > Issue Type: Improvement > Components: build-classpath >Reporter: Xinrong Meng >Assignee: Michael Osipov >Priority: Major > Labels: up-for-grabs > Fix For: 3.7.0 > > > The documentation in > [https://maven.apache.org/plugins/maven-dependency-plugin/build-classpath-mojo.html#outputProperty] > is relatively confusing. > > `A property to set to the content of the classpath string.` would give users > illusions that they can use this parameter to modify the content of the > classpath string, rather than set the content of the classpath string to some > property. > > As far as I'm concerned, I wanted to embed classifier information in the > displayed classpath string, and I misunderstood this parameter until I > checked the source code of how it is defined. > > All in all, it would be great we could explicitly point it out that this > parameter sets the content of the classpath string to some property. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (MDEP-669) Optimize the documentation of of build-classpath-mojo
[ https://issues.apache.org/jira/browse/MDEP-669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov reassigned MDEP-669: --- Assignee: Michael Osipov > Optimize the documentation of of build-classpath-mojo > -- > > Key: MDEP-669 > URL: https://issues.apache.org/jira/browse/MDEP-669 > Project: Maven Dependency Plugin > Issue Type: Improvement > Components: build-classpath >Reporter: Xinrong Meng >Assignee: Michael Osipov >Priority: Major > Labels: up-for-grabs > > The documentation in > [https://maven.apache.org/plugins/maven-dependency-plugin/build-classpath-mojo.html#outputProperty] > is relatively confusing. > > `A property to set to the content of the classpath string.` would give users > illusions that they can use this parameter to modify the content of the > classpath string, rather than set the content of the classpath string to some > property. > > As far as I'm concerned, I wanted to embed classifier information in the > displayed classpath string, and I misunderstood this parameter until I > checked the source code of how it is defined. > > All in all, it would be great we could explicitly point it out that this > parameter sets the content of the classpath string to some property. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MDEP-941) Deprecate dependency:sources in favor of dependency:resolve-sources
Michael Osipov created MDEP-941:
---
Summary: Deprecate dependency:sources in favor of
dependency:resolve-sources
Key: MDEP-941
URL: https://issues.apache.org/jira/browse/MDEP-941
Project: Maven Dependency Plugin
Issue Type: Task
Components: sources
Affects Versions: 3.6.1
Reporter: Michael Osipov
Assignee: Michael Osipov
Fix For: 3.7.0
Unfortunately, the goal name does not really depict what the goal is doing, it
fact it causes confusion as in MDEP-895. The name should clearly say that it
*resolves* sources and does not collect (semantics is imporant). The new goal
{{resolve-sources}} is functionally equivalent, but is just more expressive.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (MDEP-939) Lock down classifier in dependency:sources goal
[
https://issues.apache.org/jira/browse/MDEP-939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed MDEP-939.
---
Resolution: Fixed
Fixed with
[04c32164bcb3ecef6115616fee291d5ee071d370|https://gitbox.apache.org/repos/asf?p=maven-dependency-plugin.git;a=commit;h=04c32164bcb3ecef6115616fee291d5ee071d370].
> Lock down classifier in dependency:sources goal
> ---
>
> Key: MDEP-939
> URL: https://issues.apache.org/jira/browse/MDEP-939
> Project: Maven Dependency Plugin
> Issue Type: Improvement
> Components: sources
>Affects Versions: 3.6.1
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 3.7.0
>
>
> At the moment the classifier in {{dependency:sources}} is only set to
> {{sources}} if nothing is passed from the user, but allowing passing
> contradicts the purpose of this goal. We should make this parameter read-only
> and ignore any input to it.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MDEP-713) dependency:tree should not log info the user doesn't ask for
[
https://issues.apache.org/jira/browse/MDEP-713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MDEP-713:
Description:
I'm going to start this report here, though I kind of expect it slips into
core and a lot of other components. Suppose I run mvn dependency:tree on Guava.
As a user here's what I want to see (though probably minus the [INFO] prefix):
{noformat}
[INFO] com.google.guava:guava-gwt:jar:HEAD-jre-SNAPSHOT
[INFO] +- com.google.guava:failureaccess:jar:1.0.1:compile
[INFO] +- com.google.guava:guava:jar:HEAD-jre-SNAPSHOT:compile
[INFO] | +-
com.google.guava:listenablefuture:jar:.0-empty-to-avoid-conflict-with-guava:compile
[INFO] | +- com.google.code.findbugs:jsr305:jar:3.0.2:compile
[INFO] | +- com.google.errorprone:error_prone_annotations:jar:2.3.4:compile
[INFO] | \- com.google.j2objc:j2objc-annotations:jar:1.3:compile
[INFO] +- com.google.elemental2:elemental2-promise:jar:1.0.0-RC1:compile
[INFO] | +- com.google.jsinterop:jsinterop-annotations:jar:1.0.2:compile
[INFO] | \- com.google.jsinterop:base:jar:1.0.0-RC1:compile
[INFO] +- com.google.guava:guava-testlib:jar:HEAD-jre-SNAPSHOT:test
[INFO] | \- junit:junit:jar:4.13:test
[INFO] | \- org.hamcrest:hamcrest-core:jar:1.3:test
[INFO] +- com.google.guava:guava-testlib:jar:tests:HEAD-jre-SNAPSHOT:test
[INFO] +- com.google.guava:guava-tests:jar:tests:HEAD-jre-SNAPSHOT:test
[INFO] +- com.google.gwt:gwt-dev:jar:2.8.2:provided
[INFO] | +- com.google.code.gson:gson:jar:2.6.2:provided
[INFO] | +- org.ow2.asm:asm:jar:5.0.3:provided
[INFO] | +- org.ow2.asm:asm-util:jar:5.0.3:provided
[INFO] | | \- org.ow2.asm:asm-tree:jar:5.0.3:provided
[INFO] | +- org.ow2.asm:asm-commons:jar:5.0.3:provided
[INFO] | +- colt:colt:jar:1.2.0:provided
[INFO] | +- ant:ant:jar:1.6.5:provided
[INFO] | +- commons-collections:commons-collections:jar:3.2.2:provided
[INFO] | +- commons-io:commons-io:jar:2.4:provided
[INFO] | +- com.ibm.icu:icu4j:jar:50.1.1:provided
[INFO] | +- tapestry:tapestry:jar:4.0.2:provided
[INFO] | +- net.sourceforge.htmlunit:htmlunit:jar:2.19:provided
[INFO] | | +- xalan:xalan:jar:2.7.2:provided
[INFO] | | | \- xalan:serializer:jar:2.7.2:provided
[INFO] | | +- org.apache.commons:commons-lang3:jar:3.4:provided
[INFO] | | +- org.apache.httpcomponents:httpclient:jar:4.5.1:provided
[INFO] | | | \- org.apache.httpcomponents:httpcore:jar:4.4.3:provided
[INFO] | | +- org.apache.httpcomponents:httpmime:jar:4.5.1:provided
[INFO] | | +- commons-codec:commons-codec:jar:1.10:provided
[INFO] | | +- net.sourceforge.htmlunit:htmlunit-core-js:jar:2.17:provided
[INFO] | | +- xerces:xercesImpl:jar:2.11.0:provided
[INFO] | | | \- xml-apis:xml-apis:jar:1.4.01:provided
[INFO] | | +- net.sourceforge.nekohtml:nekohtml:jar:1.9.22:provided
[INFO] | | +- net.sourceforge.cssparser:cssparser:jar:0.9.18:provided
[INFO] | | +- commons-logging:commons-logging:jar:1.2:provided
[INFO] | | \-
org.eclipse.jetty.websocket:websocket-client:jar:9.2.13.v20150730:provided
[INFO] | | \-
org.eclipse.jetty.websocket:websocket-common:jar:9.2.13.v20150730:provided
[INFO] | |\-
org.eclipse.jetty.websocket:websocket-api:jar:9.2.13.v20150730:provided
[INFO] | +- org.eclipse.jetty:jetty-webapp:jar:9.2.14.v20151106:provided
[INFO] | | +- org.eclipse.jetty:jetty-xml:jar:9.2.14.v20151106:provided
[INFO] | | \- org.eclipse.jetty:jetty-servlet:jar:9.2.14.v20151106:provided
[INFO] | | \-
org.eclipse.jetty:jetty-security:jar:9.2.14.v20151106:provided
[INFO] | +- org.eclipse.jetty:jetty-servlets:jar:9.2.14.v20151106:provided
[INFO] | | +-
org.eclipse.jetty:jetty-continuation:jar:9.2.14.v20151106:provided
[INFO] | | +- org.eclipse.jetty:jetty-http:jar:9.2.14.v20151106:provided
[INFO] | | +- org.eclipse.jetty:jetty-util:jar:9.2.14.v20151106:provided
[INFO] | | \- org.eclipse.jetty:jetty-io:jar:9.2.14.v20151106:provided
[INFO] | +- org.eclipse.jetty:jetty-annotations:jar:9.2.14.v20151106:provided
[INFO] | | +- org.eclipse.jetty:jetty-plus:jar:9.2.14.v20151106:provided
[INFO] | | | \- org.eclipse.jetty:jetty-jndi:jar:9.2.14.v20151106:provided
[INFO] | | \- javax.annotation:javax.annotation-api:jar:1.2:provided
[INFO] | \- org.eclipse.jetty:apache-jsp:jar:9.2.14.v20151106:provided
[INFO] | +- org.eclipse.jetty:jetty-server:jar:9.2.14.v20151106:provided
[INFO] | +- org.eclipse.jetty.toolchain:jetty-schemas:jar:3.1.M0:provided
[INFO] | \- org.mortbay.jasper:apache-jsp:jar:8.0.9.M3:provided
[INFO] |\- org.mortbay.jasper:apache-el:jar:8.0.9.M3:provided
[INFO] +- com.google.gwt:gwt-user:jar:2.8.2:provided
[INFO] | +-
com.google.jsinterop:jsinterop-annotations:jar:sources:1.0.2:provided
[INFO] | +- javax.validation:validation-api:jar:1.0.0.GA:provided
[INFO] | +- javax.validation:validation-api:jar:sources:1.0.0.GA:provided
[INFO] | +- javax.servlet:javax.servlet-api:jar:3.1.0:provided
[INFO] | \-
[jira] [Commented] (MDEP-839) dependency:list should output a plain list whe used with a file
[
https://issues.apache.org/jira/browse/MDEP-839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17853408#comment-17853408
]
Michael Osipov commented on MDEP-839:
-
There is a workaround: Run Maven with {{-B}}.
> dependency:list should output a plain list whe used with a file
> ---
>
> Key: MDEP-839
> URL: https://issues.apache.org/jira/browse/MDEP-839
> Project: Maven Dependency Plugin
> Issue Type: Bug
>Reporter: Christoph Läubrich
>Priority: Minor
>
> There is a parameter to redirect the output to a file:
> https://maven.apache.org/plugins/maven-dependency-plugin/list-mojo.html#outputFile
> This currently has some issues I would not expect when redirecting such
> content to a file:
> # First line in the file is empty
> # Second line says 'The following files have been resolved:'
> # next lines are indented
> # ANSI Escape Characters are emmited e.g. [36m -- module maven.core[0;1;33m
> (auto)[m
> What I would expect:
> Each line just contains the raw resolved dependency e.g.
> "org.apache.maven:maven-core:jar:3.8.6:provided" and no more content is
> printed out, especially no ANSI Escapes
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MDEP-895) dependency:sources fails for multi-module project
[
https://issues.apache.org/jira/browse/MDEP-895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17853404#comment-17853404
]
Michael Osipov commented on MDEP-895:
-
Reverted with
[9fd4ed53b23e35de8ad8179e5b379acf3721ffbe|https://gitbox.apache.org/repos/asf?p=maven-dependency-plugin.git;a=commit;h=9fd4ed53b23e35de8ad8179e5b379acf3721ffbe].
> dependency:sources fails for multi-module project
> -
>
> Key: MDEP-895
> URL: https://issues.apache.org/jira/browse/MDEP-895
> Project: Maven Dependency Plugin
> Issue Type: Bug
> Components: sources
>Affects Versions: 3.6.1
>Reporter: Gerd Aschemann
>Assignee: Slawomir Jaranowski
>Priority: Critical
>
> When executing `mvn dependency:sources` on a multi-module project it fails to
> retrieve sources for the modules themselves (which is not necessary as the
> source code is provided locally already):
> {code:java}
> mvn dependency:sources
> ...
> [INFO] -< org.apache.maven.its.dependency:tree-multimodule-module-b
> >--
> [INFO] Building MultimoduleTest Module B 1.0-SNAPSHOT
> [3/3]
> [INFO] from module-b/pom.xml
> [INFO] [ jar
> ]-
> [INFO]
>
> [INFO] Reactor Summary for MultimoduleTest 1.0-SNAPSHOT:
> [INFO]
> [INFO] MultimoduleTest SUCCESS [ 0.390
> s]
> [INFO] MultimoduleTest Module A ... SUCCESS [ 0.063
> s]
> [INFO] MultimoduleTest Module B ... FAILURE [ 0.005
> s]
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 0.587 s
> [INFO] Finished at: 2023-11-09T10:38:16+01:00
> [INFO]
>
> [ERROR] Failed to execute goal on project tree-multimodule-module-b: Could
> not resolve dependencies for project
> org.apache.maven.its.dependency:tree-multimodule-module-b:jar:1.0-SNAPSHOT:
> The following artifacts could not be resolved:
> org.apache.maven.its.dependency:tree-multimodule-module-a:jar:1.0-SNAPSHOT
> (absent): Could not find artifact
> org.apache.maven.its.dependency:tree-multimodule-module-a:jar:1.0-SNAPSHOT ->
> [Help 1]{code}
> This is similar to the behaviour of MDEP-409.
> A test and PR is already prepared:
> https://github.com/jmle/maven-dependency-plugin/tree/fix-sources-multimodule
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (SUREFIRE-2248) Make "type" attribute on failures and errors in (surefire|failsafe)-test-report schema optional
[
https://issues.apache.org/jira/browse/SUREFIRE-2248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed SUREFIRE-2248.
Resolution: Fixed
Fixed with
[cad09319311326520e09b36cc95c06116901ec5e|https://gitbox.apache.org/repos/asf?p=maven-surefire.git;a=commit;h=cad09319311326520e09b36cc95c06116901ec5e].
> Make "type" attribute on failures and errors in
> (surefire|failsafe)-test-report schema optional
> ---
>
> Key: SUREFIRE-2248
> URL: https://issues.apache.org/jira/browse/SUREFIRE-2248
> Project: Maven Surefire
> Issue Type: Improvement
> Components: Maven Surefire Plugin
>Affects Versions: 3.2.5
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 3.3.0
>
>
> There are situations where a stack trace is not always available, in fact,
> the code path {{StatelessXmlReporter}} is structured in a way that it can
> lead to an empty/missing {{type}} from a stack trace. This would require to
> write a blank or a bogus value to satisfy the schema. This does not make
> sense. We should make this optional to better accommodate reality. See
> SUREFIRE-2232 for details.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (SUREFIRE-2047) Upgrade to maven-common-artifact-filters 3.4.0
[
https://issues.apache.org/jira/browse/SUREFIRE-2047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed SUREFIRE-2047.
Resolution: Fixed
Fixed with
[a88d786d7d9350b15dae47d8603e22748d8cdee1|https://gitbox.apache.org/repos/asf?p=maven-surefire.git;a=commit;h=a88d786d7d9350b15dae47d8603e22748d8cdee1].
> Upgrade to maven-common-artifact-filters 3.4.0
> --
>
> Key: SUREFIRE-2047
> URL: https://issues.apache.org/jira/browse/SUREFIRE-2047
> Project: Maven Surefire
> Issue Type: Dependency upgrade
>Reporter: Slawomir Jaranowski
>Assignee: Michael Osipov
>Priority: Minor
> Fix For: 3.3.0
>
>
> Currently we can't upgrade {{maven-common-artifact-filters}} to 3.2.0 due to
> MSHARED-1031
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (MPIR-455) dependencies goal: add support for multi-release JARs
[ https://issues.apache.org/jira/browse/MPIR-455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17853390#comment-17853390 ] Michael Osipov edited comment on MPIR-455 at 6/8/24 4:06 PM: - That looks promising. What about bulletpoints like here? !screenshot-1.png! and instead of "Base" "Root" as described in JEP 238? was (Author: michael-o): That looks promising. What about bulletpoints like here: !screenshot-1.png! and instead of "Base" "Root" as described in JEP 238? > dependencies goal: add support for multi-release JARs > - > > Key: MPIR-455 > URL: https://issues.apache.org/jira/browse/MPIR-455 > Project: Maven Project Info Reports Plugin > Issue Type: Bug > Components: dependencies >Affects Versions: 3.4.5, 3.5.0 >Reporter: Gabriel Belingueres >Assignee: Michael Osipov >Priority: Major > Fix For: 3.6.0 > > Attachments: image-2024-01-04-21-12-54-861.png, > image-2024-06-02-10-58-46-991.png, image-2024-06-02-11-01-26-148.png, > image-2024-06-08-11-11-22-722.png, screenshot-1.png > > > dependencies goal reports dependencies with multi-release support with the > highest version supported in the jar file, instead of the base version. > Example: plexus-utils 4.0.0 is reported as a Java 11 dependency, but their > base version is 1.8. > !image-2024-01-04-21-12-54-861.png! > Because of this the lower "Total" rows report a wrong java version too. > > This depends on https://issues.apache.org/jira/browse/MSHARED-1256. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MPIR-455) dependencies goal: add support for multi-release JARs
[ https://issues.apache.org/jira/browse/MPIR-455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17853390#comment-17853390 ] Michael Osipov commented on MPIR-455: - That looks promising. What about bulletpoints like here: !screenshot-1.png! and instead of "Base" "Root" as described in JEP 238? > dependencies goal: add support for multi-release JARs > - > > Key: MPIR-455 > URL: https://issues.apache.org/jira/browse/MPIR-455 > Project: Maven Project Info Reports Plugin > Issue Type: Bug > Components: dependencies >Affects Versions: 3.4.5, 3.5.0 >Reporter: Gabriel Belingueres >Assignee: Michael Osipov >Priority: Major > Fix For: 3.6.0 > > Attachments: image-2024-01-04-21-12-54-861.png, > image-2024-06-02-10-58-46-991.png, image-2024-06-02-11-01-26-148.png, > image-2024-06-08-11-11-22-722.png, screenshot-1.png > > > dependencies goal reports dependencies with multi-release support with the > highest version supported in the jar file, instead of the base version. > Example: plexus-utils 4.0.0 is reported as a Java 11 dependency, but their > base version is 1.8. > !image-2024-01-04-21-12-54-861.png! > Because of this the lower "Total" rows report a wrong java version too. > > This depends on https://issues.apache.org/jira/browse/MSHARED-1256. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MPIR-455) dependencies goal: add support for multi-release JARs
[ https://issues.apache.org/jira/browse/MPIR-455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MPIR-455: Attachment: screenshot-1.png > dependencies goal: add support for multi-release JARs > - > > Key: MPIR-455 > URL: https://issues.apache.org/jira/browse/MPIR-455 > Project: Maven Project Info Reports Plugin > Issue Type: Bug > Components: dependencies >Affects Versions: 3.4.5, 3.5.0 >Reporter: Gabriel Belingueres >Assignee: Michael Osipov >Priority: Major > Fix For: 3.6.0 > > Attachments: image-2024-01-04-21-12-54-861.png, > image-2024-06-02-10-58-46-991.png, image-2024-06-02-11-01-26-148.png, > image-2024-06-08-11-11-22-722.png, screenshot-1.png > > > dependencies goal reports dependencies with multi-release support with the > highest version supported in the jar file, instead of the base version. > Example: plexus-utils 4.0.0 is reported as a Java 11 dependency, but their > base version is 1.8. > !image-2024-01-04-21-12-54-861.png! > Because of this the lower "Total" rows report a wrong java version too. > > This depends on https://issues.apache.org/jira/browse/MSHARED-1256. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MPIR-455) dependencies goal: add support for multi-release JARs
[ https://issues.apache.org/jira/browse/MPIR-455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17853379#comment-17853379 ] Michael Osipov commented on MPIR-455: - [~belingueres], please let me know your timeframe where you want to deliver the PR. I'd like to do a release in the next two weeks. > dependencies goal: add support for multi-release JARs > - > > Key: MPIR-455 > URL: https://issues.apache.org/jira/browse/MPIR-455 > Project: Maven Project Info Reports Plugin > Issue Type: Bug > Components: dependencies >Affects Versions: 3.4.5, 3.5.0 >Reporter: Gabriel Belingueres >Assignee: Michael Osipov >Priority: Major > Fix For: 3.6.0 > > Attachments: image-2024-01-04-21-12-54-861.png, > image-2024-06-02-10-58-46-991.png, image-2024-06-02-11-01-26-148.png > > > dependencies goal reports dependencies with multi-release support with the > highest version supported in the jar file, instead of the base version. > Example: plexus-utils 4.0.0 is reported as a Java 11 dependency, but their > base version is 1.8. > !image-2024-01-04-21-12-54-861.png! > Because of this the lower "Total" rows report a wrong java version too. > > This depends on https://issues.apache.org/jira/browse/MSHARED-1256. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MPMD-381) MPMD-323-ruleset-basedir-jgitver is broken or flaky on JDK 17 windows
[
https://issues.apache.org/jira/browse/MPMD-381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17853295#comment-17853295
]
Michael Osipov commented on MPMD-381:
-
That is likely related to the drive letter being uppercase and lowercase.
> MPMD-323-ruleset-basedir-jgitver is broken or flaky on JDK 17 windows
> -
>
> Key: MPMD-381
> URL: https://issues.apache.org/jira/browse/MPMD-381
> Project: Maven PMD Plugin
> Issue Type: Bug
>Reporter: Elliotte Rusty Harold
>Priority: Major
>
> {noformat}
> Error: 'other' has different root
> 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.
> Running post-build script:
> D:\a\maven-pmd-plugin\maven-pmd-plugin\target\it\MPMD-323-ruleset-basedir-jgitver\verify.groovy
> Assertion failed:
> assert pmdXml.exists()
>| |
>| false
>
> D:\a\maven-pmd-plugin\maven-pmd-plugin\target\it\MPMD-323-ruleset-basedir-jgitver\target\pmd.xml
> at
> org.codehaus.groovy.runtime.InvokerHelper.assertFailed(InvokerHelper.java:436)
> at
> org.codehaus.groovy.runtime.ScriptBytecodeAdapter.assertFailed(ScriptBytecodeAdapter.java:670)
> at Script1.run(Script1.groovy:21)
> at groovy.lang.GroovyShell.evaluate(GroovyShell.java:427)
> at groovy.lang.GroovyShell.evaluate(GroovyShell.java:461)
> at groovy.lang.GroovyShell.evaluate(GroovyShell.java:436)
> at
> org.apache.maven.shared.scriptinterpreter.GroovyScriptInterpreter.evaluateScript(GroovyScriptInterpreter.java:76)
> at
> org.apache.maven.shared.scriptinterpreter.ScriptRunner.executeRun(ScriptRunner.java:236)
> at
> org.apache.maven.shared.scriptinterpreter.ScriptRunner.run(ScriptRunner.java:161)
> at
> org.apache.maven.plugins.invoker.AbstractInvokerMojo.runPostBuildHook(AbstractInvokerMojo.java:2154)
> at
> org.apache.maven.plugins.invoker.AbstractInvokerMojo.runBuild(AbstractInvokerMojo.java:2129)
> at
> org.apache.maven.plugins.invoker.AbstractInvokerMojo.runBuild(AbstractInvokerMojo.java:1721)
> at
> org.apache.maven.plugins.invoker.AbstractInvokerMojo.lambda$runBuilds$4(AbstractInvokerMojo.java:1431)
> at
> org.apache.maven.plugins.invoker.JobExecutor.lambda$null$1(JobExecutor.java:69)
> at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
> at java.base/java.lang.Thread.run(Thread.java:833)
> *** end build.log for: MPMD-323-ruleset-basedir-jgitver\pom.xml ***
> Error: -
> Error:
> [INFO] -
> [INFO] Build Summary:
> [INFO] Passed: 44, Failed: 1, Errors: 0, Skipped: 4
> [INFO] -
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MPLUGIN-528) Tone done report plugin console output
[
https://issues.apache.org/jira/browse/MPLUGIN-528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17853294#comment-17853294
]
Michael Osipov commented on MPLUGIN-528:
[~cstamas], [~hboutemy]
> Tone done report plugin console output
> --
>
> Key: MPLUGIN-528
> URL: https://issues.apache.org/jira/browse/MPLUGIN-528
> Project: Maven Plugin Tools
> Issue Type: Task
> Components: Plugin Reporting Plugin
>Affects Versions: 3.12.0, 3.13.1
>Reporter: Michael Osipov
>Priority: Major
>
> The report plugin writes too much at {{INFO}} level:
> {noformat}
> [WARNING] ^
> [INFO] Generating "Plugin Documentation" report ---
> maven-plugin-report-plugin:3.12.0:report
> Downloading from central:
> https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-pmd-plugin/maven-metadata.xml
> Downloading from apache.snapshots:
> https://repository.apache.org/snapshots/org/apache/maven/plugins/maven-pmd-plugin/maven-metadata.xml
> Downloaded from central:
> https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-pmd-plugin/maven-metadata.xml
> (1.4 kB at 20 kB/s)
> Downloaded from apache.snapshots:
> https://repository.apache.org/snapshots/org/apache/maven/plugins/maven-pmd-plugin/maven-metadata.xml
> (862 B at 3.4 kB/s)
> [INFO] Detecting plugin requirements history for range [0,): 36 releases,
> from 2.0-alpha-2 to 3.22.0
> [INFO] - RequirementsHistory{version='3.22.0', maven='3.2.5', jdk='8'}
> [INFO] - RequirementsHistory{version='3.21.2', maven='3.2.5', jdk='8'}
> [INFO] - RequirementsHistory{version='3.21.0', maven='3.2.5', jdk='8'}
> Downloading from central:
> https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-pmd-plugin/3.20.0/maven-pmd-plugin-3.20.0.pom
> Downloaded from central:
> https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-pmd-plugin/3.20.0/maven-pmd-plugin-3.20.0.pom
> (15 kB at 363 kB/s)
> [INFO] - RequirementsHistory{version='3.20.0', maven='3.2.5', jdk='8'}
> [INFO] - RequirementsHistory{version='3.19.0', maven='3.2.5', jdk='8'}
> Downloading from central:
> https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-pmd-plugin/3.18.0/maven-pmd-plugin-3.18.0.pom
> Downloaded from central:
> https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-pmd-plugin/3.18.0/maven-pmd-plugin-3.18.0.pom
> (15 kB at 392 kB/s)
> [INFO] - RequirementsHistory{version='3.18.0', maven='3.2.5', jdk='8'}
> [INFO] - RequirementsHistory{version='3.17.0', maven='3.2.5', jdk='8'}
> [INFO] - RequirementsHistory{version='3.16.0', maven='3.1.1', jdk='8'}
> Downloading from central:
> https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-pmd-plugin/3.15.0/maven-pmd-plugin-3.15.0.pom
> Downloaded from central:
> https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-pmd-plugin/3.15.0/maven-pmd-plugin-3.15.0.pom
> (14 kB at 313 kB/s)
> [INFO] - RequirementsHistory{version='3.15.0', maven='3.1.0', jdk='8'}
> Downloading from central:
> https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-pmd-plugin/3.14.0/maven-pmd-plugin-3.14.0.pom
> Downloaded from central:
> https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-pmd-plugin/3.14.0/maven-pmd-plugin-3.14.0.pom
> (13 kB at 371 kB/s)
> [INFO] - RequirementsHistory{version='3.14.0', maven='3.0', jdk='7'}
> Downloading from central:
> https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-pmd-plugin/3.13.0/maven-pmd-plugin-3.13.0.pom
> Downloaded from central:
> https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-pmd-plugin/3.13.0/maven-pmd-plugin-3.13.0.pom
> (12 kB at 213 kB/s)
> [INFO] - RequirementsHistory{version='3.13.0', maven='3.0', jdk='7'}
> Downloading from central:
> https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-pmd-plugin/3.12.0/maven-pmd-plugin-3.12.0.pom
> Downloaded from central:
> https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-pmd-plugin/3.12.0/maven-pmd-plugin-3.12.0.pom
> (12 kB at 374 kB/s)
> [INFO] - RequirementsHistory{version='3.12.0', maven='3.0', jdk='7'}
> Downloading from central:
> https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-pmd-plugin/3.11.0/maven-pmd-plugin-3.11.0.pom
> Downloaded from central:
> https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-pmd-plugin/3.11.0/maven-pmd-plugin-3.11.0.pom
> (13 kB at 341 kB/s)
> [INFO] - RequirementsHistory{version='3.11.0', maven='3.0', jdk='7'}
> Downloading from central:
> https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-pmd-plugin/3.10.0/maven-pmd-plugin-3.10.0.pom
> Downloaded from central:
> https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-pmd-plugin/3.10.0/maven-pmd-plugin-3.10.0.pom
>
[jira] [Created] (MPLUGIN-528) Tone done report plugin console output
Michael Osipov created MPLUGIN-528:
--
Summary: Tone done report plugin console output
Key: MPLUGIN-528
URL: https://issues.apache.org/jira/browse/MPLUGIN-528
Project: Maven Plugin Tools
Issue Type: Task
Components: Plugin Reporting Plugin
Affects Versions: 3.13.1
Reporter: Michael Osipov
The report plugin writes too much at {{INFO}} level:
{noformat}
[WARNING] ^
[INFO] Generating "Plugin Documentation" report ---
maven-plugin-report-plugin:3.12.0:report
Downloading from central:
https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-pmd-plugin/maven-metadata.xml
Downloading from apache.snapshots:
https://repository.apache.org/snapshots/org/apache/maven/plugins/maven-pmd-plugin/maven-metadata.xml
Downloaded from central:
https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-pmd-plugin/maven-metadata.xml
(1.4 kB at 20 kB/s)
Downloaded from apache.snapshots:
https://repository.apache.org/snapshots/org/apache/maven/plugins/maven-pmd-plugin/maven-metadata.xml
(862 B at 3.4 kB/s)
[INFO] Detecting plugin requirements history for range [0,): 36 releases, from
2.0-alpha-2 to 3.22.0
[INFO] - RequirementsHistory{version='3.22.0', maven='3.2.5', jdk='8'}
[INFO] - RequirementsHistory{version='3.21.2', maven='3.2.5', jdk='8'}
[INFO] - RequirementsHistory{version='3.21.0', maven='3.2.5', jdk='8'}
Downloading from central:
https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-pmd-plugin/3.20.0/maven-pmd-plugin-3.20.0.pom
Downloaded from central:
https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-pmd-plugin/3.20.0/maven-pmd-plugin-3.20.0.pom
(15 kB at 363 kB/s)
[INFO] - RequirementsHistory{version='3.20.0', maven='3.2.5', jdk='8'}
[INFO] - RequirementsHistory{version='3.19.0', maven='3.2.5', jdk='8'}
Downloading from central:
https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-pmd-plugin/3.18.0/maven-pmd-plugin-3.18.0.pom
Downloaded from central:
https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-pmd-plugin/3.18.0/maven-pmd-plugin-3.18.0.pom
(15 kB at 392 kB/s)
[INFO] - RequirementsHistory{version='3.18.0', maven='3.2.5', jdk='8'}
[INFO] - RequirementsHistory{version='3.17.0', maven='3.2.5', jdk='8'}
[INFO] - RequirementsHistory{version='3.16.0', maven='3.1.1', jdk='8'}
Downloading from central:
https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-pmd-plugin/3.15.0/maven-pmd-plugin-3.15.0.pom
Downloaded from central:
https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-pmd-plugin/3.15.0/maven-pmd-plugin-3.15.0.pom
(14 kB at 313 kB/s)
[INFO] - RequirementsHistory{version='3.15.0', maven='3.1.0', jdk='8'}
Downloading from central:
https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-pmd-plugin/3.14.0/maven-pmd-plugin-3.14.0.pom
Downloaded from central:
https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-pmd-plugin/3.14.0/maven-pmd-plugin-3.14.0.pom
(13 kB at 371 kB/s)
[INFO] - RequirementsHistory{version='3.14.0', maven='3.0', jdk='7'}
Downloading from central:
https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-pmd-plugin/3.13.0/maven-pmd-plugin-3.13.0.pom
Downloaded from central:
https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-pmd-plugin/3.13.0/maven-pmd-plugin-3.13.0.pom
(12 kB at 213 kB/s)
[INFO] - RequirementsHistory{version='3.13.0', maven='3.0', jdk='7'}
Downloading from central:
https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-pmd-plugin/3.12.0/maven-pmd-plugin-3.12.0.pom
Downloaded from central:
https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-pmd-plugin/3.12.0/maven-pmd-plugin-3.12.0.pom
(12 kB at 374 kB/s)
[INFO] - RequirementsHistory{version='3.12.0', maven='3.0', jdk='7'}
Downloading from central:
https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-pmd-plugin/3.11.0/maven-pmd-plugin-3.11.0.pom
Downloaded from central:
https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-pmd-plugin/3.11.0/maven-pmd-plugin-3.11.0.pom
(13 kB at 341 kB/s)
[INFO] - RequirementsHistory{version='3.11.0', maven='3.0', jdk='7'}
Downloading from central:
https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-pmd-plugin/3.10.0/maven-pmd-plugin-3.10.0.pom
Downloaded from central:
https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-pmd-plugin/3.10.0/maven-pmd-plugin-3.10.0.pom
(12 kB at 338 kB/s)
[INFO] - RequirementsHistory{version='3.10.0', maven='3.0', jdk='7'}
Downloading from central:
https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-pmd-plugin/3.9.0/maven-pmd-plugin-3.9.0.pom
Downloaded from central:
https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-pmd-plugin/3.9.0/maven-pmd-plugin-3.9.0.pom
(12 kB at 356 kB/s)
[INFO] -
[jira] [Updated] (MPLUGIN-528) Tone done report plugin console output
[
https://issues.apache.org/jira/browse/MPLUGIN-528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MPLUGIN-528:
---
Affects Version/s: 3.12.0
> Tone done report plugin console output
> --
>
> Key: MPLUGIN-528
> URL: https://issues.apache.org/jira/browse/MPLUGIN-528
> Project: Maven Plugin Tools
> Issue Type: Task
> Components: Plugin Reporting Plugin
>Affects Versions: 3.12.0, 3.13.1
>Reporter: Michael Osipov
>Priority: Major
>
> The report plugin writes too much at {{INFO}} level:
> {noformat}
> [WARNING] ^
> [INFO] Generating "Plugin Documentation" report ---
> maven-plugin-report-plugin:3.12.0:report
> Downloading from central:
> https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-pmd-plugin/maven-metadata.xml
> Downloading from apache.snapshots:
> https://repository.apache.org/snapshots/org/apache/maven/plugins/maven-pmd-plugin/maven-metadata.xml
> Downloaded from central:
> https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-pmd-plugin/maven-metadata.xml
> (1.4 kB at 20 kB/s)
> Downloaded from apache.snapshots:
> https://repository.apache.org/snapshots/org/apache/maven/plugins/maven-pmd-plugin/maven-metadata.xml
> (862 B at 3.4 kB/s)
> [INFO] Detecting plugin requirements history for range [0,): 36 releases,
> from 2.0-alpha-2 to 3.22.0
> [INFO] - RequirementsHistory{version='3.22.0', maven='3.2.5', jdk='8'}
> [INFO] - RequirementsHistory{version='3.21.2', maven='3.2.5', jdk='8'}
> [INFO] - RequirementsHistory{version='3.21.0', maven='3.2.5', jdk='8'}
> Downloading from central:
> https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-pmd-plugin/3.20.0/maven-pmd-plugin-3.20.0.pom
> Downloaded from central:
> https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-pmd-plugin/3.20.0/maven-pmd-plugin-3.20.0.pom
> (15 kB at 363 kB/s)
> [INFO] - RequirementsHistory{version='3.20.0', maven='3.2.5', jdk='8'}
> [INFO] - RequirementsHistory{version='3.19.0', maven='3.2.5', jdk='8'}
> Downloading from central:
> https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-pmd-plugin/3.18.0/maven-pmd-plugin-3.18.0.pom
> Downloaded from central:
> https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-pmd-plugin/3.18.0/maven-pmd-plugin-3.18.0.pom
> (15 kB at 392 kB/s)
> [INFO] - RequirementsHistory{version='3.18.0', maven='3.2.5', jdk='8'}
> [INFO] - RequirementsHistory{version='3.17.0', maven='3.2.5', jdk='8'}
> [INFO] - RequirementsHistory{version='3.16.0', maven='3.1.1', jdk='8'}
> Downloading from central:
> https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-pmd-plugin/3.15.0/maven-pmd-plugin-3.15.0.pom
> Downloaded from central:
> https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-pmd-plugin/3.15.0/maven-pmd-plugin-3.15.0.pom
> (14 kB at 313 kB/s)
> [INFO] - RequirementsHistory{version='3.15.0', maven='3.1.0', jdk='8'}
> Downloading from central:
> https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-pmd-plugin/3.14.0/maven-pmd-plugin-3.14.0.pom
> Downloaded from central:
> https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-pmd-plugin/3.14.0/maven-pmd-plugin-3.14.0.pom
> (13 kB at 371 kB/s)
> [INFO] - RequirementsHistory{version='3.14.0', maven='3.0', jdk='7'}
> Downloading from central:
> https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-pmd-plugin/3.13.0/maven-pmd-plugin-3.13.0.pom
> Downloaded from central:
> https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-pmd-plugin/3.13.0/maven-pmd-plugin-3.13.0.pom
> (12 kB at 213 kB/s)
> [INFO] - RequirementsHistory{version='3.13.0', maven='3.0', jdk='7'}
> Downloading from central:
> https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-pmd-plugin/3.12.0/maven-pmd-plugin-3.12.0.pom
> Downloaded from central:
> https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-pmd-plugin/3.12.0/maven-pmd-plugin-3.12.0.pom
> (12 kB at 374 kB/s)
> [INFO] - RequirementsHistory{version='3.12.0', maven='3.0', jdk='7'}
> Downloading from central:
> https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-pmd-plugin/3.11.0/maven-pmd-plugin-3.11.0.pom
> Downloaded from central:
> https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-pmd-plugin/3.11.0/maven-pmd-plugin-3.11.0.pom
> (13 kB at 341 kB/s)
> [INFO] - RequirementsHistory{version='3.11.0', maven='3.0', jdk='7'}
> Downloading from central:
> https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-pmd-plugin/3.10.0/maven-pmd-plugin-3.10.0.pom
> Downloaded from central:
> https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-pmd-plugin/3.10.0/maven-pmd-plugin-3.10.0.pom
> (12 kB at 338 kB/s)
> [INFO] -
[jira] [Created] (MDEP-939) Lock down classifier in dependency:sources goal
Michael Osipov created MDEP-939:
---
Summary: Lock down classifier in dependency:sources goal
Key: MDEP-939
URL: https://issues.apache.org/jira/browse/MDEP-939
Project: Maven Dependency Plugin
Issue Type: Improvement
Components: sources
Affects Versions: 3.6.1
Reporter: Michael Osipov
Assignee: Michael Osipov
Fix For: 3.7.0
At the moment the classifier in {{dependency:sources}} is only set to
{{sources}} if nothing is passed from the user, but allowing passing
contradicts the purpose of this goal. We should make this parameter read-only
and ignore any input to it.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MJAVADOC-656) Following redirects breaks valid links
[ https://issues.apache.org/jira/browse/MJAVADOC-656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17853286#comment-17853286 ] Michael Osipov commented on MJAVADOC-656: - I agree with your sentiment that a parameter will not really help. We need to duplicate the logic from the Javadoc tool for the time being. The tests in place for the redirect are pointless now because they rely on outbound resources and guess what, they have changed and don't send redirects anymore > Following redirects breaks valid links > -- > > Key: MJAVADOC-656 > URL: https://issues.apache.org/jira/browse/MJAVADOC-656 > Project: Maven Javadoc Plugin > Issue Type: Bug >Affects Versions: 3.0.1, 3.2.0 >Reporter: Robert Važan >Priority: Minor > > Version 3.0.1 fixed #427 by following redirects. This feature unfortunately > breaks when HTTP server is configured as follows: > /apidocs/package-list -> 200 > /apidocs -> 301 /apidocs/com/example/package-summary.html > /apidocs/ -> 301 /apidocs/com/example/package-summary.html > /apidocs/com/example/package-summary.html -> 200 > Without following redirects (in version 3.0.0), the link is passed to javadoc > tool unchanged, the javadoc tool fetches /apidocs/package-list, and > everything works fine. Since 3.0.1, javadoc plugin follows one of the > redirects (/apidocs or /apidocs/), passes the package summary URL to javadoc > tool, which then fails like this: > [WARNING] javadoc: warning - Error fetching URL: > [https://example.com/apidocs/com/example/package-summary.html/] > And if you have failOnWarnings set to true, this will fail the whole build. > The solution is fairly simple. Construct the whole URL (.../package-list) and > follow redirects on that one. Then check whether the final destination ends > in /package-list, strip the /package-list suffix, and pass the result to the > javadoc tool. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MJAVADOC-656) Following redirects breaks valid links
[ https://issues.apache.org/jira/browse/MJAVADOC-656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17853285#comment-17853285 ] Michael Osipov commented on MJAVADOC-656: - First step: https://github.com/apache/maven-javadoc-plugin/pull/287 > Following redirects breaks valid links > -- > > Key: MJAVADOC-656 > URL: https://issues.apache.org/jira/browse/MJAVADOC-656 > Project: Maven Javadoc Plugin > Issue Type: Bug >Affects Versions: 3.0.1, 3.2.0 >Reporter: Robert Važan >Priority: Minor > > Version 3.0.1 fixed #427 by following redirects. This feature unfortunately > breaks when HTTP server is configured as follows: > /apidocs/package-list -> 200 > /apidocs -> 301 /apidocs/com/example/package-summary.html > /apidocs/ -> 301 /apidocs/com/example/package-summary.html > /apidocs/com/example/package-summary.html -> 200 > Without following redirects (in version 3.0.0), the link is passed to javadoc > tool unchanged, the javadoc tool fetches /apidocs/package-list, and > everything works fine. Since 3.0.1, javadoc plugin follows one of the > redirects (/apidocs or /apidocs/), passes the package summary URL to javadoc > tool, which then fails like this: > [WARNING] javadoc: warning - Error fetching URL: > [https://example.com/apidocs/com/example/package-summary.html/] > And if you have failOnWarnings set to true, this will fail the whole build. > The solution is fairly simple. Construct the whole URL (.../package-list) and > follow redirects on that one. Then check whether the final destination ends > in /package-list, strip the /package-list suffix, and pass the result to the > javadoc tool. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MDEP-895) dependency:sources fails for multi-module project
[
https://issues.apache.org/jira/browse/MDEP-895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MDEP-895:
Fix Version/s: (was: 3.7.0)
> dependency:sources fails for multi-module project
> -
>
> Key: MDEP-895
> URL: https://issues.apache.org/jira/browse/MDEP-895
> Project: Maven Dependency Plugin
> Issue Type: Bug
> Components: sources
>Affects Versions: 3.6.1
>Reporter: Gerd Aschemann
>Assignee: Slawomir Jaranowski
>Priority: Critical
>
> When executing `mvn dependency:sources` on a multi-module project it fails to
> retrieve sources for the modules themselves (which is not necessary as the
> source code is provided locally already):
> {code:java}
> mvn dependency:sources
> ...
> [INFO] -< org.apache.maven.its.dependency:tree-multimodule-module-b
> >--
> [INFO] Building MultimoduleTest Module B 1.0-SNAPSHOT
> [3/3]
> [INFO] from module-b/pom.xml
> [INFO] [ jar
> ]-
> [INFO]
>
> [INFO] Reactor Summary for MultimoduleTest 1.0-SNAPSHOT:
> [INFO]
> [INFO] MultimoduleTest SUCCESS [ 0.390
> s]
> [INFO] MultimoduleTest Module A ... SUCCESS [ 0.063
> s]
> [INFO] MultimoduleTest Module B ... FAILURE [ 0.005
> s]
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 0.587 s
> [INFO] Finished at: 2023-11-09T10:38:16+01:00
> [INFO]
>
> [ERROR] Failed to execute goal on project tree-multimodule-module-b: Could
> not resolve dependencies for project
> org.apache.maven.its.dependency:tree-multimodule-module-b:jar:1.0-SNAPSHOT:
> The following artifacts could not be resolved:
> org.apache.maven.its.dependency:tree-multimodule-module-a:jar:1.0-SNAPSHOT
> (absent): Could not find artifact
> org.apache.maven.its.dependency:tree-multimodule-module-a:jar:1.0-SNAPSHOT ->
> [Help 1]{code}
> This is similar to the behaviour of MDEP-409.
> A test and PR is already prepared:
> https://github.com/jmle/maven-dependency-plugin/tree/fix-sources-multimodule
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Reopened] (MDEP-895) dependency:sources fails for multi-module project
[
https://issues.apache.org/jira/browse/MDEP-895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov reopened MDEP-895:
-
The applied change changes the semantics and contradicts the actual {{resolve}}
operation. The goal is poorly named. It should have been {{resolve-sources}}.
We will deprecate this one and create successor.
> dependency:sources fails for multi-module project
> -
>
> Key: MDEP-895
> URL: https://issues.apache.org/jira/browse/MDEP-895
> Project: Maven Dependency Plugin
> Issue Type: Bug
> Components: sources
>Affects Versions: 3.6.1
>Reporter: Gerd Aschemann
>Assignee: Slawomir Jaranowski
>Priority: Critical
> Fix For: 3.7.0
>
>
> When executing `mvn dependency:sources` on a multi-module project it fails to
> retrieve sources for the modules themselves (which is not necessary as the
> source code is provided locally already):
> {code:java}
> mvn dependency:sources
> ...
> [INFO] -< org.apache.maven.its.dependency:tree-multimodule-module-b
> >--
> [INFO] Building MultimoduleTest Module B 1.0-SNAPSHOT
> [3/3]
> [INFO] from module-b/pom.xml
> [INFO] [ jar
> ]-
> [INFO]
>
> [INFO] Reactor Summary for MultimoduleTest 1.0-SNAPSHOT:
> [INFO]
> [INFO] MultimoduleTest SUCCESS [ 0.390
> s]
> [INFO] MultimoduleTest Module A ... SUCCESS [ 0.063
> s]
> [INFO] MultimoduleTest Module B ... FAILURE [ 0.005
> s]
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 0.587 s
> [INFO] Finished at: 2023-11-09T10:38:16+01:00
> [INFO]
>
> [ERROR] Failed to execute goal on project tree-multimodule-module-b: Could
> not resolve dependencies for project
> org.apache.maven.its.dependency:tree-multimodule-module-b:jar:1.0-SNAPSHOT:
> The following artifacts could not be resolved:
> org.apache.maven.its.dependency:tree-multimodule-module-a:jar:1.0-SNAPSHOT
> (absent): Could not find artifact
> org.apache.maven.its.dependency:tree-multimodule-module-a:jar:1.0-SNAPSHOT ->
> [Help 1]{code}
> This is similar to the behaviour of MDEP-409.
> A test and PR is already prepared:
> https://github.com/jmle/maven-dependency-plugin/tree/fix-sources-multimodule
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MDEP-900) dependency:resolve fails for multi-module project
[
https://issues.apache.org/jira/browse/MDEP-900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17853282#comment-17853282
]
Michael Osipov commented on MDEP-900:
-
For now, this is by design. See PR for reasons.
> dependency:resolve fails for multi-module project
> -
>
> Key: MDEP-900
> URL: https://issues.apache.org/jira/browse/MDEP-900
> Project: Maven Dependency Plugin
> Issue Type: Bug
> Components: resolve
>Affects Versions: 3.6.1
>Reporter: Gerd Aschemann
>Assignee: Slawomir Jaranowski
>Priority: Critical
>
> When executing {{mvn dependency:resolve}} on a multi-module project it fails
> to retrieve artifacts for the modules themselves (which is not necessary as
> these can be installed by {{mvn install}} any time).
> This can be seen on an [OSS multi-module
> project|https://github.com/WASdev/sample.daytrader7]:
> {code:java}
> mvn dependency:resolve
> [INFO] Scanning for projects...
> [INFO]
>
> [INFO] Reactor Build Order:
> [INFO]
> [INFO] WAS Liberty Sample - Java EE7 Benchmark Sample - EJB Module
> [jar]
> [INFO] WAS Liberty Sample - Java EE7 Benchmark Sample - Web Module
> [war]
> [INFO] WAS Liberty Sample - Java EE7 Benchmark Sample
> [pom]
> [INFO] WAS Liberty Sample - Java EE7 Benchmark Sample - EAR
> [ear]
> [INFO]
> [INFO] --< net.wasdev.wlp.sample:daytrader-ee7-ejb
> >---
> [INFO] Building WAS Liberty Sample - Java EE7 Benchmark Sample - EJB Module
> 1.0-SNAPSHOT [1/4]
> [INFO] from daytrader-ee7-ejb/pom.xml
> [INFO] [ jar
> ]-
> [INFO]
> [INFO] --- dependency:3.6.0:resolve (default-cli) @ daytrader-ee7-ejb ---
> [INFO]
> [INFO] The following files have been resolved:
> [INFO] javax:javaee-api:jar:7.0:provided -- module javaee.api (auto)
> [INFO] com.sun.mail:javax.mail:jar:1.5.0:provided -- module javax.mail
> (auto)
> [INFO] javax.activation:activation:jar:1.1:provided -- module activation
> (auto)
> [INFO] javax.annotation:javax.annotation-api:jar:1.3.2:provided -- module
> java.annotation [auto]
> [INFO]
> [INFO]
> [INFO] --< net.wasdev.wlp.sample:daytrader-ee7-web
> >---
> [INFO] Building WAS Liberty Sample - Java EE7 Benchmark Sample - Web Module
> 1.0-SNAPSHOT [2/4]
> [INFO] from daytrader-ee7-web/pom.xml
> [INFO] [ war
> ]-
> [INFO]
>
> [INFO] Reactor Summary for WAS Liberty Sample - Java EE7 Benchmark Sample
> 1.0-SNAPSHOT:
> [INFO]
> [INFO] WAS Liberty Sample - Java EE7 Benchmark Sample - EJB Module SUCCESS [
> 0.402 s]
> [INFO] WAS Liberty Sample - Java EE7 Benchmark Sample - Web Module FAILURE [
> 0.012 s]
> [INFO] WAS Liberty Sample - Java EE7 Benchmark Sample . SKIPPED
> [INFO] WAS Liberty Sample - Java EE7 Benchmark Sample - EAR SKIPPED
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 0.552 s
> [INFO] Finished at: 2023-11-14T12:37:02+01:00
> [INFO]
>
> [ERROR] Failed to execute goal on project daytrader-ee7-web: Could not
> resolve dependencies for project
> net.wasdev.wlp.sample:daytrader-ee7-web:war:1.0-SNAPSHOT: The following
> artifacts could not be resolved:
> net.wasdev.wlp.sample:daytrader-ee7-ejb:jar:1.0-SNAPSHOT (absent): Could not
> find artifact net.wasdev.wlp.sample:daytrader-ee7-ejb:jar:1.0-SNAPSHOT ->
> [Help 1]{code}
> This is similar to the behaviour of MDEP-409, and MDEP-895
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MDEP-900) dependency:resolve fails for multi-module project
[
https://issues.apache.org/jira/browse/MDEP-900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MDEP-900:
Fix Version/s: (was: 3.7.0)
> dependency:resolve fails for multi-module project
> -
>
> Key: MDEP-900
> URL: https://issues.apache.org/jira/browse/MDEP-900
> Project: Maven Dependency Plugin
> Issue Type: Bug
> Components: resolve
>Affects Versions: 3.6.1
>Reporter: Gerd Aschemann
>Assignee: Slawomir Jaranowski
>Priority: Critical
>
> When executing {{mvn dependency:resolve}} on a multi-module project it fails
> to retrieve artifacts for the modules themselves (which is not necessary as
> these can be installed by {{mvn install}} any time).
> This can be seen on an [OSS multi-module
> project|https://github.com/WASdev/sample.daytrader7]:
> {code:java}
> mvn dependency:resolve
> [INFO] Scanning for projects...
> [INFO]
>
> [INFO] Reactor Build Order:
> [INFO]
> [INFO] WAS Liberty Sample - Java EE7 Benchmark Sample - EJB Module
> [jar]
> [INFO] WAS Liberty Sample - Java EE7 Benchmark Sample - Web Module
> [war]
> [INFO] WAS Liberty Sample - Java EE7 Benchmark Sample
> [pom]
> [INFO] WAS Liberty Sample - Java EE7 Benchmark Sample - EAR
> [ear]
> [INFO]
> [INFO] --< net.wasdev.wlp.sample:daytrader-ee7-ejb
> >---
> [INFO] Building WAS Liberty Sample - Java EE7 Benchmark Sample - EJB Module
> 1.0-SNAPSHOT [1/4]
> [INFO] from daytrader-ee7-ejb/pom.xml
> [INFO] [ jar
> ]-
> [INFO]
> [INFO] --- dependency:3.6.0:resolve (default-cli) @ daytrader-ee7-ejb ---
> [INFO]
> [INFO] The following files have been resolved:
> [INFO] javax:javaee-api:jar:7.0:provided -- module javaee.api (auto)
> [INFO] com.sun.mail:javax.mail:jar:1.5.0:provided -- module javax.mail
> (auto)
> [INFO] javax.activation:activation:jar:1.1:provided -- module activation
> (auto)
> [INFO] javax.annotation:javax.annotation-api:jar:1.3.2:provided -- module
> java.annotation [auto]
> [INFO]
> [INFO]
> [INFO] --< net.wasdev.wlp.sample:daytrader-ee7-web
> >---
> [INFO] Building WAS Liberty Sample - Java EE7 Benchmark Sample - Web Module
> 1.0-SNAPSHOT [2/4]
> [INFO] from daytrader-ee7-web/pom.xml
> [INFO] [ war
> ]-
> [INFO]
>
> [INFO] Reactor Summary for WAS Liberty Sample - Java EE7 Benchmark Sample
> 1.0-SNAPSHOT:
> [INFO]
> [INFO] WAS Liberty Sample - Java EE7 Benchmark Sample - EJB Module SUCCESS [
> 0.402 s]
> [INFO] WAS Liberty Sample - Java EE7 Benchmark Sample - Web Module FAILURE [
> 0.012 s]
> [INFO] WAS Liberty Sample - Java EE7 Benchmark Sample . SKIPPED
> [INFO] WAS Liberty Sample - Java EE7 Benchmark Sample - EAR SKIPPED
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 0.552 s
> [INFO] Finished at: 2023-11-14T12:37:02+01:00
> [INFO]
>
> [ERROR] Failed to execute goal on project daytrader-ee7-web: Could not
> resolve dependencies for project
> net.wasdev.wlp.sample:daytrader-ee7-web:war:1.0-SNAPSHOT: The following
> artifacts could not be resolved:
> net.wasdev.wlp.sample:daytrader-ee7-ejb:jar:1.0-SNAPSHOT (absent): Could not
> find artifact net.wasdev.wlp.sample:daytrader-ee7-ejb:jar:1.0-SNAPSHOT ->
> [Help 1]{code}
> This is similar to the behaviour of MDEP-409, and MDEP-895
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (MSKINS-248) If $bodyContent is empty HTML code is distorted
Michael Osipov created MSKINS-248:
-
Summary: If $bodyContent is empty HTML code is distorted
Key: MSKINS-248
URL: https://issues.apache.org/jira/browse/MSKINS-248
Project: Maven Skins
Issue Type: Bug
Components: Fluido Skin
Affects Versions: fluido-2.0.0-M9
Reporter: Michael Osipov
Assignee: Michael Osipov
Fix For: fluido-2.0.0-M10, fluido-2.0.0
If {{$bodyContent}} is empty HTML code is distorted because Velocity does not
expand the variable, but leaves the literal {{$bodyContent}}. We need to check
it with an {{#if}} clause.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (MJAVADOC-796) Do not follow links for Java 12+
Michael Osipov created MJAVADOC-796:
---
Summary: Do not follow links for Java 12+
Key: MJAVADOC-796
URL: https://issues.apache.org/jira/browse/MJAVADOC-796
Project: Maven Javadoc Plugin
Issue Type: Improvement
Components: javadoc
Affects Versions: 3.7.0
Reporter: Michael Osipov
Assignee: Michael Osipov
Fix For: 3.7.1
For years, we have been following redirects manually because {{javadoc}} was
not able to. with Java 12 (JDK-8190312) is was implemented and our logic can be
skipped when {{javadoc}} 12+ is used.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (MCHANGELOG-156) Add option to render the changelog as document
[
https://issues.apache.org/jira/browse/MCHANGELOG-156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17853184#comment-17853184
]
Michael Osipov edited comment on MCHANGELOG-156 at 6/7/24 2:57 PM:
---
Please note that any sink that any page-oriented (PDF, RTF) has been removed in
Doxia 2.0.0.
was (Author: michael-o):
Please note that any think that any page-oriented (PDF, RTF) sink has been
removed in Doxia 2.0.0.
> Add option to render the changelog as document
> --
>
> Key: MCHANGELOG-156
> URL: https://issues.apache.org/jira/browse/MCHANGELOG-156
> Project: Maven Changelog Plugin
> Issue Type: New Feature
>Reporter: Juul Hobert
>Priority: Major
>
> The changelog plugin uses `SiteRendererSink` as default Sink implementation.
> I can imagine it would be useful to have the changelog as document as well.
> There is another Sink implementation available in the `doxia-doc-renderer`
> library. I think a configuration like below could be used to instruct the
> plugin to create a rtf/pdf document instead.
> {code:java}
> ...
>
> maven-changelog-plugin
>
> ...
> html/pdf/rtf
> ...
>
>
> ...{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MCHANGELOG-156) Add option to render the changelog as document
[
https://issues.apache.org/jira/browse/MCHANGELOG-156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17853184#comment-17853184
]
Michael Osipov commented on MCHANGELOG-156:
---
Please note that any think that any page-oriented (PDF, RTF) sink has been
removed in Doxia 2.0.0.
> Add option to render the changelog as document
> --
>
> Key: MCHANGELOG-156
> URL: https://issues.apache.org/jira/browse/MCHANGELOG-156
> Project: Maven Changelog Plugin
> Issue Type: New Feature
>Reporter: Juul Hobert
>Priority: Major
>
> The changelog plugin uses `SiteRendererSink` as default Sink implementation.
> I can imagine it would be useful to have the changelog as document as well.
> There is another Sink implementation available in the `doxia-doc-renderer`
> library. I think a configuration like below could be used to instruct the
> plugin to create a rtf/pdf document instead.
> {code:java}
> ...
>
> maven-changelog-plugin
>
> ...
> html/pdf/rtf
> ...
>
>
> ...{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (MPMD-397) Upgrade to Maven 3.6.3
[ https://issues.apache.org/jira/browse/MPMD-397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed MPMD-397. --- Resolution: Fixed Fixed with [872fcd87d292abe9a28774201840651f98233142|https://gitbox.apache.org/repos/asf?p=maven-pmd-plugin.git=commit=872fcd87d292abe9a28774201840651f98233142]. > Upgrade to Maven 3.6.3 > -- > > Key: MPMD-397 > URL: https://issues.apache.org/jira/browse/MPMD-397 > Project: Maven PMD Plugin > Issue Type: Dependency upgrade >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: 3.23.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (SUREFIRE-2248) Make "type" attribute on failures and errors in (surefire|failsafe)-test-report schema optional
[
https://issues.apache.org/jira/browse/SUREFIRE-2248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated SUREFIRE-2248:
-
Summary: Make "type" attribute on failures and errors in
(surefire|failsafe)-test-report schema optional (was: Make "type" attribute on
failures and errors in surefire-test-report schema optional)
> Make "type" attribute on failures and errors in
> (surefire|failsafe)-test-report schema optional
> ---
>
> Key: SUREFIRE-2248
> URL: https://issues.apache.org/jira/browse/SUREFIRE-2248
> Project: Maven Surefire
> Issue Type: Improvement
> Components: Maven Surefire Plugin
>Affects Versions: 3.2.5
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 3.3.0
>
>
> There are situations where a stack trace is not always available, in fact,
> the code path {{StatelessXmlReporter}} is structured in a way that it can
> lead to an empty/missing {{type}} from a stack trace. This would require to
> write a blank or a bogus value to satisfy the schema. This does not make
> sense. We should make this optional to better accommodate reality. See
> SUREFIRE-2232 for details.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (SUREFIRE-1939) Build fails if java.home has <=2 path components
[
https://issues.apache.org/jira/browse/SUREFIRE-1939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed SUREFIRE-1939.
Resolution: Fixed
Fixed with
[9a43d063f755a3fb2e300668f1cd5aac27019205|https://gitbox.apache.org/repos/asf?p=maven-surefire.git;a=commit;h=9a43d063f755a3fb2e300668f1cd5aac27019205].
> Build fails if java.home has <=2 path components
>
>
> Key: SUREFIRE-1939
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1939
> Project: Maven Surefire
> Issue Type: Bug
> Environment: Gentoo Linux openjdk-bin-11.0.11_p9
>Reporter: Ciprian Ciubotariu
>Assignee: Michael Osipov
>Priority: Trivial
> Fix For: 3.3.0
>
>
> For {{JAVA_HOME=/opt/openjdk-bin-11.0.11_p9}},
> {{SystemUtilsTest.PlainUnitTests.incorrectJdkPath()}} throws a NPE at
> {{SystemUtils.toJdkHomeFromJvmExec(SystemUtils.java:91)}}.
> Trivial fix will follow soon
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MNG-8145) GOAWAY received
[
https://issues.apache.org/jira/browse/MNG-8145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17852666#comment-17852666
]
Michael Osipov commented on MNG-8145:
-
>From my PoV, we are out of control on low level issues unless what [~cstamas]
>has written
> GOAWAY received
>
>
> Key: MNG-8145
> URL: https://issues.apache.org/jira/browse/MNG-8145
> Project: Maven
> Issue Type: Bug
> Components: Artifacts and Repositories
>Affects Versions: 4.0.0-beta-3
>Reporter: Filipe Roque
>Priority: Major
>
> When using a repository mirror with an nginx reverse proxy, HTTP/2 connection
> may fail due to reaching
> [keepalive_requests:|http://nginx.org/en/docs/http/ngx_http_core_module.html#keepalive_requests]
> {code:java}
> [ERROR] Failed to execute goal
> org.apache.felix:maven-bundle-plugin:5.1.9:manifest (bundle-manifest) on
> project commons-io: Execution bundle-manifest of goal
> org.apache.felix:maven-bundle-plugin:5.1.9:manifest failed: Plugin
> org.apache.felix:maven-bundle-plugin:5.1.9 or one of its dependencies could
> not be resolved: Failed to collect dependencies at
> org.apache.felix:maven-bundle-plugin:jar:5.1.9 ->
> org.apache.maven:maven-archiver:jar:3.5.2: Failed to read artifact descriptor
> for org.slf4j:slf4j-api:jar:1.7.25: The following artifacts could not be
> resolved: org.slf4j:slf4j-api:pom:1.7.25 (absent): Could not transfer
> artifact org.slf4j:slf4j-api:pom:1.7.25 from/to maven-localrepository1
> (https://localhost:8443/central): /127.0.0.1:42086: GOAWAY received -> [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 verbose output
> [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/PluginResolutionException
> {code}
>
> This can be reproduced with:
> {code:bash}
> git clone --quiet --branch rel/commons-io-2.16.1
> g...@github.com:apache/commons-io.git && cd commons-io
> # builds OK without mirror and empty local repository
> TEMP_M2=$(mktemp -d)
> echo $TEMP_M2
> cat >$TEMP_M2/empty_settings.xml <
> http://maven.apache.org/SETTINGS/1.0.0;
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
> xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0
> http://maven.apache.org/xsd/settings-1.0.0.xsd;>
>
> EOF
> /opt/maven/apache-maven-4.0.0-beta-3/bin/mvn -s $TEMP_M2/empty_settings.xml
> -Dmaven.repo.local=$TEMP_M2 -q clean verify -DskipTests
> # prepare a nginx mirror
> mkdir -p /tmp/docker-ssl-proxy/
> openssl req -subj '/CN=localhost' -x509 -newkey rsa:4096 -nodes -keyout
> /tmp/docker-ssl-proxy/key.pem -out /tmp/docker-ssl-proxy/cert.pem -days 365
> cat >/tmp/docker-ssl-proxy/default.conf < server {
> listen 443 ssl;
> http2 on;
> # lower default value of 1000 for easier demonstration
> keepalive_requests 500;
> ssl_certificate /etc/nginx/conf.d/cert.pem;
> ssl_certificate_key /etc/nginx/conf.d/key.pem;
> location /central {
> proxy_pass https://repo.maven.apache.org/maven2;
> }
> }
> EOF
> docker run -d --rm \
> --name my-custom-nginx-container \
> -p 8443:443 \
> -v /tmp/docker-ssl-proxy/:/etc/nginx/conf.d/ \
> nginx:1.27.0
> cp /etc/ssl/certs/adoptium/cacerts /tmp/docker-ssl-proxy/mykeystore.jks
> keytool \
> -keystore /tmp/docker-ssl-proxy/mykeystore.jks \
> -storepass changeit \
> -importcert \
> -alias SITENAME \
> -trustcacerts \
> -file /tmp/docker-ssl-proxy/cert.pem
> TEMP_M2=$(mktemp -d)
> echo $TEMP_M2
> cat >$TEMP_M2/mirror_settings.xml <
> http://maven.apache.org/SETTINGS/1.0.0;
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
> xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0
> http://maven.apache.org/xsd/settings-1.0.0.xsd;>
>
>
> maven-localrepository1
> central
> https://localhost:8443/central
>
>
>
> EOF
> export
> MAVEN_OPTS='-Djavax.net.ssl.trustStore=/tmp/docker-ssl-proxy/mykeystore.jks
> -Djavax.net.ssl.trustStorePassword=changeit'
> /opt/maven/apache-maven-4.0.0-beta-3/bin/mvn -s $TEMP_M2/mirror_settings.xml
> -Dmaven.repo.local=$TEMP_M2 -q clean verify -DskipTests {code}
>
> Does not happen with, which only use HTTP/1.1
> {code:java}
> /opt/maven/apache-maven-3.9.7/bin/mvn -s $TEMP_M2/mirror_settings.xml
> -Dmaven.repo.local=$TEMP_M2 -q clean verify -DskipTests
> /opt/maven/apache-maven-4.0.0-beta-3/bin/mvn -s $TEMP_M2/mirror_settings.xml
> -Dmaven.repo.local=$TEMP_M2 -Dmaven.resolver.transport=apache -q clean verify
> -DskipTests
> /opt/maven/apache-maven-4.0.0-beta-3/bin/mvn -s $TEMP_M2/mirror_settings.xml
> -Dmaven.repo.local=$TEMP_M2 -Dmaven.resolver.transport=wagon -q clean verify
> -DskipTests
>
[jira] [Updated] (MDEP-933) Document new output format: JSON of dependency:tree
[ https://issues.apache.org/jira/browse/MDEP-933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MDEP-933: Fix Version/s: (was: 3.7.0) > Document new output format: JSON of dependency:tree > --- > > Key: MDEP-933 > URL: https://issues.apache.org/jira/browse/MDEP-933 > Project: Maven Dependency Plugin > Issue Type: Improvement > Components: tree >Reporter: Slawomir Jaranowski >Priority: Major > > We add new output format for dependency:tree but we are lack of documentation > We should add to Mojo description: > [https://maven.apache.org/plugins/maven-dependency-plugin/tree-mojo.html] > and to parameter > [https://maven.apache.org/plugins/maven-dependency-plugin/tree-mojo.html#outputType] > I would to see an example page with format description. > In other case it will be complicated to use new feature. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MDEP-933) Document new output format: JSON of dependency:tree
[ https://issues.apache.org/jira/browse/MDEP-933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17852573#comment-17852573 ] Michael Osipov commented on MDEP-933: - We also lack documentation for the other formats... > Document new output format: JSON of dependency:tree > --- > > Key: MDEP-933 > URL: https://issues.apache.org/jira/browse/MDEP-933 > Project: Maven Dependency Plugin > Issue Type: Improvement > Components: tree >Reporter: Slawomir Jaranowski >Priority: Major > Fix For: 3.7.0 > > > We add new output format for dependency:tree but we are lack of documentation > We should add to Mojo description: > [https://maven.apache.org/plugins/maven-dependency-plugin/tree-mojo.html] > and to parameter > [https://maven.apache.org/plugins/maven-dependency-plugin/tree-mojo.html#outputType] > I would to see an example page with format description. > In other case it will be complicated to use new feature. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MDEP-933) Document new output format: JSON of dependency:tree
[ https://issues.apache.org/jira/browse/MDEP-933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MDEP-933: Summary: Document new output format: JSON of dependency:tree (was: Documents new output format - JSON of dependency:tree) > Document new output format: JSON of dependency:tree > --- > > Key: MDEP-933 > URL: https://issues.apache.org/jira/browse/MDEP-933 > Project: Maven Dependency Plugin > Issue Type: Improvement > Components: tree >Reporter: Slawomir Jaranowski >Priority: Major > Fix For: 3.7.0 > > > We add new output format for dependency:tree but we are lack of documentation > We should add to Mojo description: > [https://maven.apache.org/plugins/maven-dependency-plugin/tree-mojo.html] > and to parameter > [https://maven.apache.org/plugins/maven-dependency-plugin/tree-mojo.html#outputType] > I would to see an example page with format description. > In other case it will be complicated to use new feature. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MDEP-576) maven-dependency-plugin ignores class of object passed as a parameter to method references
[
https://issues.apache.org/jira/browse/MDEP-576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MDEP-576:
Fix Version/s: (was: 3.7.0)
> maven-dependency-plugin ignores class of object passed as a parameter to
> method references
> --
>
> Key: MDEP-576
> URL: https://issues.apache.org/jira/browse/MDEP-576
> Project: Maven Dependency Plugin
> Issue Type: Bug
>Affects Versions: 3.0.1
>Reporter: Vladimir Dergachev
>Priority: Minor
>
> Hi there, i created a project on
> [github|https://github.com/vdergachev/dependency-plugin-vs-java-lambda] that
> can help you to reproduce the issue. Just clone it and make {code}mvn clean
> install{code}
> In my case plugin ignored Server class from jetty-server.jar and a as result
> i got message {code}Unused declared dependencies found{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] (MDEP-900) dependency:resolve fails for multi-module project
[ https://issues.apache.org/jira/browse/MDEP-900 ]
Michael Osipov deleted comment on MDEP-900:
-
was (Author: michael-o):
I don't consider this as a bug because the module aren't part of the reactor
because no lifecycle is being involved, but only a direct goal. It would likely
require -- at least -- to fork the compile phase
> dependency:resolve fails for multi-module project
> -
>
> Key: MDEP-900
> URL: https://issues.apache.org/jira/browse/MDEP-900
> Project: Maven Dependency Plugin
> Issue Type: Bug
> Components: resolve
>Affects Versions: 3.6.1
>Reporter: Gerd Aschemann
>Assignee: Slawomir Jaranowski
>Priority: Critical
> Fix For: 3.7.0
>
>
> When executing {{mvn dependency:resolve}} on a multi-module project it fails
> to retrieve artifacts for the modules themselves (which is not necessary as
> these can be installed by {{mvn install}} any time).
> This can be seen on an [OSS multi-module
> project|https://github.com/WASdev/sample.daytrader7]:
> {code:java}
> mvn dependency:resolve
> [INFO] Scanning for projects...
> [INFO]
>
> [INFO] Reactor Build Order:
> [INFO]
> [INFO] WAS Liberty Sample - Java EE7 Benchmark Sample - EJB Module
> [jar]
> [INFO] WAS Liberty Sample - Java EE7 Benchmark Sample - Web Module
> [war]
> [INFO] WAS Liberty Sample - Java EE7 Benchmark Sample
> [pom]
> [INFO] WAS Liberty Sample - Java EE7 Benchmark Sample - EAR
> [ear]
> [INFO]
> [INFO] --< net.wasdev.wlp.sample:daytrader-ee7-ejb
> >---
> [INFO] Building WAS Liberty Sample - Java EE7 Benchmark Sample - EJB Module
> 1.0-SNAPSHOT [1/4]
> [INFO] from daytrader-ee7-ejb/pom.xml
> [INFO] [ jar
> ]-
> [INFO]
> [INFO] --- dependency:3.6.0:resolve (default-cli) @ daytrader-ee7-ejb ---
> [INFO]
> [INFO] The following files have been resolved:
> [INFO] javax:javaee-api:jar:7.0:provided -- module javaee.api (auto)
> [INFO] com.sun.mail:javax.mail:jar:1.5.0:provided -- module javax.mail
> (auto)
> [INFO] javax.activation:activation:jar:1.1:provided -- module activation
> (auto)
> [INFO] javax.annotation:javax.annotation-api:jar:1.3.2:provided -- module
> java.annotation [auto]
> [INFO]
> [INFO]
> [INFO] --< net.wasdev.wlp.sample:daytrader-ee7-web
> >---
> [INFO] Building WAS Liberty Sample - Java EE7 Benchmark Sample - Web Module
> 1.0-SNAPSHOT [2/4]
> [INFO] from daytrader-ee7-web/pom.xml
> [INFO] [ war
> ]-
> [INFO]
>
> [INFO] Reactor Summary for WAS Liberty Sample - Java EE7 Benchmark Sample
> 1.0-SNAPSHOT:
> [INFO]
> [INFO] WAS Liberty Sample - Java EE7 Benchmark Sample - EJB Module SUCCESS [
> 0.402 s]
> [INFO] WAS Liberty Sample - Java EE7 Benchmark Sample - Web Module FAILURE [
> 0.012 s]
> [INFO] WAS Liberty Sample - Java EE7 Benchmark Sample . SKIPPED
> [INFO] WAS Liberty Sample - Java EE7 Benchmark Sample - EAR SKIPPED
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 0.552 s
> [INFO] Finished at: 2023-11-14T12:37:02+01:00
> [INFO]
>
> [ERROR] Failed to execute goal on project daytrader-ee7-web: Could not
> resolve dependencies for project
> net.wasdev.wlp.sample:daytrader-ee7-web:war:1.0-SNAPSHOT: The following
> artifacts could not be resolved:
> net.wasdev.wlp.sample:daytrader-ee7-ejb:jar:1.0-SNAPSHOT (absent): Could not
> find artifact net.wasdev.wlp.sample:daytrader-ee7-ejb:jar:1.0-SNAPSHOT ->
> [Help 1]{code}
> This is similar to the behaviour of MDEP-409, and MDEP-895
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MDEP-900) dependency:resolve fails for multi-module project
[
https://issues.apache.org/jira/browse/MDEP-900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17852566#comment-17852566
]
Michael Osipov commented on MDEP-900:
-
I don't consider this as a bug because the module aren't part of the reactor
because no lifecycle is being involved, but only a direct goal. It would likely
require -- at least -- to fork the compile phase
> dependency:resolve fails for multi-module project
> -
>
> Key: MDEP-900
> URL: https://issues.apache.org/jira/browse/MDEP-900
> Project: Maven Dependency Plugin
> Issue Type: Bug
> Components: resolve
>Affects Versions: 3.6.1
>Reporter: Gerd Aschemann
>Assignee: Slawomir Jaranowski
>Priority: Critical
> Fix For: 3.7.0
>
>
> When executing {{mvn dependency:resolve}} on a multi-module project it fails
> to retrieve artifacts for the modules themselves (which is not necessary as
> these can be installed by {{mvn install}} any time).
> This can be seen on an [OSS multi-module
> project|https://github.com/WASdev/sample.daytrader7]:
> {code:java}
> mvn dependency:resolve
> [INFO] Scanning for projects...
> [INFO]
>
> [INFO] Reactor Build Order:
> [INFO]
> [INFO] WAS Liberty Sample - Java EE7 Benchmark Sample - EJB Module
> [jar]
> [INFO] WAS Liberty Sample - Java EE7 Benchmark Sample - Web Module
> [war]
> [INFO] WAS Liberty Sample - Java EE7 Benchmark Sample
> [pom]
> [INFO] WAS Liberty Sample - Java EE7 Benchmark Sample - EAR
> [ear]
> [INFO]
> [INFO] --< net.wasdev.wlp.sample:daytrader-ee7-ejb
> >---
> [INFO] Building WAS Liberty Sample - Java EE7 Benchmark Sample - EJB Module
> 1.0-SNAPSHOT [1/4]
> [INFO] from daytrader-ee7-ejb/pom.xml
> [INFO] [ jar
> ]-
> [INFO]
> [INFO] --- dependency:3.6.0:resolve (default-cli) @ daytrader-ee7-ejb ---
> [INFO]
> [INFO] The following files have been resolved:
> [INFO] javax:javaee-api:jar:7.0:provided -- module javaee.api (auto)
> [INFO] com.sun.mail:javax.mail:jar:1.5.0:provided -- module javax.mail
> (auto)
> [INFO] javax.activation:activation:jar:1.1:provided -- module activation
> (auto)
> [INFO] javax.annotation:javax.annotation-api:jar:1.3.2:provided -- module
> java.annotation [auto]
> [INFO]
> [INFO]
> [INFO] --< net.wasdev.wlp.sample:daytrader-ee7-web
> >---
> [INFO] Building WAS Liberty Sample - Java EE7 Benchmark Sample - Web Module
> 1.0-SNAPSHOT [2/4]
> [INFO] from daytrader-ee7-web/pom.xml
> [INFO] [ war
> ]-
> [INFO]
>
> [INFO] Reactor Summary for WAS Liberty Sample - Java EE7 Benchmark Sample
> 1.0-SNAPSHOT:
> [INFO]
> [INFO] WAS Liberty Sample - Java EE7 Benchmark Sample - EJB Module SUCCESS [
> 0.402 s]
> [INFO] WAS Liberty Sample - Java EE7 Benchmark Sample - Web Module FAILURE [
> 0.012 s]
> [INFO] WAS Liberty Sample - Java EE7 Benchmark Sample . SKIPPED
> [INFO] WAS Liberty Sample - Java EE7 Benchmark Sample - EAR SKIPPED
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 0.552 s
> [INFO] Finished at: 2023-11-14T12:37:02+01:00
> [INFO]
>
> [ERROR] Failed to execute goal on project daytrader-ee7-web: Could not
> resolve dependencies for project
> net.wasdev.wlp.sample:daytrader-ee7-web:war:1.0-SNAPSHOT: The following
> artifacts could not be resolved:
> net.wasdev.wlp.sample:daytrader-ee7-ejb:jar:1.0-SNAPSHOT (absent): Could not
> find artifact net.wasdev.wlp.sample:daytrader-ee7-ejb:jar:1.0-SNAPSHOT ->
> [Help 1]{code}
> This is similar to the behaviour of MDEP-409, and MDEP-895
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MDEP-900) dependency:resolve fails for multi-module project
[
https://issues.apache.org/jira/browse/MDEP-900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MDEP-900:
Description:
When executing {{mvn dependency:resolve}} on a multi-module project it fails to
retrieve artifacts for the modules themselves (which is not necessary as these
can be installed by {{mvn install}} any time).
This can be seen on an [OSS multi-module
project|https://github.com/WASdev/sample.daytrader7]:
{code:java}
mvn dependency:resolve
[INFO] Scanning for projects...
[INFO]
[INFO] Reactor Build Order:
[INFO]
[INFO] WAS Liberty Sample - Java EE7 Benchmark Sample - EJB Module [jar]
[INFO] WAS Liberty Sample - Java EE7 Benchmark Sample - Web Module [war]
[INFO] WAS Liberty Sample - Java EE7 Benchmark Sample [pom]
[INFO] WAS Liberty Sample - Java EE7 Benchmark Sample - EAR [ear]
[INFO]
[INFO] --< net.wasdev.wlp.sample:daytrader-ee7-ejb >---
[INFO] Building WAS Liberty Sample - Java EE7 Benchmark Sample - EJB Module
1.0-SNAPSHOT [1/4]
[INFO] from daytrader-ee7-ejb/pom.xml
[INFO] [ jar ]-
[INFO]
[INFO] --- dependency:3.6.0:resolve (default-cli) @ daytrader-ee7-ejb ---
[INFO]
[INFO] The following files have been resolved:
[INFO] javax:javaee-api:jar:7.0:provided -- module javaee.api (auto)
[INFO] com.sun.mail:javax.mail:jar:1.5.0:provided -- module javax.mail (auto)
[INFO] javax.activation:activation:jar:1.1:provided -- module activation
(auto)
[INFO] javax.annotation:javax.annotation-api:jar:1.3.2:provided -- module
java.annotation [auto]
[INFO]
[INFO]
[INFO] --< net.wasdev.wlp.sample:daytrader-ee7-web >---
[INFO] Building WAS Liberty Sample - Java EE7 Benchmark Sample - Web Module
1.0-SNAPSHOT [2/4]
[INFO] from daytrader-ee7-web/pom.xml
[INFO] [ war ]-
[INFO]
[INFO] Reactor Summary for WAS Liberty Sample - Java EE7 Benchmark Sample
1.0-SNAPSHOT:
[INFO]
[INFO] WAS Liberty Sample - Java EE7 Benchmark Sample - EJB Module SUCCESS [
0.402 s]
[INFO] WAS Liberty Sample - Java EE7 Benchmark Sample - Web Module FAILURE [
0.012 s]
[INFO] WAS Liberty Sample - Java EE7 Benchmark Sample . SKIPPED
[INFO] WAS Liberty Sample - Java EE7 Benchmark Sample - EAR SKIPPED
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 0.552 s
[INFO] Finished at: 2023-11-14T12:37:02+01:00
[INFO]
[ERROR] Failed to execute goal on project daytrader-ee7-web: Could not resolve
dependencies for project
net.wasdev.wlp.sample:daytrader-ee7-web:war:1.0-SNAPSHOT: The following
artifacts could not be resolved:
net.wasdev.wlp.sample:daytrader-ee7-ejb:jar:1.0-SNAPSHOT (absent): Could not
find artifact net.wasdev.wlp.sample:daytrader-ee7-ejb:jar:1.0-SNAPSHOT -> [Help
1]{code}
This is similar to the behaviour of MDEP-409, and MDEP-895
was:
When executing `mvn dependency:resolve` on a multi-module project it fails to
retrieve artifacts for the modules themselves (which is not necessary as these
can be installed by `mvn install` any time).
This can be seen on an [OSS multi-module
project|https://github.com/WASdev/sample.daytrader7]:
{code:java}
mvn dependency:resolve
[INFO] Scanning for projects...
[INFO]
[INFO] Reactor Build Order:
[INFO]
[INFO] WAS Liberty Sample - Java EE7 Benchmark Sample - EJB Module [jar]
[INFO] WAS Liberty Sample - Java EE7 Benchmark Sample - Web Module [war]
[INFO] WAS Liberty Sample - Java EE7 Benchmark Sample [pom]
[INFO] WAS Liberty Sample - Java EE7 Benchmark Sample - EAR [ear]
[INFO]
[INFO] --< net.wasdev.wlp.sample:daytrader-ee7-ejb >---
[INFO] Building WAS Liberty Sample - Java EE7 Benchmark Sample - EJB Module
1.0-SNAPSHOT [1/4]
[INFO] from daytrader-ee7-ejb/pom.xml
[INFO] [ jar ]-
[INFO]
[INFO] --- dependency:3.6.0:resolve (default-cli) @ daytrader-ee7-ejb ---
[INFO]
[INFO] The following files have been resolved:
[INFO] javax:javaee-api:jar:7.0:provided -- module javaee.api (auto)
[INFO] com.sun.mail:javax.mail:jar:1.5.0:provided -- module javax.mail (auto)
[INFO] javax.activation:activation:jar:1.1:provided -- module activation
(auto)
[INFO] javax.annotation:javax.annotation-api:jar:1.3.2:provided -- module
java.annotation [auto]
[INFO]
[INFO]
[INFO] --<
[jira] [Created] (SUREFIRE-2248) Make "type" attribute on failures and errors in surefire-test-report schema optional
Michael Osipov created SUREFIRE-2248:
Summary: Make "type" attribute on failures and errors in
surefire-test-report schema optional
Key: SUREFIRE-2248
URL: https://issues.apache.org/jira/browse/SUREFIRE-2248
Project: Maven Surefire
Issue Type: Improvement
Components: Maven Surefire Plugin
Affects Versions: 3.2.5
Reporter: Michael Osipov
Assignee: Michael Osipov
Fix For: 3.3.0
There are situations where a stack trace is not always available, in fact, the
code path {{StatelessXmlReporter}} is structured in a way that it can lead to
an empty/missing {{type}} from a stack trace. This would require to write a
blank or a bogus value to satisfy the schema. This does not make sense. We
should make this optional to better accommodate reality. See SUREFIRE-2232 for
details.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MSITE-1010) site-deployment for POM projects does not create project folders in site-repository
[
https://issues.apache.org/jira/browse/MSITE-1010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17852496#comment-17852496
]
Michael Osipov commented on MSITE-1010:
---
Are you able to create a sample project for me? I'd take a look.
> site-deployment for POM projects does not create project folders in
> site-repository
> ---
>
> Key: MSITE-1010
> URL: https://issues.apache.org/jira/browse/MSITE-1010
> Project: Maven Site Plugin
> Issue Type: Bug
> Components: site:deploy
>Affects Versions: 3.12.0, 4.0.0-M14
> Environment: Nexus, since at least Maven 3.6.3 (not tested with 3.9.7
> or 4.0.0-beta)
>Reporter: Matthias Bünger
>Priority: Minor
>
> I noticed the following issue while updating the plugins in our teams
> META-POM and could backtrack it at least until 3.12 but might be an even
> older issue. Havn't checked 4.0.0-M15 but from the releases notes I doubt it
> is fixed.
> When you do "site-deploy" for a single module or multi module project the
> site files (.html, css-folders, etc.) are stored in the site-repository (we
> have current Nexus version) within a subfolder with the name of the project,
> e.g
> {code}
> / (root of site-repository)
> /- project-A
>/css
>report.html
> /- project-B
>/css
>report.html
> /project-C
> {code}
> If you do the same for a "POM" project (e.g. a META-POM or BOM) the site
> files are all stored at root level (instead of creating a project folder) and
> ofc overwriting the ones from other POM-projects:
> {code}
> / (root of site-repository)
> /css
> /project-A
> /project-B
> /project-C
> report.html
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MSITE-1010) site-deployment for POM projects does not create project folders in site-repository
[
https://issues.apache.org/jira/browse/MSITE-1010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MSITE-1010:
--
Fix Version/s: waiting-for-feedback
> site-deployment for POM projects does not create project folders in
> site-repository
> ---
>
> Key: MSITE-1010
> URL: https://issues.apache.org/jira/browse/MSITE-1010
> Project: Maven Site Plugin
> Issue Type: Bug
> Components: site:deploy
>Affects Versions: 3.12.0, 4.0.0-M14
> Environment: Nexus, since at least Maven 3.6.3 (not tested with 3.9.7
> or 4.0.0-beta)
>Reporter: Matthias Bünger
>Priority: Minor
> Fix For: waiting-for-feedback
>
>
> I noticed the following issue while updating the plugins in our teams
> META-POM and could backtrack it at least until 3.12 but might be an even
> older issue. Havn't checked 4.0.0-M15 but from the releases notes I doubt it
> is fixed.
> When you do "site-deploy" for a single module or multi module project the
> site files (.html, css-folders, etc.) are stored in the site-repository (we
> have current Nexus version) within a subfolder with the name of the project,
> e.g
> {code}
> / (root of site-repository)
> /- project-A
>/css
>report.html
> /- project-B
>/css
>report.html
> /project-C
> {code}
> If you do the same for a "POM" project (e.g. a META-POM or BOM) the site
> files are all stored at root level (instead of creating a project folder) and
> ofc overwriting the ones from other POM-projects:
> {code}
> / (root of site-repository)
> /css
> /project-A
> /project-B
> /project-C
> report.html
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (SUREFIRE-2232) [REGRESSION] StatelessXmlReporter fails to process failed result without a throwable
[
https://issues.apache.org/jira/browse/SUREFIRE-2232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated SUREFIRE-2232:
-
Affects Version/s: 3.2.5
> [REGRESSION] StatelessXmlReporter fails to process failed result without a
> throwable
>
>
> Key: SUREFIRE-2232
> URL: https://issues.apache.org/jira/browse/SUREFIRE-2232
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
>Affects Versions: 3.0.0-M6, 3.2.3, 3.2.5
>Reporter: Artem Yak
>Assignee: Michael Osipov
>Priority: Minor
> Fix For: 3.3.0
>
>
>
> A regression bug appeared in 3.0.0-M6:
> A testNG test class has a listener which updates results from SUCCESS to
> FAILURE:
>
> {noformat}
> @Override
> public void onTestSuccess(ITestResult result) {
> result.setStatus(ITestResult.FAILURE);
> result.getTestContext().getPassedTests().removeResult(result);
> result.getTestContext().getFailedTests().addResult(result);
> }{noformat}
>
> Surefire fails to process a failed test result without a throwable and
> reports 0 total tests.
> {code:java}
> ForkStarter IOException: java.util.NoSuchElementException.
> org.apache.maven.plugin.surefire.booterclient.output.MultipleFailureException:
> java.util.NoSuchElementException
> at
> org.apache.maven.plugin.surefire.booterclient.output.ThreadedStreamConsumer$Pumper.(ThreadedStreamConsumer.java:59)
> at
> org.apache.maven.plugin.surefire.booterclient.output.ThreadedStreamConsumer.(ThreadedStreamConsumer.java:107)
> at
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:546)
> at
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:285)
> at
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:250)
> {code}
>
> Reproducible unit test.
> {code:java}
> package org.apache.maven.plugin.surefire.report;
> import java.io.File;
> import java.util.HashMap;
> import java.util.concurrent.atomic.AtomicInteger;
> import junit.framework.TestCase;
> import
> org.apache.maven.plugin.surefire.booterclient.output.DeserializedStacktraceWriter;
> import org.apache.maven.surefire.api.report.SimpleReportEntry;
> import org.apache.maven.surefire.api.report.StackTraceWriter;
> import static org.apache.maven.plugin.surefire.report.ReportEntryType.ERROR;
> import static org.apache.maven.surefire.api.report.RunMode.NORMAL_RUN;
> @SuppressWarnings({"ResultOfMethodCallIgnored", "checkstyle:magicnumber"})
> public class StatelessXmlReporter2Test extends TestCase {
> private static final String XSD =
>
> "https://maven.apache.org/surefire/maven-surefire-plugin/xsd/surefire-test-report-3.0.xsd;;
> private static final AtomicInteger FOLDER_POSTFIX = new AtomicInteger();
> private File reportDir;
> @Override
> protected void setUp() throws Exception {
> File basedir = new File(".");
> File target = new File(basedir.getCanonicalFile(), "target");
> target.mkdir();
> String reportRelDir = getClass().getSimpleName() + "-" +
> FOLDER_POSTFIX.incrementAndGet();
> reportDir = new File(target, reportRelDir);
> reportDir.mkdir();
> }
> @Override
> protected void tearDown() {
> }
> public void testOutputFailedTestWithoutThrowable() {
> StackTraceWriter stackTraceWriterOne = new
> DeserializedStacktraceWriter(null, null, "");
> WrappedReportEntry testReport = new WrappedReportEntry(
> new SimpleReportEntry(
> NORMAL_RUN, 1L, getClass().getName(), null, "a test name",
> null, stackTraceWriterOne, 5),
> ERROR,
> 5,
> null,
> null);
> TestSetStats testSetStats = new TestSetStats(false, false);
> testSetStats.testError(testReport);
> StatelessXmlReporter reporter = new StatelessXmlReporter(
> reportDir, null, false, 1, new HashMap<>(), XSD, "3.0", false,
> false, false, false);
> reporter.testSetCompleted(testReport, testSetStats);
> }
> } {code}
>
>
>
> {code:java}
> java.util.NoSuchElementException
> at java.base/java.util.StringTokenizer.nextToken(StringTokenizer.java:349)
> at
> org.apache.maven.plugin.surefire.report.StatelessXmlReporter.getTestProblems(StatelessXmlReporter.java:454)
> at
> org.apache.maven.plugin.surefire.report.StatelessXmlReporter.serializeTestClassWithRerun(StatelessXmlReporter.java:256)
> at
> org.apache.maven.plugin.surefire.report.StatelessXmlReporter.serializeTestClass(StatelessXmlReporter.java:207)
> at
> org.apache.maven.plugin.surefire.report.StatelessXmlReporter.testSetCompleted(StatelessXmlReporter.java:161)
>
[jira] [Updated] (SUREFIRE-2232) [REGRESSION] StatelessXmlReporter fails to process failed result without a throwable
[
https://issues.apache.org/jira/browse/SUREFIRE-2232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated SUREFIRE-2232:
-
Summary: [REGRESSION] StatelessXmlReporter fails to process failed result
without a throwable (was: StatelessXmlReporter fails to process failed result
without a throwable)
> [REGRESSION] StatelessXmlReporter fails to process failed result without a
> throwable
>
>
> Key: SUREFIRE-2232
> URL: https://issues.apache.org/jira/browse/SUREFIRE-2232
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
>Affects Versions: 3.0.0-M6, 3.2.3
>Reporter: Artem Yak
>Assignee: Michael Osipov
>Priority: Minor
> Fix For: 3.3.0
>
>
>
> A regression bug appeared in 3.0.0-M6:
> A testNG test class has a listener which updates results from SUCCESS to
> FAILURE:
>
> {noformat}
> @Override
> public void onTestSuccess(ITestResult result) {
> result.setStatus(ITestResult.FAILURE);
> result.getTestContext().getPassedTests().removeResult(result);
> result.getTestContext().getFailedTests().addResult(result);
> }{noformat}
>
> Surefire fails to process a failed test result without a throwable and
> reports 0 total tests.
> {code:java}
> ForkStarter IOException: java.util.NoSuchElementException.
> org.apache.maven.plugin.surefire.booterclient.output.MultipleFailureException:
> java.util.NoSuchElementException
> at
> org.apache.maven.plugin.surefire.booterclient.output.ThreadedStreamConsumer$Pumper.(ThreadedStreamConsumer.java:59)
> at
> org.apache.maven.plugin.surefire.booterclient.output.ThreadedStreamConsumer.(ThreadedStreamConsumer.java:107)
> at
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:546)
> at
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:285)
> at
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:250)
> {code}
>
> Reproducible unit test.
> {code:java}
> package org.apache.maven.plugin.surefire.report;
> import java.io.File;
> import java.util.HashMap;
> import java.util.concurrent.atomic.AtomicInteger;
> import junit.framework.TestCase;
> import
> org.apache.maven.plugin.surefire.booterclient.output.DeserializedStacktraceWriter;
> import org.apache.maven.surefire.api.report.SimpleReportEntry;
> import org.apache.maven.surefire.api.report.StackTraceWriter;
> import static org.apache.maven.plugin.surefire.report.ReportEntryType.ERROR;
> import static org.apache.maven.surefire.api.report.RunMode.NORMAL_RUN;
> @SuppressWarnings({"ResultOfMethodCallIgnored", "checkstyle:magicnumber"})
> public class StatelessXmlReporter2Test extends TestCase {
> private static final String XSD =
>
> "https://maven.apache.org/surefire/maven-surefire-plugin/xsd/surefire-test-report-3.0.xsd;;
> private static final AtomicInteger FOLDER_POSTFIX = new AtomicInteger();
> private File reportDir;
> @Override
> protected void setUp() throws Exception {
> File basedir = new File(".");
> File target = new File(basedir.getCanonicalFile(), "target");
> target.mkdir();
> String reportRelDir = getClass().getSimpleName() + "-" +
> FOLDER_POSTFIX.incrementAndGet();
> reportDir = new File(target, reportRelDir);
> reportDir.mkdir();
> }
> @Override
> protected void tearDown() {
> }
> public void testOutputFailedTestWithoutThrowable() {
> StackTraceWriter stackTraceWriterOne = new
> DeserializedStacktraceWriter(null, null, "");
> WrappedReportEntry testReport = new WrappedReportEntry(
> new SimpleReportEntry(
> NORMAL_RUN, 1L, getClass().getName(), null, "a test name",
> null, stackTraceWriterOne, 5),
> ERROR,
> 5,
> null,
> null);
> TestSetStats testSetStats = new TestSetStats(false, false);
> testSetStats.testError(testReport);
> StatelessXmlReporter reporter = new StatelessXmlReporter(
> reportDir, null, false, 1, new HashMap<>(), XSD, "3.0", false,
> false, false, false);
> reporter.testSetCompleted(testReport, testSetStats);
> }
> } {code}
>
>
>
> {code:java}
> java.util.NoSuchElementException
> at java.base/java.util.StringTokenizer.nextToken(StringTokenizer.java:349)
> at
> org.apache.maven.plugin.surefire.report.StatelessXmlReporter.getTestProblems(StatelessXmlReporter.java:454)
> at
> org.apache.maven.plugin.surefire.report.StatelessXmlReporter.serializeTestClassWithRerun(StatelessXmlReporter.java:256)
> at
>
[jira] [Assigned] (SUREFIRE-2232) StatelessXmlReporter fails to process failed result without a throwable
[
https://issues.apache.org/jira/browse/SUREFIRE-2232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov reassigned SUREFIRE-2232:
Assignee: Michael Osipov
> StatelessXmlReporter fails to process failed result without a throwable
> ---
>
> Key: SUREFIRE-2232
> URL: https://issues.apache.org/jira/browse/SUREFIRE-2232
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
>Affects Versions: 3.0.0-M6, 3.2.3
>Reporter: Artem Yak
>Assignee: Michael Osipov
>Priority: Minor
> Fix For: 3.3.0
>
>
>
> A regression bug appeared in 3.0.0-M6:
> A testNG test class has a listener which updates results from SUCCESS to
> FAILURE:
>
> {noformat}
> @Override
> public void onTestSuccess(ITestResult result) {
> result.setStatus(ITestResult.FAILURE);
> result.getTestContext().getPassedTests().removeResult(result);
> result.getTestContext().getFailedTests().addResult(result);
> }{noformat}
>
> Surefire fails to process a failed test result without a throwable and
> reports 0 total tests.
> {code:java}
> ForkStarter IOException: java.util.NoSuchElementException.
> org.apache.maven.plugin.surefire.booterclient.output.MultipleFailureException:
> java.util.NoSuchElementException
> at
> org.apache.maven.plugin.surefire.booterclient.output.ThreadedStreamConsumer$Pumper.(ThreadedStreamConsumer.java:59)
> at
> org.apache.maven.plugin.surefire.booterclient.output.ThreadedStreamConsumer.(ThreadedStreamConsumer.java:107)
> at
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:546)
> at
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:285)
> at
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:250)
> {code}
>
> Reproducible unit test.
> {code:java}
> package org.apache.maven.plugin.surefire.report;
> import java.io.File;
> import java.util.HashMap;
> import java.util.concurrent.atomic.AtomicInteger;
> import junit.framework.TestCase;
> import
> org.apache.maven.plugin.surefire.booterclient.output.DeserializedStacktraceWriter;
> import org.apache.maven.surefire.api.report.SimpleReportEntry;
> import org.apache.maven.surefire.api.report.StackTraceWriter;
> import static org.apache.maven.plugin.surefire.report.ReportEntryType.ERROR;
> import static org.apache.maven.surefire.api.report.RunMode.NORMAL_RUN;
> @SuppressWarnings({"ResultOfMethodCallIgnored", "checkstyle:magicnumber"})
> public class StatelessXmlReporter2Test extends TestCase {
> private static final String XSD =
>
> "https://maven.apache.org/surefire/maven-surefire-plugin/xsd/surefire-test-report-3.0.xsd;;
> private static final AtomicInteger FOLDER_POSTFIX = new AtomicInteger();
> private File reportDir;
> @Override
> protected void setUp() throws Exception {
> File basedir = new File(".");
> File target = new File(basedir.getCanonicalFile(), "target");
> target.mkdir();
> String reportRelDir = getClass().getSimpleName() + "-" +
> FOLDER_POSTFIX.incrementAndGet();
> reportDir = new File(target, reportRelDir);
> reportDir.mkdir();
> }
> @Override
> protected void tearDown() {
> }
> public void testOutputFailedTestWithoutThrowable() {
> StackTraceWriter stackTraceWriterOne = new
> DeserializedStacktraceWriter(null, null, "");
> WrappedReportEntry testReport = new WrappedReportEntry(
> new SimpleReportEntry(
> NORMAL_RUN, 1L, getClass().getName(), null, "a test name",
> null, stackTraceWriterOne, 5),
> ERROR,
> 5,
> null,
> null);
> TestSetStats testSetStats = new TestSetStats(false, false);
> testSetStats.testError(testReport);
> StatelessXmlReporter reporter = new StatelessXmlReporter(
> reportDir, null, false, 1, new HashMap<>(), XSD, "3.0", false,
> false, false, false);
> reporter.testSetCompleted(testReport, testSetStats);
> }
> } {code}
>
>
>
> {code:java}
> java.util.NoSuchElementException
> at java.base/java.util.StringTokenizer.nextToken(StringTokenizer.java:349)
> at
> org.apache.maven.plugin.surefire.report.StatelessXmlReporter.getTestProblems(StatelessXmlReporter.java:454)
> at
> org.apache.maven.plugin.surefire.report.StatelessXmlReporter.serializeTestClassWithRerun(StatelessXmlReporter.java:256)
> at
> org.apache.maven.plugin.surefire.report.StatelessXmlReporter.serializeTestClass(StatelessXmlReporter.java:207)
> at
> org.apache.maven.plugin.surefire.report.StatelessXmlReporter.testSetCompleted(StatelessXmlReporter.java:161)
> at
>
[jira] [Updated] (SUREFIRE-2232) StatelessXmlReporter fails to process failed result without a throwable
[
https://issues.apache.org/jira/browse/SUREFIRE-2232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated SUREFIRE-2232:
-
Fix Version/s: 3.3.0
(was: waiting-for-feedback)
> StatelessXmlReporter fails to process failed result without a throwable
> ---
>
> Key: SUREFIRE-2232
> URL: https://issues.apache.org/jira/browse/SUREFIRE-2232
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
>Affects Versions: 3.0.0-M6, 3.2.3
>Reporter: Artem Yak
>Priority: Minor
> Fix For: 3.3.0
>
>
>
> A regression bug appeared in 3.0.0-M6:
> A testNG test class has a listener which updates results from SUCCESS to
> FAILURE:
>
> {noformat}
> @Override
> public void onTestSuccess(ITestResult result) {
> result.setStatus(ITestResult.FAILURE);
> result.getTestContext().getPassedTests().removeResult(result);
> result.getTestContext().getFailedTests().addResult(result);
> }{noformat}
>
> Surefire fails to process a failed test result without a throwable and
> reports 0 total tests.
> {code:java}
> ForkStarter IOException: java.util.NoSuchElementException.
> org.apache.maven.plugin.surefire.booterclient.output.MultipleFailureException:
> java.util.NoSuchElementException
> at
> org.apache.maven.plugin.surefire.booterclient.output.ThreadedStreamConsumer$Pumper.(ThreadedStreamConsumer.java:59)
> at
> org.apache.maven.plugin.surefire.booterclient.output.ThreadedStreamConsumer.(ThreadedStreamConsumer.java:107)
> at
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:546)
> at
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:285)
> at
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:250)
> {code}
>
> Reproducible unit test.
> {code:java}
> package org.apache.maven.plugin.surefire.report;
> import java.io.File;
> import java.util.HashMap;
> import java.util.concurrent.atomic.AtomicInteger;
> import junit.framework.TestCase;
> import
> org.apache.maven.plugin.surefire.booterclient.output.DeserializedStacktraceWriter;
> import org.apache.maven.surefire.api.report.SimpleReportEntry;
> import org.apache.maven.surefire.api.report.StackTraceWriter;
> import static org.apache.maven.plugin.surefire.report.ReportEntryType.ERROR;
> import static org.apache.maven.surefire.api.report.RunMode.NORMAL_RUN;
> @SuppressWarnings({"ResultOfMethodCallIgnored", "checkstyle:magicnumber"})
> public class StatelessXmlReporter2Test extends TestCase {
> private static final String XSD =
>
> "https://maven.apache.org/surefire/maven-surefire-plugin/xsd/surefire-test-report-3.0.xsd;;
> private static final AtomicInteger FOLDER_POSTFIX = new AtomicInteger();
> private File reportDir;
> @Override
> protected void setUp() throws Exception {
> File basedir = new File(".");
> File target = new File(basedir.getCanonicalFile(), "target");
> target.mkdir();
> String reportRelDir = getClass().getSimpleName() + "-" +
> FOLDER_POSTFIX.incrementAndGet();
> reportDir = new File(target, reportRelDir);
> reportDir.mkdir();
> }
> @Override
> protected void tearDown() {
> }
> public void testOutputFailedTestWithoutThrowable() {
> StackTraceWriter stackTraceWriterOne = new
> DeserializedStacktraceWriter(null, null, "");
> WrappedReportEntry testReport = new WrappedReportEntry(
> new SimpleReportEntry(
> NORMAL_RUN, 1L, getClass().getName(), null, "a test name",
> null, stackTraceWriterOne, 5),
> ERROR,
> 5,
> null,
> null);
> TestSetStats testSetStats = new TestSetStats(false, false);
> testSetStats.testError(testReport);
> StatelessXmlReporter reporter = new StatelessXmlReporter(
> reportDir, null, false, 1, new HashMap<>(), XSD, "3.0", false,
> false, false, false);
> reporter.testSetCompleted(testReport, testSetStats);
> }
> } {code}
>
>
>
> {code:java}
> java.util.NoSuchElementException
> at java.base/java.util.StringTokenizer.nextToken(StringTokenizer.java:349)
> at
> org.apache.maven.plugin.surefire.report.StatelessXmlReporter.getTestProblems(StatelessXmlReporter.java:454)
> at
> org.apache.maven.plugin.surefire.report.StatelessXmlReporter.serializeTestClassWithRerun(StatelessXmlReporter.java:256)
> at
> org.apache.maven.plugin.surefire.report.StatelessXmlReporter.serializeTestClass(StatelessXmlReporter.java:207)
> at
> org.apache.maven.plugin.surefire.report.StatelessXmlReporter.testSetCompleted(StatelessXmlReporter.java:161)
> at
>
[jira] [Commented] (MJAVADOC-656) Following redirects breaks valid links
[ https://issues.apache.org/jira/browse/MJAVADOC-656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17852485#comment-17852485 ] Michael Osipov commented on MJAVADOC-656: - A global one, but I'd like to do this in steps. Our redirect handling is obsolete from Java 12+. I'd do this first, then fix for < Java 12. WDYT? > Following redirects breaks valid links > -- > > Key: MJAVADOC-656 > URL: https://issues.apache.org/jira/browse/MJAVADOC-656 > Project: Maven Javadoc Plugin > Issue Type: Bug >Affects Versions: 3.0.1, 3.2.0 >Reporter: Robert Važan >Priority: Minor > > Version 3.0.1 fixed #427 by following redirects. This feature unfortunately > breaks when HTTP server is configured as follows: > /apidocs/package-list -> 200 > /apidocs -> 301 /apidocs/com/example/package-summary.html > /apidocs/ -> 301 /apidocs/com/example/package-summary.html > /apidocs/com/example/package-summary.html -> 200 > Without following redirects (in version 3.0.0), the link is passed to javadoc > tool unchanged, the javadoc tool fetches /apidocs/package-list, and > everything works fine. Since 3.0.1, javadoc plugin follows one of the > redirects (/apidocs or /apidocs/), passes the package summary URL to javadoc > tool, which then fails like this: > [WARNING] javadoc: warning - Error fetching URL: > [https://example.com/apidocs/com/example/package-summary.html/] > And if you have failOnWarnings set to true, this will fail the whole build. > The solution is fairly simple. Construct the whole URL (.../package-list) and > follow redirects on that one. Then check whether the final destination ends > in /package-list, strip the /package-list suffix, and pass the result to the > javadoc tool. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MSHARED-1303) Declare and undeclare used and unused dependencies
[ https://issues.apache.org/jira/browse/MSHARED-1303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed MSHARED-1303. --- Resolution: Fixed Fixed implicitly with MSHARED-1301. > Declare and undeclare used and unused dependencies > -- > > Key: MSHARED-1303 > URL: https://issues.apache.org/jira/browse/MSHARED-1303 > Project: Maven Shared Components > Issue Type: Improvement > Components: maven-common-artifact-filters >Reporter: Elliotte Rusty Harold >Assignee: Michael Osipov >Priority: Minor > Fix For: maven-common-artifact-filters-3.4.0 > > > [WARNING] Used undeclared dependencies found: > [WARNING]org.eclipse.aether:aether-util:jar:1.0.0.v20140518:provided > [WARNING]org.eclipse.aether:aether-api:jar:1.0.0.v20140518:provided > [WARNING] Unused declared dependencies found: > [WARNING]org.apache.maven.resolver:maven-resolver-api:jar:1.6.3:provided > [WARNING]org.apache.maven.resolver:maven-resolver-util:jar:1.6.3:provided > [WARNING]org.openjdk.jmh:jmh-generator-annprocess:jar:1.35:test -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MSHARED-1301) Upgrade to Parent 42 and Maven 3.6.3
[ https://issues.apache.org/jira/browse/MSHARED-1301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed MSHARED-1301. --- Resolution: Fixed Fixed with [888d69aee331d183a5f1e6343246fbe2dd712965|https://gitbox.apache.org/repos/asf?p=maven-common-artifact-filters.git;a=commit;h=888d69aee331d183a5f1e6343246fbe2dd712965]. > Upgrade to Parent 42 and Maven 3.6.3 > > > Key: MSHARED-1301 > URL: https://issues.apache.org/jira/browse/MSHARED-1301 > Project: Maven Shared Components > Issue Type: Dependency upgrade > Components: maven-common-artifact-filters >Reporter: Elliotte Rusty Harold >Assignee: Michael Osipov >Priority: Major > Labels: up-for-grabs > Fix For: maven-common-artifact-filters-3.4.0 > > Attachments: maven_parent_poms.300.png > > > will require a spotless run -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (SUREFIRE-1939) Build fails if java.home has <=2 path components
[
https://issues.apache.org/jira/browse/SUREFIRE-1939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated SUREFIRE-1939:
-
Fix Version/s: 3.3.0
> Build fails if java.home has <=2 path components
>
>
> Key: SUREFIRE-1939
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1939
> Project: Maven Surefire
> Issue Type: Bug
> Environment: Gentoo Linux openjdk-bin-11.0.11_p9
>Reporter: Ciprian Ciubotariu
>Assignee: Slawomir Jaranowski
>Priority: Trivial
> Fix For: 3.3.0
>
>
> For {{JAVA_HOME=/opt/openjdk-bin-11.0.11_p9}},
> {{SystemUtilsTest.PlainUnitTests.incorrectJdkPath()}} throws a NPE at
> {{SystemUtils.toJdkHomeFromJvmExec(SystemUtils.java:91)}}.
> Trivial fix will follow soon
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (SUREFIRE-1939) Build fails if java.home has <=2 path components
[
https://issues.apache.org/jira/browse/SUREFIRE-1939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov reassigned SUREFIRE-1939:
Assignee: Michael Osipov (was: Slawomir Jaranowski)
> Build fails if java.home has <=2 path components
>
>
> Key: SUREFIRE-1939
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1939
> Project: Maven Surefire
> Issue Type: Bug
> Environment: Gentoo Linux openjdk-bin-11.0.11_p9
>Reporter: Ciprian Ciubotariu
>Assignee: Michael Osipov
>Priority: Trivial
> Fix For: 3.3.0
>
>
> For {{JAVA_HOME=/opt/openjdk-bin-11.0.11_p9}},
> {{SystemUtilsTest.PlainUnitTests.incorrectJdkPath()}} throws a NPE at
> {{SystemUtils.toJdkHomeFromJvmExec(SystemUtils.java:91)}}.
> Trivial fix will follow soon
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MJAVADOC-656) Following redirects breaks valid links
[
https://issues.apache.org/jira/browse/MJAVADOC-656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17852360#comment-17852360
]
Michael Osipov commented on MJAVADOC-656:
-
[~robert.vazan], are you interested still in addressing this? I agree with you
that the follow redirects approach is too naive. As a stop gap solution we
could add a parameter {{followLinks=true}} which you could disable. WDYT?
> Following redirects breaks valid links
> --
>
> Key: MJAVADOC-656
> URL: https://issues.apache.org/jira/browse/MJAVADOC-656
> Project: Maven Javadoc Plugin
> Issue Type: Bug
>Affects Versions: 3.0.1, 3.2.0
>Reporter: Robert Važan
>Priority: Minor
>
> Version 3.0.1 fixed #427 by following redirects. This feature unfortunately
> breaks when HTTP server is configured as follows:
> /apidocs/package-list -> 200
> /apidocs -> 301 /apidocs/com/example/package-summary.html
> /apidocs/ -> 301 /apidocs/com/example/package-summary.html
> /apidocs/com/example/package-summary.html -> 200
> Without following redirects (in version 3.0.0), the link is passed to javadoc
> tool unchanged, the javadoc tool fetches /apidocs/package-list, and
> everything works fine. Since 3.0.1, javadoc plugin follows one of the
> redirects (/apidocs or /apidocs/), passes the package summary URL to javadoc
> tool, which then fails like this:
> [WARNING] javadoc: warning - Error fetching URL:
> [https://example.com/apidocs/com/example/package-summary.html/]
> And if you have failOnWarnings set to true, this will fail the whole build.
> The solution is fairly simple. Construct the whole URL (.../package-list) and
> follow redirects on that one. Then check whether the final destination ends
> in /package-list, strip the /package-list suffix, and pass the result to the
> javadoc tool.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (SUREFIRE-1939) Build fails if java.home has <=2 path components
[
https://issues.apache.org/jira/browse/SUREFIRE-1939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17852308#comment-17852308
]
Michael Osipov commented on SUREFIRE-1939:
--
I can confirm this issue on Java 11:
{noformat}
$ /tmp/apache-maven-3.8.8/bin/mvn -V clean install
Apache Maven 3.8.8 (4c87b05d9aedce574290d1acc98575ed5eb6cd39)
Maven home: /tmp/apache-maven-3.8.8
Java version: 11.0.6, vendor: Hewlett Packard Enterprise, runtime: /opt/java11
Default locale: de_DE, platform encoding: UTF8
OS name: "hp-ux", version: "b.11.31", arch: "ia64n", family: "unix"
{noformat}
> Build fails if java.home has <=2 path components
>
>
> Key: SUREFIRE-1939
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1939
> Project: Maven Surefire
> Issue Type: Bug
> Environment: Gentoo Linux openjdk-bin-11.0.11_p9
>Reporter: Ciprian Ciubotariu
>Assignee: Slawomir Jaranowski
>Priority: Trivial
>
> For {{JAVA_HOME=/opt/openjdk-bin-11.0.11_p9}},
> {{SystemUtilsTest.PlainUnitTests.incorrectJdkPath()}} throws a NPE at
> {{SystemUtils.toJdkHomeFromJvmExec(SystemUtils.java:91)}}.
> Trivial fix will follow soon
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (SUREFIRE-2084) Jenkins junit plugin fails to parse surefire reports of failed tests
[
https://issues.apache.org/jira/browse/SUREFIRE-2084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17533240#comment-17533240
]
Michael Osipov edited comment on SUREFIRE-2084 at 6/4/24 9:45 PM:
--
I think I have found a similar issue - SUREFIRE-1556 - and it seems to have
been fixed in M6 release by
[https://github.com/apache/maven-surefire/pull/450], I will try the new release
and will monitor.
was (Author: JIRAUSER289138):
I think I have found a similar issue -
https://issues.apache.org/jira/browse/SUREFIRE-1556 - and it seems to have been
fixed in M6 release by [https://github.com/apache/maven-surefire/pull/450], I
will try the new release and will monitor.
> Jenkins junit plugin fails to parse surefire reports of failed tests
>
>
> Key: SUREFIRE-2084
> URL: https://issues.apache.org/jira/browse/SUREFIRE-2084
> Project: Maven Surefire
> Issue Type: Bug
>Affects Versions: 3.0.0-M4
>Reporter: Praveen Sreepada
>Priority: Major
>
> We use junit plugin in jenkins to export the results of the test runs. While
> doing so for the failed tests, I see the plugin throwing the following
> exception:
> {code:java}
> Failed to read test report file .xml
> org.dom4j.DocumentException: Error on line 144 of document : The content of
> elements must consist of well-formed character data or markup.
> at org.dom4j.io.SAXReader.read(SAXReader.java:511)
> at org.dom4j.io.SAXReader.read(SAXReader.java:392)
> at hudson.tasks.junit.SuiteResult.parse(SuiteResult.java:177)
> at hudson.tasks.junit.TestResult.parse(TestResult.java:349)
> at hudson.tasks.junit.TestResult.parsePossiblyEmpty(TestResult.java:279)
> at hudson.tasks.junit.TestResult.parse(TestResult.java:223)
> at hudson.tasks.junit.TestResult.parse(TestResult.java:197)
> at hudson.tasks.junit.TestResult.(TestResult.java:151)
> at
> hudson.tasks.junit.JUnitParser$ParseResultCallable.invoke(JUnitParser.java:147)
> at hudson.FilePath$FileCallableWrapper.call(FilePath.java:3329)
> at hudson.remoting.UserRequest.perform(UserRequest.java:211)
> at hudson.remoting.UserRequest.perform(UserRequest.java:54)
> at hudson.remoting.Request$2.run(Request.java:376)
> at
> hudson.remoting.InterceptingExecutorService.lambda$wrap$0(InterceptingExecutorService.java:78)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: org.xml.sax.SAXParseException; lineNumber: 144; columnNumber: 6;
> The content of elements must consist of well-formed character data or markup.
> at
> com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:203)
> at
> com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.fatalError(ErrorHandlerWrapper.java:177)
> at
> com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:400)
> at
> com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:327)
> at
> com.sun.org.apache.xerces.internal.impl.XMLScanner.reportFatalError(XMLScanner.java:1473)
> at
> com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.startOfMarkup(XMLDocumentFragmentScannerImpl.java:2635)
> at
> com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(XMLDocumentFragmentScannerImpl.java:2732)
> at
> com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:602)
> at
> com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.next(XMLNSDocumentScannerImpl.java:112)
> at
> com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:505)
> at
> com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:842)
> at
> com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:771)
> at
> com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:141)
> at
> com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1213)
> at
> com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.java:643)
> at org.dom4j.io.SAXReader.read(SAXReader.java:494)
> ... 17 more{code}
> Upon opening the generated xml file, this is what I found - This is the point
>
[jira] [Closed] (SUREFIRE-2084) Jenkins junit plugin fails to parse surefire reports of failed tests
[
https://issues.apache.org/jira/browse/SUREFIRE-2084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed SUREFIRE-2084.
Resolution: Not A Problem
Assuming not be a problem anymore.
> Jenkins junit plugin fails to parse surefire reports of failed tests
>
>
> Key: SUREFIRE-2084
> URL: https://issues.apache.org/jira/browse/SUREFIRE-2084
> Project: Maven Surefire
> Issue Type: Bug
>Affects Versions: 3.0.0-M4
>Reporter: Praveen Sreepada
>Priority: Major
>
> We use junit plugin in jenkins to export the results of the test runs. While
> doing so for the failed tests, I see the plugin throwing the following
> exception:
> {code:java}
> Failed to read test report file .xml
> org.dom4j.DocumentException: Error on line 144 of document : The content of
> elements must consist of well-formed character data or markup.
> at org.dom4j.io.SAXReader.read(SAXReader.java:511)
> at org.dom4j.io.SAXReader.read(SAXReader.java:392)
> at hudson.tasks.junit.SuiteResult.parse(SuiteResult.java:177)
> at hudson.tasks.junit.TestResult.parse(TestResult.java:349)
> at hudson.tasks.junit.TestResult.parsePossiblyEmpty(TestResult.java:279)
> at hudson.tasks.junit.TestResult.parse(TestResult.java:223)
> at hudson.tasks.junit.TestResult.parse(TestResult.java:197)
> at hudson.tasks.junit.TestResult.(TestResult.java:151)
> at
> hudson.tasks.junit.JUnitParser$ParseResultCallable.invoke(JUnitParser.java:147)
> at hudson.FilePath$FileCallableWrapper.call(FilePath.java:3329)
> at hudson.remoting.UserRequest.perform(UserRequest.java:211)
> at hudson.remoting.UserRequest.perform(UserRequest.java:54)
> at hudson.remoting.Request$2.run(Request.java:376)
> at
> hudson.remoting.InterceptingExecutorService.lambda$wrap$0(InterceptingExecutorService.java:78)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: org.xml.sax.SAXParseException; lineNumber: 144; columnNumber: 6;
> The content of elements must consist of well-formed character data or markup.
> at
> com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:203)
> at
> com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.fatalError(ErrorHandlerWrapper.java:177)
> at
> com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:400)
> at
> com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:327)
> at
> com.sun.org.apache.xerces.internal.impl.XMLScanner.reportFatalError(XMLScanner.java:1473)
> at
> com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.startOfMarkup(XMLDocumentFragmentScannerImpl.java:2635)
> at
> com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(XMLDocumentFragmentScannerImpl.java:2732)
> at
> com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:602)
> at
> com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.next(XMLNSDocumentScannerImpl.java:112)
> at
> com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:505)
> at
> com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:842)
> at
> com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:771)
> at
> com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:141)
> at
> com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1213)
> at
> com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.java:643)
> at org.dom4j.io.SAXReader.read(SAXReader.java:494)
> ... 17 more{code}
> Upon opening the generated xml file, this is what I found - This is the point
> (line 144) where it is failing to parse the XML, due to an extra space
> between `<` and `message=`
> {code:java}
>
>
>
> < message="Tests enabled on ONS3(stage and Prod) stack only ">{code}
> This message has been added due to a `Assume.assumeTrue` statement in the test
> We use maven-surefire-plugin version 3.0.0-M4
> Is this a known issue that has been fixed in later releases? if not, can this
> be fixed? Please let me know if you need any more information
>
--
This
[jira] [Closed] (SUREFIRE-1841) no longer finds tests starting with 3.0.0-M4
[
https://issues.apache.org/jira/browse/SUREFIRE-1841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed SUREFIRE-1841.
Resolution: Cannot Reproduce
I get with both M3 and M4 the same results:
{noformat}
D:\Entwicklung\Projekte\junit-deptest\demo [master ≡ +0 ~1 -0 !]> mvn test
-Pintegration -pl demo-integration
[INFO] Scanning for projects...
[WARNING]
[WARNING] Some problems were encountered while building the effective model for
com.example.demo:demo:pom:0.0.1-SNAPSHOT
[WARNING] 'parent.relativePath' of POM com.example.demo:demo:0.0.1-SNAPSHOT
(D:\Entwicklung\Projekte\junit-deptest\demo\pom.xml) points at
test.group:surefire-dependency-test instead of
org.springframework.boot:spring-boot-starter-parent, please verify your project
structure @ line 5, column 10
[WARNING]
[WARNING] It is highly recommended to fix these problems because they threaten
the stability of your build.
[WARNING]
[WARNING] For this reason, future Maven versions might no longer support
building such malformed projects.
[WARNING]
[INFO]
[INFO] -< com.example.demo:demo-integration >--
[INFO] Building demo-integration 0.0.1-SNAPSHOT
[INFO] from pom.xml
[INFO] [ jar ]-
[INFO]
[INFO] --- maven-resources-plugin:3.1.0:resources (default-resources) @
demo-integration ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory
D:\Entwicklung\Projekte\junit-deptest\demo\demo-integration\src\main\resources
[INFO] skip non existing resourceDirectory
D:\Entwicklung\Projekte\junit-deptest\demo\demo-integration\src\main\resources
[INFO]
[INFO] --- maven-compiler-plugin:3.8.0:compile (default-compile) @
demo-integration ---
[INFO] No sources to compile
[INFO]
[INFO] --- maven-resources-plugin:3.1.0:testResources (default-testResources) @
demo-integration ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 2 resources
[INFO]
[INFO] --- maven-compiler-plugin:3.8.0:testCompile (default-testCompile) @
demo-integration ---
[INFO] Nothing to compile - all classes are up to date
[INFO]
[INFO] --- maven-surefire-plugin:3.0.0-M3:test (default-test) @
demo-integration ---
[INFO]
[INFO] ---
[INFO] T E S T S
[INFO] ---
[INFO] Running TestSuite
Starting EndpointsTest...
Finished EndpointsTest in 69 ms
Begin testGetHeartbeat...
End testGetHeartbeat
Finished EndpointsTest in 85 ms
Finished EndpointsTest in 85 ms
[ERROR] Tests run: 7, Failures: 4, Errors: 0, Skipped: 3, Time elapsed: 0.539 s
<<< FAILURE! - in TestSuite
[ERROR] afterMethod(com.example.demo.integration.suite.EndpointsTest) Time
elapsed: 0.385 s <<< FAILURE!
java.lang.NullPointerException
at
com.example.demo.integration.suite.EndpointsTest.afterMethod(EndpointsTest.java:28)
[ERROR] beforeMethod(com.example.demo.integration.suite.EndpointsTest) Time
elapsed: 0.385 s <<< FAILURE!
java.lang.NullPointerException
at
com.example.demo.integration.suite.EndpointsTest.beforeMethod(EndpointsTest.java:23)
[ERROR] beforeMethod(com.example.demo.integration.suite.EndpointsTest) Time
elapsed: 0 s <<< FAILURE!
java.lang.NullPointerException
at
com.example.demo.integration.suite.EndpointsTest.beforeMethod(EndpointsTest.java:23)
[ERROR] afterMethod(com.example.demo.integration.suite.EndpointsTest) Time
elapsed: 0 s <<< FAILURE!
java.lang.NullPointerException
at
com.example.demo.integration.suite.EndpointsTest.afterMethod(EndpointsTest.java:28)
[INFO]
[INFO] Results:
[INFO]
[ERROR] Failures:
[ERROR]
com.example.demo.integration.suite.EndpointsTest.afterMethod(com.example.demo.integration.suite.EndpointsTest)
[ERROR] Run 1: EndpointsTest.afterMethod:28 NullPointer
[ERROR] Run 2: EndpointsTest.afterMethod:28 NullPointer
[INFO]
[ERROR]
com.example.demo.integration.suite.EndpointsTest.beforeMethod(com.example.demo.integration.suite.EndpointsTest)
[ERROR] Run 1: EndpointsTest.beforeMethod:23 NullPointer
[ERROR] Run 2: EndpointsTest.beforeMethod:23 NullPointer
[INFO]
[INFO]
[ERROR] Tests run: 4, Failures: 2, Errors: 0, Skipped: 2
[INFO]
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 3.652 s
[INFO] Finished at: 2024-06-04T23:43:25+02:00
[INFO]
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M3:test (default-test) on
project demo-integration: There are test failures.
[ERROR]
[ERROR] Please refer to
D:\Entwicklung\Projekte\junit-deptest\demo\demo-integration\target\surefire-reports
for the individual test results.
[ERROR] Please
[jira] [Commented] (SUREFIRE-1943) give surefirebooter jar an useful name
[
https://issues.apache.org/jira/browse/SUREFIRE-1943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17852199#comment-17852199
]
Michael Osipov commented on SUREFIRE-1943:
--
Where is {{executionId}} expected to come from?
> give surefirebooter jar an useful name
> --
>
> Key: SUREFIRE-1943
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1943
> Project: Maven Surefire
> Issue Type: Improvement
>Reporter: Romain Manni-Bucau
>Priority: Trivial
>
> Surefire booter jar name generally looks like "surefirebooter.jar".
> Would be way better to name it
> "surefirebooter--.jar" since it would enable to
> identify it using jps (or equivalent) very quickly and is not that crazy
> since all the info are in the mojo anyway.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (SUREFIRE-1868) writing to System.outwriting to System.errwriting to System.outwriting to System.errwriting
[
https://issues.apache.org/jira/browse/SUREFIRE-1868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17852196#comment-17852196
]
Michael Osipov commented on SUREFIRE-1868:
--
FTR: Tried all relevant versions and did a {{git bisect}}.
> writing to System.outwriting to System.errwriting to System.outwriting to
> System.errwriting
> ---
>
> Key: SUREFIRE-1868
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1868
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
>Affects Versions: 3.0.0-M5, 3.2.5
> Environment: W10, oracle jdk8.0_202, mvn 3.6.3
>Reporter: Tilman Hausherr
>Priority: Minor
>
> I'm getting this text at the end of the tests
> "Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 s - in
> org.apache.tika.utils.ServiceLoaderUtilsTest
> writing to System.outwriting to System.errwriting to System.outwriting to
> System.errwriting to System.outwriting to System.errwriting to
> System.outwriting to System.errwriting to System.outwriting to System.err"
> How to reproduce:
> - get the Apache Tika project ("main" branch) from
> https://github.com/apache/tika/
> - change "3.0.0-M4" to "3.0.0-M5" in the pom.xml of the parent subproject
> - build
> - it happens with the first subproject (tika-core)
> The build doesn't stop, but in my IDE it appears in red so it's probably a
> warning or an error.
> It does not happen with 3.0.0-M4.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (SUREFIRE-1868) writing to System.outwriting to System.errwriting to System.outwriting to System.errwriting
[
https://issues.apache.org/jira/browse/SUREFIRE-1868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed SUREFIRE-1868.
Resolution: Invalid
It happens indeed, but for a reason and is caused by SUREFIRE-1788. The output
comes from *your* code:
https://github.com/apache/tika/blob/b6a1112909348db296c513b5efcbc2eeec835c80/tika-parsers/tika-parsers-standard/tika-parsers-standard-package/src/test/java/org/apache/tika/parser/mock/MockParserTest.java#L53-L74.
3.0.0-M5 started to handle this correctly, before that it was simply
swallowed/ignored.
> writing to System.outwriting to System.errwriting to System.outwriting to
> System.errwriting
> ---
>
> Key: SUREFIRE-1868
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1868
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
>Affects Versions: 3.0.0-M5, 3.2.5
> Environment: W10, oracle jdk8.0_202, mvn 3.6.3
>Reporter: Tilman Hausherr
>Priority: Minor
>
> I'm getting this text at the end of the tests
> "Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 s - in
> org.apache.tika.utils.ServiceLoaderUtilsTest
> writing to System.outwriting to System.errwriting to System.outwriting to
> System.errwriting to System.outwriting to System.errwriting to
> System.outwriting to System.errwriting to System.outwriting to System.err"
> How to reproduce:
> - get the Apache Tika project ("main" branch) from
> https://github.com/apache/tika/
> - change "3.0.0-M4" to "3.0.0-M5" in the pom.xml of the parent subproject
> - build
> - it happens with the first subproject (tika-core)
> The build doesn't stop, but in my IDE it appears in red so it's probably a
> warning or an error.
> It does not happen with 3.0.0-M4.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (SUREFIRE-1868) writing to System.outwriting to System.errwriting to System.outwriting to System.errwriting
[
https://issues.apache.org/jira/browse/SUREFIRE-1868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated SUREFIRE-1868:
-
Affects Version/s: 3.2.5
> writing to System.outwriting to System.errwriting to System.outwriting to
> System.errwriting
> ---
>
> Key: SUREFIRE-1868
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1868
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
>Affects Versions: 3.0.0-M5, 3.2.5
> Environment: W10, oracle jdk8.0_202, mvn 3.6.3
>Reporter: Tilman Hausherr
>Priority: Minor
>
> I'm getting this text at the end of the tests
> "Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 s - in
> org.apache.tika.utils.ServiceLoaderUtilsTest
> writing to System.outwriting to System.errwriting to System.outwriting to
> System.errwriting to System.outwriting to System.errwriting to
> System.outwriting to System.errwriting to System.outwriting to System.err"
> How to reproduce:
> - get the Apache Tika project ("main" branch) from
> https://github.com/apache/tika/
> - change "3.0.0-M4" to "3.0.0-M5" in the pom.xml of the parent subproject
> - build
> - it happens with the first subproject (tika-core)
> The build doesn't stop, but in my IDE it appears in red so it's probably a
> warning or an error.
> It does not happen with 3.0.0-M4.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (SUREFIRE-2172) StringUtils: yet more of them
[ https://issues.apache.org/jira/browse/SUREFIRE-2172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated SUREFIRE-2172: - Labels: up-for-grabs (was: ) > StringUtils: yet more of them > - > > Key: SUREFIRE-2172 > URL: https://issues.apache.org/jira/browse/SUREFIRE-2172 > Project: Maven Surefire > Issue Type: Improvement >Reporter: Elliotte Rusty Harold >Priority: Minor > Labels: up-for-grabs > > This project contains not one, not two, but **three** different StringUtils > classes that duplicate functionality in the JDK and elsewhere. One or two of > them imght be built by shading other classes. They're even sometimes both > imported in the same classes such as LegacyPojoStackTraceWriter: > import org.apache.maven.surefire.api.util.internal.StringUtils; > import static org.apache.maven.surefire.shared.utils.StringUtils.isNotEmpty; > Figure out what to do about this. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (SUREFIRE-2099) NPE when Description is null
[
https://issues.apache.org/jira/browse/SUREFIRE-2099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17852182#comment-17852182
]
Michael Osipov commented on SUREFIRE-2099:
--
Still valid 3.2.5.
> NPE when Description is null
>
>
> Key: SUREFIRE-2099
> URL: https://issues.apache.org/jira/browse/SUREFIRE-2099
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
>Affects Versions: 2.22.2, 3.0.0-M7
> Environment: Platform: Java 8
> Build tool: maven 3.8.3 (version is not important), maven-surefire-plugin +
> surefire-junit47 provider
> Framework: spring-boot 2.5.12, junit-vintage-engine 5.7.2, JUnit 4.13.2
> JUnitParams: 1.1.1
>Reporter: victor lalykin
>Priority: Major
>
> using maven-surefire-plugin + surefire-junit47 provider.
> pom.xml:
>
>
>
> org.apache.maven.plugins
> maven-surefire-plugin
> 3.0.0-M7
>
>
> org.apache.maven.surefire
> surefire-junit47
> 3.0.0-M7
>
>
>
>
>
> if null is passed as description in the
> {*}_NonConcurrentRunListener.describesNewTestSet()_{*}, then the test run
> (mvn test) will fail. This situation sometimes occurs when working with
> JUnitParams.
> If you use the default provider (delete the "dependencies" section), then
> there is no error, everything is ok. This suggests that different providers
> behave differently, but it seems that the behavior should be unified and
> without errors.
> It is also not clear from the log on which test the crash occurred.
> -
> the maven log:
> -
> [INFO]
> [INFO] Results:
> [INFO]
> *[INFO] Tests run: 5735, Failures: 0, Errors: 0, Skipped: 0*
> [INFO]
> [INFO]
>
> *[INFO] BUILD FAILURE*
> [INFO]
>
> [INFO] Total time: 05:20 min
> [INFO] Finished at: 2022-06-14T11:25:24+03:00
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M7:test (default-test)
> on project ...:
> [ERROR]
> [ERROR] Please refer to ...\target\surefire-reports for the individual test
> results.
> *[ERROR] Please refer to dump files (if any exist) [date].dump,
> [date]-jvmRun[N].dump and [date].dumpstream.*
> [ERROR] There was an error in the forked process
> [ERROR] Test mechanism :: null
> [ERROR] org.apache.maven.surefire.booter.SurefireBooterForkException: There
> was an error in the forked process
> [ERROR] Test mechanism :: null
> [ERROR] at
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:701)
> [ERROR] at
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:311)
> [ERROR] at
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:268)
> [ERROR] at
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider(AbstractSurefireMojo.java:1334)
> [ERROR] at
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:1167)
> [ERROR] at
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:931)
> [ERROR] at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:137)
> [ERROR] at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:210)
> [ERROR] at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:156)
> [ERROR] at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:148)
> [ERROR] at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)
> [ERROR] at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)
> [ERROR] at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:56)
> [ERROR] at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
> [ERROR] at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:305)
> [ERROR] at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:192)
> [ERROR] at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:105)
> [ERROR] at org.apache.maven.cli.MavenCli.execute(MavenCli.java:972)
> [ERROR] at
[jira] [Closed] (SUREFIRE-1917) Surefire plug-in level dependency doesn't work
[
https://issues.apache.org/jira/browse/SUREFIRE-1917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed SUREFIRE-1917.
Resolution: Invalid
Your setup is invalid. Look what docs say:
https://maven.apache.org/surefire/maven-surefire-plugin/examples/junit.html#using-custom-listeners-and-reporters
Did it:
{code:xml}
http://maven.apache.org/POM/4.0.0;
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
https://maven.apache.org/xsd/maven-4.0.0.xsd;>
4.0.0
test.group
surefire-dependency-test
0.0.1-SNAPSHOT
11
${maven.compiler.source}
junit
junit
4.13.2
test
uk.ac.ebi
jutils
10.0-SNAPSHOT
test
org.slf4j
slf4j-api
1.7.36
org.slf4j
slf4j-simple
1.7.36
test
org.apache.maven.plugins
maven-surefire-plugin
3.2.5
listener
uk.ac.ebi.utils.test.junit.TestOutputDecorator
{code}
output:
{noformat}
Apache Maven 3.8.8 (4c87b05d9aedce574290d1acc98575ed5eb6cd39)
Maven home: D:\Entwicklung\Programme\apache-maven-3.8.8
Java version: 11.0.21, vendor: Eclipse Adoptium, runtime: C:\Program
Files\Eclipse Adoptium\jdk-11.0.21.9-hotspot
Default locale: de_DE, platform encoding: UTF-8
OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
[INFO] Scanning for projects...
[INFO]
[INFO] < test.group:surefire-dependency-test >-
[INFO] Building surefire-dependency-test 0.0.1-SNAPSHOT
[INFO] from pom.xml
[INFO] [ jar ]-
[INFO]
[INFO] --- maven-resources-plugin:2.6:resources (default-resources) @
surefire-dependency-test ---
[WARNING] Using platform encoding (UTF-8 actually) to copy filtered resources,
i.e. build is platform dependent!
[INFO] Copying 0 resource
[INFO]
[INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @
surefire-dependency-test ---
[INFO] Nothing to compile - all classes are up to date
[INFO]
[INFO] --- maven-resources-plugin:2.6:testResources (default-testResources) @
surefire-dependency-test ---
[WARNING] Using platform encoding (UTF-8 actually) to copy filtered resources,
i.e. build is platform dependent!
[INFO] Copying 0 resource
[INFO]
[INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @
surefire-dependency-test ---
[INFO] Nothing to compile - all classes are up to date
[INFO]
[INFO] --- maven-surefire-plugin:3.2.5:test (default-test) @
surefire-dependency-test ---
[INFO] Using auto detected provider
org.apache.maven.surefire.junit4.JUnit4Provider
[INFO]
[INFO] ---
[INFO] T E S T S
[INFO] ---
[INFO] Running test.pkg.FooTest
[main] INFO uk.ac.ebi.utils.test.junit.TestOutputDecorator -
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= testFoo(test.pkg.FooTest)
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
[main] INFO uk.ac.ebi.utils.test.junit.TestOutputDecorator -
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- /end: testFoo(test.pkg.FooTest)
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.080 s
-- in test.pkg.FooTest
[INFO]
[INFO] Results:
[INFO]
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
[INFO]
[INFO]
[INFO] --- maven-jar-plugin:2.4:jar (default-jar) @ surefire-dependency-test ---
[INFO]
[INFO] BUILD SUCCESS
[INFO]
[INFO] Total time: 2.074 s
[INFO] Finished at: 2024-06-04T22:22:24+02:00
[INFO]
{noformat}
> Surefire plug-in level dependency doesn't work
> --
>
> Key: SUREFIRE-1917
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1917
> Project: Maven Surefire
> Issue Type: Bug
> Components: Junit 4.x support
>Affects Versions: 3.0.0-M5
> Environment: 18:41:33 [root@MAC10143-ROTH tmp]# mvn -v
> Apache Maven 3.6.3 (cecedd343002696d0abb50b32b541b8a6ba2883f)
> Maven home: /usr/local/Cellar/maven/3.6.3/libexec
> Java version: 11.0.10, vendor: AdoptOpenJDK, runtime:
> /Library/Java/JavaVirtualMachines/adoptopenjdk-11.jdk/Contents/Home
> Default locale: en_GB, platform encoding: UTF-8
> OS name: "mac os x", version: "10.16", arch: "x86_64", family: "mac"
> 18:48:39 [root@MAC10143-ROTH tmp]#
>Reporter: Marco Brandizi
>
[jira] [Commented] (SUREFIRE-1917) Surefire plug-in level dependency doesn't work
[ https://issues.apache.org/jira/browse/SUREFIRE-1917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17852176#comment-17852176 ] Michael Osipov commented on SUREFIRE-1917: -- This still fails with 3.2.5, I am bisecting to the offending change... > Surefire plug-in level dependency doesn't work > -- > > Key: SUREFIRE-1917 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1917 > Project: Maven Surefire > Issue Type: Bug > Components: Junit 4.x support >Affects Versions: 3.0.0-M5 > Environment: 18:41:33 [root@MAC10143-ROTH tmp]# mvn -v > Apache Maven 3.6.3 (cecedd343002696d0abb50b32b541b8a6ba2883f) > Maven home: /usr/local/Cellar/maven/3.6.3/libexec > Java version: 11.0.10, vendor: AdoptOpenJDK, runtime: > /Library/Java/JavaVirtualMachines/adoptopenjdk-11.jdk/Contents/Home > Default locale: en_GB, platform encoding: UTF-8 > OS name: "mac os x", version: "10.16", arch: "x86_64", family: "mac" > 18:48:39 [root@MAC10143-ROTH tmp]# >Reporter: Marco Brandizi >Priority: Major > Attachments: junit-deptest.zip > > > I've been using a Junit 4.x > [listener|https://github.com/marco-brandizi/jutils/blob/master/jutils/src/main/java/uk/ac/ebi/utils/test/junit/TestOutputDecorator.java] > for years, to wrap every test method run with nice header/trailer > decorations. > I've been doing this by adding the dependency to the listener class in the > surefire's section and then using the property listener. > I've just discovered that this doesn't work anymore with 3.0.0-M5 version: it > says that the listener's ClassNotFoundException for the listener class. > You can verify this with the attached simple project. > Using it, I've tried several older versions until I found that the latest > working is 2.19.1, the 2.20.1 raises a NullPointerEx and I didn't get exactly > where (see the .out in the attachment). > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (SUREFIRE-2047) Upgrade to maven-common-artifact-filters 3.4.0
[
https://issues.apache.org/jira/browse/SUREFIRE-2047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated SUREFIRE-2047:
-
Fix Version/s: 3.3.0
> Upgrade to maven-common-artifact-filters 3.4.0
> --
>
> Key: SUREFIRE-2047
> URL: https://issues.apache.org/jira/browse/SUREFIRE-2047
> Project: Maven Surefire
> Issue Type: Dependency upgrade
>Reporter: Slawomir Jaranowski
>Assignee: Michael Osipov
>Priority: Minor
> Fix For: 3.3.0
>
>
> Currently we can't upgrade {{maven-common-artifact-filters}} to 3.2.0 due to
> MSHARED-1031
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (SUREFIRE-2047) Upgrade to maven-common-artifact-filters 3.4.0
[
https://issues.apache.org/jira/browse/SUREFIRE-2047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated SUREFIRE-2047:
-
Summary: Upgrade to maven-common-artifact-filters 3.4.0 (was: Upgrade
maven-common-artifact-filters)
> Upgrade to maven-common-artifact-filters 3.4.0
> --
>
> Key: SUREFIRE-2047
> URL: https://issues.apache.org/jira/browse/SUREFIRE-2047
> Project: Maven Surefire
> Issue Type: Dependency upgrade
>Reporter: Slawomir Jaranowski
>Assignee: Slawomir Jaranowski
>Priority: Minor
>
> Currently we can't upgrade {{maven-common-artifact-filters}} to 3.2.0 due to
> MSHARED-1031
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (SUREFIRE-2047) Upgrade to maven-common-artifact-filters 3.4.0
[
https://issues.apache.org/jira/browse/SUREFIRE-2047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov reassigned SUREFIRE-2047:
Assignee: Michael Osipov (was: Slawomir Jaranowski)
> Upgrade to maven-common-artifact-filters 3.4.0
> --
>
> Key: SUREFIRE-2047
> URL: https://issues.apache.org/jira/browse/SUREFIRE-2047
> Project: Maven Surefire
> Issue Type: Dependency upgrade
>Reporter: Slawomir Jaranowski
>Assignee: Michael Osipov
>Priority: Minor
>
> Currently we can't upgrade {{maven-common-artifact-filters}} to 3.2.0 due to
> MSHARED-1031
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (MSHARED-1303) Declare and undeclare used and unused dependencies
[ https://issues.apache.org/jira/browse/MSHARED-1303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov reassigned MSHARED-1303: --- Assignee: Michael Osipov > Declare and undeclare used and unused dependencies > -- > > Key: MSHARED-1303 > URL: https://issues.apache.org/jira/browse/MSHARED-1303 > Project: Maven Shared Components > Issue Type: Improvement > Components: maven-common-artifact-filters >Reporter: Elliotte Rusty Harold >Assignee: Michael Osipov >Priority: Minor > Fix For: maven-common-artifact-filters-next-release > > > [WARNING] Used undeclared dependencies found: > [WARNING]org.eclipse.aether:aether-util:jar:1.0.0.v20140518:provided > [WARNING]org.eclipse.aether:aether-api:jar:1.0.0.v20140518:provided > [WARNING] Unused declared dependencies found: > [WARNING]org.apache.maven.resolver:maven-resolver-api:jar:1.6.3:provided > [WARNING]org.apache.maven.resolver:maven-resolver-util:jar:1.6.3:provided > [WARNING]org.openjdk.jmh:jmh-generator-annprocess:jar:1.35:test -- This message was sent by Atlassian Jira (v8.20.10#820010)
