RE: maven compiler plugin 3.12.0 and Kotlin project

[Stefan CORDES]

Hi Hantsy,
that should be the same like
https://issues.apache.org/jira/browse/MCOMPILER-567
and fixed in 3.12.1

Workaround is to stay on 3.11.0 or use 
false

Gruß,
Stefan

-Original Message-
From: hantsy bai 
Sent: Friday, December 22, 2023 5:20 AM
To: Maven Users List 
Subject: maven compiler plugin 3.12.0 and Kotlin project

I tried to update Maven compiler plugin version to the latest 3.12.0 version, 
and got the error message like the following when compiling the
projects:

[INFO] --- compiler:3.12.0:compile (default-compile) @ mongodb-kotlin --- 
[INFO] Recompiling the module because of changed dependency.
[INFO]

[INFO] BUILD FAILURE
[INFO]

[INFO] Total time:  02:12 min
[INFO] Finished at: 2023-12-22T12:14:43+08:00 [INFO]

[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-compiler-plugin:3.12.0:compile
(default-compile) on project mongodb-kotlin: Fatal error compiling: basedir 
D:\hantsylabs\quarkus-sample\mongodb-kotlin\target\generated-sources\annotations
does not exist -> [Help 1]

I found the error only occurred in a Kotlin project, check an example of the 
updated pom.xml here, 
https://github.com/hantsy/quarkus-sandbox/blob/master/resteasy-kotlin-co/pom.xml
---

Regards,

*Hantsy Bai*

Self-employed consultant, fullstack developer, agile coach, freelancer/remote 
worker

GitHub: https://github.com/hantsy

Twitter: https://twitter.com/@hantsy
Medium: https://medium.com/@hantsy

C Services GmbH & Co. OHG | Wanheimer Straße 70 | D-40468 Düsseldorf | Sitz: 
Düsseldorf | Registergericht: Düsseldorf HRA 12655 | Telefon: +49 (211) 9872-01
Persönlich haftende Gesellschafter: C Retail GmbH | Sitz: Baar/Schweiz | UID: 
CHE-116.290.471
Geschäftsführung: Giny Boer, Christoph Hammer
FRM Participations S.A. | Sitz: Strassen/Luxemburg | Handels- und 
Firmenregister Luxemburg: B 58158
Verwaltungsratsmitglieder: Dr. Christian Bank, Remco Gerlof, Dr. Franz-Josef 
Leuchtenberg
Hinweise zur Verarbeitung Ihrer Daten finden Sie unter: 
www.c-a.com/GDPR

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

[ANN] Apache Maven 4.0.0-alpha-10 released

[Guillaume Nodet]

The Apache Maven team is pleased to announce the release of
Apache Maven 4.0.0-alpha-10.

Apache Maven is a software project management and comprehension tool.
Based on the concept of a project object model (POM), Maven can manage
a project's build, reporting and documentation from a central piece of
information.

Maven 4.0.0-alpha-10 is available via https://maven.apache.org/download.cgi

This is an alpha release, not suitable for production. If you hit any
problem,
please raise a JIRA issue or send an email to the mailing list.

The full list of changes can be found in our issue management system [1].
Among those are:
 * user controlled relocations
 * fix broken javadoc:jar goal
 * fix resolver that may cause maven never to quit

For more information read
https://maven.apache.org/docs/4.0.0-alpha-10/release-notes.html

[1]
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922=12354013

Enjoy !
Guillaume Nodet

Re: maven compiler plugin 3.12.0 and Kotlin project

[Slawomir Jaranowski]

Hi,

The problem is known ... we have a thread on ML about it [1]

Bug was fixed, version 3.12.1 will be available after voting [2]

[1] https://lists.apache.org/thread/dkzy7vx609m0lndt4vy5pn8pk4zvst46
[2] https://lists.apache.org/thread/scb8qw1or396l4hqgf5h78z5h0km60z4


pt., 22 gru 2023 o 05:20 hantsy bai  napisał(a):

> I tried to update Maven compiler plugin version to the latest 3.12.0
> version, and got the error message like the following when compiling the
> projects:
>
> [INFO] --- compiler:3.12.0:compile (default-compile) @ mongodb-kotlin ---
> [INFO] Recompiling the module because of changed dependency.
> [INFO]
>
> 
> [INFO] BUILD FAILURE
> [INFO]
>
> 
> [INFO] Total time:  02:12 min
> [INFO] Finished at: 2023-12-22T12:14:43+08:00
> [INFO]
>
> 
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-compiler-plugin:3.12.0:compile
> (default-compile) on project mongodb-kotlin: Fatal error compiling: basedir
>
> D:\hantsylabs\quarkus-sample\mongodb-kotlin\target\generated-sources\annotations
> does not exist -> [Help 1]
>
> I found the error only occurred in a Kotlin project, check an example of
> the updated pom.xml here,
>
> https://github.com/hantsy/quarkus-sandbox/blob/master/resteasy-kotlin-co/pom.xml
> ---
>
> Regards,
>
> *Hantsy Bai*
>
> Self-employed consultant, fullstack developer, agile coach,
> freelancer/remote worker
>
> GitHub: https://github.com/hantsy
>
> Twitter: https://twitter.com/@hantsy
> Medium: https://medium.com/@hantsy
>


-- 
Sławomir Jaranowski

maven compiler plugin 3.12.0 and Kotlin project

[hantsy bai]

I tried to update Maven compiler plugin version to the latest 3.12.0
version, and got the error message like the following when compiling the
projects:

[INFO] --- compiler:3.12.0:compile (default-compile) @ mongodb-kotlin ---
[INFO] Recompiling the module because of changed dependency.
[INFO]

[INFO] BUILD FAILURE
[INFO]

[INFO] Total time:  02:12 min
[INFO] Finished at: 2023-12-22T12:14:43+08:00
[INFO]

[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-compiler-plugin:3.12.0:compile
(default-compile) on project mongodb-kotlin: Fatal error compiling: basedir
D:\hantsylabs\quarkus-sample\mongodb-kotlin\target\generated-sources\annotations
does not exist -> [Help 1]

I found the error only occurred in a Kotlin project, check an example of
the updated pom.xml here,
https://github.com/hantsy/quarkus-sandbox/blob/master/resteasy-kotlin-co/pom.xml
---

Regards,

*Hantsy Bai*

Self-employed consultant, fullstack developer, agile coach,
freelancer/remote worker

GitHub: https://github.com/hantsy

Twitter: https://twitter.com/@hantsy
Medium: https://medium.com/@hantsy

Re: maven debugging frustrations

[Alexander Kriegisch]

Mark, you asked for help here, now I am asking for your help to make
Maven Compiler and Maven Plexus Java better. Can you please switch back
to the too-low memory settings you used before and reproduce the javac
error output when compiled outside Maven? Was it something as simple as:

$ javac -J-Xmx32k org/example/MySecondAnnotation.java 
Error occurred during initialization of VM
Initial heap size set to a larger value than the maximum heap size

This would be silently swallowed even after my fix, because my fix was
about stack trace parsing. It is, however, much more difficult to
separate other JVM or javac error output from output possibly produced
by e.g. annotation processors. It does not get easier, given the fact,
that JVM output is localised to a handful of languages, not just
English.

Or did you get some kind of out of memory error with a stack trace? The
error parser for forked javac undoubtedly needs more hardening and
improvements to at least parse (and display!) the most common error
messages correctly. I scratched my own itch lately by contributing an
improvement for the first time. Before I forget about the source code
context again and move on to other projects, maybe I can contribute a
little bit more. But then, I need input.

Thanks in advance and kind regards
-- 
Alexander Kriegisch
https://scrum-master.de

mark.yagnatin...@barclays.com.INVALID schrieb am 21.12.2023 23:43 (GMT +07:00):

> Forked: yes
> Other questions: didn't check, because using a bigger heap ("maxmem") fixed 
> it.
> But thanks for this, that looks like it would have helped us!
> (in a hypothetical world where that PR was merged ten years earlier)
> (We're mostly using version 3.8 of maven-compiler-plugin...perhaps it's time 
> to
> upgrade.)
> 
> -Original Message-
> From: Alexander Kriegisch  
> Sent: Wednesday, December 20, 2023 12:41 AM
> To: users@maven.apache.org
> Subject: Re: maven debugging frustrations
> 
> 
> CAUTION: This email originated from outside our organisation -
> alexan...@kriegisch.name Do not click on links, open attachments, or respond
> unless you recognize the sender and can validate the content is safe.
> Hello Mark.
> 
> Feel free to let me know if your situation is as follows:
>   -- forked build (i.e. not in process)
>   -- when disabling the fork and enabling "-e" or running the build with
>  javac directly outside of Maven, suddenly error messages appear at
>  the end of the build
>   -- optionally (not necessarily) using a JDK locale other than English
>  (e.g. javac in JDK 21 comes with localised messages in Chinese,
>  Japanese, German)
>   -- optionally (not necessarily) using an annotation processor
> 
> I recently had the symptom of build errors with forked compiler swallowing
> error messages and scratched my own itch by adding a PR to Plexus Javac which
> for me solves the problem. If your problem happens to be the same category, 
> you
> would be the perfect sentient test particle for
> https://clicktime.symantec.com/15siFBZrUArbTHh6FWx5d?h=_vziVdl8fIA-_du7fPQDmEDaVPK6D7XlieIqn88Lnv0==https://github.com/codehaus-plexus/plexus-compiler/pull/337.
> I can advise you how to get that running in your project.
> 
> Regards
> --
> Alexander Kriegisch
> https://clicktime.symantec.com/15siL1m8vnYBsEX1o5MEF?h=EIrFDp-q7MAJaGlzS3rT2Qpp_OrLzsXNXIASmesIlO4==https://scrum-master.de
> 
> 
> mark.yagnatin...@barclays.com.INVALID schrieb am 20.12.2023 05:27 (GMT 
> +07:00):
> 
>> Indeed, if there were ACTUAL error messages from the java compiler,
>> this would be far less mysterious :) The trouble is that there are NOT
>> any error messages coming from the Java compiler. There are a few
>> warnings (from javac), followed soon after by "Compilation failure"
>> (from maven, NOT from javac)
> 
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
> 
> 
> This message is for information purposes only. It is not a recommendation,
> advice, offer or solicitation to buy or sell a product or service, nor an
> official confirmation of any transaction. It is directed at persons who are
> professionals and is intended for the recipient(s) only. It is not directed at
> retail customers. This message is subject to the terms at:
> https://www.cib.barclays/disclosures/web-and-email-disclaimer.html. 
> 
> For important disclosures, please see:
> https://www.cib.barclays/disclosures/sales-and-trading-disclaimer.html
> regarding marketing commentary from Barclays Sales and/or Trading desks, who
> are active market participants;
> https://www.cib.barclays/disclosures/barclays-global-markets-disclosures.html
> regarding our standard terms for Barclays Corporate and Investment Bank where
> we trade with you in principal-to-principal wholesale markets transactions; 
> and
> in respect to Barclays Research, including disclosures relating to specific
> 

Re: Maven 4.0 release timeline

[Tamás Cservenák]

Well,

we have some notes and scratches around like these:
https://cwiki.apache.org/confluence/display/MAVEN/Maven+Ecosystem+Cleanup
https://cwiki.apache.org/confluence/display/MAVEN/Towards+Doxia+2.0.0+Stack

But these are about Maven "ecosystem" that needed a lot of work to make
those up to date.
The "battle" with Maven4 API is _not present here_, as we can only work by
data that "trickles" to us,
or we spend our own energy to look up all the plugins out there...

Thanks
T

On Wed, Dec 20, 2023 at 12:55 PM Debraj Manna 
wrote:

> When I asked about the release timeline, I was enquiring whether Maven also
> has release management documentation like the way some other apache
> projects Flink or Kafka do. I was not able to find it for maven 4.
>
> Anyways thanks, Marteen for the references.
>
> https://cwiki.apache.org/confluence/display/FLINK/2.0+Release
> https://cwiki.apache.org/confluence/display/KAFKA/Release+Plan+3.7.0
>
> On Tue, Dec 19, 2023 at 9:53 PM 
> wrote:
>
> > Thank you!  I'd seen [4] but not sure if I've seen [2]
> >
> > -Original Message-
> > From: Maarten Mulders 
> > Sent: Tuesday, December 19, 2023 9:07 AM
> > To: users@maven.apache.org
> > Subject: Re: Maven 4.0 release timeline
> >
> >
> > CAUTION: This email originated from outside our organisation -
> > mthmuld...@apache.org Do not click on links, open attachments, or
> respond
> > unless you recognize the sender and can validate the content is safe.
> > On 18/12/2023 21:38, mark.yagnatin...@barclays.com.INVALID wrote:
> > > I'm not the original asker but this kind of answer tends to annoy me.
> > > Yes, there is no "official" release timeline, you're obviously not
> going
> > to promise anything, all this is (hopefully?) clear, BUT!
> > > You no doubt have GUESSES.  And your guesses are no doubt better than
> > that of most uninformed outsiders.
> > > As an outsider, I have no idea what the "status" of maven 4 is, and I
> > can't even begin to guess how I would find out.
> > > Should I try to catch up on the last few years of traffic on the
> > developer email lists?
> > > Or perhaps the answer can be divined from the issue tracker?  If so,
> how?
> > > Is it expected that alpha-10 will be the last alpha, and the next build
> > will be a beta?
> > > If that is NOT what you expect, then what's the primary hold up?
> > > Are there major features that have yet to be implemented?
> > > Or perhaps the features are mostly done but they're still a bit buggy?
> > > Or perhaps the code quality is pretty solid and you just want to
> reserve
> > the right to make backwards incompatible changes, and there's a policy to
> > not do that after hitting beta?
> > >
> > > You get the idea.  As an insider, you probably think to yourself
> > "there's no telling when we'll be done; it depends on a zillion
> > unpredictable things".
> > > But as outsiders, we don't even know whether the ETA is a few months or
> > a few years or a few decades or perhaps just a few weeks.
> > >
> > > Sorry if that came off as a bit of a rant :)
> > The good news is, you don't have to read the mailing list history, nor
> > dive into the issue tracker, nor read the git history. If you're curious
> > what Maven 4 will bring, I can highly recommend watching Karl-Heinz'
> > talk [1]. Don't feel like watching somebody talk? You can read about some
> > interesting articles and documentation: [2], [3], [4].
> >
> > Hope this helps,
> >
> >
> > Maarten
> >
> >
> > [1]
> >
> https://clicktime.symantec.com/15sMvS6QDE6q6Jf47vc58?h=tZSjeMLRMnL1sHS93b7vt02NnPNvJwK6-ee8iyLMi5Q==https://youtu.be/fHeVMbQNbgQ
> > [2]
> >
> https://clicktime.symantec.com/15sMFnY8YJe5nk3fmTQtA?h=sQem5P67RYOhsiW9Hm_YeD-PIfsaReOsBbMYvlLdgRk==https://maven.apache.org/guides/mini/guide-multiple-modules-4.html
> > [3]
> >
> https://clicktime.symantec.com/15sM1HxHATbJYuZu8nDSJ?h=s87AfscrtMWpDN9FZxBHl_MjXK1i_ohGn2TWRZhFFZ4==https://cwiki.apache.org/confluence/display/MAVEN/Build%2Bvs%2BConsumer%2BPOM
> > [4]
> >
> https://clicktime.symantec.com/15sMqbu7kcREgMq8aNCvW?h=2OV2Xb8OY1yozkosb4XLJzGzmH5eCx0rkkaq0thqbr4==https://www.javaadvent.com/2021/12/from-maven-3-to-maven-5.html
> >
> > PS. Most of the above was exactly one Google search away...: "Maven 4"
> >
> > > -Original Message-
> > > From: Karl Heinz Marbaise 
> > > Sent: Monday, December 18, 2023 3:18 PM
> > > To: Maven Users List ; Debraj Manna
> > > 
> > > Subject: Re: Maven 4.0 release timeline
> > >
> > >
> > > CAUTION: This email originated from outside our organisation -
> > khmarba...@gmx.de.INVALID Do not click on links, open attachments, or
> > respond unless you recognize the sender and can validate the content is
> > safe.
> > > On 18.12.23 06:27, Debraj Manna wrote:
> > >> Can someone let me know when Maven 4 is expected to be released?
> > >> Where can I view its release timelines?
> > >>
> > >
> > > We are an open source project. We don't have a release timeline.
> > >
> > > Maven 4.0.0 will be there when it's there.
> > >
> > >
> 

Re: Fatal error compiling: basedir .../target/generated-sources/annotations does not exist

[Stanimir Stamenkov]

Thu, 21 Dec 2023 09:10:44 +0100, /Slawomir Jaranowski/:


Release under vote ... you can check candidate version:
https://lists.apache.org/thread/scb8qw1or396l4hqgf5h78z5h0km60z4


Tried maven-compiler-plugin 3.12.1 from the staging repository – no 
error during the build.


--
Stanimir

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Releasing a multi-module project to Maven Central?

[Nils Breunese]

Maybe the BuildPlan Maven Plugin [0] can provide interesting insights?

Nils.

[0] https://www.mojohaus.org/buildplan-maven-plugin/

> Op 21 dec 2023, om 17:46 heeft Laird Nelson  het volgende 
> geschreven:
> 
> Thanks. I'll take whatever help I can get right now.
> 
> I've tried the jar goal and the jar-no-fork goal. Somehow the goal always
> runs multiple times. It is difficult to tell what is causing the rebuild.
> 
> (The javadoc plugin doesn't have a jar goal that doesn't fork, as far as I
> can tell. But also as far as I can tell even when forking it doesn't invoke
> the package phase, so the source plugin goal doesn't get kicked off by it
> again.)
> 
> Yes, I've read the publishing guide (and have released dozens of projects
> to Maven Central in the past using nothing more complicated than the
> recommended maven-release-plugin recipes). I don't remember, however, the
> last time I tried it with a multi-module project.
> 
> I'm beginning to suspect something about the Nexus staging plugin and its
> interaction with multi-module projects. It does want to do the actual
> deploy step at the very end of the project, and I just now noticed that I'm
> getting some strange log output. The reactor messages about which project
> is building contain strange counts.
> 
> For example, I have a grand total of four modules: the parent/aggregator,
> and three children. So as the parent is building, you see "[1/4]" (for
> example) in the logs. At the end of the Nexus-staging-plugin-managed
> deployment step, you see things like "[7/4]" which suggests to me something
> is going on deep in the reactor somewhere.
> 
> L
> 
> On Thu, Dec 21, 2023 at 12:04 AM Thomas Broyer  wrote:
> 
>> Shouldn't you use the jar-no-fork *goal* of the maven-source-plugin? Using
>> that value as execution id does nothing special.
>> 
>> BTW, did you read https://central.sonatype.org/publish/publish-maven/ ?
>> 
>> (No idea if any of this would solve your problem though)
>> 
>> Le jeu. 21 déc. 2023, 03:15, Laird Nelson  a écrit :
>> 
>>> On Wed, Dec 20, 2023 at 5:45 PM Laird Nelson  wrote:
>>> 
 That is, when I tell the maven-release-plugin to activate the
>>> "deployment"
 profile (via the releaseProfiles user property), I am told that the
>>> source
 plugin has been invoked twice, and the build fails.
 
>>> 
>>> I think this is because the maven-javadoc-plugin's jar goal invokes the
>>> lifecycle, which of course contains the maven-source-plugin's jar-no-fork
>>> goal, which attaches the source jar. How would I make this work?
>>> 
>>> Best,
>>> Laird
>>> 
 
>>> 
>> 


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Releasing a multi-module project to Maven Central?

[Slawomir Jaranowski]

Hi,

Can you show a log from your build... especially lines like:

[INFO] --- jar:3.3.0:jar (default-jar) @ . ---

Is your project available publicly?

czw., 21 gru 2023 o 17:47 Laird Nelson  napisał(a):

> Thanks. I'll take whatever help I can get right now.
>
> I've tried the jar goal and the jar-no-fork goal. Somehow the goal always
> runs multiple times. It is difficult to tell what is causing the rebuild.
>
> (The javadoc plugin doesn't have a jar goal that doesn't fork, as far as I
> can tell. But also as far as I can tell even when forking it doesn't invoke
> the package phase, so the source plugin goal doesn't get kicked off by it
> again.)
>
> Yes, I've read the publishing guide (and have released dozens of projects
> to Maven Central in the past using nothing more complicated than the
> recommended maven-release-plugin recipes). I don't remember, however, the
> last time I tried it with a multi-module project.
>
> I'm beginning to suspect something about the Nexus staging plugin and its
> interaction with multi-module projects. It does want to do the actual
> deploy step at the very end of the project, and I just now noticed that I'm
> getting some strange log output. The reactor messages about which project
> is building contain strange counts.
>
> For example, I have a grand total of four modules: the parent/aggregator,
> and three children. So as the parent is building, you see "[1/4]" (for
> example) in the logs. At the end of the Nexus-staging-plugin-managed
> deployment step, you see things like "[7/4]" which suggests to me something
> is going on deep in the reactor somewhere.
>
> L
>
> On Thu, Dec 21, 2023 at 12:04 AM Thomas Broyer  wrote:
>
> > Shouldn't you use the jar-no-fork *goal* of the maven-source-plugin?
> Using
> > that value as execution id does nothing special.
> >
> > BTW, did you read https://central.sonatype.org/publish/publish-maven/ ?
> >
> > (No idea if any of this would solve your problem though)
> >
> > Le jeu. 21 déc. 2023, 03:15, Laird Nelson  a écrit :
> >
> > > On Wed, Dec 20, 2023 at 5:45 PM Laird Nelson 
> wrote:
> > >
> > > > That is, when I tell the maven-release-plugin to activate the
> > > "deployment"
> > > > profile (via the releaseProfiles user property), I am told that the
> > > source
> > > > plugin has been invoked twice, and the build fails.
> > > >
> > >
> > > I think this is because the maven-javadoc-plugin's jar goal invokes the
> > > lifecycle, which of course contains the maven-source-plugin's
> jar-no-fork
> > > goal, which attaches the source jar. How would I make this work?
> > >
> > > Best,
> > > Laird
> > >
> > > >
> > >
> >
>


-- 
Sławomir Jaranowski

Re: Releasing a multi-module project to Maven Central?

[Laird Nelson]

Thanks. I'll take whatever help I can get right now.

I've tried the jar goal and the jar-no-fork goal. Somehow the goal always
runs multiple times. It is difficult to tell what is causing the rebuild.

(The javadoc plugin doesn't have a jar goal that doesn't fork, as far as I
can tell. But also as far as I can tell even when forking it doesn't invoke
the package phase, so the source plugin goal doesn't get kicked off by it
again.)

Yes, I've read the publishing guide (and have released dozens of projects
to Maven Central in the past using nothing more complicated than the
recommended maven-release-plugin recipes). I don't remember, however, the
last time I tried it with a multi-module project.

I'm beginning to suspect something about the Nexus staging plugin and its
interaction with multi-module projects. It does want to do the actual
deploy step at the very end of the project, and I just now noticed that I'm
getting some strange log output. The reactor messages about which project
is building contain strange counts.

For example, I have a grand total of four modules: the parent/aggregator,
and three children. So as the parent is building, you see "[1/4]" (for
example) in the logs. At the end of the Nexus-staging-plugin-managed
deployment step, you see things like "[7/4]" which suggests to me something
is going on deep in the reactor somewhere.

L

On Thu, Dec 21, 2023 at 12:04 AM Thomas Broyer  wrote:

> Shouldn't you use the jar-no-fork *goal* of the maven-source-plugin? Using
> that value as execution id does nothing special.
>
> BTW, did you read https://central.sonatype.org/publish/publish-maven/ ?
>
> (No idea if any of this would solve your problem though)
>
> Le jeu. 21 déc. 2023, 03:15, Laird Nelson  a écrit :
>
> > On Wed, Dec 20, 2023 at 5:45 PM Laird Nelson  wrote:
> >
> > > That is, when I tell the maven-release-plugin to activate the
> > "deployment"
> > > profile (via the releaseProfiles user property), I am told that the
> > source
> > > plugin has been invoked twice, and the build fails.
> > >
> >
> > I think this is because the maven-javadoc-plugin's jar goal invokes the
> > lifecycle, which of course contains the maven-source-plugin's jar-no-fork
> > goal, which attaches the source jar. How would I make this work?
> >
> > Best,
> > Laird
> >
> > >
> >
>

RE: maven debugging frustrations

[mark.yagnatinsky]

Forked: yes
Other questions: didn't check, because using a bigger heap ("maxmem") fixed it.
But thanks for this, that looks like it would have helped us!
(in a hypothetical world where that PR was merged ten years earlier)
(We're mostly using version 3.8 of maven-compiler-plugin...perhaps it's time to 
upgrade.)

-Original Message-
From: Alexander Kriegisch  
Sent: Wednesday, December 20, 2023 12:41 AM
To: users@maven.apache.org
Subject: Re: maven debugging frustrations


CAUTION: This email originated from outside our organisation - 
alexan...@kriegisch.name Do not click on links, open attachments, or respond 
unless you recognize the sender and can validate the content is safe.
Hello Mark.

Feel free to let me know if your situation is as follows:
  -- forked build (i.e. not in process)
  -- when disabling the fork and enabling "-e" or running the build with
 javac directly outside of Maven, suddenly error messages appear at
 the end of the build
  -- optionally (not necessarily) using a JDK locale other than English
 (e.g. javac in JDK 21 comes with localised messages in Chinese,
 Japanese, German)
  -- optionally (not necessarily) using an annotation processor

I recently had the symptom of build errors with forked compiler swallowing 
error messages and scratched my own itch by adding a PR to Plexus Javac which 
for me solves the problem. If your problem happens to be the same category, you 
would be the perfect sentient test particle for 
https://clicktime.symantec.com/15siFBZrUArbTHh6FWx5d?h=_vziVdl8fIA-_du7fPQDmEDaVPK6D7XlieIqn88Lnv0==https://github.com/codehaus-plexus/plexus-compiler/pull/337.
 I can advise you how to get that running in your project.

Regards
--
Alexander Kriegisch
https://clicktime.symantec.com/15siL1m8vnYBsEX1o5MEF?h=EIrFDp-q7MAJaGlzS3rT2Qpp_OrLzsXNXIASmesIlO4==https://scrum-master.de


mark.yagnatin...@barclays.com.INVALID schrieb am 20.12.2023 05:27 (GMT +07:00):

> Indeed, if there were ACTUAL error messages from the java compiler,
> this would be far less mysterious :) The trouble is that there are NOT
> any error messages coming from the Java compiler. There are a few
> warnings (from javac), followed soon after by "Compilation failure"
> (from maven, NOT from javac)

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org


This message is for information purposes only. It is not a recommendation, 
advice, offer or solicitation to buy or sell a product or service, nor an 
official confirmation of any transaction. It is directed at persons who are 
professionals and is intended for the recipient(s) only. It is not directed at 
retail customers. This message is subject to the terms at: 
https://www.cib.barclays/disclosures/web-and-email-disclaimer.html. 

For important disclosures, please see: 
https://www.cib.barclays/disclosures/sales-and-trading-disclaimer.html 
regarding marketing commentary from Barclays Sales and/or Trading desks, who 
are active market participants; 
https://www.cib.barclays/disclosures/barclays-global-markets-disclosures.html 
regarding our standard terms for Barclays Corporate and Investment Bank where 
we trade with you in principal-to-principal wholesale markets transactions; and 
in respect to Barclays Research, including disclosures relating to specific 
issuers, see: http://publicresearch.barclays.com.
__
 
If you are incorporated or operating in Australia, read these important 
disclosures: 
https://www.cib.barclays/disclosures/important-disclosures-asia-pacific.html.
__
For more details about how we use personal information, see our privacy notice: 
https://www.cib.barclays/disclosures/personal-information-use.html. 
__

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Fatal error compiling: basedir .../target/generated-sources/annotations does not exist

[Slawomir Jaranowski]

Hi,

Release under vote ... you can check candidate version:
https://lists.apache.org/thread/scb8qw1or396l4hqgf5h78z5h0km60z4

śr., 20 gru 2023 o 21:04 Slawomir Jaranowski 
napisał(a):

> Hi
>
> MCOMPILER-379 - was about missing SourcesDirectory and we have IT for it:
> https://github.com/apache/maven-compiler-plugin/commit/6fd3a46885edd81e62ae62cfc798c1e1b903e170
>
> MCOMPILER-567 - is for missing generated-sources/annotations - now we also
> have IT for it: https://github.com/apache/maven-compiler-plugin/pull/218
>
> Additionally I add a check in plexus-compiler
> https://github.com/codehaus-plexus/plexus-compiler/pull/338
>
> So we should be safe with mentioned fixes.
>
>
> śr., 20 gru 2023 o 20:43 Greg Chabala  napisał(a):
>
>> Hello Sławomir,
>>
>> Do you know if MCOMPILER-379 is the same issue as MCOMPILER-567 ? If so,
>> shouldn't the IT test in MCOMPILER-379 have caught it?
>>
>> Greg
>>
>
>
> --
> Sławomir Jaranowski
>


-- 
Sławomir Jaranowski

Re: Releasing a multi-module project to Maven Central?

[Thomas Broyer]

Shouldn't you use the jar-no-fork *goal* of the maven-source-plugin? Using
that value as execution id does nothing special.

BTW, did you read https://central.sonatype.org/publish/publish-maven/ ?

(No idea if any of this would solve your problem though)

Le jeu. 21 déc. 2023, 03:15, Laird Nelson  a écrit :

> On Wed, Dec 20, 2023 at 5:45 PM Laird Nelson  wrote:
>
> > That is, when I tell the maven-release-plugin to activate the
> "deployment"
> > profile (via the releaseProfiles user property), I am told that the
> source
> > plugin has been invoked twice, and the build fails.
> >
>
> I think this is because the maven-javadoc-plugin's jar goal invokes the
> lifecycle, which of course contains the maven-source-plugin's jar-no-fork
> goal, which attaches the source jar. How would I make this work?
>
> Best,
> Laird
>
> >
>