HI,
The Apache Maven team is pleased to announce the release of the Apache
Maven Javadoc Plugin 3.12.0
The Javadoc Plugin uses the Javadoc tool to generate javadocs for the
specified project.
https://maven.apache.org/plugins/maven-javadoc-plugin/
You should specify the version in your
aw it
> was not reported yet but wasn't sure how it was occurring, when I looked
> yesterday before this started floating around, I saw it fixed on master.
> That said, I think Javadoc really needs to progress for a release shortly
> here. Is the plugin ready for a release or
hen I looked yesterday
before this started floating around, I saw it fixed on master. That said, I
think Javadoc really needs to progress for a release shortly here. Is the
plugin ready for a release or waiting on other stuff?
-Original Message-
From: Gary Gregory
Sent: Saturday, Augu
Ah, thank you for the link. Waiting for 3.11.4 to fix the regression then.
Gary
On Fri, Aug 29, 2025, 18:00 Elliotte Rusty Harold
wrote:
> I haven't analyzed your failure in detail, but this smells like
> another instance of
> https://github.com/apache/maven-javadoc-plugin/issues
I haven't analyzed your failure in detail, but this smells like
another instance of
https://github.com/apache/maven-javadoc-plugin/issues/1241 which is
fixed at HEAD.
On Fri, Aug 29, 2025 at 8:30 PM Gary D. Gregory wrote:
>
> Hi All,
>
> A MalformedInputException started happen
9 20:42:55 Matthias Bünger wrote:
> > From my experience this is mostly an encoding issue, e.g. not using
> > UTF-8 everywhere.
> >
> > Am 29.08.2025 um 22:30 schrieb Gary D. Gregory:
> > > Hi All,
> > >
> > > A MalformedInputException star
Oh. Sorry, wrong list. I was thinking in terms of Xalan's Javadoc and plugins.
--
Joe (new phone, no quip yet)
From: Joseph Kesselman
Sent: Friday, August 29, 2025 5:14:14 PM
To: Maven Users List
Subject: Re: Javadoc plugin
Not so hugely weird. Remembe
Not so hugely weird. Remember, we already have had to rework our custom tags
once to stay in sync with Javadoc, and if I'm remembering correctly that is the
part which needed a switch to select between older apis and the Java 9 and
later jdks.
I'm away from keyboard right now but w
name: "windows 11", version: "10.0", arch: "amd64", family: "windows"
Could this be related to this PR
https://github.com/apache/maven-javadoc-plugin/pull/1215/files (no uni tests in
the PR?)
Gary
On 2025/08/29 21:08:12 "Gary D. Gregory" wro
er wrote:
> From my experience this is mostly an encoding issue, e.g. not using
> UTF-8 everywhere.
>
> Am 29.08.2025 um 22:30 schrieb Gary D. Gregory:
> > Hi All,
> >
> > A MalformedInputException started happening today when we updated our
> > parent pom in Comm
From my experience this is mostly an encoding issue, e.g. not using
UTF-8 everywhere.
Am 29.08.2025 um 22:30 schrieb Gary D. Gregory:
Hi All,
A MalformedInputException started happening today when we updated our parent
pom in Command Lang which includes updating the Javadoc plugin from
I'll try to take a look at it. I had heard reports that there were
compatibility issues between older and newer javadoc plug in apis; there may be
other differences.
--
Joe (new phone, no quip yet)
From: Gary D. Gregory
Sent: Friday, August 29, 2025 4:30:
Hi All,
A MalformedInputException started happening today when we updated our parent
pom in Command Lang which includes updating the Javadoc plugin from 3.11.2 to
3.11.3. Do you think this failure is related to
https://stackoverflow.com/questions/53449049/maven-javadoc-plugin-error-javadoc
Gary,
On Fri, Aug 29, 2025 at 2:23 PM Gary Gregory wrote:
> The new Javadoc plugin 3.11.3 always says:
>
> [WARNING] Javadoc 1.4+ doesn't support the -1.1 switch anymore. Ignore
> this option.
>
> How do I make it stop?
>
Unfortunately you cannot (at least not witho
The new Javadoc plugin 3.11.3 always says:
[WARNING] Javadoc 1.4+ doesn't support the -1.1 switch anymore. Ignore
this option.
How do I make it stop?
This did not happen in 3.11.2.
TY,
Gary
-
To unsubscribe, e-mail:
The Apache Maven team is pleased to announce the release of the Apache
Maven Javadoc Plugin, version 3.11.3
The Javadoc Plugin uses the Javadoc tool to generate javadocs for the
specified project..
https://maven.apache.org/plugins/maven-javadoc-plugin/
You should specify the version in your
me applies to any branch/tag where maven.compiler.release is
> > > > 8. Java and maven versions [1].
> > >
> > > When we run `mvn clean package javadoc:aggregate` we get a successful
> > > run, but the main project is skipped:
> > >
> > >
va 11. See [0]
> >
> > This tag specifically: https://github.com/apache/tika/tree/3.2.0-rc2
> > but the same applies to any branch/tag where maven.compiler.release is
> > > 8. Java and maven versions [1].
> >
> > When we run `mvn clean package javadoc:aggregate` we get a
ompiler.release is
> > 8. Java and maven versions [1].
>
> When we run `mvn clean package javadoc:aggregate` we get a successful
> run, but the main project is skipped:
>
> --- javadoc:3.11.2:aggregate (default-cli) @ tika ---
> [INFO] Skipping
> org.apache.maven.pl
vn clean package javadoc:aggregate` we get a successful
run, but the main project is skipped:
--- javadoc:3.11.2:aggregate (default-cli) @ tika ---
[INFO] Skipping
org.apache.maven.plugins:maven-javadoc-plugin:3.11.2:aggregate report
goal
We found at least on a subset of our project that if we re
FYI, this is fixed this in the Commons parent POM, Javadoc does not
like you to link to Javadocs for Java 21 when the target release is
Java 8 (using Javadoc 17). I don't know what the version boundaries
are for the various pieces. Now, the build will just link to the
Javadoc that matche
On Sun, Jan 19, 2025 at 2:24 PM Gary Gregory wrote:
>
> Right, if I run "mvn javadoc:javadoc -X", I see:
>
> [DEBUG] (f) release = 8
The above is logged as part of:
[DEBUG] Configuring mojo execution
'org.apache.maven.plugins:maven-javadoc-plugin:3.11.2:java
gt; > I meant:
> >
> > https://maven.apache.org/plugins/maven-javadoc-plugin/javadoc-mojo.html#release
> >
> > On Sun, Jan 19, 2025 at 6:37 PM Gary Gregory
> > wrote:
> > >
> > > Of course ;-) that's baked in our parent POM and set
rent/blob/87e668d63c62f57175585625d0176fc130ced38f/pom.xml#L440
>
> I meant:
>
> https://maven.apache.org/plugins/maven-javadoc-plugin/javadoc-mojo.html#release
>
> On Sun, Jan 19, 2025 at 6:37 PM Gary Gregory
> wrote:
> >
> > Of course ;-) that's baked in our parent POM and set to 8 for m
Hm, I dont see it here
https://github.com/apache/commons-parent/blob/87e668d63c62f57175585625d0176fc130ced38f/pom.xml#L440
I meant:
https://maven.apache.org/plugins/maven-javadoc-plugin/javadoc-mojo.html#release
On Sun, Jan 19, 2025 at 6:37 PM Gary Gregory wrote:
>
> Of course ;-) that&#
Of course ;-) that's baked in our parent POM and set to 8 for most
components.
Gary
On Sun, Jan 19, 2025, 11:35 Tamás Cservenák wrote:
> Howdy.
>
> Did you try
>
> https://docs.oracle.com/en/java/javase/17/docs/specs/man/javac.html#option-release
> ?
>
> I think
Howdy.
Did you try
https://docs.oracle.com/en/java/javase/17/docs/specs/man/javac.html#option-release
?
I think javadoc has a "release" param... so no need to mess with args or alike
Thanks
On Sun, Jan 19, 2025 at 1:44 PM Gary Gregory wrote:
>
> Any thoughts on this?
>
>
Any thoughts on this?
Ty,
Gary
On Tue, Dec 17, 2024, 09:47 Gary D. Gregory wrote:
> Hi All:
>
> I'd like to build Apache Commons components with the build failing if
> there are Javadoc warnings. This idea would fail today for all components
> because we get this Javado
Stone wrote:
Typical use case I think:
1. Have dependency
2. Download JavaDoc
3. Expect resolution in code (but doesn't work... maybe a separate
email)
4. Right-click dependency, select view JavaDoc
5. Browser opens to 127.0.0.1:8082 (see below)
6. HTTP 500 from Tomcat 9.0.71
NetBean
I've opened https://github.com/apache/netbeans/issues/8128 for resolution.
Thanks!
Tim
On 1/7/25 8:36 PM, Timothy Stone wrote:
Wrong email list. Apologies.
On 1/7/25 8:34 PM, Timothy Stone wrote:
Typical use case I think:
1. Have dependency
2. Download JavaDoc
3. Expect resolution in
Wrong email list. Apologies.
On 1/7/25 8:34 PM, Timothy Stone wrote:
Typical use case I think:
1. Have dependency
2. Download JavaDoc
3. Expect resolution in code (but doesn't work... maybe a separate
email)
4. Right-click dependency, select view JavaDoc
5. Browser opens to 127.0.0.1
Typical use case I think:
1. Have dependency
2. Download JavaDoc
3. Expect resolution in code (but doesn't work... maybe a separate
email)
4. Right-click dependency, select view JavaDoc
5. Browser opens to 127.0.0.1:8082 (see below)
6. HTTP 500 from Tomcat 9.0.71
NetBeans 24 (Ja
Hi All:
I'd like to build Apache Commons components with the build failing if there are
Javadoc warnings. This idea would fail today for all components because we get
this Javadoc warning:
[INFO] --- javadoc:3.10.1:javadoc (default-cli) @ commons-csv ---
[INFO] Configuration change
The Apache Maven team is pleased to announce the release of the Apache
Maven Javadoc Plugin, version 3.11.2
The Javadoc Plugin uses the Javadoc tool to generate javadocs for the
specified project
https://maven.apache.org/plugins/maven-javadoc-plugin/
You should specify the version in your
I was generating the missing 3.11.1 so I did 3.11.0 as well but right there
is a tag but nothing deployed.
I will remove this
On Sat, 23 Nov 2024 at 8:10 pm, Piotr Żygieło
wrote:
> Hello
>
> I see the GitHub release
>
> https://github.com/apache/maven-javadoc-plugin/releases/ta
Hello
I see the GitHub release
https://github.com/apache/maven-javadoc-plugin/releases/tag/maven-javadoc-plugin-3.11.0
was created while there was no such release for that plugin.
This confused me.
--
Piotrek
-
To unsubscribe
The Apache Maven team is pleased to announce the release of the Maven
Javadoc Plugin, version 3.11.1.
This module generates browsable HTML pages from Java source code.
https://maven.apache.org/plugins/maven-javadoc-plugin/
You should specify the version in your project's plugin configur
The Apache Maven team is pleased to announce the release of the Maven
Javadoc Plugin, version 3.10.1.
This module generates browsable HTML pages from Java source code.
https://maven.apache.org/plugins/maven-javadoc-plugin/
You should specify the version in your project's plugin configur
The Apache Maven team is pleased to announce the release of the Maven
Javadoc Plugin, version 3.10.0.
This module generates browsable HTML pages from Java source code.
https://maven.apache.org/plugins/maven-javadoc-plugin/
You should specify the version in your project's plugin configur
The Apache Maven team is pleased to announce the release of the Maven
Javadoc Plugin, version 3.8.0.
This module generates browsable HTML pages from Java source code.
https://maven.apache.org/plugins/maven-javadoc-plugin/
You should specify the version in your project's plugin configur
The Apache Maven team is pleased to announce the release of the Maven
Javadoc Plugin, version 3.7.0.
This module generates browsable HTML pages from Java source code.
https://maven.apache.org/plugins/maven-javadoc-plugin/
You should specify the version in your project's plugin configur
After setting up Lombok in Netbeans 21 Maven project, I noticed that
JavaDoc does not produce a full description of the Lombok tags.
For instance for:
*protected @Getter @Setter @NonNull String message;*
JavaDoc only recognizes the @NonNull tag, omitting the other tags, i.e. :
|protected
gt; Hi Tamás,
> >
> > Thank you for your comments.
> >
> > My question is more regarding the need to place a javadoc
> > element in the BOM file, i.e top level pom.xml, instead of
> parent/pom.xml.
> >
> > Once the javadoc related element is in the BOM
for your comments.
>
> My question is more regarding the need to place a javadoc
> element in the BOM file, i.e top level pom.xml, instead of parent/pom.xml.
>
> Once the javadoc related element is in the BOM file, it works fine.
>
> However, given the BOM file is inten
Hi Tamás,
Thank you for your comments.
My question is more regarding the need to place a javadoc
element in the BOM file, i.e top level pom.xml, instead of parent/pom.xml.
Once the javadoc related element is in the BOM file, it works fine.
However, given the BOM file is intended to be
Hej Ceki,
I also experience javadoc misbehaviour when JPMS/jigsaw is involved, and _I
think_ it boils down when it tries to be "smart" when it comes to JPMS...
See master of maven-resolver, as it was suffering with similar issues, and
this change:
https://github.com/apache/maven-resol
Hello all,
Given the javadoc generation is an important part of software projects,
maybe someone would care to comment whether the behavior described below
is expected or not?
In the meantime, happy new year to all,
--
Ceki Gülcü
Sponsoring SLF4J/logback/reload4j at https://github.com
Hello,
I would like to share what looks to me like an unexpected behavior of
the javadoc plugin, more specifically when run as javadoc:aggregate.
The SLF4J project uses the "Refining the BOM Pattern" variant as
explained in Garret Wilson's "Improving the BOM Pattern&quo
The Apache Maven team is pleased to announce the release of the Maven
Javadoc Plugin, version 3.6.3.
This module generates browsable HTML pages from Java source code.
https://maven.apache.org/plugins/maven-javadoc-plugin/
You should specify the version in your project's plugin configur
The Apache Maven team is pleased to announce the release of the Maven
Javadoc Plugin, version 3.6.2.
This module generates browsable HTML pages from Java source code.
https://maven.apache.org/plugins/maven-javadoc-plugin/
You should specify the version in your project's plugin configur
Wed, 4 Oct 2023 15:52:14 +, /Joseph Kesselman/:
My only other real gripe with Maven at the moment is that I haven't
yet found a way to tell the javadoc plugin "Yes, I know there's lots
that can be improved, but for now please consider that a Warning
rather than an Error
Oh. Duh.
com.sun
tools
1.6.0
system
${toolsjar}
On 10/3/2023 10:04 PM, Alexander Kriegisch wrote:
Hi Joseph.
I think you uncovered a bug in Maven Javadoc Plugin. I just created
https://issues.apache.org/jira/browse/MJAVADOC-775 on your
und a
way to tell the javadoc plugin "Yes, I know there's lots that can be improved,
but for now please consider that a Warning rather than an Error."
--
/_ Joe Kesselman (he/him/his)
-/ _) My Alexa skill for New Music/New Sounds fans:
/ https://www.amazon.com/dp/B09WJ3H
Hi Joseph.
I think you uncovered a bug in Maven Javadoc Plugin. I just created
https://issues.apache.org/jira/browse/MJAVADOC-775 on your behalf.
As a workaround for the non-functioning 'tagletpath' option, I recommend
to separately publish the taglet library as a Maven artifact, whic
Hi, folks. I'm in the process of trying to port the Apache Xalan build
from Ant to Maven. It's close to usable, but I'm still struggling with a
few odd corners.
One of the odder corners: The Xalan documentation uses a javadoc taglet,
@xsl.usage, to indicate whether a method i
Hello,
I am compiling a multi-module project with Maven. When I run maven clean
install the compilation succeeds on a submodule but the javadoc plugin
throws error while trying to generate javadoc for the submodule that has
dependency on another submodule. My parent pom has
The Apache Maven team is pleased to announce the release of the Apache
Maven Javadoc Plugin, version 3.6.0
The Javadoc Plugin uses the Javadoc tool to generate javadocs for the
specified project.
https://maven.apache.org/plugins/maven-javadoc-plugin/
You should specify the version in your
details?
> > Or my English is not good enough? :(
> >
> > This issue blocks our release process, I'd love to get some help
> >
> > Thanks in advance :)
> >
> > On Sat, 25 Mar 2023 at 23:34, Maxim Solodovnik
> > wrote:
> > >
> > > Here is th
nglish is not good enough? :(
>
> This issue blocks our release process, I'd love to get some help
>
> Thanks in advance :)
>
> On Sat, 25 Mar 2023 at 23:34, Maxim Solodovnik
> wrote:
> >
> > Here is the sample project: https://github.com/solomax/javadoc-e
hanks a lot for the answer!
I'll try to contact authors of problematic library.
It is weirs this library causing the issue, since it's classes are not
being used directly
(it it is transitive dependency)
Compilation is successful and only Javadoc is failing ...
On Mon, 27 Mar 202
Thanks a lot for the answer!
I'll try to contact authors of problematic library.
It is weirs this library causing the issue, since it's classes are not
being used directly
(it it is transitive dependency)
Compilation is successful and only Javadoc is failing ...
On Mon, 27 Mar 202
including that, it attempts to build on the module path and the
Javadoc plugin apparently does not handle that well.
I fought similar issues for a while and eventually got rid of the problematic
dependency.
You might try moditect to insert a module name of your choice. You might try
appro
ject: https://github.com/solomax/javadoc-exclude
>
> The issue is NOT reproducible if "Automatic-Module-Name" is absent
>
> On Tue, 14 Feb 2023 at 13:42, Maxim Solodovnik wrote:
> >
> > Same results with version 3.5.0
> >
> > On Tue, 14 Feb 2023
Here is the sample project: https://github.com/solomax/javadoc-exclude
The issue is NOT reproducible if "Automatic-Module-Name" is absent
On Tue, 14 Feb 2023 at 13:42, Maxim Solodovnik wrote:
>
> Same results with version 3.5.0
>
> On Tue, 14 Feb 2023 at 12:07, M
Hi there,
context: https://issues.apache.org/jira/browse/OAK-10144
We recently updated Jackrabbit Oak to require Java 11, and since then,
one subproject fails to build Javadocs, but depending on how the goal is
invoked (I discovered this when trying to do a release and the javadoc
jar
Hi Bernhard,
[snip]
> Initially I tried to find a solution with a short command to produce and
> deploy the javadoc archive manually. However, the next step is anyway to
> automate this process and then it's less of a problem to split creation of
> the javadoc archive and depl
Hi Tamás,
thanks for following up!
So let me try to provide some context:
1) the javadoc archive contains only a subset of the classes from the project
2) the jar as the main file of the project is built in a normal build and then
in a later build stage outside of the maven build packaged
Hello!
I'm building a JavaDoc archive for a jar file with
mvn javadoc:javadoc assembly:single deploy
and maven-jar-plugin disabled so that only the JavaDoc archive gets deployed.
This has been working until updating to 3.9.0 (maven-deploy-plugin 3.x)
-because I only attach the Ja
Howdy,
so, personally I am in "limbo" about this, and let me explain why.
First let me state that I lack some context here:
- why is Bernhard doing this? (is he editing and then "testing" the edited
Javadoc? I mean, why is roundtrip needed [the deploy])
- where is he deplo
, I am really unsure about the exact intent.
> > But, there is already a comment on issue (someone else having similar
> > problem)
> >
> > Let's see if anyone else chimes in.
> >
> > HTH
> > Tamas
> >
> > On Wed, Feb 22, 2023 at 7:20 PM Bernha
at 7:20 PM Bernhard Schuhmann <
> bernhard.schuhm...@jedox.com> wrote:
>
>> Hello!
>>
>>
>>
>> I'm building a JavaDoc archive for a jar file with
>>
>>
>>
>> mvn javadoc:javadoc assembly:single deploy
>>
>>
nyone else chimes in.
HTH
Tamas
On Wed, Feb 22, 2023 at 7:20 PM Bernhard Schuhmann <
bernhard.schuhm...@jedox.com> wrote:
> Hello!
>
>
>
> I'm building a JavaDoc archive for a jar file with
>
>
>
> mvn javadoc:javadoc assembly:single deploy
>
>
>
>
Hello!
I'm building a JavaDoc archive for a jar file with
mvn javadoc:javadoc assembly:single deploy
and maven-jar-plugin disabled so that only the JavaDoc archive gets deployed.
This has been working until updating to 3.9.0 (maven-deploy-plugin 3.x)
-because I only attach the Ja
The Apache Maven team is pleased to announce the release of the Maven
Javadoc Plugin, version 3.5.0.
This module generates browsable HTML pages from Java source code.
https://maven.apache.org/plugins/maven-javadoc-plugin/
You should specify the version in your project's plugin configur
Same results with version 3.5.0
On Tue, 14 Feb 2023 at 12:07, Maxim Solodovnik wrote:
>
> Hello All,
>
> I'm getting following error while running `javadoc:3.4.1:jar`:
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-javadoc-plugin:3.4.1:jar
>
Hello All,
I'm getting following error while running `javadoc:3.4.1:jar`:
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-javadoc-plugin:3.4.1:jar
(attach-javadocs) on project openmeetings-util: Execution
attach-javadocs of goal
org.apache.maven.plugins:maven-javadoc-plugin:
Subject: Re: m-javadoc-plugin with JPMS
Ah, finally got past this bug to release by just backing out the one change in
my POM that I’d dismissed as irrelevant. I had entered this code in the
problematic module’s POM to work around a bug failing modular builds without an
intervening clean
install (or possibly site?) prior to the goal you’re trying to use.
From: "Daniel B. Widdis"
Date: Sunday, October 16, 2022 at 10:04 PM
To: Maven Users List
Subject: Re: m-javadoc-plugin with JPMS
It's amusing when you come upon an error, google the error message, and
le name in addition to the module
descriptor. Same problem.
I have tried changing the lifecycle phase during which these javadoc goals
are executed. Same problem.
I have tried adding "dummy" class files in the problematic module's source
tree just in case the solo file and lack of sup
maven-javadoc-plugin:3.4.1 - same error :(((
On Wed, 20 Jul 2022 at 22:19, Maxim Solodovnik wrote:
>
> done,
>
> same error :(
>
> On Wed, 20 Jul 2022 at 22:13, Maxim Solodovnik wrote:
> >
> > well,
> >
> > m-javadoc-plugin is being called at `*db
The Apache Maven team is pleased to announce the release of the Maven
Javadoc Plugin, version 3.4.1.
This module generates browsable HTML pages from Java source code.
https://maven.apache.org/plugins/maven-javadoc-plugin/
You should specify the version in your project's plugin configur
done,
same error :(
On Wed, 20 Jul 2022 at 22:13, Maxim Solodovnik wrote:
>
> well,
>
> m-javadoc-plugin is being called at `*db` module only which is only
> depends on `*util` module
> both has `module-info.java`
>
> let me add `module-info.java` to all modules
well,
m-javadoc-plugin is being called at `*db` module only which is only
depends on `*util` module
both has `module-info.java`
let me add `module-info.java` to all modules (not sure why) so we can
ensure this is not a problem :)
On Wed, 20 Jul 2022 at 21:51, Daniel Widdis wrote:
>
>
licitly name it. It will use your jar filename to deduce
>>> one. Unless you use a reserved word in your jar, and then the world
>>> breaks. __
>>>
>>> I thought maybe this is the issue in m-javadoc-plugin: it is weird to
>>> check `automat
gt; Technically speaking, you always have an automatic module name even if
> > you don't explicitly name it. It will use your jar filename to deduce
> > one. Unless you use a reserved word in your jar, and then the world
> > breaks. __
> >
> > I thought maybe t
explicitly name it. It will use your jar filename to deduce
> one. Unless you use a reserved word in your jar, and then the world
> breaks. __
>
> I thought maybe this is the issue in m-javadoc-plugin: it is weird to
> check `automatic module name` in manifest if module-info.java
ss you use a reserved word in your jar, and then the world breaks. __
I thought maybe this is the issue in m-javadoc-plugin: it is weird to
check `automatic module name` in manifest if module-info.java present
>
> On 7/18/22, 11:07 PM, "Maxim Solodovnik" wrote:
>
> Th
> > Hello All,
> >
> > I'm trying to migrate our project to JPMS
> > After adding module-info.java to my modules (and removing explicitly
> > set `Automatic-Module-Name`)
> > I'm getting:
> >
> After adding module-info.java to my modules (and removing explicitly
> > set `Automatic-Module-Name`)
> > I'm getting:
> >
> > [INFO] --- maven-javadoc-plugin:3.4.0:javadoc-no-fork (default)
> > [ERROR] Creating an aggregated report for both
wrong list? :)
On Fri, 15 Jul 2022 at 15:41, Maxim Solodovnik wrote:
>
> Hello All,
>
> I'm trying to migrate our project to JPMS
> After adding module-info.java to my modules (and removing explicitly
> set `Automatic-Module-Name`)
> I'
utomatic-Module-Name`)
> I'm getting:
>
> [INFO] --- maven-javadoc-plugin:3.4.0:javadoc-no-fork (default)
> [ERROR] Creating an aggregated report for both named and unnamed
> modules is not possible.
> [ERROR] Ensure that every module has a module descriptor or is a jar
>
Hello All,
I'm trying to migrate our project to JPMS
After adding module-info.java to my modules (and removing explicitly
set `Automatic-Module-Name`)
I'm getting:
[INFO] --- maven-javadoc-plugin:3.4.0:javadoc-no-fork (default)
[ERROR] Creating an aggregated report for both named a
ly anything
> using ASM.
> I've tried adding additional dependencies to the javadoc plugin referencing
> the non-shaded ASM artifacts, but no dice.
>
> Haven't had much luck searching this one out.
> Any suggestions?
>
> Thanks,
> -rl
>
-
ding additional dependencies to the javadoc plugin referencing
the non-shaded ASM artifacts, but no dice.
Haven't had much luck searching this one out.
Any suggestions?
Thanks,
-rl
The Apache Maven team is pleased to announce the release of the Maven
Javadoc Plugin, version 3.4.0.
This module generates browsable HTML pages from Java source code.
https://maven.apache.org/plugins/maven-javadoc-plugin/
You should specify the version in your project's plugin configur
The Apache Maven team is pleased to announce the release of the Maven
Javadoc Plugin, version 3.3.2.
This module generates browsable HTML pages from Java source code.
https://maven.apache.org/plugins/maven-javadoc-plugin/
You should specify the version in your project's plugin configur
The Apache Maven team is pleased to announce the release of the Apache
Maven Javadoc Plugin, version 3.3.1
The Javadoc Plugin uses the Javadoc tool to generate javadocs for the
specified project.
https://maven.apache.org/plugins/maven-javadoc-plugin/
You should specify the version in your
n
> >>>
> >>> This [1] guide instruct me to set
> >>> 1
> >>> and add
> >>> true
> >>> to javadoc configuration in pluginManagement
> >>>
> >>> as a result I'm getting
> >>>
> &g
7;m a bit confused with documentation
This [1] guide instruct me to set
1
and add
true
to javadoc configuration in pluginManagement
as a result I'm getting
Caused by: java.time.format.DateTimeParseException: Text '1' could not be
parsed
umentation
> >
> > This [1] guide instruct me to set
> > 1
> > and add
> > true
> > to javadoc configuration in pluginManagement
> >
> > as a result I'm getting
> >
> > Caused by: java.
1 - 100 of 1657 matches
Mail list logo
