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
or 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 find
It's amusing when you come upon an error, google the error message, and
find an email thread you participated in and forgot about.
Resurrecting this thread from last July and hoping for some insight.
I last released my project using maven-release-plugin on July 20, 2022 with
no issues. My
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` module only which is only
> > depends on
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 (not sure why) so we can
>
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:
>
> Some
Some modules have module-info.java and some don’t. That’s exactly what the
error says.
> On Jul 20, 2022, at 7:24 AM, Maxim Solodovnik wrote:
>
> On Tue, 19 Jul 2022 at 17:20, Olivier Lamy wrote:
>>
>>> On Tue, 19 Jul 2022 at 16:42, Maxim Solodovnik wrote:
>>>
>>> On Tue, 19 Jul 2022
On Tue, 19 Jul 2022 at 17:20, Olivier Lamy wrote:
>
> On Tue, 19 Jul 2022 at 16:42, Maxim Solodovnik wrote:
>
> > On Tue, 19 Jul 2022 at 13:16, Daniel Widdis wrote:
> > >
> > > > The only problem of having both is redundancy :)
> > >
> > > Technically speaking, you always have an automatic
On Tue, 19 Jul 2022 at 16:42, Maxim Solodovnik wrote:
> On Tue, 19 Jul 2022 at 13:16, Daniel Widdis wrote:
> >
> > > The only problem of having both is redundancy :)
> >
> > Technically speaking, you always have an automatic module name even if
> you don't explicitly name it. It will use your
On Tue, 19 Jul 2022 at 13:16, Daniel Widdis wrote:
>
> > The only problem of having both is redundancy :)
>
> 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
> The only problem of having both is redundancy :)
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. __
On 7/18/22, 11:07
Thanks for the answer Daniel :)
On Tue, 19 Jul 2022 at 13:03, Daniel Widdis wrote:
>
> I think you're asking on the right list. And it's not a "basic" question but
> it isn't an obvious answer either.
>
> I'm not sure your question has enough detail for anyone to deduce the answer.
> Linking
I think you're asking on the right list. And it's not a "basic" question but
it isn't an obvious answer either.
I'm not sure your question has enough detail for anyone to deduce the answer.
Linking to your project may help you get more attention on it.
FWIW, I have both an automatic module
Hello,
Is the question too basic?
Or maybe I'm asking 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'm
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 and unnamed
15 matches
Mail list logo
