[jira] [Comment Edited] (MJAVADOC-602) "Aggregating Javadocs For Multi-Projects" code snippet is garbled and tag example is missing
[
https://issues.apache.org/jira/browse/MJAVADOC-602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17382180#comment-17382180
]
Peter Ivanov edited comment on MJAVADOC-602 at 7/16/21, 5:50 PM:
-
[~famod], do you know the way to use new javadoc plugin with just {{mvn
javadoc:aggregate}} command and proper settings in pom.xml or in command line?
I tried all variants of your solution, but root module just does nothing on any
aggregate goal.
was (Author: vveider):
[~famod], do you know the way to use new javadoc plugin with just {{mvn
javadoc:aggregate}} command and proper settings in pom.xml or in command line?
I too can't make javadoc plugin to make aggregate report from root module...
> "Aggregating Javadocs For Multi-Projects" code snippet is garbled and
> tag example is missing
> -
>
> Key: MJAVADOC-602
> URL: https://issues.apache.org/jira/browse/MJAVADOC-602
> Project: Maven Javadoc Plugin
> Issue Type: Bug
>Affects Versions: 3.1.0
>Reporter: Falko Modler
>Assignee: Robert Scholte
>Priority: Major
> Attachments: javadoc-aggregation-doc-formatting.PNG
>
>
> After MJAVADOC-134, I was trying to find out how to migrate my working 2.10.4
> aggregation setup to 3.1.0.
> It seems [the respective
> documentation|https://maven.apache.org/plugins/maven-javadoc-plugin/examples/aggregate.html]
> was extended with the info of [this JIRA
> comment|https://issues.apache.org/jira/browse/MJAVADOC-134?focusedCommentId=16724514=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16724514],
> but something went wrong with the formatting:
> !javadoc-aggregation-doc-formatting.PNG!
> The other issue is that this bit doesn't cover the {{}} tag approach
> so I was fiddling around with this and ended up with:
> {code:xml}
>
>
>
> org.apache.maven.plugins
> maven-javadoc-plugin
>
> true
>
>
>
> aggregate-javadoc
>
> aggregate-no-fork
>
> false
>
> false
>
>
>
>
>
>
> {code}
> Notes: {{mvn -N ...}} does not work, but I don't want a separate aggregation
> for each module. So I skip the plugin in general/for all modules by _not_
> inheriting {{false}}.
> This (or some better solution) should be added to the docs.
> PS: A flag/property to just skip the individual aggregations per module would
> be very much appreciated!
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Comment Edited] (MJAVADOC-602) "Aggregating Javadocs For Multi-Projects" code snippet is garbled and tag example is missing
[
https://issues.apache.org/jira/browse/MJAVADOC-602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17382180#comment-17382180
]
Peter Ivanov edited comment on MJAVADOC-602 at 7/16/21, 4:09 PM:
-
[~famod], do you know the way to use new javadoc plugin with just {{mvn
javadoc:aggregate}} command and proper settings in pom.xml or in command line?
I too can't make javadoc plugin to make aggregate report from root module...
was (Author: vveider):
[~famod], do you know the way to use new javadoc plugin with just {{mvn
javadoc:aggregate}} command and proper settings in pom.xml or in command line?
> "Aggregating Javadocs For Multi-Projects" code snippet is garbled and
> tag example is missing
> -
>
> Key: MJAVADOC-602
> URL: https://issues.apache.org/jira/browse/MJAVADOC-602
> Project: Maven Javadoc Plugin
> Issue Type: Bug
>Affects Versions: 3.1.0
>Reporter: Falko Modler
>Assignee: Robert Scholte
>Priority: Major
> Attachments: javadoc-aggregation-doc-formatting.PNG
>
>
> After MJAVADOC-134, I was trying to find out how to migrate my working 2.10.4
> aggregation setup to 3.1.0.
> It seems [the respective
> documentation|https://maven.apache.org/plugins/maven-javadoc-plugin/examples/aggregate.html]
> was extended with the info of [this JIRA
> comment|https://issues.apache.org/jira/browse/MJAVADOC-134?focusedCommentId=16724514=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16724514],
> but something went wrong with the formatting:
> !javadoc-aggregation-doc-formatting.PNG!
> The other issue is that this bit doesn't cover the {{}} tag approach
> so I was fiddling around with this and ended up with:
> {code:xml}
>
>
>
> org.apache.maven.plugins
> maven-javadoc-plugin
>
> true
>
>
>
> aggregate-javadoc
>
> aggregate-no-fork
>
> false
>
> false
>
>
>
>
>
>
> {code}
> Notes: {{mvn -N ...}} does not work, but I don't want a separate aggregation
> for each module. So I skip the plugin in general/for all modules by _not_
> inheriting {{false}}.
> This (or some better solution) should be added to the docs.
> PS: A flag/property to just skip the individual aggregations per module would
> be very much appreciated!
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (MJAVADOC-602) "Aggregating Javadocs For Multi-Projects" code snippet is garbled and tag example is missing
[
https://issues.apache.org/jira/browse/MJAVADOC-602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17382180#comment-17382180
]
Peter Ivanov commented on MJAVADOC-602:
---
[~famod], do you know the way to use new javadoc plugin with just {{mvn
javadoc:aggregate}} command and proper settings in pom.xml or in command line?
> "Aggregating Javadocs For Multi-Projects" code snippet is garbled and
> tag example is missing
> -
>
> Key: MJAVADOC-602
> URL: https://issues.apache.org/jira/browse/MJAVADOC-602
> Project: Maven Javadoc Plugin
> Issue Type: Bug
>Affects Versions: 3.1.0
>Reporter: Falko Modler
>Assignee: Robert Scholte
>Priority: Major
> Attachments: javadoc-aggregation-doc-formatting.PNG
>
>
> After MJAVADOC-134, I was trying to find out how to migrate my working 2.10.4
> aggregation setup to 3.1.0.
> It seems [the respective
> documentation|https://maven.apache.org/plugins/maven-javadoc-plugin/examples/aggregate.html]
> was extended with the info of [this JIRA
> comment|https://issues.apache.org/jira/browse/MJAVADOC-134?focusedCommentId=16724514=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16724514],
> but something went wrong with the formatting:
> !javadoc-aggregation-doc-formatting.PNG!
> The other issue is that this bit doesn't cover the {{}} tag approach
> so I was fiddling around with this and ended up with:
> {code:xml}
>
>
>
> org.apache.maven.plugins
> maven-javadoc-plugin
>
> true
>
>
>
> aggregate-javadoc
>
> aggregate-no-fork
>
> false
>
> false
>
>
>
>
>
>
> {code}
> Notes: {{mvn -N ...}} does not work, but I don't want a separate aggregation
> for each module. So I skip the plugin in general/for all modules by _not_
> inheriting {{false}}.
> This (or some better solution) should be added to the docs.
> PS: A flag/property to just skip the individual aggregations per module would
> be very much appreciated!
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (MJAR-138) jar:test-jar is skipped when maven.test.skip=true
[ https://issues.apache.org/jira/browse/MJAR-138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17351920#comment-17351920 ] Peter Ivanov commented on MJAR-138: --- +1 to resolving the problem on Maven side itself. > jar:test-jar is skipped when maven.test.skip=true > - > > Key: MJAR-138 > URL: https://issues.apache.org/jira/browse/MJAR-138 > Project: Maven JAR Plugin > Issue Type: Improvement >Affects Versions: 2.3.1 > Environment: jar:test-jar >Reporter: Andrew Hughes >Priority: Major > Fix For: more-investigation > > Attachments: MJAR-138-maven-jar-plugin.patch > > > Not sure if this is a bug or improvement... > Example: > * ./pom.xml > * ./moduleA/pom.xml > * ./moduleB/pom.xml > Situation: > * moduleA produces moduleA-1.2.3-test.jar with the jar:test-jar goal > * moduleB consumes moduleA-1.2.3-test.jar as a > ...test > Problem: > * When -Dmaven.test.skip=true the moduleA-1.2.3-test.jar is never built. > * Then when moduleB tries to build, it's moduleA-1.2.3-test.jar dependency is > unresolved. FAIL! Even with -Dmaven.test.skip=true this will fail. > You might argue that this is a bug with dependency resolution with > -Dmaven.test.skip=true - should a missing dependency @ test scope really fail > the build??? It probably should - which is why the bug is submitted here :) > I've no idea what could be done to fix this either? > --- > p.s. for anyone with this bug the only workaround I can suggest is running > another module... > ./moduleA-test/pom.xml > and have > ...moduleA-test...test -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (MASSEMBLY-824) Use of appendAssemblyId and finalName can cause problems
[
https://issues.apache.org/jira/browse/MASSEMBLY-824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17093269#comment-17093269
]
Peter Ivanov commented on MASSEMBLY-824:
Why do I see the same problem in maven-assembly-plugin-3.2.0 if it was fixed in
3.0.0?
> Use of appendAssemblyId and finalName can cause problems
>
>
> Key: MASSEMBLY-824
> URL: https://issues.apache.org/jira/browse/MASSEMBLY-824
> Project: Maven Assembly Plugin
> Issue Type: Bug
>Affects Versions: 2.6
>Reporter: Sebastian Geiger
>Assignee: Guillaume Boué
>Priority: Major
> Fix For: 3.0.0
>
>
> I recently had a usecase where I wanted to rename an artifact locally in the
> target/ folder. I configured the maven-assembly-plugin with the following
> options:
> {code}
> false
> helper-${project.version}
> {code}
> As expected the resulting name was `helper-5.0.0-SNAPSHOT.jar`.
> Next when I built the project I noticed warnings about a conflict with the
> default artifact for the project.
> {quote}
> [WARNING] Configuration options: 'appendAssemblyId' is set to false, and
> 'classifier' is missing. Instead of attaching the assembly file:
> [...]/target/helper-5.0.0-SNAPSHOT.jar, it will become the file for main
> project artifact.
> NOTE: If multiple descriptors or descriptor-formats are provided for this
> project, the value of this file will be non-deterministic!
> [WARNING] Replacing pre-existing project main-artifact file:
> [...]/target/my.module-5.0.0-SNAPSHOT.jar with assembly file:
> [...]/target/helper-5.0.0-SNAPSHOT.jar
> {quote}
> Irritated by these warnings I asked about this on
> [StackOverflow|http://stackoverflow.com/questions/38482839/maven-assembly-plugin-how-to-use-appendassemblyid/38484021#38484021]
> and received the following explanation:
> Essentially during installation the standard maven coordinates (G-A-V-C) are
> still used independent of the {{finalName}} used to for the artifact, since
> this only affects the local name inside the {{target}} folder. Now, when the
> {{appendAssemblyId}} is set to {{false}} the classifier will be dropped not
> only from the local name, but also from the artifact's name used during
> installation and there will be a clash with the default artifact name if the
> project's packaging is set to jar.
> Currently there seem to be only two solutions:
> # Do not set the {{appendAssemblyId}} option to {{false}}, which means that
> the local name used inside the target folder will still get the assemblyId
> appended (e.g. -jar-with-dependencies.jar).
> # Alternatively, set the option {{attach}} to {{false}}, this will avoid the
> above mentioned warning but also means that the artifact will no longer be
> installed.
> Of course I could just ignore he warning, but the after all the warning has a
> reason and I would rather fix that then ignore the warning.
> h1. Suggested solutions:
> IMHO there are several solutions to resolve this:
> # Omit the assemblyId on the local name by default if {{finalName}} is used.
> Additionally change the semantics of the {{appendAssemblyId}} option to only
> affect the installed artifact's name.
> # Add an additional option to control if the assemblyId is appended to the
> local file name.
> In any case, also if none of the suggested options are feasible I suggest to
> document this better.
> * Make it clear in the {{appendAssemblyId}} option, that this affects both
> the local and the installed artifact's file name. Also clarify the warning
> that appears when this option is set to false. Also, maybe suggest to set
> {{attach}} to {{false}} if a conflict is detected?
> * Make it clear in the {{finalName}} option, that this only affects the local
> file name and NOT the installed artifact's file name.
> Thank you for your time and attention.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (MJAVADOC-621) Flaky "Error fetching URL" on https links
[
https://issues.apache.org/jira/browse/MJAVADOC-621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16984793#comment-16984793
]
Peter Ivanov commented on MJAVADOC-621:
---
[~michael-o], do you know where I can file the issue for the Javadoc itself?
> Flaky "Error fetching URL" on https links
> -
>
> Key: MJAVADOC-621
> URL: https://issues.apache.org/jira/browse/MJAVADOC-621
> Project: Maven Javadoc Plugin
> Issue Type: Bug
>Affects Versions: 3.1.1
> Environment: OS: Ubuntu Linux 18.04 | macOS Mohave 10.14.6
> Java: 1.8.0_222 | 1.8.0_181
> Maven: 3.6.1
> Javadoc Maven Plugin: 2.10.4, 3.1.1
>Reporter: Peter Ivanov
>Priority: Critical
> Fix For: waiting-for-feedback
>
>
> https://github.com/apache/ignite/blob/2d871005fdc5228479c0aa700e94b7c757e6deae/parent/pom.xml#L342
> When changed http to https, build started triggering Javadoc Warnings from
> time to time with no visible pattern.
> It is reproduced on latest (3.1.1) version of Maven Javadoc Plugin
> {code}
> [WARNING] Javadoc Warnings
> [WARNING] javadoc: warning - Error fetching URL:
> https://hadoop.apache.org/docs/current/api/
> {code}
> h3. Reproducer
> {code}
> git clone g...@github.com:apache/ignite.git
> cd ignite
> git checkout 2d871005fdc5228479c0aa700e94b7c757e6deae
> mvn clean package -pl :ignite-tools -am -DskipTests
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (MJAVADOC-621) Flaky "Error fetching URL" on https links
[
https://issues.apache.org/jira/browse/MJAVADOC-621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter Ivanov updated MJAVADOC-621:
--
Description:
https://github.com/apache/ignite/blob/2d871005fdc5228479c0aa700e94b7c757e6deae/parent/pom.xml#L342
When changed http to https, build started triggering Javadoc Warnings from time
to time with no visible pattern.
It is reproduced on latest (3.1.1) version of Maven Javadoc Plugin
{code}
[WARNING] Javadoc Warnings
[WARNING] javadoc: warning - Error fetching URL:
https://hadoop.apache.org/docs/current/api/
{code}
h3. Reproducer
{code}
git clone g...@github.com:apache/ignite.git
cd ignite
git checkout 2d871005fdc5228479c0aa700e94b7c757e6deae
mvn clean package -pl :ignite-tools -am -DskipTests
{code}
was:
https://github.com/apache/ignite/blob/2d871005fdc5228479c0aa700e94b7c757e6deae/parent/pom.xml#L342
When changed http to https, build started triggering Javadoc Warnings from time
to time with no visible pattern.
It is reproduced on latest (3.1.1) version of Maven Javadoc Plugin
{code}
[WARNING] Javadoc Warnings
[WARNING] javadoc: warning - Error fetching URL:
https://hadoop.apache.org/docs/current/api/
{code}
h3. Reproducer
{code}
git clone g...@github.com:apache/ignite.git
cd ignite
mvn clean package -pl :ignite-tools -am -DskipTests
{code}
> Flaky "Error fetching URL" on https links
> -
>
> Key: MJAVADOC-621
> URL: https://issues.apache.org/jira/browse/MJAVADOC-621
> Project: Maven Javadoc Plugin
> Issue Type: Bug
>Affects Versions: 3.1.1
> Environment: OS: Ubuntu Linux 18.04 | macOS Mohave 10.14.6
> Java: 1.8.0_222 | 1.8.0_181
> Maven: 3.6.1
> Javadoc Maven Plugin: 2.10.4, 3.1.1
>Reporter: Peter Ivanov
>Priority: Critical
>
> https://github.com/apache/ignite/blob/2d871005fdc5228479c0aa700e94b7c757e6deae/parent/pom.xml#L342
> When changed http to https, build started triggering Javadoc Warnings from
> time to time with no visible pattern.
> It is reproduced on latest (3.1.1) version of Maven Javadoc Plugin
> {code}
> [WARNING] Javadoc Warnings
> [WARNING] javadoc: warning - Error fetching URL:
> https://hadoop.apache.org/docs/current/api/
> {code}
> h3. Reproducer
> {code}
> git clone g...@github.com:apache/ignite.git
> cd ignite
> git checkout 2d871005fdc5228479c0aa700e94b7c757e6deae
> mvn clean package -pl :ignite-tools -am -DskipTests
> {code}
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Updated] (MJAVADOC-621) Flaky "Error fetching URL" on https links
[
https://issues.apache.org/jira/browse/MJAVADOC-621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter Ivanov updated MJAVADOC-621:
--
Affects Version/s: 3.1.1
> Flaky "Error fetching URL" on https links
> -
>
> Key: MJAVADOC-621
> URL: https://issues.apache.org/jira/browse/MJAVADOC-621
> Project: Maven Javadoc Plugin
> Issue Type: Bug
>Affects Versions: 3.1.1
> Environment: OS: Ubuntu Linux 18.04 | macOS Mohave 10.14.6
> Java: 1.8.0_222 | 1.8.0_181
> Maven: 3.6.1
> Javadoc Maven Plugin: 2.10.4, 3.1.1
>Reporter: Peter Ivanov
>Priority: Critical
>
> https://github.com/apache/ignite/blob/2d871005fdc5228479c0aa700e94b7c757e6deae/parent/pom.xml#L342
> When changed http to https, build started triggering Javadoc Warnings from
> time to time with no visible pattern.
> It is reproduced on latest (3.1.1) version of Maven Javadoc Plugin
> {code}
> [WARNING] Javadoc Warnings
> [WARNING] javadoc: warning - Error fetching URL:
> https://hadoop.apache.org/docs/current/api/
> {code}
> h3. Reproducer
> {code}
> git clone g...@github.com:apache/ignite.git
> cd ignite
> mvn clean package -pl :ignite-tools -am -DskipTests
> {code}
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Created] (MJAVADOC-621) Flaky "Error fetching URL" on https links
Peter Ivanov created MJAVADOC-621:
-
Summary: Flaky "Error fetching URL" on https links
Key: MJAVADOC-621
URL: https://issues.apache.org/jira/browse/MJAVADOC-621
Project: Maven Javadoc Plugin
Issue Type: Bug
Environment: OS: Ubuntu Linux 18.04 | macOS Mohave 10.14.6
Java: 1.8.0_222 | 1.8.0_181
Maven: 3.6.1
Javadoc Maven Plugin: 2.10.4, 3.1.1
Reporter: Peter Ivanov
https://github.com/apache/ignite/blob/2d871005fdc5228479c0aa700e94b7c757e6deae/parent/pom.xml#L342
When changed http to https, build started triggering Javadoc Warnings from time
to time with no visible pattern.
It is reproduced on latest (3.1.1) version of Maven Javadoc Plugin
{code}
[WARNING] Javadoc Warnings
[WARNING] javadoc: warning - Error fetching URL:
https://hadoop.apache.org/docs/current/api/
{code}
h3. Reproducer
{code}
git clone g...@github.com:apache/ignite.git
cd ignite
mvn clean package -pl :ignite-tools -am -DskipTests
{code}
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Comment Edited] (MJAVADOC-427) "Error fetching URL" for valid non-Java API links
[
https://issues.apache.org/jira/browse/MJAVADOC-427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16363803#comment-16363803
]
Peter Ivanov edited comment on MJAVADOC-427 at 2/14/18 11:03 AM:
-
Bug still presents in plugin version {{3.0.0}}.
was (Author: vveider):
Bug still present in plugin version {{3.0.0}}.
> "Error fetching URL" for valid non-Java API links
> -
>
> Key: MJAVADOC-427
> URL: https://issues.apache.org/jira/browse/MJAVADOC-427
> Project: Maven Javadoc Plugin
> Issue Type: Bug
>Affects Versions: 2.10.3
> Environment: Windows 7
> Apache Maven 3.2.1
> java version "1.8.0_05"
> Java(TM) SE Runtime Environment (build 1.8.0_05-b13)
> Java HotSpot(TM) 64-Bit Server VM (build 25.5-b02, mixed mode)
>Reporter: Selena Renee Phillips
>Priority: Major
> Attachments: testcase-detectLinks-enabled-no-manual-link-config.zip,
> testcase-detectLinks-enabled-with-manual-link-config-no-trailing-slash.zip,
> testcase-detectLinks-enabled-with-manual-link-config-trailing-slash.zip,
> testcases-detectLinks-disabled-with-manual-link-config-no-trailing-slash.zip,
> testcases-detectLinks-disabled-with-manual-link-config-trailing-slash.zip
>
>
> When I generate Javadoc for a simple project with 3rd party dependencies, no
> configuration generates links for these dependencies. For valid Javadoc links
> which have a package-list, I get the following error:
> [WARNING] javadoc: warning - Error fetching URL
> Test Cases w/ results (sample project(s)) attached:
> *1. No manual link configuration. 'detectLinks' is set to true.*
> {code:title=pom.xml - No manual link configuration with
> detectLinks=true|borderStyle=solid}
>
> org.apache.maven.plugins
> maven-javadoc-plugin
> 2.10.3
>
>
> ${project.basedir}/target
> javadoc
> Epiphany
> Epiphany
> private
> true
> true
> true
> true
>
>
>
>
> javadoc
> test-javadoc
>
>
>
>
> {code}
> Output of 'mvn javadoc:javadoc':
> {code:title=Resulting output for mvn javadoc:javadoc - No manual link
> configuration with detectLinks=true|borderStyle=solid}
> [INFO] Scanning for projects...
> [INFO]
> [INFO] Using the builder
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder
> with a thread count of 1
> [INFO]
> [INFO]
>
> [INFO] Building epiphany 1.0-SNAPSHOT
> [INFO]
>
> [INFO]
> [INFO] >>> maven-javadoc-plugin:2.10.3:javadoc (default-cli) @ epiphany >>>
> [INFO]
> [INFO] <<< maven-javadoc-plugin:2.10.3:javadoc (default-cli) @ epiphany <<<
> SNIP DOWNLOADING INFO.
> [INFO]
> [INFO] --- maven-javadoc-plugin:2.10.3:javadoc (default-cli) @ epiphany ---
> [ERROR] Error fetching link:
> http://selenium.googlecode.com/selenium-java/apidocs/package-list. Ignored it.
> [ERROR] Error fetching link:
> http://selenium.googlecode.com/selenium-api/apidocs/package-list. Ignored it.
> [ERROR] Error fetching link:
> http://selenium.googlecode.com/selenium-support/apidocs/package-list. Ignored
> it.
> [ERROR] Error fetching link:
> http://code.google.com/p/guava-libraries/guava/apidocs/package-list. Ignored
> it.
> [ERROR] Error fetching link:
> http://logback.qos.ch/logback-core/apidocs/package-list. Ignored it.
> [ERROR] Error fetching link:
> http://logback.qos.ch/logback-classic/apidocs/package-list. Ignored it.
> [ERROR] Error fetching link: http://testng.org/apidocs/package-list. Ignored
> it.
> [INFO]
> Loading source files for package com.example...
> Constructing Javadoc information...
> Standard Doclet version 1.8.0_05
> Building tree for all the packages and classes...
> Generating
> C:\Users\sephilli\git\javadoc-bug\target\javadoc\com\example\AbstractLoadable.html...
> .SNIP
> 1 warning
> [WARNING] Javadoc Warnings
> [WARNING] javadoc: warning - Error fetching URL: http://www.slf4j.org/apidocs
> [INFO]
>
> [INFO] BUILD SUCCESS
> [INFO]
>
> [INFO] Total time: 13.694 s
> [INFO] Finished at: 2015-04-18T08:24:05-05:00
> [INFO] Final Memory: 16M/92M
> [INFO]
>
> {code}
> I
[jira] [Commented] (MJAVADOC-427) "Error fetching URL" for valid non-Java API links
[
https://issues.apache.org/jira/browse/MJAVADOC-427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16363803#comment-16363803
]
Peter Ivanov commented on MJAVADOC-427:
---
Bug still present in plugin version {{3.0.0}}.
> "Error fetching URL" for valid non-Java API links
> -
>
> Key: MJAVADOC-427
> URL: https://issues.apache.org/jira/browse/MJAVADOC-427
> Project: Maven Javadoc Plugin
> Issue Type: Bug
>Affects Versions: 2.10.3
> Environment: Windows 7
> Apache Maven 3.2.1
> java version "1.8.0_05"
> Java(TM) SE Runtime Environment (build 1.8.0_05-b13)
> Java HotSpot(TM) 64-Bit Server VM (build 25.5-b02, mixed mode)
>Reporter: Selena Renee Phillips
>Priority: Major
> Attachments: testcase-detectLinks-enabled-no-manual-link-config.zip,
> testcase-detectLinks-enabled-with-manual-link-config-no-trailing-slash.zip,
> testcase-detectLinks-enabled-with-manual-link-config-trailing-slash.zip,
> testcases-detectLinks-disabled-with-manual-link-config-no-trailing-slash.zip,
> testcases-detectLinks-disabled-with-manual-link-config-trailing-slash.zip
>
>
> When I generate Javadoc for a simple project with 3rd party dependencies, no
> configuration generates links for these dependencies. For valid Javadoc links
> which have a package-list, I get the following error:
> [WARNING] javadoc: warning - Error fetching URL
> Test Cases w/ results (sample project(s)) attached:
> *1. No manual link configuration. 'detectLinks' is set to true.*
> {code:title=pom.xml - No manual link configuration with
> detectLinks=true|borderStyle=solid}
>
> org.apache.maven.plugins
> maven-javadoc-plugin
> 2.10.3
>
>
> ${project.basedir}/target
> javadoc
> Epiphany
> Epiphany
> private
> true
> true
> true
> true
>
>
>
>
> javadoc
> test-javadoc
>
>
>
>
> {code}
> Output of 'mvn javadoc:javadoc':
> {code:title=Resulting output for mvn javadoc:javadoc - No manual link
> configuration with detectLinks=true|borderStyle=solid}
> [INFO] Scanning for projects...
> [INFO]
> [INFO] Using the builder
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder
> with a thread count of 1
> [INFO]
> [INFO]
>
> [INFO] Building epiphany 1.0-SNAPSHOT
> [INFO]
>
> [INFO]
> [INFO] >>> maven-javadoc-plugin:2.10.3:javadoc (default-cli) @ epiphany >>>
> [INFO]
> [INFO] <<< maven-javadoc-plugin:2.10.3:javadoc (default-cli) @ epiphany <<<
> SNIP DOWNLOADING INFO.
> [INFO]
> [INFO] --- maven-javadoc-plugin:2.10.3:javadoc (default-cli) @ epiphany ---
> [ERROR] Error fetching link:
> http://selenium.googlecode.com/selenium-java/apidocs/package-list. Ignored it.
> [ERROR] Error fetching link:
> http://selenium.googlecode.com/selenium-api/apidocs/package-list. Ignored it.
> [ERROR] Error fetching link:
> http://selenium.googlecode.com/selenium-support/apidocs/package-list. Ignored
> it.
> [ERROR] Error fetching link:
> http://code.google.com/p/guava-libraries/guava/apidocs/package-list. Ignored
> it.
> [ERROR] Error fetching link:
> http://logback.qos.ch/logback-core/apidocs/package-list. Ignored it.
> [ERROR] Error fetching link:
> http://logback.qos.ch/logback-classic/apidocs/package-list. Ignored it.
> [ERROR] Error fetching link: http://testng.org/apidocs/package-list. Ignored
> it.
> [INFO]
> Loading source files for package com.example...
> Constructing Javadoc information...
> Standard Doclet version 1.8.0_05
> Building tree for all the packages and classes...
> Generating
> C:\Users\sephilli\git\javadoc-bug\target\javadoc\com\example\AbstractLoadable.html...
> .SNIP
> 1 warning
> [WARNING] Javadoc Warnings
> [WARNING] javadoc: warning - Error fetching URL: http://www.slf4j.org/apidocs
> [INFO]
>
> [INFO] BUILD SUCCESS
> [INFO]
>
> [INFO] Total time: 13.694 s
> [INFO] Finished at: 2015-04-18T08:24:05-05:00
> [INFO] Final Memory: 16M/92M
> [INFO]
>
> {code}
> I expected that the plugin would fail to find javadoc to link for Selenium,
> Logback, Guava and TestNg, but to succeed in
