[GitHub] [maven-surefire] sbabcoc commented on a diff in pull request #517: [SUREFIRE-2064] Allow all supported values of [parallel] option
sbabcoc commented on code in PR #517:
URL: https://github.com/apache/maven-surefire/pull/517#discussion_r851694849
##
surefire-providers/surefire-testng/src/main/java/org/apache/maven/surefire/testng/conf/TestNG740Configurator.java:
##
@@ -37,33 +36,77 @@
*
* @since 3.0.0-M6
*/
-public class TestNG740Configurator extends TestNG60Configurator
+public class TestNG740Configurator
+extends TestNG60Configurator
{
+/**
+ * Convert and apply the value of the [threadcount] option.
+ *
+ * @param suite TestNG {@link XmlSuite} object
+ * @param options Surefire plugin configuration options
+ * @throws TestSetFailedException if unable to convert specified
[threadcount] setting
+ */
@Override
-public void configure( XmlSuite suite, Map options )
+protected void configureThreadCount( XmlSuite suite, Map
options )
throws TestSetFailedException
{
-String threadCountAsString = options.get( THREADCOUNT_PROP );
-int threadCount = threadCountAsString == null ? 1 : parseInt(
threadCountAsString );
-suite.setThreadCount( threadCount );
-
-String parallel = options.get( PARALLEL_PROP );
-if ( parallel != null )
+String threadCount = options.get( THREADCOUNT_PROP );
+// if [threadcount] spec'd
+if ( threadCount != null )
{
-if ( !"methods".equalsIgnoreCase( parallel ) &&
!"classes".equalsIgnoreCase( parallel ) )
+try
{
-throw new TestSetFailedException( "Unsupported TestNG parallel
setting: "
-+ parallel + " ( only METHODS or CLASSES supported )" );
+// convert and apply [threadcount] setting
+suite.setThreadCount( Integer.parseInt( threadCount ) );
Review Comment:
If all supported versions of TestNG provide a default for this setting, it
may be best to not inject a default here. Just let TestNG provide its own
default value. That's how the new code for TestNG 7.4+ behaves. I don't know
the history of the original code to understand why this was coded to inject a
default value of 1. (What's the benefit of specifying parallel execution if the
thread count is 1?)
If the default implementation is changed so that it behaves like the new
override, this override can be removed.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
[GitHub] [maven-surefire] sbabcoc commented on a diff in pull request #517: [SUREFIRE-2064] Allow all supported values of [parallel] option
sbabcoc commented on code in PR #517:
URL: https://github.com/apache/maven-surefire/pull/517#discussion_r851697867
##
surefire-providers/surefire-testng/src/main/java/org/apache/maven/surefire/testng/conf/TestNG740Configurator.java:
##
@@ -37,33 +36,77 @@
*
* @since 3.0.0-M6
*/
-public class TestNG740Configurator extends TestNG60Configurator
+public class TestNG740Configurator
+extends TestNG60Configurator
{
+/**
+ * Convert and apply the value of the [threadcount] option.
+ *
+ * @param suite TestNG {@link XmlSuite} object
+ * @param options Surefire plugin configuration options
+ * @throws TestSetFailedException if unable to convert specified
[threadcount] setting
+ */
@Override
-public void configure( XmlSuite suite, Map options )
+protected void configureThreadCount( XmlSuite suite, Map
options )
throws TestSetFailedException
{
-String threadCountAsString = options.get( THREADCOUNT_PROP );
-int threadCount = threadCountAsString == null ? 1 : parseInt(
threadCountAsString );
-suite.setThreadCount( threadCount );
-
-String parallel = options.get( PARALLEL_PROP );
-if ( parallel != null )
+String threadCount = options.get( THREADCOUNT_PROP );
+// if [threadcount] spec'd
+if ( threadCount != null )
{
-if ( !"methods".equalsIgnoreCase( parallel ) &&
!"classes".equalsIgnoreCase( parallel ) )
+try
{
-throw new TestSetFailedException( "Unsupported TestNG parallel
setting: "
-+ parallel + " ( only METHODS or CLASSES supported )" );
+// convert and apply [threadcount] setting
+suite.setThreadCount( Integer.parseInt( threadCount ) );
Review Comment:
Why would we override the default value provided by TestNG? What's the
benefit of specifying parallel execution if the thread count is 1?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
[GitHub] [maven-surefire] sbabcoc commented on a diff in pull request #517: [SUREFIRE-2064] Allow all supported values of [parallel] option
sbabcoc commented on code in PR #517:
URL: https://github.com/apache/maven-surefire/pull/517#discussion_r851694849
##
surefire-providers/surefire-testng/src/main/java/org/apache/maven/surefire/testng/conf/TestNG740Configurator.java:
##
@@ -37,33 +36,77 @@
*
* @since 3.0.0-M6
*/
-public class TestNG740Configurator extends TestNG60Configurator
+public class TestNG740Configurator
+extends TestNG60Configurator
{
+/**
+ * Convert and apply the value of the [threadcount] option.
+ *
+ * @param suite TestNG {@link XmlSuite} object
+ * @param options Surefire plugin configuration options
+ * @throws TestSetFailedException if unable to convert specified
[threadcount] setting
+ */
@Override
-public void configure( XmlSuite suite, Map options )
+protected void configureThreadCount( XmlSuite suite, Map
options )
throws TestSetFailedException
{
-String threadCountAsString = options.get( THREADCOUNT_PROP );
-int threadCount = threadCountAsString == null ? 1 : parseInt(
threadCountAsString );
-suite.setThreadCount( threadCount );
-
-String parallel = options.get( PARALLEL_PROP );
-if ( parallel != null )
+String threadCount = options.get( THREADCOUNT_PROP );
+// if [threadcount] spec'd
+if ( threadCount != null )
{
-if ( !"methods".equalsIgnoreCase( parallel ) &&
!"classes".equalsIgnoreCase( parallel ) )
+try
{
-throw new TestSetFailedException( "Unsupported TestNG parallel
setting: "
-+ parallel + " ( only METHODS or CLASSES supported )" );
+// convert and apply [threadcount] setting
+suite.setThreadCount( Integer.parseInt( threadCount ) );
Review Comment:
If all supported versions of TestNG provide a default for this setting, it
may be best to not inject a default here. Just let TestNG provide its own
default value. That's how the new code for TestNG 7.4+ behaves. I don't know
the history of the original code to understand why this was coded to inject a
default value of 1.
If the default implementation is changed so that it behaves like the new
override, this override can be removed.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
[GitHub] [maven-surefire] sbabcoc commented on a diff in pull request #517: [SUREFIRE-2064] Allow all supported values of [parallel] option
sbabcoc commented on code in PR #517:
URL: https://github.com/apache/maven-surefire/pull/517#discussion_r851694849
##
surefire-providers/surefire-testng/src/main/java/org/apache/maven/surefire/testng/conf/TestNG740Configurator.java:
##
@@ -37,33 +36,77 @@
*
* @since 3.0.0-M6
*/
-public class TestNG740Configurator extends TestNG60Configurator
+public class TestNG740Configurator
+extends TestNG60Configurator
{
+/**
+ * Convert and apply the value of the [threadcount] option.
+ *
+ * @param suite TestNG {@link XmlSuite} object
+ * @param options Surefire plugin configuration options
+ * @throws TestSetFailedException if unable to convert specified
[threadcount] setting
+ */
@Override
-public void configure( XmlSuite suite, Map options )
+protected void configureThreadCount( XmlSuite suite, Map
options )
throws TestSetFailedException
{
-String threadCountAsString = options.get( THREADCOUNT_PROP );
-int threadCount = threadCountAsString == null ? 1 : parseInt(
threadCountAsString );
-suite.setThreadCount( threadCount );
-
-String parallel = options.get( PARALLEL_PROP );
-if ( parallel != null )
+String threadCount = options.get( THREADCOUNT_PROP );
+// if [threadcount] spec'd
+if ( threadCount != null )
{
-if ( !"methods".equalsIgnoreCase( parallel ) &&
!"classes".equalsIgnoreCase( parallel ) )
+try
{
-throw new TestSetFailedException( "Unsupported TestNG parallel
setting: "
-+ parallel + " ( only METHODS or CLASSES supported )" );
+// convert and apply [threadcount] setting
+suite.setThreadCount( Integer.parseInt( threadCount ) );
Review Comment:
If all supported versions of TestNG provide a default for this setting, it
may be best to not inject a default here. Just let TestNG provide its own
default value. That's how the new code for TestNG 7.4+ behaves. I don't know
the history of the original code to understand why this was coded to inject a
default value of 1.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
[jira] [Commented] (MJAVADOC-714) Upgrade to Maven 3.2.5
[ https://issues.apache.org/jira/browse/MJAVADOC-714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17523258#comment-17523258 ] Hudson commented on MJAVADOC-714: - Build unstable in Jenkins: Maven » Maven TLP » maven-javadoc-plugin » master #16 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-javadoc-plugin/job/master/16/ > Upgrade to Maven 3.2.5 > -- > > Key: MJAVADOC-714 > URL: https://issues.apache.org/jira/browse/MJAVADOC-714 > Project: Maven Javadoc Plugin > Issue Type: Dependency upgrade >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: 3.4.0 > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Closed] (MJAVADOC-714) Upgrade to Maven 3.2.5
[ https://issues.apache.org/jira/browse/MJAVADOC-714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed MJAVADOC-714. --- Resolution: Fixed Fixed with [0c6b32fb5ec9c31b4e38d9f32616ff51102623da|https://gitbox.apache.org/repos/asf?p=maven-javadoc-plugin.git;a=commit;h=0c6b32fb5ec9c31b4e38d9f32616ff51102623da]. > Upgrade to Maven 3.2.5 > -- > > Key: MJAVADOC-714 > URL: https://issues.apache.org/jira/browse/MJAVADOC-714 > Project: Maven Javadoc 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.1#820001)
[GitHub] [maven-javadoc-plugin] asfgit closed pull request #134: [MJAVADOC-714] Upgrade to Maven 3.2.5
asfgit closed pull request #134: [MJAVADOC-714] Upgrade to Maven 3.2.5 URL: https://github.com/apache/maven-javadoc-plugin/pull/134 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Updated] (MJAVADOC-510) Investigate JavadocUtil.invokeMaven
[ https://issues.apache.org/jira/browse/MJAVADOC-510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MJAVADOC-510: Fix Version/s: (was: next-release) > Investigate JavadocUtil.invokeMaven > --- > > Key: MJAVADOC-510 > URL: https://issues.apache.org/jira/browse/MJAVADOC-510 > Project: Maven Javadoc Plugin > Issue Type: Task > Components: fix >Reporter: Stephen Connolly >Priority: Major > > Spotted while fine-tuning the Jenkinsfile builds. Unclear why Javadoc plugin > needs to fork Maven and whether it is doing it the correct way if the > requirement is actually valid. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[GitHub] [maven-surefire] Tibor17 commented on a diff in pull request #517: [SUREFIRE-2064] Allow all supported values of [parallel] option
Tibor17 commented on code in PR #517:
URL: https://github.com/apache/maven-surefire/pull/517#discussion_r851683061
##
surefire-providers/surefire-testng/src/main/java/org/apache/maven/surefire/testng/conf/TestNG740Configurator.java:
##
@@ -37,33 +36,77 @@
*
* @since 3.0.0-M6
*/
-public class TestNG740Configurator extends TestNG60Configurator
+public class TestNG740Configurator
+extends TestNG60Configurator
{
+/**
+ * Convert and apply the value of the [threadcount] option.
+ *
+ * @param suite TestNG {@link XmlSuite} object
+ * @param options Surefire plugin configuration options
+ * @throws TestSetFailedException if unable to convert specified
[threadcount] setting
+ */
@Override
-public void configure( XmlSuite suite, Map options )
+protected void configureThreadCount( XmlSuite suite, Map
options )
throws TestSetFailedException
{
-String threadCountAsString = options.get( THREADCOUNT_PROP );
-int threadCount = threadCountAsString == null ? 1 : parseInt(
threadCountAsString );
-suite.setThreadCount( threadCount );
-
-String parallel = options.get( PARALLEL_PROP );
-if ( parallel != null )
+String threadCount = options.get( THREADCOUNT_PROP );
+// if [threadcount] spec'd
+if ( threadCount != null )
{
-if ( !"methods".equalsIgnoreCase( parallel ) &&
!"classes".equalsIgnoreCase( parallel ) )
+try
{
-throw new TestSetFailedException( "Unsupported TestNG parallel
setting: "
-+ parallel + " ( only METHODS or CLASSES supported )" );
+// convert and apply [threadcount] setting
+suite.setThreadCount( Integer.parseInt( threadCount ) );
Review Comment:
I found the default value in TestNG:
`private int m_threadCount = 5;`
We should use the same line as before, means `suite.setThreadCount(
threadCount == null ? 1 : Integer.parseInt( threadCount ) )`
##
surefire-providers/surefire-testng/src/main/java/org/apache/maven/surefire/testng/conf/TestNG740Configurator.java:
##
@@ -37,33 +36,77 @@
*
* @since 3.0.0-M6
*/
-public class TestNG740Configurator extends TestNG60Configurator
+public class TestNG740Configurator
+extends TestNG60Configurator
{
+/**
+ * Convert and apply the value of the [threadcount] option.
+ *
+ * @param suite TestNG {@link XmlSuite} object
+ * @param options Surefire plugin configuration options
+ * @throws TestSetFailedException if unable to convert specified
[threadcount] setting
+ */
@Override
-public void configure( XmlSuite suite, Map options )
+protected void configureThreadCount( XmlSuite suite, Map
options )
throws TestSetFailedException
{
-String threadCountAsString = options.get( THREADCOUNT_PROP );
-int threadCount = threadCountAsString == null ? 1 : parseInt(
threadCountAsString );
-suite.setThreadCount( threadCount );
-
-String parallel = options.get( PARALLEL_PROP );
-if ( parallel != null )
+String threadCount = options.get( THREADCOUNT_PROP );
+// if [threadcount] spec'd
+if ( threadCount != null )
{
-if ( !"methods".equalsIgnoreCase( parallel ) &&
!"classes".equalsIgnoreCase( parallel ) )
+try
{
-throw new TestSetFailedException( "Unsupported TestNG parallel
setting: "
-+ parallel + " ( only METHODS or CLASSES supported )" );
+// convert and apply [threadcount] setting
+suite.setThreadCount( Integer.parseInt( threadCount ) );
Review Comment:
I found the default value in TestNG:
`private int m_threadCount = 5;`
We should use the same line as before, means `suite.setThreadCount(
threadCount == null ? 1 : parseInt( threadCount ) )`
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
[GitHub] [maven-surefire] Tibor17 commented on a diff in pull request #517: [SUREFIRE-2064] Allow all supported values of [parallel] option
Tibor17 commented on code in PR #517:
URL: https://github.com/apache/maven-surefire/pull/517#discussion_r851683061
##
surefire-providers/surefire-testng/src/main/java/org/apache/maven/surefire/testng/conf/TestNG740Configurator.java:
##
@@ -37,33 +36,77 @@
*
* @since 3.0.0-M6
*/
-public class TestNG740Configurator extends TestNG60Configurator
+public class TestNG740Configurator
+extends TestNG60Configurator
{
+/**
+ * Convert and apply the value of the [threadcount] option.
+ *
+ * @param suite TestNG {@link XmlSuite} object
+ * @param options Surefire plugin configuration options
+ * @throws TestSetFailedException if unable to convert specified
[threadcount] setting
+ */
@Override
-public void configure( XmlSuite suite, Map options )
+protected void configureThreadCount( XmlSuite suite, Map
options )
throws TestSetFailedException
{
-String threadCountAsString = options.get( THREADCOUNT_PROP );
-int threadCount = threadCountAsString == null ? 1 : parseInt(
threadCountAsString );
-suite.setThreadCount( threadCount );
-
-String parallel = options.get( PARALLEL_PROP );
-if ( parallel != null )
+String threadCount = options.get( THREADCOUNT_PROP );
+// if [threadcount] spec'd
+if ( threadCount != null )
{
-if ( !"methods".equalsIgnoreCase( parallel ) &&
!"classes".equalsIgnoreCase( parallel ) )
+try
{
-throw new TestSetFailedException( "Unsupported TestNG parallel
setting: "
-+ parallel + " ( only METHODS or CLASSES supported )" );
+// convert and apply [threadcount] setting
+suite.setThreadCount( Integer.parseInt( threadCount ) );
Review Comment:
I found the default value in TestNG:
`private int m_threadCount = 5;`
We should use the same line as before, means `suite.setThreadCount(
threadCountAsString == null ? 1 : Integer.parseInt( threadCount ) )`
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
[GitHub] [maven-surefire] Tibor17 commented on a diff in pull request #517: [SUREFIRE-2064] Allow all supported values of [parallel] option
Tibor17 commented on code in PR #517:
URL: https://github.com/apache/maven-surefire/pull/517#discussion_r851683061
##
surefire-providers/surefire-testng/src/main/java/org/apache/maven/surefire/testng/conf/TestNG740Configurator.java:
##
@@ -37,33 +36,77 @@
*
* @since 3.0.0-M6
*/
-public class TestNG740Configurator extends TestNG60Configurator
+public class TestNG740Configurator
+extends TestNG60Configurator
{
+/**
+ * Convert and apply the value of the [threadcount] option.
+ *
+ * @param suite TestNG {@link XmlSuite} object
+ * @param options Surefire plugin configuration options
+ * @throws TestSetFailedException if unable to convert specified
[threadcount] setting
+ */
@Override
-public void configure( XmlSuite suite, Map options )
+protected void configureThreadCount( XmlSuite suite, Map
options )
throws TestSetFailedException
{
-String threadCountAsString = options.get( THREADCOUNT_PROP );
-int threadCount = threadCountAsString == null ? 1 : parseInt(
threadCountAsString );
-suite.setThreadCount( threadCount );
-
-String parallel = options.get( PARALLEL_PROP );
-if ( parallel != null )
+String threadCount = options.get( THREADCOUNT_PROP );
+// if [threadcount] spec'd
+if ( threadCount != null )
{
-if ( !"methods".equalsIgnoreCase( parallel ) &&
!"classes".equalsIgnoreCase( parallel ) )
+try
{
-throw new TestSetFailedException( "Unsupported TestNG parallel
setting: "
-+ parallel + " ( only METHODS or CLASSES supported )" );
+// convert and apply [threadcount] setting
+suite.setThreadCount( Integer.parseInt( threadCount ) );
Review Comment:
I found the default value in TestNG:
`private int m_threadCount = 5;`
We should use the same as before, means `suite.setThreadCount(
threadCountAsString == null ? 1 : Integer.parseInt( threadCount ) )`
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
[jira] [Created] (MJAVADOC-714) Upgrade to Maven 3.2.5
Michael Osipov created MJAVADOC-714: --- Summary: Upgrade to Maven 3.2.5 Key: MJAVADOC-714 URL: https://issues.apache.org/jira/browse/MJAVADOC-714 Project: Maven Javadoc Plugin Issue Type: Dependency upgrade Reporter: Michael Osipov Assignee: Michael Osipov Fix For: next-release -- This message was sent by Atlassian Jira (v8.20.1#820001)
[GitHub] [maven-surefire] Tibor17 commented on a diff in pull request #517: [SUREFIRE-2064] Allow all supported values of [parallel] option
Tibor17 commented on code in PR #517:
URL: https://github.com/apache/maven-surefire/pull/517#discussion_r851681413
##
surefire-providers/surefire-testng/src/main/java/org/apache/maven/surefire/testng/conf/TestNG740Configurator.java:
##
@@ -37,33 +36,77 @@
*
* @since 3.0.0-M6
*/
-public class TestNG740Configurator extends TestNG60Configurator
+public class TestNG740Configurator
+extends TestNG60Configurator
{
+/**
+ * Convert and apply the value of the [threadcount] option.
+ *
+ * @param suite TestNG {@link XmlSuite} object
+ * @param options Surefire plugin configuration options
+ * @throws TestSetFailedException if unable to convert specified
[threadcount] setting
+ */
@Override
-public void configure( XmlSuite suite, Map options )
+protected void configureThreadCount( XmlSuite suite, Map
options )
throws TestSetFailedException
{
-String threadCountAsString = options.get( THREADCOUNT_PROP );
-int threadCount = threadCountAsString == null ? 1 : parseInt(
threadCountAsString );
-suite.setThreadCount( threadCount );
-
-String parallel = options.get( PARALLEL_PROP );
-if ( parallel != null )
+String threadCount = options.get( THREADCOUNT_PROP );
+// if [threadcount] spec'd
+if ( threadCount != null )
{
-if ( !"methods".equalsIgnoreCase( parallel ) &&
!"classes".equalsIgnoreCase( parallel ) )
+try
{
-throw new TestSetFailedException( "Unsupported TestNG parallel
setting: "
-+ parallel + " ( only METHODS or CLASSES supported )" );
+// convert and apply [threadcount] setting
+suite.setThreadCount( Integer.parseInt( threadCount ) );
Review Comment:
Previously it was `threadCountAsString == null ? 1 : ...`. What would happen
if parallel=classes but the ThreadCount is not set? How is TestNG implemented?
It has default value 1?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
[jira] [Commented] (MSITE-890) Upgrade Jetty to 9.4.46.v20220331
[ https://issues.apache.org/jira/browse/MSITE-890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17523232#comment-17523232 ] Hudson commented on MSITE-890: -- Build failed in Jenkins: Maven » Maven TLP » maven-site-plugin » master #14 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-site-plugin/job/master/14/ > Upgrade Jetty to 9.4.46.v20220331 > - > > Key: MSITE-890 > URL: https://issues.apache.org/jira/browse/MSITE-890 > Project: Maven Site Plugin > Issue Type: Dependency upgrade >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: 3.12.0 > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (MSITE-891) Upgrade plugins in ITs
[ https://issues.apache.org/jira/browse/MSITE-891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17523233#comment-17523233 ] Hudson commented on MSITE-891: -- Build failed in Jenkins: Maven » Maven TLP » maven-site-plugin » master #14 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-site-plugin/job/master/14/ > Upgrade plugins in ITs > -- > > Key: MSITE-891 > URL: https://issues.apache.org/jira/browse/MSITE-891 > Project: Maven Site Plugin > Issue Type: Dependency upgrade >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: 3.12.0 > > > * Maven Checkstyle Plugin to 3.1.2 > * Maven PMD Plugin to 3.16.0 > * Maven JXR Plugin to 3.2.0 > * Maven Project Info Reports Plugin to 3.2.2 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (MSITE-857) Jetty engine fails to resolve web.xml DTD behind corporate proxy
r.java:347)
> {code}
>
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[GitHub] [maven-javadoc-plugin] michael-o opened a new pull request, #134: start
michael-o opened a new pull request, #134: URL: https://github.com/apache/maven-javadoc-plugin/pull/134 Following this checklist to help us incorporate your contribution quickly and easily: - [ ] Make sure there is a [JIRA issue](https://issues.apache.org/jira/browse/MJAVADOC) filed for the change (usually before you start working on it). Trivial changes like typos do not require a JIRA issue. Your pull request should address just this issue, without pulling in other changes. - [ ] Each commit in the pull request should have a meaningful subject line and body. - [ ] Format the pull request title like `[MJAVADOC-XXX] - Fixes bug in ApproximateQuantiles`, where you replace `MJAVADOC-XXX` with the appropriate JIRA issue. Best practice is to use the JIRA issue title in the pull request title and in the first line of the commit message. - [ ] Write a pull request description that is detailed enough to understand what the pull request does, how, and why. - [ ] Run `mvn clean verify -Prun-its` to make sure basic checks pass. A more thorough check will be performed on your pull request automatically. If your pull request is about ~20 lines of code you don't need to sign an [Individual Contributor License Agreement](https://www.apache.org/licenses/icla.pdf) if you are unsure please ask on the developers list. To make clear that you license your contribution under the [Apache License Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0) you have to acknowledge this by using the following check-box. - [ ] I hereby declare this contribution to be licenced under the [Apache License Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0) - [ ] In any other case, please file an [Apache Individual Contributor License Agreement](https://www.apache.org/licenses/icla.pdf). -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-site-plugin] dependabot[bot] closed pull request #79: Bump mavenVersion from 3.0.5 to 3.8.5
dependabot[bot] closed pull request #79: Bump mavenVersion from 3.0.5 to 3.8.5 URL: https://github.com/apache/maven-site-plugin/pull/79 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-site-plugin] dependabot[bot] commented on pull request #79: Bump mavenVersion from 3.0.5 to 3.8.5
dependabot[bot] commented on PR #79: URL: https://github.com/apache/maven-site-plugin/pull/79#issuecomment-1100754693 Looks like these dependencies are no longer updatable, so this is no longer needed. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (MSITE-888) Upgrade to Maven 3.2.5
[ https://issues.apache.org/jira/browse/MSITE-888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17523226#comment-17523226 ] Hudson commented on MSITE-888: -- Build failed in Jenkins: Maven » Maven TLP » maven-site-plugin » master #15 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-site-plugin/job/master/15/ > Upgrade to Maven 3.2.5 > -- > > Key: MSITE-888 > URL: https://issues.apache.org/jira/browse/MSITE-888 > Project: Maven Site Plugin > Issue Type: Dependency upgrade >Affects Versions: 3.11.0 >Reporter: Michael Osipov >Assignee: Tamás Cservenák >Priority: Major > Fix For: 3.12.0 > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (MSITE-874) Skip site:deploy instead of fail if distributionManagement.site.url is scm:*
[ https://issues.apache.org/jira/browse/MSITE-874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MSITE-874: - Fix Version/s: (was: 3.12.0) > Skip site:deploy instead of fail if distributionManagement.site.url is scm:* > > > Key: MSITE-874 > URL: https://issues.apache.org/jira/browse/MSITE-874 > Project: Maven Site Plugin > Issue Type: Wish > Components: site:deploy >Affects Versions: 3.9.1 >Reporter: Herve Boutemy >Priority: Major > > when deploying to SCM, > [maven-scm-publish-plugin|https://maven.apache.org/plugins/maven-scm-publish-plugin/] > is the way to go > instead of failing, site:deploy could simply skip deploy because it is known: > this would permit simpler config for > https://maven.apache.org/plugins/maven-scm-publish-plugin/examples/one-module-configuration.html > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[GitHub] [maven-site-plugin] michael-o commented on pull request #74: Example of passing ITs for PR #73
michael-o commented on PR #74: URL: https://github.com/apache/maven-site-plugin/pull/74#issuecomment-1100753468 There was a bug in Plexus Utils which is now fixed with: https://github.com/codehaus-plexus/plexus-utils/commit/b99f7c0e46d8b08d63afa4c2c7d274ebf5ebcc94 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-site-plugin] dependabot[bot] commented on pull request #78: Bump jettyVersion from 9.4.44.v20210927 to 11.0.9
dependabot[bot] commented on PR #78: URL: https://github.com/apache/maven-site-plugin/pull/78#issuecomment-1100752746 OK, I won't notify you again about this release, but will get in touch when a new version is available. You can also ignore all major, minor, or patch releases for a dependency by adding an [`ignore` condition](https://docs.github.com/en/code-security/supply-chain-security/configuration-options-for-dependency-updates#ignore) with the desired `update_types` to your config file. If you change your mind, just re-open this PR and I'll resolve any conflicts on it. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-site-plugin] michael-o closed pull request #78: Bump jettyVersion from 9.4.44.v20210927 to 11.0.9
michael-o closed pull request #78: Bump jettyVersion from 9.4.44.v20210927 to 11.0.9 URL: https://github.com/apache/maven-site-plugin/pull/78 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Closed] (MSITE-888) Upgrade to Maven 3.2.5
[ https://issues.apache.org/jira/browse/MSITE-888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed MSITE-888. Resolution: Fixed Fixed with [32be6ad8b99916dec6f908484f2d690044bf0b47|https://gitbox.apache.org/repos/asf?p=maven-site-plugin.git;a=commit;h=32be6ad8b99916dec6f908484f2d690044bf0b47]. > Upgrade to Maven 3.2.5 > -- > > Key: MSITE-888 > URL: https://issues.apache.org/jira/browse/MSITE-888 > Project: Maven Site Plugin > Issue Type: Dependency upgrade >Affects Versions: 3.11.0 >Reporter: Michael Osipov >Assignee: Tamás Cservenák >Priority: Major > Fix For: 3.12.0 > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[GitHub] [maven-site-plugin] asfgit merged pull request #73: Upgrade to maven 3.2.5 + Java8
asfgit merged PR #73: URL: https://github.com/apache/maven-site-plugin/pull/73 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Closed] (MSITE-857) Jetty engine fails to resolve web.xml DTD behind corporate proxy
[
https://issues.apache.org/jira/browse/MSITE-857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed MSITE-857.
Resolution: Fixed
Fixed with
[606a327097202f3f90bfd60e66a7c4cb6a53d004|https://gitbox.apache.org/repos/asf?p=maven-site-plugin.git;a=commit;h=606a327097202f3f90bfd60e66a7c4cb6a53d004].
> Jetty engine fails to resolve web.xml DTD behind corporate proxy
>
>
> Key: MSITE-857
> URL: https://issues.apache.org/jira/browse/MSITE-857
> Project: Maven Site Plugin
> Issue Type: Bug
> Components: site:run
>Affects Versions: 3.9.0
> Environment: Windows 10, Intel 4 cores, 16GB RAM
>Reporter: Valentino Pinna
>Assignee: Michael Osipov
>Priority: Critical
> Fix For: 3.12.0
>
>
> To reproduce, ensure to be behind corporate proxy (with settings.xml
> correctly configured) and execute:
> {code:java}
> mvn -X org.apache.maven.plugins:maven-site-plugin:3.9.0:run
> {code}
> Extract from log:
> {code:java}
> [DEBUG] resolveEntity(-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN,
> http://java.sun.com/dtd/web-app_2_3.dtd)
> [DEBUG] Can't exact match entity in redirect map, trying web-app_2_3.dtd
> [WARNING] Failed startup of context
> o.e.j.w.WebAppContext@523a7801{/,file:///C:/Users/m027907/eclipse-workspace/vtl/target/site-stage/,UNAVAILABLE}
> java.net.ConnectException: Connection timed out: connect
> at java.net.PlainSocketImpl.connect0 (Native Method)
> at java.net.PlainSocketImpl.socketConnect (PlainSocketImpl.java:101)
> at java.net.AbstractPlainSocketImpl.doConnect
> (AbstractPlainSocketImpl.java:399)
> at java.net.AbstractPlainSocketImpl.connectToAddress
> (AbstractPlainSocketImpl.java:242)
> at java.net.AbstractPlainSocketImpl.connect
> (AbstractPlainSocketImpl.java:224)
> at java.net.Socket.connect (Socket.java:609)
> at java.net.Socket.connect (Socket.java:558)
> at sun.net.NetworkClient.doConnect (NetworkClient.java:182)
> at sun.net.www.http.HttpClient.openServer (HttpClient.java:474)
> at sun.net.www.http.HttpClient.openServer (HttpClient.java:569)
> at sun.net.www.http.HttpClient. (HttpClient.java:242)
> at sun.net.www.http.HttpClient.New (HttpClient.java:341)
> at sun.net.www.http.HttpClient.New (HttpClient.java:362)
> at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient
> (HttpURLConnection.java:1248)
> at sun.net.www.protocol.http.HttpURLConnection.plainConnect0
> (HttpURLConnection.java:1187)
> at sun.net.www.protocol.http.HttpURLConnection.plainConnect
> (HttpURLConnection.java:1081)
> at sun.net.www.protocol.http.HttpURLConnection.connect
> (HttpURLConnection.java:1015)
> at sun.net.www.protocol.http.HttpURLConnection.getInputStream0
> (HttpURLConnection.java:1587)
> at sun.net.www.protocol.http.HttpURLConnection.getInputStream
> (HttpURLConnection.java:1515)
> at
> com.sun.org.apache.xerces.internal.impl.XMLEntityManager.setupCurrentEntity
> (XMLEntityManager.java:676)
> at com.sun.org.apache.xerces.internal.impl.XMLEntityManager.startEntity
> (XMLEntityManager.java:1398)
> at
> com.sun.org.apache.xerces.internal.impl.XMLEntityManager.startDTDEntity
> (XMLEntityManager.java:1364)
> at
> com.sun.org.apache.xerces.internal.impl.XMLDTDScannerImpl.setInputSource
> (XMLDTDScannerImpl.java:257)
> at
> com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$DTDDriver.dispatch
> (XMLDocumentScannerImpl.java:1152)
> at
> com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$DTDDriver.next
> (XMLDocumentScannerImpl.java:1040)
> at
> com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$PrologDriver.next
> (XMLDocumentScannerImpl.java:943)
> at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next
> (XMLDocumentScannerImpl.java:605)
> 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:534)
> at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse
> (XML11Configuration.java:888)
> at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse
> (XML11Configuration.java:824)
> 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:1216)
> at
> com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse
> (SAXParserImpl.java:635)
> at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl.parse
> (SAXParserImpl.java:324)
> at org.eclipse.jetty.xml.XmlParser.par
[jira] [Closed] (MSITE-891) Upgrade plugins in ITs
[ https://issues.apache.org/jira/browse/MSITE-891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed MSITE-891. Resolution: Fixed Fixed with [bf434e5d0e37ce85392a96587ad2f4ec58c63641|https://gitbox.apache.org/repos/asf?p=maven-site-plugin.git;a=commit;h=bf434e5d0e37ce85392a96587ad2f4ec58c63641]. > Upgrade plugins in ITs > -- > > Key: MSITE-891 > URL: https://issues.apache.org/jira/browse/MSITE-891 > Project: Maven Site Plugin > Issue Type: Dependency upgrade >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: 3.12.0 > > > * Maven Checkstyle Plugin to 3.1.2 > * Maven PMD Plugin to 3.16.0 > * Maven JXR Plugin to 3.2.0 > * Maven Project Info Reports Plugin to 3.2.2 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Closed] (MSITE-890) Upgrade Jetty to 9.4.46.v20220331
[ https://issues.apache.org/jira/browse/MSITE-890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed MSITE-890. Resolution: Fixed Fixed with [5f10ad146fec988f892a56b82b83e5c41ede3604|https://gitbox.apache.org/repos/asf?p=maven-site-plugin.git;a=commit;h=5f10ad146fec988f892a56b82b83e5c41ede3604]. > Upgrade Jetty to 9.4.46.v20220331 > - > > Key: MSITE-890 > URL: https://issues.apache.org/jira/browse/MSITE-890 > Project: Maven Site Plugin > Issue Type: Dependency upgrade >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: 3.12.0 > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[GitHub] [maven-surefire] Tibor17 commented on pull request #517: [SUREFIRE-2064] Allow all supported values of [parallel] option
Tibor17 commented on PR #517: URL: https://github.com/apache/maven-surefire/pull/517#issuecomment-1100747935 @slawekjaranowski Can you pls help me making a review as well? Pls participate. @sbabcoc Feel free to work on the Parser, pls don't stop. We can introduce it in any PR or here if we are fast. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Created] (MSITE-891) Upgrade plugins in ITs
Michael Osipov created MSITE-891: Summary: Upgrade plugins in ITs Key: MSITE-891 URL: https://issues.apache.org/jira/browse/MSITE-891 Project: Maven Site Plugin Issue Type: Dependency upgrade Reporter: Michael Osipov Assignee: Michael Osipov Fix For: 3.12.0 * Maven Checkstyle Plugin to 3.1.2 * Maven PMD Plugin to 3.16.0 * Maven JXR Plugin to 3.2.0 * Maven Project Info Reports Plugin to 3.2.2 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (MSITE-890) Upgrade Jetty to 9.4.46.v20220331
Michael Osipov created MSITE-890: Summary: Upgrade Jetty to 9.4.46.v20220331 Key: MSITE-890 URL: https://issues.apache.org/jira/browse/MSITE-890 Project: Maven Site Plugin Issue Type: Dependency upgrade Reporter: Michael Osipov Assignee: Michael Osipov Fix For: 3.12.0 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (MSITE-857) Jetty engine fails to resolve web.xml DTD behind corporate proxy
[
https://issues.apache.org/jira/browse/MSITE-857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov reassigned MSITE-857:
Assignee: Michael Osipov
> Jetty engine fails to resolve web.xml DTD behind corporate proxy
>
>
> Key: MSITE-857
> URL: https://issues.apache.org/jira/browse/MSITE-857
> Project: Maven Site Plugin
> Issue Type: Bug
> Components: site:run
>Affects Versions: 3.9.0
> Environment: Windows 10, Intel 4 cores, 16GB RAM
>Reporter: Valentino Pinna
>Assignee: Michael Osipov
>Priority: Critical
>
> To reproduce, ensure to be behind corporate proxy (with settings.xml
> correctly configured) and execute:
> {code:java}
> mvn -X org.apache.maven.plugins:maven-site-plugin:3.9.0:run
> {code}
> Extract from log:
> {code:java}
> [DEBUG] resolveEntity(-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN,
> http://java.sun.com/dtd/web-app_2_3.dtd)
> [DEBUG] Can't exact match entity in redirect map, trying web-app_2_3.dtd
> [WARNING] Failed startup of context
> o.e.j.w.WebAppContext@523a7801{/,file:///C:/Users/m027907/eclipse-workspace/vtl/target/site-stage/,UNAVAILABLE}
> java.net.ConnectException: Connection timed out: connect
> at java.net.PlainSocketImpl.connect0 (Native Method)
> at java.net.PlainSocketImpl.socketConnect (PlainSocketImpl.java:101)
> at java.net.AbstractPlainSocketImpl.doConnect
> (AbstractPlainSocketImpl.java:399)
> at java.net.AbstractPlainSocketImpl.connectToAddress
> (AbstractPlainSocketImpl.java:242)
> at java.net.AbstractPlainSocketImpl.connect
> (AbstractPlainSocketImpl.java:224)
> at java.net.Socket.connect (Socket.java:609)
> at java.net.Socket.connect (Socket.java:558)
> at sun.net.NetworkClient.doConnect (NetworkClient.java:182)
> at sun.net.www.http.HttpClient.openServer (HttpClient.java:474)
> at sun.net.www.http.HttpClient.openServer (HttpClient.java:569)
> at sun.net.www.http.HttpClient. (HttpClient.java:242)
> at sun.net.www.http.HttpClient.New (HttpClient.java:341)
> at sun.net.www.http.HttpClient.New (HttpClient.java:362)
> at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient
> (HttpURLConnection.java:1248)
> at sun.net.www.protocol.http.HttpURLConnection.plainConnect0
> (HttpURLConnection.java:1187)
> at sun.net.www.protocol.http.HttpURLConnection.plainConnect
> (HttpURLConnection.java:1081)
> at sun.net.www.protocol.http.HttpURLConnection.connect
> (HttpURLConnection.java:1015)
> at sun.net.www.protocol.http.HttpURLConnection.getInputStream0
> (HttpURLConnection.java:1587)
> at sun.net.www.protocol.http.HttpURLConnection.getInputStream
> (HttpURLConnection.java:1515)
> at
> com.sun.org.apache.xerces.internal.impl.XMLEntityManager.setupCurrentEntity
> (XMLEntityManager.java:676)
> at com.sun.org.apache.xerces.internal.impl.XMLEntityManager.startEntity
> (XMLEntityManager.java:1398)
> at
> com.sun.org.apache.xerces.internal.impl.XMLEntityManager.startDTDEntity
> (XMLEntityManager.java:1364)
> at
> com.sun.org.apache.xerces.internal.impl.XMLDTDScannerImpl.setInputSource
> (XMLDTDScannerImpl.java:257)
> at
> com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$DTDDriver.dispatch
> (XMLDocumentScannerImpl.java:1152)
> at
> com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$DTDDriver.next
> (XMLDocumentScannerImpl.java:1040)
> at
> com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$PrologDriver.next
> (XMLDocumentScannerImpl.java:943)
> at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next
> (XMLDocumentScannerImpl.java:605)
> 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:534)
> at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse
> (XML11Configuration.java:888)
> at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse
> (XML11Configuration.java:824)
> 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:1216)
> at
> com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse
> (SAXParserImpl.java:635)
> at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl.parse
> (SAXParserImpl.java:324)
> at org.eclipse.jetty.xml.XmlParser.parse (XmlParser.java:244)
> at org.eclipse.jetty.webapp.Descriptor.parse (Descriptor.java:53)
> at org.eclipse.jetty.webapp.WebDescriptor.parse (WebDescriptor.java:213)
> at o
[jira] [Updated] (MSITE-857) Jetty engine fails to resolve web.xml DTD behind corporate proxy
[
https://issues.apache.org/jira/browse/MSITE-857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MSITE-857:
-
Fix Version/s: 3.12.0
> Jetty engine fails to resolve web.xml DTD behind corporate proxy
>
>
> Key: MSITE-857
> URL: https://issues.apache.org/jira/browse/MSITE-857
> Project: Maven Site Plugin
> Issue Type: Bug
> Components: site:run
>Affects Versions: 3.9.0
> Environment: Windows 10, Intel 4 cores, 16GB RAM
>Reporter: Valentino Pinna
>Assignee: Michael Osipov
>Priority: Critical
> Fix For: 3.12.0
>
>
> To reproduce, ensure to be behind corporate proxy (with settings.xml
> correctly configured) and execute:
> {code:java}
> mvn -X org.apache.maven.plugins:maven-site-plugin:3.9.0:run
> {code}
> Extract from log:
> {code:java}
> [DEBUG] resolveEntity(-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN,
> http://java.sun.com/dtd/web-app_2_3.dtd)
> [DEBUG] Can't exact match entity in redirect map, trying web-app_2_3.dtd
> [WARNING] Failed startup of context
> o.e.j.w.WebAppContext@523a7801{/,file:///C:/Users/m027907/eclipse-workspace/vtl/target/site-stage/,UNAVAILABLE}
> java.net.ConnectException: Connection timed out: connect
> at java.net.PlainSocketImpl.connect0 (Native Method)
> at java.net.PlainSocketImpl.socketConnect (PlainSocketImpl.java:101)
> at java.net.AbstractPlainSocketImpl.doConnect
> (AbstractPlainSocketImpl.java:399)
> at java.net.AbstractPlainSocketImpl.connectToAddress
> (AbstractPlainSocketImpl.java:242)
> at java.net.AbstractPlainSocketImpl.connect
> (AbstractPlainSocketImpl.java:224)
> at java.net.Socket.connect (Socket.java:609)
> at java.net.Socket.connect (Socket.java:558)
> at sun.net.NetworkClient.doConnect (NetworkClient.java:182)
> at sun.net.www.http.HttpClient.openServer (HttpClient.java:474)
> at sun.net.www.http.HttpClient.openServer (HttpClient.java:569)
> at sun.net.www.http.HttpClient. (HttpClient.java:242)
> at sun.net.www.http.HttpClient.New (HttpClient.java:341)
> at sun.net.www.http.HttpClient.New (HttpClient.java:362)
> at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient
> (HttpURLConnection.java:1248)
> at sun.net.www.protocol.http.HttpURLConnection.plainConnect0
> (HttpURLConnection.java:1187)
> at sun.net.www.protocol.http.HttpURLConnection.plainConnect
> (HttpURLConnection.java:1081)
> at sun.net.www.protocol.http.HttpURLConnection.connect
> (HttpURLConnection.java:1015)
> at sun.net.www.protocol.http.HttpURLConnection.getInputStream0
> (HttpURLConnection.java:1587)
> at sun.net.www.protocol.http.HttpURLConnection.getInputStream
> (HttpURLConnection.java:1515)
> at
> com.sun.org.apache.xerces.internal.impl.XMLEntityManager.setupCurrentEntity
> (XMLEntityManager.java:676)
> at com.sun.org.apache.xerces.internal.impl.XMLEntityManager.startEntity
> (XMLEntityManager.java:1398)
> at
> com.sun.org.apache.xerces.internal.impl.XMLEntityManager.startDTDEntity
> (XMLEntityManager.java:1364)
> at
> com.sun.org.apache.xerces.internal.impl.XMLDTDScannerImpl.setInputSource
> (XMLDTDScannerImpl.java:257)
> at
> com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$DTDDriver.dispatch
> (XMLDocumentScannerImpl.java:1152)
> at
> com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$DTDDriver.next
> (XMLDocumentScannerImpl.java:1040)
> at
> com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$PrologDriver.next
> (XMLDocumentScannerImpl.java:943)
> at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next
> (XMLDocumentScannerImpl.java:605)
> 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:534)
> at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse
> (XML11Configuration.java:888)
> at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse
> (XML11Configuration.java:824)
> 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:1216)
> at
> com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse
> (SAXParserImpl.java:635)
> at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl.parse
> (SAXParserImpl.java:324)
> at org.eclipse.jetty.xml.XmlParser.parse (XmlParser.java:244)
> at org.eclipse.jetty.webapp.Descriptor.parse (Descriptor.java:53)
> at org.eclipse.jetty.webapp.WebDescriptor.parse (WebDescripto
[jira] [Commented] (MSITE-889) Upgrade Plexus Utils to 3.3.1
[ https://issues.apache.org/jira/browse/MSITE-889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17523196#comment-17523196 ] Hudson commented on MSITE-889: -- Build failed in Jenkins: Maven » Maven TLP » maven-site-plugin » master #13 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-site-plugin/job/master/13/ > Upgrade Plexus Utils to 3.3.1 > - > > Key: MSITE-889 > URL: https://issues.apache.org/jira/browse/MSITE-889 > Project: Maven Site Plugin > Issue Type: Dependency upgrade >Affects Versions: 3.11.0 >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: 3.12.0 > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Closed] (MSITE-889) Upgrade Plexus Utils to 3.3.1
[ https://issues.apache.org/jira/browse/MSITE-889?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed MSITE-889. Resolution: Fixed Fixed with [522eddd70e4b822d8a14eba845c94b3f88edef7e|https://gitbox.apache.org/repos/asf?p=maven-site-plugin.git;a=commit;h=522eddd70e4b822d8a14eba845c94b3f88edef7e]. > Upgrade Plexus Utils to 3.3.1 > - > > Key: MSITE-889 > URL: https://issues.apache.org/jira/browse/MSITE-889 > Project: Maven Site Plugin > Issue Type: Dependency upgrade >Affects Versions: 3.11.0 >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: 3.12.0 > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (MSITE-886) Upgrade Maven Wagon to 3.5.1
[ https://issues.apache.org/jira/browse/MSITE-886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17523191#comment-17523191 ] Hudson commented on MSITE-886: -- Build failed in Jenkins: Maven » Maven TLP » maven-site-plugin » master #12 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-site-plugin/job/master/12/ > Upgrade Maven Wagon to 3.5.1 > > > Key: MSITE-886 > URL: https://issues.apache.org/jira/browse/MSITE-886 > Project: Maven Site Plugin > Issue Type: Dependency upgrade >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: 3.12.0 > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (MSITE-887) Deprecate templateFile parameter
[ https://issues.apache.org/jira/browse/MSITE-887?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17523192#comment-17523192 ] Hudson commented on MSITE-887: -- Build failed in Jenkins: Maven » Maven TLP » maven-site-plugin » master #12 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-site-plugin/job/master/12/ > Deprecate templateFile parameter > > > Key: MSITE-887 > URL: https://issues.apache.org/jira/browse/MSITE-887 > Project: Maven Site Plugin > Issue Type: Task > Components: doxia integration >Affects Versions: 3.11.0 >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: 3.12.0 > > > Doxia 2 will remove support for templates files and will only support skins > from JARs, no template files. We are going to deprecate this parameter for > removal. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (MSITE-884) Drop/replace usage of Commons Lang 3
[ https://issues.apache.org/jira/browse/MSITE-884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17523189#comment-17523189 ] Hudson commented on MSITE-884: -- Build failed in Jenkins: Maven » Maven TLP » maven-site-plugin » master #12 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-site-plugin/job/master/12/ > Drop/replace usage of Commons Lang 3 > > > Key: MSITE-884 > URL: https://issues.apache.org/jira/browse/MSITE-884 > Project: Maven Site Plugin > Issue Type: Task >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: 3.12.0 > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (MSITE-885) Upgrade Commons IO to 2.11.0
[ https://issues.apache.org/jira/browse/MSITE-885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17523190#comment-17523190 ] Hudson commented on MSITE-885: -- Build failed in Jenkins: Maven » Maven TLP » maven-site-plugin » master #12 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-site-plugin/job/master/12/ > Upgrade Commons IO to 2.11.0 > > > Key: MSITE-885 > URL: https://issues.apache.org/jira/browse/MSITE-885 > Project: Maven Site Plugin > Issue Type: Dependency upgrade >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: 3.12.0 > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (MSITE-889) Upgrade Plexus Utils to 3.3.1
Michael Osipov created MSITE-889: Summary: Upgrade Plexus Utils to 3.3.1 Key: MSITE-889 URL: https://issues.apache.org/jira/browse/MSITE-889 Project: Maven Site Plugin Issue Type: Dependency upgrade Affects Versions: 3.11.0 Reporter: Michael Osipov Assignee: Michael Osipov Fix For: 3.12.0 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (MSITE-888) Upgrade to Maven 3.2.5
Michael Osipov created MSITE-888: Summary: Upgrade to Maven 3.2.5 Key: MSITE-888 URL: https://issues.apache.org/jira/browse/MSITE-888 Project: Maven Site Plugin Issue Type: Dependency upgrade Affects Versions: 3.11.0 Reporter: Michael Osipov Assignee: Tamás Cservenák Fix For: 3.12.0 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Closed] (MSITE-887) Deprecate templateFile parameter
[ https://issues.apache.org/jira/browse/MSITE-887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed MSITE-887. Resolution: Fixed Fixed with [d1bfb429cc41a79fbbeaed3fa725fbcb9cd9285d|https://gitbox.apache.org/repos/asf?p=maven-site-plugin.git;a=commit;h=d1bfb429cc41a79fbbeaed3fa725fbcb9cd9285d]. > Deprecate templateFile parameter > > > Key: MSITE-887 > URL: https://issues.apache.org/jira/browse/MSITE-887 > Project: Maven Site Plugin > Issue Type: Task > Components: doxia integration >Affects Versions: 3.11.0 >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: 3.12.0 > > > Doxia 2 will remove support for templates files and will only support skins > from JARs, no template files. We are going to deprecate this parameter for > removal. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Closed] (MSITE-885) Upgrade Commons IO to 2.11.0
[ https://issues.apache.org/jira/browse/MSITE-885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed MSITE-885. Resolution: Fixed Fixed with [628f5b3a315ddd3431dd00bee5d0d81b666e353d|https://gitbox.apache.org/repos/asf?p=maven-site-plugin.git;a=commit;h=628f5b3a315ddd3431dd00bee5d0d81b666e353d]. > Upgrade Commons IO to 2.11.0 > > > Key: MSITE-885 > URL: https://issues.apache.org/jira/browse/MSITE-885 > Project: Maven Site Plugin > Issue Type: Dependency upgrade >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: 3.12.0 > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Closed] (MSITE-884) Drop/replace usage of Commons Lang 3
[ https://issues.apache.org/jira/browse/MSITE-884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed MSITE-884. Resolution: Fixed Fixed with [8382743ceaf55dc1f4695e12ed8d3a1e2917a2c9|https://gitbox.apache.org/repos/asf?p=maven-site-plugin.git;a=commit;h=8382743ceaf55dc1f4695e12ed8d3a1e2917a2c9]. > Drop/replace usage of Commons Lang 3 > > > Key: MSITE-884 > URL: https://issues.apache.org/jira/browse/MSITE-884 > Project: Maven Site Plugin > Issue Type: Task >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: 3.12.0 > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Closed] (MSITE-886) Upgrade Maven Wagon to 3.5.1
[ https://issues.apache.org/jira/browse/MSITE-886?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed MSITE-886. Resolution: Fixed Fixed with [7a3ed19c5ff6339615b997d97dcfbae926dfbad1|https://gitbox.apache.org/repos/asf?p=maven-site-plugin.git;a=commit;h=7a3ed19c5ff6339615b997d97dcfbae926dfbad1]. > Upgrade Maven Wagon to 3.5.1 > > > Key: MSITE-886 > URL: https://issues.apache.org/jira/browse/MSITE-886 > Project: Maven Site Plugin > Issue Type: Dependency upgrade >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: 3.12.0 > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (MSITE-887) Deprecate templateFile parameter
Michael Osipov created MSITE-887: Summary: Deprecate templateFile parameter Key: MSITE-887 URL: https://issues.apache.org/jira/browse/MSITE-887 Project: Maven Site Plugin Issue Type: Task Components: doxia integration Affects Versions: 3.11.0 Reporter: Michael Osipov Assignee: Michael Osipov Fix For: 3.12.0 Doxia 2 will remove support for templates files and will only support skins from JARs, no template files. We are going to deprecate this parameter for removal. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[GitHub] [maven-surefire] sbabcoc commented on pull request #517: [SUREFIRE-2064] Allow all supported values of [parallel] option
sbabcoc commented on PR #517: URL: https://github.com/apache/maven-surefire/pull/517#issuecomment-1100729707 Resolves #517 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-surefire] sbabcoc commented on pull request #517: [SUREFIRE-2064] Allow all supported values of [parallel] option
sbabcoc commented on PR #517: URL: https://github.com/apache/maven-surefire/pull/517#issuecomment-1100727903 @Tibor17: The revisions in this PR have been squashed to a single commit. Thanks for all your efforts on this project! -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Closed] (MSITE-829) Upgrade Jetty to 9.4.x
[ https://issues.apache.org/jira/browse/MSITE-829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed MSITE-829. > Upgrade Jetty to 9.4.x > -- > > Key: MSITE-829 > URL: https://issues.apache.org/jira/browse/MSITE-829 > Project: Maven Site Plugin > Issue Type: Dependency upgrade >Reporter: Olivier Lamy >Assignee: Olivier Lamy >Priority: Major > Fix For: 3.12.0 > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Closed] (MSITE-828) Upgrade to Java 8
[ https://issues.apache.org/jira/browse/MSITE-828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed MSITE-828. > Upgrade to Java 8 > - > > Key: MSITE-828 > URL: https://issues.apache.org/jira/browse/MSITE-828 > Project: Maven Site Plugin > Issue Type: Task >Reporter: Olivier Lamy >Assignee: Olivier Lamy >Priority: Major > Fix For: 3.12.0 > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (MSITE-886) Upgrade Maven Wagon to 3.5.1
Michael Osipov created MSITE-886: Summary: Upgrade Maven Wagon to 3.5.1 Key: MSITE-886 URL: https://issues.apache.org/jira/browse/MSITE-886 Project: Maven Site Plugin Issue Type: Dependency upgrade Reporter: Michael Osipov Assignee: Michael Osipov Fix For: 3.12.0 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (MSITE-885) Upgrade Commons IO to 2.11.0
Michael Osipov created MSITE-885: Summary: Upgrade Commons IO to 2.11.0 Key: MSITE-885 URL: https://issues.apache.org/jira/browse/MSITE-885 Project: Maven Site Plugin Issue Type: Dependency upgrade Reporter: Michael Osipov Assignee: Michael Osipov Fix For: 3.12.0 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (MSITE-884) Drop/replace usage of Commons Lang 3
Michael Osipov created MSITE-884: Summary: Drop/replace usage of Commons Lang 3 Key: MSITE-884 URL: https://issues.apache.org/jira/browse/MSITE-884 Project: Maven Site Plugin Issue Type: Task Reporter: Michael Osipov Assignee: Michael Osipov Fix For: 3.12.0 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (MNG-7454) Include resolver-transport-http in Maven
[
https://issues.apache.org/jira/browse/MNG-7454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17523160#comment-17523160
]
Hudson commented on MNG-7454:
-
Build succeeded in Jenkins: Maven » Maven TLP » maven » master #32
See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/master/32/
> Include resolver-transport-http in Maven
>
>
> Key: MNG-7454
> URL: https://issues.apache.org/jira/browse/MNG-7454
> Project: Maven
> Issue Type: New Feature
> Components: Dependencies
>Reporter: Tamás Cservenák
>Assignee: Tamás Cservenák
>Priority: Major
> Fix For: 3.9.0, 4.0.0-alpha-1, 4.0.0
>
>
> We should include maven-resolver-transport-http (along with existing
> maven-resolver-transport-wagon) but retain Wagon as default transport, while
> offer ability for users to use http transport to utilize new resolver
> features like "smart checksums".
> On positive side, this will finally get rid of shaded httpClient and
> wagon-http-shaded as well.
> To switch transport use {{-Dmaven.resolver.transport}} with following values:
> * {{wagon}} - to use wagon (is default as well)
> * {{native}} - to use resolver own highly optimized HTTP and FILE transport
> (supports "smart checksums")
> * {{auto}} - to rely on resolver own discovery, or if another transport
> extension used
> The selected transport can be seen in debug (-X) output on line `[DEBUG]
> Using transporter XXX...`
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (MNG-7454) Include resolver-transport-http in Maven
[
https://issues.apache.org/jira/browse/MNG-7454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17523151#comment-17523151
]
Hudson commented on MNG-7454:
-
Build succeeded in Jenkins: Maven » Maven TLP » maven » maven-3.9.x #18
See
https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/maven-3.9.x/18/
> Include resolver-transport-http in Maven
>
>
> Key: MNG-7454
> URL: https://issues.apache.org/jira/browse/MNG-7454
> Project: Maven
> Issue Type: New Feature
> Components: Dependencies
>Reporter: Tamás Cservenák
>Assignee: Tamás Cservenák
>Priority: Major
> Fix For: 3.9.0, 4.0.0-alpha-1, 4.0.0
>
>
> We should include maven-resolver-transport-http (along with existing
> maven-resolver-transport-wagon) but retain Wagon as default transport, while
> offer ability for users to use http transport to utilize new resolver
> features like "smart checksums".
> On positive side, this will finally get rid of shaded httpClient and
> wagon-http-shaded as well.
> To switch transport use {{-Dmaven.resolver.transport}} with following values:
> * {{wagon}} - to use wagon (is default as well)
> * {{native}} - to use resolver own highly optimized HTTP and FILE transport
> (supports "smart checksums")
> * {{auto}} - to rely on resolver own discovery, or if another transport
> extension used
> The selected transport can be seen in debug (-X) output on line `[DEBUG]
> Using transporter XXX...`
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (MJAVADOC-700) Plugin duplicates classes in Java 8 all-classes lists
[
https://issues.apache.org/jira/browse/MJAVADOC-700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17523144#comment-17523144
]
Michael Osipov commented on MJAVADOC-700:
-
My fix does not work. Windows fails.
> Plugin duplicates classes in Java 8 all-classes lists
> --
>
> Key: MJAVADOC-700
> URL: https://issues.apache.org/jira/browse/MJAVADOC-700
> Project: Maven Javadoc Plugin
> Issue Type: Bug
>Affects Versions: 3.3.0, 3.3.1
>Reporter: Rob Spoor
>Priority: Major
>
> Versions 3.3.0 and 3.3.1 of the Javadoc Plugin create allclasses-frame.html
> and allclasses-noframe.html files that duplicate all classes, interfaces, etc.
> To reproduce:
> * Clone https://github.com/robtimus/data-url (a simple and small project that
> can be used to showcase the issue)
> * Run {{mvn javadoc:javadoc}}, which uses version 3.2.0
> * Check target/site/apidocs/allclasses-frame.html - no duplicates
> * Run {{mvn javadoc:javadoc -Dversion.plugin.javadoc=3.3.0}} to build the
> same with version 3.3.0
> * Check target/site/apidocs/allclasses-frame.html - all classes are duplicated
> The same issue occurs with {{javadoc:aggregate}}, possibly others as well.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Closed] (MPOM-316) Upgrade ASF Parent to 26
[ https://issues.apache.org/jira/browse/MPOM-316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Slawomir Jaranowski closed MPOM-316. Resolution: Fixed > Upgrade ASF Parent to 26 > > > Key: MPOM-316 > URL: https://issues.apache.org/jira/browse/MPOM-316 > Project: Maven POMs > Issue Type: Dependency upgrade > Components: maven >Reporter: Slawomir Jaranowski >Assignee: Slawomir Jaranowski >Priority: Major > Fix For: MAVEN-36 > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[GitHub] [maven-parent] slawekjaranowski merged pull request #62: Bump apache from 25 to 26
slawekjaranowski merged PR #62: URL: https://github.com/apache/maven-parent/pull/62 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Updated] (MNG-7454) Include resolver-transport-http in Maven
[
https://issues.apache.org/jira/browse/MNG-7454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tamás Cservenák updated MNG-7454:
-
Description:
We should include maven-resolver-transport-http (along with existing
maven-resolver-transport-wagon) but retain Wagon as default transport, while
offer ability for users to use http transport to utilize new resolver features
like "smart checksums".
On positive side, this will finally get rid of shaded httpClient and
wagon-http-shaded as well.
To switch transport use {{-Dmaven.resolver.transport}} with following values:
* {{wagon}} - to use wagon (is default as well)
* {{native}} - to use resolver own highly optimized HTTP and FILE transport
(supports "smart checksums")
* {{auto}} - to rely on resolver own discovery, or if another transport
extension used
The selected transport can be seen in debug (-X) output on line `[DEBUG] Using
transporter XXX...`
was:
We should include maven-resolver-transport-http (along with existing
maven-resolver-transport-wagon) but retain Wagon as default transport, while
offer ability for users to use http transport to utilize new resolver features
like "smart checksums".
On positive side, this will finally get rid of shaded httpClient and
wagon-http-shaded as well.
> Include resolver-transport-http in Maven
>
>
> Key: MNG-7454
> URL: https://issues.apache.org/jira/browse/MNG-7454
> Project: Maven
> Issue Type: New Feature
> Components: Dependencies
>Reporter: Tamás Cservenák
>Assignee: Tamás Cservenák
>Priority: Major
> Fix For: 3.9.0, 4.0.0-alpha-1, 4.0.0
>
>
> We should include maven-resolver-transport-http (along with existing
> maven-resolver-transport-wagon) but retain Wagon as default transport, while
> offer ability for users to use http transport to utilize new resolver
> features like "smart checksums".
> On positive side, this will finally get rid of shaded httpClient and
> wagon-http-shaded as well.
> To switch transport use {{-Dmaven.resolver.transport}} with following values:
> * {{wagon}} - to use wagon (is default as well)
> * {{native}} - to use resolver own highly optimized HTTP and FILE transport
> (supports "smart checksums")
> * {{auto}} - to rely on resolver own discovery, or if another transport
> extension used
> The selected transport can be seen in debug (-X) output on line `[DEBUG]
> Using transporter XXX...`
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Comment Edited] (MJAVADOC-700) Plugin duplicates classes in Java 8 all-classes lists
[
https://issues.apache.org/jira/browse/MJAVADOC-700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17523140#comment-17523140
]
Michael Osipov edited comment on MJAVADOC-700 at 4/16/22 4:24 PM:
--
I can confirm this:
{noformat}
commit 55982df63f8de5bfbb48aee353bc29b35b1c6a2c
Author: rfscholte
Date: Mon May 17 22:50:04 2021 +0200
[MJAVADOC-584] excludePackageNames is not working as documented anymore
{noformat}
[~rfscholte], WDYT?
I am currently evaluating
{noformat}
diff --git a/src/main/java/org/apache/maven/plugins/javadoc/JavadocUtil.java
b/src/main/java/org/apache/maven/plugins/javadoc/JavadocUtil.java
index 0e5eda01..3f9cb2b5 100644
--- a/src/main/java/org/apache/maven/plugins/javadoc/JavadocUtil.java
+++ b/src/main/java/org/apache/maven/plugins/javadoc/JavadocUtil.java
@@ -379,7 +379,7 @@ public class JavadocUtil
if ( !excluded )
{
-files.add( file.replace( '\\', '/' ) );
+files.add( file.replace( '\\', File.separatorChar ) );
}
}
{noformat}
was (Author: michael-o):
I can confirm this:
{noformat}
commit 55982df63f8de5bfbb48aee353bc29b35b1c6a2c
Author: rfscholte
Date: Mon May 17 22:50:04 2021 +0200
[MJAVADOC-584] excludePackageNames is not working as documented anymore
{noformat}
[~rfscholte], WDYT?
I am currently evaluating
{noformat}
diff --git a/src/main/java/org/apache/maven/plugins/javadoc/JavadocUtil.java
b/src/main/java/org/apache/maven/plugins/javadoc/JavadocUtil.java
index 0e5eda01..3f9cb2b5 100644
--- a/src/main/java/org/apache/maven/plugins/javadoc/JavadocUtil.java
+++ b/src/main/java/org/apache/maven/plugins/javadoc/JavadocUtil.java
@@ -379,7 +379,7 @@ public class JavadocUtil
if ( !excluded )
{
-files.add( file.replace( '\\', '/' ) );
+files.add( file.replace( '\\', File.separatorChar ) );^M
}
}
{noformat}
> Plugin duplicates classes in Java 8 all-classes lists
> --
>
> Key: MJAVADOC-700
> URL: https://issues.apache.org/jira/browse/MJAVADOC-700
> Project: Maven Javadoc Plugin
> Issue Type: Bug
>Affects Versions: 3.3.0, 3.3.1
>Reporter: Rob Spoor
>Priority: Major
>
> Versions 3.3.0 and 3.3.1 of the Javadoc Plugin create allclasses-frame.html
> and allclasses-noframe.html files that duplicate all classes, interfaces, etc.
> To reproduce:
> * Clone https://github.com/robtimus/data-url (a simple and small project that
> can be used to showcase the issue)
> * Run {{mvn javadoc:javadoc}}, which uses version 3.2.0
> * Check target/site/apidocs/allclasses-frame.html - no duplicates
> * Run {{mvn javadoc:javadoc -Dversion.plugin.javadoc=3.3.0}} to build the
> same with version 3.3.0
> * Check target/site/apidocs/allclasses-frame.html - all classes are duplicated
> The same issue occurs with {{javadoc:aggregate}}, possibly others as well.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (MJAVADOC-700) Plugin duplicates classes in Java 8 all-classes lists
[
https://issues.apache.org/jira/browse/MJAVADOC-700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17523140#comment-17523140
]
Michael Osipov commented on MJAVADOC-700:
-
I can confirm this:
{noformat}
commit 55982df63f8de5bfbb48aee353bc29b35b1c6a2c
Author: rfscholte
Date: Mon May 17 22:50:04 2021 +0200
[MJAVADOC-584] excludePackageNames is not working as documented anymore
{noformat}
[~rfscholte], WDYT?
I am currently evaluating
{noformat}
diff --git a/src/main/java/org/apache/maven/plugins/javadoc/JavadocUtil.java
b/src/main/java/org/apache/maven/plugins/javadoc/JavadocUtil.java
index 0e5eda01..3f9cb2b5 100644
--- a/src/main/java/org/apache/maven/plugins/javadoc/JavadocUtil.java
+++ b/src/main/java/org/apache/maven/plugins/javadoc/JavadocUtil.java
@@ -379,7 +379,7 @@ public class JavadocUtil
if ( !excluded )
{
-files.add( file.replace( '\\', '/' ) );
+files.add( file.replace( '\\', File.separatorChar ) );^M
}
}
{noformat}
> Plugin duplicates classes in Java 8 all-classes lists
> --
>
> Key: MJAVADOC-700
> URL: https://issues.apache.org/jira/browse/MJAVADOC-700
> Project: Maven Javadoc Plugin
> Issue Type: Bug
>Affects Versions: 3.3.0, 3.3.1
>Reporter: Rob Spoor
>Priority: Major
>
> Versions 3.3.0 and 3.3.1 of the Javadoc Plugin create allclasses-frame.html
> and allclasses-noframe.html files that duplicate all classes, interfaces, etc.
> To reproduce:
> * Clone https://github.com/robtimus/data-url (a simple and small project that
> can be used to showcase the issue)
> * Run {{mvn javadoc:javadoc}}, which uses version 3.2.0
> * Check target/site/apidocs/allclasses-frame.html - no duplicates
> * Run {{mvn javadoc:javadoc -Dversion.plugin.javadoc=3.3.0}} to build the
> same with version 3.3.0
> * Check target/site/apidocs/allclasses-frame.html - all classes are duplicated
> The same issue occurs with {{javadoc:aggregate}}, possibly others as well.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[GitHub] [maven] cstamas merged pull request #720: [MNG-7454] Include resolver-transport-http in Maven
cstamas merged PR #720: URL: https://github.com/apache/maven/pull/720 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (MJAVADOC-696) Invalid anchors in Javadoc and plugin mojo
[
https://issues.apache.org/jira/browse/MJAVADOC-696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17523137#comment-17523137
]
Michael Osipov commented on MJAVADOC-696:
-
I understood that. Whatever is {{@Parameter}} is mostly private and linking to
private is going into nirvana.
> Invalid anchors in Javadoc and plugin mojo
> --
>
> Key: MJAVADOC-696
> URL: https://issues.apache.org/jira/browse/MJAVADOC-696
> Project: Maven Javadoc Plugin
> Issue Type: Bug
> Components: javadoc
>Affects Versions: 3.3.1
>Reporter: Olivier Cailloux
>Assignee: Michael Osipov
>Priority: Minor
> Fix For: next-release
>
>
> The
> [documentation|https://maven.apache.org/plugins/maven-javadoc-plugin/javadoc-mojo.html#detectJavaApiLink]
> of {{detectJavaApiLink}} mentions: {{See Javadoc for the default values}},
> linking to
> {{https://maven.apache.org/plugins/maven-javadoc-plugin/apidocs/org/apache/maven/plugins/javadoc/AbstractJavadocMojo.html#DEFAULT_JAVA_API_LINKS}}.
> This anchor does not exist currently.
> Relatedly, several references in the [AbstractJavadocMojo javadoc
> page|https://maven.apache.org/plugins/maven-javadoc-plugin/apidocs/org/apache/maven/plugins/javadoc/AbstractJavadocMojo.html]
> do not exist, for example, the references called {{detectJavaApiLink}} or
> {{javaApiLinks}}.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (MJAVADOC-696) Invalid anchors in Javadoc and plugin mojo
[
https://issues.apache.org/jira/browse/MJAVADOC-696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17523136#comment-17523136
]
Olivier Cailloux commented on MJAVADOC-696:
---
I see (and thanks for the update, anyway). I guess that the title of this issue
was a poor choice of mine, then. What I meant with this issue really was that
documentation is currently missing about which javadoc links are used when
using detectJavaApiLink.
> Invalid anchors in Javadoc and plugin mojo
> --
>
> Key: MJAVADOC-696
> URL: https://issues.apache.org/jira/browse/MJAVADOC-696
> Project: Maven Javadoc Plugin
> Issue Type: Bug
> Components: javadoc
>Affects Versions: 3.3.1
>Reporter: Olivier Cailloux
>Assignee: Michael Osipov
>Priority: Minor
> Fix For: next-release
>
>
> The
> [documentation|https://maven.apache.org/plugins/maven-javadoc-plugin/javadoc-mojo.html#detectJavaApiLink]
> of {{detectJavaApiLink}} mentions: {{See Javadoc for the default values}},
> linking to
> {{https://maven.apache.org/plugins/maven-javadoc-plugin/apidocs/org/apache/maven/plugins/javadoc/AbstractJavadocMojo.html#DEFAULT_JAVA_API_LINKS}}.
> This anchor does not exist currently.
> Relatedly, several references in the [AbstractJavadocMojo javadoc
> page|https://maven.apache.org/plugins/maven-javadoc-plugin/apidocs/org/apache/maven/plugins/javadoc/AbstractJavadocMojo.html]
> do not exist, for example, the references called {{detectJavaApiLink}} or
> {{javaApiLinks}}.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (MJAVADOC-696) Invalid anchors in Javadoc and plugin mojo
[
https://issues.apache.org/jira/browse/MJAVADOC-696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17523133#comment-17523133
]
Michael Osipov commented on MJAVADOC-696:
-
I have only updated the source code, generation will happen at release only.
Removing them is the only way to solve this because Javadoc does not show
anything below {{protected}}, this making the links dead. Where is the point in
having them if they are not accessible?
> Invalid anchors in Javadoc and plugin mojo
> --
>
> Key: MJAVADOC-696
> URL: https://issues.apache.org/jira/browse/MJAVADOC-696
> Project: Maven Javadoc Plugin
> Issue Type: Bug
> Components: javadoc
>Affects Versions: 3.3.1
>Reporter: Olivier Cailloux
>Assignee: Michael Osipov
>Priority: Minor
> Fix For: next-release
>
>
> The
> [documentation|https://maven.apache.org/plugins/maven-javadoc-plugin/javadoc-mojo.html#detectJavaApiLink]
> of {{detectJavaApiLink}} mentions: {{See Javadoc for the default values}},
> linking to
> {{https://maven.apache.org/plugins/maven-javadoc-plugin/apidocs/org/apache/maven/plugins/javadoc/AbstractJavadocMojo.html#DEFAULT_JAVA_API_LINKS}}.
> This anchor does not exist currently.
> Relatedly, several references in the [AbstractJavadocMojo javadoc
> page|https://maven.apache.org/plugins/maven-javadoc-plugin/apidocs/org/apache/maven/plugins/javadoc/AbstractJavadocMojo.html]
> do not exist, for example, the references called {{detectJavaApiLink}} or
> {{javaApiLinks}}.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (MJAVADOC-696) Invalid anchors in Javadoc and plugin mojo
[
https://issues.apache.org/jira/browse/MJAVADOC-696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17523128#comment-17523128
]
Olivier Cailloux commented on MJAVADOC-696:
---
It does not seem to me that the proposed fix solves the stated problem, in
particular, the first part of the description. The documentation of
detectJavaApiLink still mentions: See Javadoc for the default values, linking
to
https://maven.apache.org/plugins/maven-javadoc-plugin/apidocs/org/apache/maven/plugins/javadoc/AbstractJavadocMojo.html#DEFAULT_JAVA_API_LINKS.
This anchor still does not exist.
Please note that the intent of this request is for the reader to be able to
effectively find which values are used. Solving the dead links by removing the
links is not really a solution…
Please tell me if I missed something.
> Invalid anchors in Javadoc and plugin mojo
> --
>
> Key: MJAVADOC-696
> URL: https://issues.apache.org/jira/browse/MJAVADOC-696
> Project: Maven Javadoc Plugin
> Issue Type: Bug
> Components: javadoc
>Affects Versions: 3.3.1
>Reporter: Olivier Cailloux
>Assignee: Michael Osipov
>Priority: Minor
> Fix For: next-release
>
>
> The
> [documentation|https://maven.apache.org/plugins/maven-javadoc-plugin/javadoc-mojo.html#detectJavaApiLink]
> of {{detectJavaApiLink}} mentions: {{See Javadoc for the default values}},
> linking to
> {{https://maven.apache.org/plugins/maven-javadoc-plugin/apidocs/org/apache/maven/plugins/javadoc/AbstractJavadocMojo.html#DEFAULT_JAVA_API_LINKS}}.
> This anchor does not exist currently.
> Relatedly, several references in the [AbstractJavadocMojo javadoc
> page|https://maven.apache.org/plugins/maven-javadoc-plugin/apidocs/org/apache/maven/plugins/javadoc/AbstractJavadocMojo.html]
> do not exist, for example, the references called {{detectJavaApiLink}} or
> {{javaApiLinks}}.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (MJAVADOC-696) Invalid anchors in Javadoc and plugin mojo
[
https://issues.apache.org/jira/browse/MJAVADOC-696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17523127#comment-17523127
]
Hudson commented on MJAVADOC-696:
-
Build succeeded in Jenkins: Maven » Maven TLP » maven-javadoc-plugin » master
#15
See
https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-javadoc-plugin/job/master/15/
> Invalid anchors in Javadoc and plugin mojo
> --
>
> Key: MJAVADOC-696
> URL: https://issues.apache.org/jira/browse/MJAVADOC-696
> Project: Maven Javadoc Plugin
> Issue Type: Bug
> Components: javadoc
>Affects Versions: 3.3.1
>Reporter: Olivier Cailloux
>Assignee: Michael Osipov
>Priority: Minor
> Fix For: next-release
>
>
> The
> [documentation|https://maven.apache.org/plugins/maven-javadoc-plugin/javadoc-mojo.html#detectJavaApiLink]
> of {{detectJavaApiLink}} mentions: {{See Javadoc for the default values}},
> linking to
> {{https://maven.apache.org/plugins/maven-javadoc-plugin/apidocs/org/apache/maven/plugins/javadoc/AbstractJavadocMojo.html#DEFAULT_JAVA_API_LINKS}}.
> This anchor does not exist currently.
> Relatedly, several references in the [AbstractJavadocMojo javadoc
> page|https://maven.apache.org/plugins/maven-javadoc-plugin/apidocs/org/apache/maven/plugins/javadoc/AbstractJavadocMojo.html]
> do not exist, for example, the references called {{detectJavaApiLink}} or
> {{javaApiLinks}}.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (MJAVADOC-685) Stylesheet "maven" does look ugly
[
https://issues.apache.org/jira/browse/MJAVADOC-685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17523126#comment-17523126
]
Michael Osipov commented on MJAVADOC-685:
-
Not only the CSS would go, but also the {{stylesheet}} parameter.
> Stylesheet "maven" does look ugly
> -
>
> Key: MJAVADOC-685
> URL: https://issues.apache.org/jira/browse/MJAVADOC-685
> Project: Maven Javadoc Plugin
> Issue Type: Improvement
>Affects Versions: 3.3.0
>Reporter: Konrad Windszus
>Priority: Major
> Attachments: Screenshot 2021-07-25 at 10.55.44.png
>
>
> When configuring m-javadoc-p 3.3.0 with stylesheet {{maven}} (according to
> https://maven.apache.org/plugins/maven-javadoc-plugin/examples/stylesheet-configuration.html)
> it only loads the simple CSS from
> https://github.com/apache/maven-javadoc-plugin/blob/master/src/main/resources/org/apache/maven/plugins/javadoc/css/stylesheet.css
> which has only very few styling options and is not suited for styling the
> markup emitted by javadoc correctly. This affects both JDK8 and JDK11.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Closed] (MJAVADOC-696) Invalid anchors in Javadoc and plugin mojo
[
https://issues.apache.org/jira/browse/MJAVADOC-696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed MJAVADOC-696.
---
Resolution: Fixed
Fixed with
[506cb74e6abc4b108121b0c586a15b75dd5ccc39|https://gitbox.apache.org/repos/asf?p=maven-javadoc-plugin.git;a=commit;h=506cb74e6abc4b108121b0c586a15b75dd5ccc39].
> Invalid anchors in Javadoc and plugin mojo
> --
>
> Key: MJAVADOC-696
> URL: https://issues.apache.org/jira/browse/MJAVADOC-696
> Project: Maven Javadoc Plugin
> Issue Type: Bug
> Components: javadoc
>Affects Versions: 3.3.1
>Reporter: Olivier Cailloux
>Assignee: Michael Osipov
>Priority: Minor
> Fix For: next-release
>
>
> The
> [documentation|https://maven.apache.org/plugins/maven-javadoc-plugin/javadoc-mojo.html#detectJavaApiLink]
> of {{detectJavaApiLink}} mentions: {{See Javadoc for the default values}},
> linking to
> {{https://maven.apache.org/plugins/maven-javadoc-plugin/apidocs/org/apache/maven/plugins/javadoc/AbstractJavadocMojo.html#DEFAULT_JAVA_API_LINKS}}.
> This anchor does not exist currently.
> Relatedly, several references in the [AbstractJavadocMojo javadoc
> page|https://maven.apache.org/plugins/maven-javadoc-plugin/apidocs/org/apache/maven/plugins/javadoc/AbstractJavadocMojo.html]
> do not exist, for example, the references called {{detectJavaApiLink}} or
> {{javaApiLinks}}.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (MNG-7438) add execution id to "Configuring mojo xxx with basic configurator" debug message
[
https://issues.apache.org/jira/browse/MNG-7438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17523123#comment-17523123
]
Hudson commented on MNG-7438:
-
Build succeeded in Jenkins: Maven » Maven TLP » maven » PR-565 #14
See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/PR-565/14/
> add execution id to "Configuring mojo xxx with basic configurator" debug
> message
>
>
> Key: MNG-7438
> URL: https://issues.apache.org/jira/browse/MNG-7438
> Project: Maven
> Issue Type: Improvement
> Components: Core
>Affects Versions: 3.8.5
>Reporter: Herve Boutemy
>Assignee: Herve Boutemy
>Priority: Major
> Fix For: 3.9.0, 4.0.0-alpha-1, 4.0.0
>
>
> currently, when running goals/mojos, we have in debug logs
> {noformat}
> [INFO] --- maven-surefire-plugin:3.0.0-M5:test (default-test) @
> org.example.apache.maven.execution ---
> [DEBUG] Configuring mojo
> org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M5:test from plugin
> realm
> ClassRealm[plugin>org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M5,
> parent: sun.misc.Launcher$AppClassLoader@7852e922]
> [DEBUG] Configuring mojo
> 'org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M5:test' with basic
> configurator -->
> [DEBUG] (s) additionalClasspathElements = []
> [DEBUG] (s) basedir = /home/herve/tmp/org.example.apache.maven.execution
> {noformat}
> on the "{{Configuring mojo
> 'org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M5:test' with basic
> configurator}}" line, it completely hides the fact that configuration is
> valid for an execution id, that has a default value when nobody defined any
> (see https://maven.apache.org/guides/mini/guide-default-execution-ids.html )
> Just adding "{{execution 'default-test'}}" would make things more clear so
> people learn about execution ids
> {noformat}
> [DEBUG] Configuring mojo
> 'org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M5:test' execution
> 'default-test' with basic configurator -->
> {noformat}
> h2. final debug messages
> {noformat}
> [DEBUG] Loading mojo
> org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M5:test from plugin
> realm
> ClassRealm[plugin>org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M5,
> parent: sun.misc.Launcher$AppClassLoader@7852e922]
> [DEBUG] Configuring mojo execution
> 'org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M5:test:default-test'
> with basic configurator -->
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (MNG-7438) add execution id to "Configuring mojo xxx with basic configurator" debug message
[
https://issues.apache.org/jira/browse/MNG-7438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17523122#comment-17523122
]
Hudson commented on MNG-7438:
-
Build succeeded in Jenkins: Maven » Maven TLP » maven » PR-691 #9
See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/PR-691/9/
> add execution id to "Configuring mojo xxx with basic configurator" debug
> message
>
>
> Key: MNG-7438
> URL: https://issues.apache.org/jira/browse/MNG-7438
> Project: Maven
> Issue Type: Improvement
> Components: Core
>Affects Versions: 3.8.5
>Reporter: Herve Boutemy
>Assignee: Herve Boutemy
>Priority: Major
> Fix For: 3.9.0, 4.0.0-alpha-1, 4.0.0
>
>
> currently, when running goals/mojos, we have in debug logs
> {noformat}
> [INFO] --- maven-surefire-plugin:3.0.0-M5:test (default-test) @
> org.example.apache.maven.execution ---
> [DEBUG] Configuring mojo
> org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M5:test from plugin
> realm
> ClassRealm[plugin>org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M5,
> parent: sun.misc.Launcher$AppClassLoader@7852e922]
> [DEBUG] Configuring mojo
> 'org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M5:test' with basic
> configurator -->
> [DEBUG] (s) additionalClasspathElements = []
> [DEBUG] (s) basedir = /home/herve/tmp/org.example.apache.maven.execution
> {noformat}
> on the "{{Configuring mojo
> 'org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M5:test' with basic
> configurator}}" line, it completely hides the fact that configuration is
> valid for an execution id, that has a default value when nobody defined any
> (see https://maven.apache.org/guides/mini/guide-default-execution-ids.html )
> Just adding "{{execution 'default-test'}}" would make things more clear so
> people learn about execution ids
> {noformat}
> [DEBUG] Configuring mojo
> 'org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M5:test' execution
> 'default-test' with basic configurator -->
> {noformat}
> h2. final debug messages
> {noformat}
> [DEBUG] Loading mojo
> org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M5:test from plugin
> realm
> ClassRealm[plugin>org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M5,
> parent: sun.misc.Launcher$AppClassLoader@7852e922]
> [DEBUG] Configuring mojo execution
> 'org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M5:test:default-test'
> with basic configurator -->
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (MNG-7438) add execution id to "Configuring mojo xxx with basic configurator" debug message
[
https://issues.apache.org/jira/browse/MNG-7438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17523121#comment-17523121
]
Hudson commented on MNG-7438:
-
Build unstable in Jenkins: Maven » Maven TLP » maven » PR-509 #14
See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/PR-509/14/
> add execution id to "Configuring mojo xxx with basic configurator" debug
> message
>
>
> Key: MNG-7438
> URL: https://issues.apache.org/jira/browse/MNG-7438
> Project: Maven
> Issue Type: Improvement
> Components: Core
>Affects Versions: 3.8.5
>Reporter: Herve Boutemy
>Assignee: Herve Boutemy
>Priority: Major
> Fix For: 3.9.0, 4.0.0-alpha-1, 4.0.0
>
>
> currently, when running goals/mojos, we have in debug logs
> {noformat}
> [INFO] --- maven-surefire-plugin:3.0.0-M5:test (default-test) @
> org.example.apache.maven.execution ---
> [DEBUG] Configuring mojo
> org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M5:test from plugin
> realm
> ClassRealm[plugin>org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M5,
> parent: sun.misc.Launcher$AppClassLoader@7852e922]
> [DEBUG] Configuring mojo
> 'org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M5:test' with basic
> configurator -->
> [DEBUG] (s) additionalClasspathElements = []
> [DEBUG] (s) basedir = /home/herve/tmp/org.example.apache.maven.execution
> {noformat}
> on the "{{Configuring mojo
> 'org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M5:test' with basic
> configurator}}" line, it completely hides the fact that configuration is
> valid for an execution id, that has a default value when nobody defined any
> (see https://maven.apache.org/guides/mini/guide-default-execution-ids.html )
> Just adding "{{execution 'default-test'}}" would make things more clear so
> people learn about execution ids
> {noformat}
> [DEBUG] Configuring mojo
> 'org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M5:test' execution
> 'default-test' with basic configurator -->
> {noformat}
> h2. final debug messages
> {noformat}
> [DEBUG] Loading mojo
> org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M5:test from plugin
> realm
> ClassRealm[plugin>org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M5,
> parent: sun.misc.Launcher$AppClassLoader@7852e922]
> [DEBUG] Configuring mojo execution
> 'org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M5:test:default-test'
> with basic configurator -->
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (MNG-7438) add execution id to "Configuring mojo xxx with basic configurator" debug message
[
https://issues.apache.org/jira/browse/MNG-7438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17523118#comment-17523118
]
Hudson commented on MNG-7438:
-
Build succeeded in Jenkins: Maven » Maven TLP » maven » PR-600 #14
See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/PR-600/14/
> add execution id to "Configuring mojo xxx with basic configurator" debug
> message
>
>
> Key: MNG-7438
> URL: https://issues.apache.org/jira/browse/MNG-7438
> Project: Maven
> Issue Type: Improvement
> Components: Core
>Affects Versions: 3.8.5
>Reporter: Herve Boutemy
>Assignee: Herve Boutemy
>Priority: Major
> Fix For: 3.9.0, 4.0.0-alpha-1, 4.0.0
>
>
> currently, when running goals/mojos, we have in debug logs
> {noformat}
> [INFO] --- maven-surefire-plugin:3.0.0-M5:test (default-test) @
> org.example.apache.maven.execution ---
> [DEBUG] Configuring mojo
> org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M5:test from plugin
> realm
> ClassRealm[plugin>org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M5,
> parent: sun.misc.Launcher$AppClassLoader@7852e922]
> [DEBUG] Configuring mojo
> 'org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M5:test' with basic
> configurator -->
> [DEBUG] (s) additionalClasspathElements = []
> [DEBUG] (s) basedir = /home/herve/tmp/org.example.apache.maven.execution
> {noformat}
> on the "{{Configuring mojo
> 'org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M5:test' with basic
> configurator}}" line, it completely hides the fact that configuration is
> valid for an execution id, that has a default value when nobody defined any
> (see https://maven.apache.org/guides/mini/guide-default-execution-ids.html )
> Just adding "{{execution 'default-test'}}" would make things more clear so
> people learn about execution ids
> {noformat}
> [DEBUG] Configuring mojo
> 'org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M5:test' execution
> 'default-test' with basic configurator -->
> {noformat}
> h2. final debug messages
> {noformat}
> [DEBUG] Loading mojo
> org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M5:test from plugin
> realm
> ClassRealm[plugin>org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M5,
> parent: sun.misc.Launcher$AppClassLoader@7852e922]
> [DEBUG] Configuring mojo execution
> 'org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M5:test:default-test'
> with basic configurator -->
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (MNG-7438) add execution id to "Configuring mojo xxx with basic configurator" debug message
[
https://issues.apache.org/jira/browse/MNG-7438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17523117#comment-17523117
]
Hudson commented on MNG-7438:
-
Build succeeded in Jenkins: Maven » Maven TLP » maven » PR-721 #2
See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/PR-721/2/
> add execution id to "Configuring mojo xxx with basic configurator" debug
> message
>
>
> Key: MNG-7438
> URL: https://issues.apache.org/jira/browse/MNG-7438
> Project: Maven
> Issue Type: Improvement
> Components: Core
>Affects Versions: 3.8.5
>Reporter: Herve Boutemy
>Assignee: Herve Boutemy
>Priority: Major
> Fix For: 3.9.0, 4.0.0-alpha-1, 4.0.0
>
>
> currently, when running goals/mojos, we have in debug logs
> {noformat}
> [INFO] --- maven-surefire-plugin:3.0.0-M5:test (default-test) @
> org.example.apache.maven.execution ---
> [DEBUG] Configuring mojo
> org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M5:test from plugin
> realm
> ClassRealm[plugin>org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M5,
> parent: sun.misc.Launcher$AppClassLoader@7852e922]
> [DEBUG] Configuring mojo
> 'org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M5:test' with basic
> configurator -->
> [DEBUG] (s) additionalClasspathElements = []
> [DEBUG] (s) basedir = /home/herve/tmp/org.example.apache.maven.execution
> {noformat}
> on the "{{Configuring mojo
> 'org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M5:test' with basic
> configurator}}" line, it completely hides the fact that configuration is
> valid for an execution id, that has a default value when nobody defined any
> (see https://maven.apache.org/guides/mini/guide-default-execution-ids.html )
> Just adding "{{execution 'default-test'}}" would make things more clear so
> people learn about execution ids
> {noformat}
> [DEBUG] Configuring mojo
> 'org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M5:test' execution
> 'default-test' with basic configurator -->
> {noformat}
> h2. final debug messages
> {noformat}
> [DEBUG] Loading mojo
> org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M5:test from plugin
> realm
> ClassRealm[plugin>org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M5,
> parent: sun.misc.Launcher$AppClassLoader@7852e922]
> [DEBUG] Configuring mojo execution
> 'org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M5:test:default-test'
> with basic configurator -->
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (MNG-7438) add execution id to "Configuring mojo xxx with basic configurator" debug message
[
https://issues.apache.org/jira/browse/MNG-7438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17523116#comment-17523116
]
Hudson commented on MNG-7438:
-
Build unstable in Jenkins: Maven » Maven TLP » maven » PR-394 #15
See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/PR-394/15/
> add execution id to "Configuring mojo xxx with basic configurator" debug
> message
>
>
> Key: MNG-7438
> URL: https://issues.apache.org/jira/browse/MNG-7438
> Project: Maven
> Issue Type: Improvement
> Components: Core
>Affects Versions: 3.8.5
>Reporter: Herve Boutemy
>Assignee: Herve Boutemy
>Priority: Major
> Fix For: 3.9.0, 4.0.0-alpha-1, 4.0.0
>
>
> currently, when running goals/mojos, we have in debug logs
> {noformat}
> [INFO] --- maven-surefire-plugin:3.0.0-M5:test (default-test) @
> org.example.apache.maven.execution ---
> [DEBUG] Configuring mojo
> org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M5:test from plugin
> realm
> ClassRealm[plugin>org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M5,
> parent: sun.misc.Launcher$AppClassLoader@7852e922]
> [DEBUG] Configuring mojo
> 'org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M5:test' with basic
> configurator -->
> [DEBUG] (s) additionalClasspathElements = []
> [DEBUG] (s) basedir = /home/herve/tmp/org.example.apache.maven.execution
> {noformat}
> on the "{{Configuring mojo
> 'org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M5:test' with basic
> configurator}}" line, it completely hides the fact that configuration is
> valid for an execution id, that has a default value when nobody defined any
> (see https://maven.apache.org/guides/mini/guide-default-execution-ids.html )
> Just adding "{{execution 'default-test'}}" would make things more clear so
> people learn about execution ids
> {noformat}
> [DEBUG] Configuring mojo
> 'org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M5:test' execution
> 'default-test' with basic configurator -->
> {noformat}
> h2. final debug messages
> {noformat}
> [DEBUG] Loading mojo
> org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M5:test from plugin
> realm
> ClassRealm[plugin>org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M5,
> parent: sun.misc.Launcher$AppClassLoader@7852e922]
> [DEBUG] Configuring mojo execution
> 'org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M5:test:default-test'
> with basic configurator -->
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (MJAVADOC-696) Invalid anchors in Javadoc and plugin mojo
[
https://issues.apache.org/jira/browse/MJAVADOC-696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MJAVADOC-696:
Summary: Invalid anchors in Javadoc and plugin mojo (was: Default values
for detectJavaApiLink)
> Invalid anchors in Javadoc and plugin mojo
> --
>
> Key: MJAVADOC-696
> URL: https://issues.apache.org/jira/browse/MJAVADOC-696
> Project: Maven Javadoc Plugin
> Issue Type: Bug
> Components: javadoc
>Affects Versions: 3.3.1
>Reporter: Olivier Cailloux
>Assignee: Michael Osipov
>Priority: Minor
> Fix For: next-release
>
>
> The
> [documentation|https://maven.apache.org/plugins/maven-javadoc-plugin/javadoc-mojo.html#detectJavaApiLink]
> of {{detectJavaApiLink}} mentions: {{See Javadoc for the default values}},
> linking to
> {{https://maven.apache.org/plugins/maven-javadoc-plugin/apidocs/org/apache/maven/plugins/javadoc/AbstractJavadocMojo.html#DEFAULT_JAVA_API_LINKS}}.
> This anchor does not exist currently.
> Relatedly, several references in the [AbstractJavadocMojo javadoc
> page|https://maven.apache.org/plugins/maven-javadoc-plugin/apidocs/org/apache/maven/plugins/javadoc/AbstractJavadocMojo.html]
> do not exist, for example, the references called {{detectJavaApiLink}} or
> {{javaApiLinks}}.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[GitHub] [maven] slawekjaranowski commented on pull request #722: [MNG-5222] Improvement in deprecated params detection
slawekjaranowski commented on PR #722: URL: https://github.com/apache/maven/pull/722#issuecomment-1100660353 PR description updated. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-integration-testing] michael-o commented on a diff in pull request #151: [MNG-5222] Improvement in deprecated params detection
michael-o commented on code in PR #151:
URL:
https://github.com/apache/maven-integration-testing/pull/151#discussion_r851625439
##
core-it-support/core-it-plugins/maven-it-plugin-configuration/src/main/java/org/apache/maven/plugin/coreit/DeprecatedConfigMojo.java:
##
@@ -47,6 +48,18 @@
@Parameter( defaultValue = "${basedir}", readonly = true )
private File basedir;
+/**
+ * @deprecated bean read only
+ */
+@Parameter( defaultValue = "${project.artifact}", readonly = true )
+private Artifact deprecatedBeanReadOnly;
+
+/**
+ * @deprecated bean
+ */
+@Parameter( defaultValue = "${project.artifact}" )
+private Artifact deprecatedBean;
Review Comment:
I see, there is one space too much
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
[jira] [Assigned] (MJAVADOC-696) Default values for detectJavaApiLink
[
https://issues.apache.org/jira/browse/MJAVADOC-696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov reassigned MJAVADOC-696:
---
Assignee: Michael Osipov
> Default values for detectJavaApiLink
>
>
> Key: MJAVADOC-696
> URL: https://issues.apache.org/jira/browse/MJAVADOC-696
> Project: Maven Javadoc Plugin
> Issue Type: Bug
> Components: javadoc
>Affects Versions: 3.3.1
>Reporter: Olivier Cailloux
>Assignee: Michael Osipov
>Priority: Minor
>
> The
> [documentation|https://maven.apache.org/plugins/maven-javadoc-plugin/javadoc-mojo.html#detectJavaApiLink]
> of {{detectJavaApiLink}} mentions: {{See Javadoc for the default values}},
> linking to
> {{https://maven.apache.org/plugins/maven-javadoc-plugin/apidocs/org/apache/maven/plugins/javadoc/AbstractJavadocMojo.html#DEFAULT_JAVA_API_LINKS}}.
> This anchor does not exist currently.
> Relatedly, several references in the [AbstractJavadocMojo javadoc
> page|https://maven.apache.org/plugins/maven-javadoc-plugin/apidocs/org/apache/maven/plugins/javadoc/AbstractJavadocMojo.html]
> do not exist, for example, the references called {{detectJavaApiLink}} or
> {{javaApiLinks}}.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (MJAVADOC-696) Default values for detectJavaApiLink
[
https://issues.apache.org/jira/browse/MJAVADOC-696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MJAVADOC-696:
Fix Version/s: next-release
> Default values for detectJavaApiLink
>
>
> Key: MJAVADOC-696
> URL: https://issues.apache.org/jira/browse/MJAVADOC-696
> Project: Maven Javadoc Plugin
> Issue Type: Bug
> Components: javadoc
>Affects Versions: 3.3.1
>Reporter: Olivier Cailloux
>Assignee: Michael Osipov
>Priority: Minor
> Fix For: next-release
>
>
> The
> [documentation|https://maven.apache.org/plugins/maven-javadoc-plugin/javadoc-mojo.html#detectJavaApiLink]
> of {{detectJavaApiLink}} mentions: {{See Javadoc for the default values}},
> linking to
> {{https://maven.apache.org/plugins/maven-javadoc-plugin/apidocs/org/apache/maven/plugins/javadoc/AbstractJavadocMojo.html#DEFAULT_JAVA_API_LINKS}}.
> This anchor does not exist currently.
> Relatedly, several references in the [AbstractJavadocMojo javadoc
> page|https://maven.apache.org/plugins/maven-javadoc-plugin/apidocs/org/apache/maven/plugins/javadoc/AbstractJavadocMojo.html]
> do not exist, for example, the references called {{detectJavaApiLink}} or
> {{javaApiLinks}}.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (MJAVADOC-696) Default values for detectJavaApiLink
[
https://issues.apache.org/jira/browse/MJAVADOC-696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17523094#comment-17523094
]
Michael Osipov commented on MJAVADOC-696:
-
193ff34935bd9ebb60613dfc37c42e33b8017169 has removed that property/anchor.
> Default values for detectJavaApiLink
>
>
> Key: MJAVADOC-696
> URL: https://issues.apache.org/jira/browse/MJAVADOC-696
> Project: Maven Javadoc Plugin
> Issue Type: Bug
> Components: javadoc
>Affects Versions: 3.3.1
>Reporter: Olivier Cailloux
>Priority: Minor
>
> The
> [documentation|https://maven.apache.org/plugins/maven-javadoc-plugin/javadoc-mojo.html#detectJavaApiLink]
> of {{detectJavaApiLink}} mentions: {{See Javadoc for the default values}},
> linking to
> {{https://maven.apache.org/plugins/maven-javadoc-plugin/apidocs/org/apache/maven/plugins/javadoc/AbstractJavadocMojo.html#DEFAULT_JAVA_API_LINKS}}.
> This anchor does not exist currently.
> Relatedly, several references in the [AbstractJavadocMojo javadoc
> page|https://maven.apache.org/plugins/maven-javadoc-plugin/apidocs/org/apache/maven/plugins/javadoc/AbstractJavadocMojo.html]
> do not exist, for example, the references called {{detectJavaApiLink}} or
> {{javaApiLinks}}.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[GitHub] [maven-integration-testing] slawekjaranowski commented on a diff in pull request #151: [MNG-5222] Improvement in deprecated params detection
slawekjaranowski commented on code in PR #151:
URL:
https://github.com/apache/maven-integration-testing/pull/151#discussion_r851624698
##
core-it-support/core-it-plugins/maven-it-plugin-configuration/src/main/java/org/apache/maven/plugin/coreit/DeprecatedConfigMojo.java:
##
@@ -47,6 +48,18 @@
@Parameter( defaultValue = "${basedir}", readonly = true )
private File basedir;
+/**
+ * @deprecated bean read only
+ */
+@Parameter( defaultValue = "${project.artifact}", readonly = true )
+private Artifact deprecatedBeanReadOnly;
+
+/**
+ * @deprecated bean
+ */
+@Parameter( defaultValue = "${project.artifact}" )
+private Artifact deprecatedBean;
Review Comment:
It is corner case when internal value, project object is used as property
without read only flags.
Such parameter should not generated warning.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
[GitHub] [maven-integration-testing] slawekjaranowski commented on a diff in pull request #151: [MNG-5222] Improvement in deprecated params detection
slawekjaranowski commented on code in PR #151:
URL:
https://github.com/apache/maven-integration-testing/pull/151#discussion_r851624623
##
core-it-suite/src/test/java/org/apache/maven/it/MavenITmng5222MojoDeprecatedParamsTest.java:
##
@@ -35,7 +35,7 @@
{
public MavenITmng5222MojoDeprecatedParamsTest()
{
-super( "[3.9.0,)" );
+super( "[4.0.0-alpha-1,)" );
Review Comment:
When this change will be merged with current fix to Maven master test on 3.9
will fail.
I will restore it with together cherry pick/port change to 3.9.x branch of
Maven core.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
[jira] [Updated] (MJAVADOC-713) Skipping Javadoc reportset leaves empty Javadoc link in site
[ https://issues.apache.org/jira/browse/MJAVADOC-713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MJAVADOC-713: Fix Version/s: waiting-for-feedback > Skipping Javadoc reportset leaves empty Javadoc link in site > > > Key: MJAVADOC-713 > URL: https://issues.apache.org/jira/browse/MJAVADOC-713 > Project: Maven Javadoc Plugin > Issue Type: Bug >Affects Versions: 3.3.0 >Reporter: Joshua >Priority: Major > Fix For: waiting-for-feedback > > Attachments: image-2022-04-15-17-47-49-771.png > > > I am trying to skip a reportset that is inherited from a parent pom > This is what the report plugin looks like in the parent pom > > org.apache.maven.plugins > maven-javadoc-plugin > > > javadoc-no-fork > > javadoc-no-fork > > > > test-javadoc-no-fork > > test-javadoc-no-fork > > > package > > > > > I don't want the test-javadoc-no-fork report in my project > > If I do this in my pom > > org.apache.maven.plugins > maven-javadoc-plugin > > > test-javadoc-no-fork > > true > > > > > > It will skip the Javadoc generation but still adds a link to site and when > you click on the link you get a 404 since the test Javadoc wasn't inherited. > !image-2022-04-15-17-47-49-771.png! > I logged this as a defect because I would think skip would prevent the > Javadoc generation and NOT add a link to the site for a report set that > wasn't generated. > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (MJAVADOC-713) Skipping Javadoc reportset leaves empty Javadoc link in site
[ https://issues.apache.org/jira/browse/MJAVADOC-713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17523090#comment-17523090 ] Michael Osipov commented on MJAVADOC-713: - Provide a sample project. > Skipping Javadoc reportset leaves empty Javadoc link in site > > > Key: MJAVADOC-713 > URL: https://issues.apache.org/jira/browse/MJAVADOC-713 > Project: Maven Javadoc Plugin > Issue Type: Bug >Affects Versions: 3.3.0 >Reporter: Joshua >Priority: Major > Attachments: image-2022-04-15-17-47-49-771.png > > > I am trying to skip a reportset that is inherited from a parent pom > This is what the report plugin looks like in the parent pom > > org.apache.maven.plugins > maven-javadoc-plugin > > > javadoc-no-fork > > javadoc-no-fork > > > > test-javadoc-no-fork > > test-javadoc-no-fork > > > package > > > > > I don't want the test-javadoc-no-fork report in my project > > If I do this in my pom > > org.apache.maven.plugins > maven-javadoc-plugin > > > test-javadoc-no-fork > > true > > > > > > It will skip the Javadoc generation but still adds a link to site and when > you click on the link you get a 404 since the test Javadoc wasn't inherited. > !image-2022-04-15-17-47-49-771.png! > I logged this as a defect because I would think skip would prevent the > Javadoc generation and NOT add a link to the site for a report set that > wasn't generated. > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Closed] (MJAVADOC-669) Generated javadoc JARs contain jQuery and other MIT-licenced works without reproducing a copy of the MIT licence, same for GPL-licenced works
[
https://issues.apache.org/jira/browse/MJAVADOC-669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed MJAVADOC-669.
---
Resolution: Not A Bug
Basically, this has been partially addressed by the OpenJDK team, there is
nothing we can do about. Closing.
> Generated javadoc JARs contain jQuery and other MIT-licenced works without
> reproducing a copy of the MIT licence, same for GPL-licenced works
> -
>
> Key: MJAVADOC-669
> URL: https://issues.apache.org/jira/browse/MJAVADOC-669
> Project: Maven Javadoc Plugin
> Issue Type: Bug
> Components: javadoc
>Affects Versions: 3.2.0
>Reporter: Thorsten Glaser
>Priority: Blocker
> Labels: legal, licensing
>
> A javadoc JAR generated by the Maven Javadoc Plugin 3.2.0 contains multiple
> components under the MIT licence:
> * jQuery 3.5.1
> ** {{jquery/external/jquery/jquery.js}}
> ** {{jquery/jquery-3.5.1.js}} (duplicate of the above, blowing up the PKZIP
> archive size of the JAR, why is it included like this?)
> * JSZip 3.2.1
> ** {{jquery/jszip/dist/jszip.js}}
> ** {{jquery/jszip-utils/dist/jszip-utils-ie.js}}
> ** {{jquery/jszip-utils/dist/jszip-utils.js}}
> * jQuery UI 1.12.1
> ** {{jquery/jquery-ui.css}}
> ** {{jquery/jquery-ui.js}}
> ** {{jquery/jquery-ui.structure.css}}
> * and their respective minified versions
> It also contains {{script.js}} and {{search.js}} which are
> GPLv2-with-Classpath-exception-licenced and refer to “as provided by Oracle
> in the LICENSE file that accompanied this code” but no such file accompanies
> said code.
> There are also multiple static {{resources}} and {{jquery/images}} whose
> licence is not documented.
> The MIT licence specifically *requires* that “The […] copyright notice and
> this permission notice [the licence body] shall be included in all copies or
> substantial portions of the Software.” The distribution PKZIP archives (JAR
> files) created by the Maven Javadoc Plugin violate this licence, making them
> not redistributable.
> Similarily, the GPLv2 used by the Oracle-provided files *requires* that
> redistributors “give any other recipients of the Program a copy of this
> License along with the Program.” The “if not, write to the Free Software
> Foundation” comment is specifically *not sufficient* for this and only
> provided as fallback should distributors violate this clause, as Maven
> Javadoc Plugin-generated PKZIP archives do. To be effective, the Classpath
> exception must also be provided.
> h2. Suggested fix
> Include the following new files:
> * {{jquery/LICENCE}} containing the MIT licence and all respective copyright
> notices for the various jQuery-related projects (including those _they_
> include, i.e. Sizzle, widget.js, position.js, keycode.js, unique-id.js,
> widgets/autocomplete.js, widgets/menu.js, pako, and possibly others)
> * {{js/LICENSE}} (creating a new subdirectory) containing the Classpath
> exception as provided by Oracle
> * {{COPYING}} or {{js/COPYING}} (this being the customary name for this
> file) containing the verbatim text of the GNU GPL version 2
> * Ideally, add a top-level {{LICENCE}} file pointing out those three and
> briefly documenting the licence of all other non-generated files and state
> all other files are generated from the original project and share its licence
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Closed] (MJAVADOC-708) How to get javadoc "locale" configuration from a Taglet in jdk9
[ https://issues.apache.org/jira/browse/MJAVADOC-708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed MJAVADOC-708. --- Resolution: Information Provided You should rather ask the OpenJDK javadoc mailing list whether this is possible at all. If not, nothing can be exposed through this plugin. > How to get javadoc "locale" configuration from a Taglet in jdk9 > --- > > Key: MJAVADOC-708 > URL: https://issues.apache.org/jira/browse/MJAVADOC-708 > Project: Maven Javadoc Plugin > Issue Type: Wish > Components: javadoc >Affects Versions: 3.3.2 >Reporter: DavidHsing >Priority: Trivial > Labels: locale > > I'm writting a target class which extends from jdk.javadoc.doclet.Taglet, > this taglet needs to display multilingual “” in javadoc. > Is there any way to detect the "locale" configuration of > maven-javadoc-plugin,? > Thanks very much! -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Closed] (MJAVADOC-695) Default link to Java 17 API is dead
[
https://issues.apache.org/jira/browse/MJAVADOC-695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed MJAVADOC-695.
---
Fix Version/s: (was: next-release)
Resolution: Not A Problem
>From Java 16, this is done automatically:
>https://github.com/openjdk/jdk/commit/1e8e543b#diff-42c90a8eded4f2fafe6386521e56956312a33016f23ce8a8316ff10f8bc358fe
> Default link to Java 17 API is dead
> ---
>
> Key: MJAVADOC-695
> URL: https://issues.apache.org/jira/browse/MJAVADOC-695
> Project: Maven Javadoc Plugin
> Issue Type: Bug
> Components: javadoc
>Affects Versions: 3.3.1
>Reporter: Olivier Cailloux
>Assignee: Michael Osipov
>Priority: Minor
>
> The default base url to the Java 17 API, used by
> [detectJavaApiLink|https://maven.apache.org/plugins/maven-javadoc-plugin/javadoc-mojo.html#detectJavaApiLink],
> seems to be {{https://download.java.net/java/early_access/jdk17/docs/api/}}.
> This url is now dead and should be replaced by
> {{https://docs.oracle.com/en/java/javase/17/docs/api/}}.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (MJAVADOC-695) Default link to Java 17 API is dead
[
https://issues.apache.org/jira/browse/MJAVADOC-695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MJAVADOC-695:
Fix Version/s: next-release
> Default link to Java 17 API is dead
> ---
>
> Key: MJAVADOC-695
> URL: https://issues.apache.org/jira/browse/MJAVADOC-695
> Project: Maven Javadoc Plugin
> Issue Type: Bug
> Components: javadoc
>Affects Versions: 3.3.1
>Reporter: Olivier Cailloux
>Assignee: Michael Osipov
>Priority: Minor
> Fix For: next-release
>
>
> The default base url to the Java 17 API, used by
> [detectJavaApiLink|https://maven.apache.org/plugins/maven-javadoc-plugin/javadoc-mojo.html#detectJavaApiLink],
> seems to be {{https://download.java.net/java/early_access/jdk17/docs/api/}}.
> This url is now dead and should be replaced by
> {{https://docs.oracle.com/en/java/javase/17/docs/api/}}.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Assigned] (MJAVADOC-695) Default link to Java 17 API is dead
[
https://issues.apache.org/jira/browse/MJAVADOC-695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov reassigned MJAVADOC-695:
---
Assignee: Michael Osipov
> Default link to Java 17 API is dead
> ---
>
> Key: MJAVADOC-695
> URL: https://issues.apache.org/jira/browse/MJAVADOC-695
> Project: Maven Javadoc Plugin
> Issue Type: Bug
> Components: javadoc
>Affects Versions: 3.3.1
>Reporter: Olivier Cailloux
>Assignee: Michael Osipov
>Priority: Minor
>
> The default base url to the Java 17 API, used by
> [detectJavaApiLink|https://maven.apache.org/plugins/maven-javadoc-plugin/javadoc-mojo.html#detectJavaApiLink],
> seems to be {{https://download.java.net/java/early_access/jdk17/docs/api/}}.
> This url is now dead and should be replaced by
> {{https://docs.oracle.com/en/java/javase/17/docs/api/}}.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Closed] (MJAVADOC-703) maven-javadoc-plugin > 3.0.1 fail on JDK 8
[
https://issues.apache.org/jira/browse/MJAVADOC-703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed MJAVADOC-703.
---
Resolution: Not A Problem
> maven-javadoc-plugin > 3.0.1 fail on JDK 8
> --
>
> Key: MJAVADOC-703
> URL: https://issues.apache.org/jira/browse/MJAVADOC-703
> Project: Maven Javadoc Plugin
> Issue Type: Bug
>Affects Versions: 3.1.0, 3.3.1
>Reporter: Thorsten Glaser
>Priority: Major
> Attachments: verbose1.txt
>
>
> Trying to use 3.1.0 or 3.3.1 with JDK 8 results in {{--release}} being passed
> to the {{javadoc}} command, which does not know it in JDK 8:
> {{[ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-javadoc-plugin:3.3.1:jar (attach-javadocs) on
> project maven-parent-lib: MavenReportException: Error while generating
> Javadoc: }}
> {{[ERROR] Exit code: 1 - javadoc: error - invalid flag: --release}}
> {{[ERROR]}}
> {{[ERROR] Command line was:
> /usr/lib/jvm/java-8-openjdk-i386/jre/../bin/javadoc @options @packages}}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[GitHub] [maven-integration-testing] michael-o commented on a diff in pull request #151: [MNG-5222] Improvement in deprecated params detection
michael-o commented on code in PR #151:
URL:
https://github.com/apache/maven-integration-testing/pull/151#discussion_r851620420
##
core-it-support/core-it-plugins/maven-it-plugin-configuration/src/main/java/org/apache/maven/plugin/coreit/DeprecatedConfigMojo.java:
##
@@ -47,6 +48,18 @@
@Parameter( defaultValue = "${basedir}", readonly = true )
private File basedir;
+/**
+ * @deprecated bean read only
+ */
+@Parameter( defaultValue = "${project.artifact}", readonly = true )
+private Artifact deprecatedBeanReadOnly;
+
+/**
+ * @deprecated bean
+ */
+@Parameter( defaultValue = "${project.artifact}" )
+private Artifact deprecatedBean;
Review Comment:
I don't see the corresponding test...
##
core-it-suite/src/test/java/org/apache/maven/it/MavenITmng5222MojoDeprecatedParamsTest.java:
##
@@ -35,7 +35,7 @@
{
public MavenITmng5222MojoDeprecatedParamsTest()
{
-super( "[3.9.0,)" );
+super( "[4.0.0-alpha-1,)" );
Review Comment:
Why back to 4 and not with 3.9?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
[jira] [Updated] (SUREFIRE-2074) Junit 5 @Nested Tests executes when excluded
[
https://issues.apache.org/jira/browse/SUREFIRE-2074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tibor Digana updated SUREFIRE-2074:
---
Fix Version/s: waiting-for-apache-feedback
> Junit 5 @Nested Tests executes when excluded
>
>
> Key: SUREFIRE-2074
> URL: https://issues.apache.org/jira/browse/SUREFIRE-2074
> Project: Maven Surefire
> Issue Type: Bug
> Components: JUnit 5.x support
>Affects Versions: 3.0.0-M6
>Reporter: Henrik Josefsson
>Priority: Minor
> Fix For: waiting-for-apache-feedback
>
>
> Test classes with the Junit 5 `@Nested` annotation is executed even when
> explicitly excluded with the `` tag.
> h2. Minimal reproducing example
> [https://github.com/Steinstark/surefire-issue] see the IssueTest.
> h2. Surefire configuration
> {code:java}
>
> org.apache.maven.plugins
> maven-surefire-plugin
> 3.0.0-M6
>
>
> **/IssueTest$NestedTests
>
>
> {code}
> h2. Expected behavior
> The tests inside the `@Nested` excluded class is not run.
> h2. Actual behavior
> The tests inside the `@Nested` excluded class is run.
> h2. Additional info
> I believe the problem is caused by only setting the selectors based on the
> exact classes surefire is expected to run for the
> LauncherDiscoveryRequestBuilder in JunitPlatformProvider but as far as I can
> tell Junit will by default discover `@Nested` classes aswell from the
> selectors.
> The solution is probably to provide a filter in addition to the selector. Not
> sure if it is a good solution but locally I changed the newFilters method to
> always add the TestMethodFilter and it appear to have worked. Might be
> something worth looking further into at least.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Created] (SUREFIRE-2074) Junit 5 @Nested Tests executes when excluded
Henrik Josefsson created SUREFIRE-2074:
--
Summary: Junit 5 @Nested Tests executes when excluded
Key: SUREFIRE-2074
URL: https://issues.apache.org/jira/browse/SUREFIRE-2074
Project: Maven Surefire
Issue Type: Bug
Components: JUnit 5.x support
Affects Versions: 3.0.0-M6
Reporter: Henrik Josefsson
Test classes with the Junit 5 `@Nested` annotation is executed even when
explicitly excluded with the `` tag.
h2. Minimal reproducing example
[https://github.com/Steinstark/surefire-issue] see the IssueTest.
h2. Surefire configuration
{code:java}
org.apache.maven.plugins
maven-surefire-plugin
3.0.0-M6
**/IssueTest$NestedTests
{code}
h2. Expected behavior
The tests inside the `@Nested` excluded class is not run.
h2. Actual behavior
The tests inside the `@Nested` excluded class is run.
h2. Additional info
I believe the problem is caused by only setting the selectors based on the
exact classes surefire is expected to run for the
LauncherDiscoveryRequestBuilder in JunitPlatformProvider but as far as I can
tell Junit will by default discover `@Nested` classes aswell from the
selectors.
The solution is probably to provide a filter in addition to the selector. Not
sure if it is a good solution but locally I changed the newFilters method to
always add the TestMethodFilter and it appear to have worked. Might be
something worth looking further into at least.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[GitHub] [maven-surefire] Tibor17 commented on pull request #517: [SUREFIRE-2064] Allow all supported values of [parallel] option
Tibor17 commented on PR #517: URL: https://github.com/apache/maven-surefire/pull/517#issuecomment-1100627414 @sbabcoc Pls squash these commits to one and we wil make a final review. The situation is as follows. We are in a little progress with our internal wishes and we have to fix broken M6. Additionally, I have backported cca 20 bug fixes from M6 to 2.22.3 but also the TestNG 7.4 bug fix and this one is missing. I guess @slawekjaranowski would continue on fixing `Configuration` implementation and removal of 5.x. The fix of impl of `Configuration` interface is important for M7 and it would be nice in 2.22.3. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven] slawekjaranowski commented on pull request #722: [MNG-5222] Improvement in deprecated params detection
slawekjaranowski commented on PR #722: URL: https://github.com/apache/maven/pull/722#issuecomment-1100623733 build on Jenkins fails due to using master branch from integration-test -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (MNG-5222) Maven 3 no longer logs warnings about deprecated plugin parameters.
[ https://issues.apache.org/jira/browse/MNG-5222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17523052#comment-17523052 ] Hudson commented on MNG-5222: - Build unstable in Jenkins: Maven » Maven TLP » maven » PR-722 #2 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/PR-722/2/ > Maven 3 no longer logs warnings about deprecated plugin parameters. > --- > > Key: MNG-5222 > URL: https://issues.apache.org/jira/browse/MNG-5222 > Project: Maven > Issue Type: Bug > Components: Plugins and Lifecycle >Affects Versions: 3.0.3 >Reporter: Christian Schulte >Assignee: Slawomir Jaranowski >Priority: Minor > Fix For: 3.9.0, 4.0.0-alpha-1, 4.0.0 > > Time Spent: 10m > Remaining Estimate: 0h > > Providing a value for a deprecated plugin parameter, Maven 2.2.1 used to log > a warning. Currently Maven 3 does not. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[GitHub] [maven] Aylinee-RH-Arletee commented on pull request #720: [MNG-7454] Include resolver-transport-http in Maven
Aylinee-RH-Arletee commented on PR #720: URL: https://github.com/apache/maven/pull/720#issuecomment-1100612599 d826b7c78ccf3edcb9ea365480c2cfff2332c335 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-integration-testing] slawekjaranowski opened a new pull request, #151: [MNG-5222] Improvement in deprecated params detection
slawekjaranowski opened a new pull request, #151: URL: https://github.com/apache/maven-integration-testing/pull/151 for https://github.com/apache/maven/pull/722 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
