e.org
Subject: Re: Why does Plexus Compiler parse compiler output, when forked? (was:
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 val
Thanks for the feedback. Happy it works for you now.
Catch-all category: I am on it (probably after Xmas). I will also add a
few more categories to be recognised correctly and salvage their headers
in multiple languages, too. Or maybe, the catch-all will replace all the
special stuff, if I can mak
t make sense of doesn't silently swallowed.)
But it works!
-Original Message-
From: Alexander Kriegisch
Sent: Saturday, December 23, 2023 7:53 PM
To: users@maven.apache.org
Subject: Re: Why does Plexus Compiler parse compiler output, when forked? (was:
maven debugging frustrations)
s version.
> Is there a way to be sure?
>
> -Original Message-
> From: mark.yagnatin...@barclays.com.INVALID
>
> Sent: Saturday, December 23, 2023 1:51 PM
> To: users@maven.apache.org
> Subject: RE: Why does Plexus Compiler parse compiler output, when forked?
>
Thanks for the stack trace. :-) I quickly tested it in a unit test with
Plexus Compiler 2.14.2, and like I guessed already, the stack trace is
detected, but not the two header lines above, because Plexus Javac does
not search for them (yet). I would expect you to see the stack trace,
but you said y
: RE: Why does Plexus Compiler parse compiler output, when forked? (was:
maven debugging frustrations)
CAUTION: This email originated from outside our organisation -
mark.yagnatin...@barclays.com.INVALID Do not click on links, open attachments,
or respond unless you recognize the sender and can
--
From: Yagnatinsky, Mark : Markets Pre Trade
Sent: Saturday, December 23, 2023 12:50 PM
To: Maven Users List
Subject: RE: Why does Plexus Compiler parse compiler output, when forked? (was:
maven debugging frustrations)
Okay you win, stack trace below. My bad, sorry, I should know bett
s black
> box binary blob with totally unknown behaviour?
>
> -Original Message-----
> From: Alexander Kriegisch
> Sent: Friday, December 22, 2023 10:23 PM
> To: users@maven.apache.org
> Subject: Re: maven debugging frustrations
>
>
> CAUTION: This email originated f
> -Original Message-
> From: Alexander Kriegisch
> Sent: Friday, December 22, 2023 10:23 PM
> To: users@maven.apache.org
> Subject: Re: maven debugging frustrations
>
>
> CAUTION: This email originated from outside our organisation -
> alexan...@kriegisch.name Do not cl
blob with totally unknown behaviour?
-Original Message-
From: Alexander Kriegisch
Sent: Friday, December 22, 2023 10:23 PM
To: users@maven.apache.org
Subject: Re: maven debugging frustrations
CAUTION: This email originated from outside our organisation -
alexan...@kriegisch.name Do
>> How can I can find out EXACTLY how maven invoked javac, so I can
>> invoke it the same way?
I think, somebody already mentioned earlier that you can just activate
debug output in Maven. Then search for the line following "Command line
options":
$ mvn -X compile | grep --after-context 1 'Comman
: Friday, December 22, 2023 9:45 AM
To: users@maven.apache.org
Subject: RE: maven debugging frustrations
CAUTION: This email originated from outside our organisation -
mark.yagnatin...@barclays.com.INVALID Do not click on links, open attachments,
or respond unless you recognize the sender and can
PM
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.
Mark, you asked for
> 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 -
&g
lugin...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.n
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 (
his theory has problems.
>
> -Original Message-
> From: Tomo Suzuki
> Sent: Tuesday, December 19, 2023 6:15 PM
> To: Maven Users List
> Subject: Re: maven debugging frustrations
>
>
> CAUTION: This email originated from outside our organisation -
> suzt...@googl
2023 6:15 PM
To: Maven Users List
Subject: Re: maven debugging frustrations
CAUTION: This email originated from outside our organisation -
suzt...@google.com.INVALID Do not click on links, open attachments, or respond
unless you recognize the sender and can validate the content is safe.
My gue
> > I do not recommend feeling my maven-based pain :)
> > But if you happen to know where to get some pain relief, I'd love to know
> >
> > -Original Message-
> > From: Tomo Suzuki
> > Sent: Tuesday, December 19, 2023 5:18 PM
> > To: Maven
from maven, NOT from javac)
> I do not recommend feeling my maven-based pain :)
> But if you happen to know where to get some pain relief, I'd love to know
>
> -Original Message-
> From: Tomo Suzuki
> Sent: Tuesday, December 19, 2023 5:18 PM
> To: Maven Users List
> -Original Message-
> From: Mark Eggers
> Sent: Tuesday, December 19, 2023 5:11 PM
> To: users@maven.apache.org
> Subject: Re: maven debugging frustrations
>
>
> CAUTION: This email originated from outside our organisation -
> its_toas...@yahoo.com.INVALID Do not
December 19, 2023 5:11 PM
To: users@maven.apache.org
Subject: Re: maven debugging frustrations
CAUTION: This email originated from outside our organisation -
its_toas...@yahoo.com.INVALID Do not click on links, open attachments, or
respond unless you recognize the sender and can validate the content is
, NOT from javac)
I do not recommend feeling my maven-based pain :)
But if you happen to know where to get some pain relief, I'd love to know
-Original Message-
From: Tomo Suzuki
Sent: Tuesday, December 19, 2023 5:18 PM
To: Maven Users List
Subject: Re: maven debugging frustrations
What’s the exact error messages?
(Maybe I’m too old to feel your pain) If you use Java, you need to know
what compilation means (converting Java code to Java bytecode). Your Maven
invocation was telling it was failing due to some error messages.
On Tue, Dec 19, 2023 at 16:57 wrote:
> When my J
Thanks, I've heard of all three; the first two don't seem like they'd help here.
The third tends to spew junk and not useful stuff
-Original Message-
From: Mark Eggers
Sent: Tuesday, December 19, 2023 5:11 PM
To: users@maven.apache.org
Subject: Re: maven debugging frustra
Some commands that might help you get started:
What are you using to build the artifact
mvn help:effective-pom
mvn help:effective-pom -Dverbose
What artifacts are being brought in
--
mvn dependency:t
When my Java code does something I didn't expect, I can run it under a debugger
and step through it line by line until things make sense again.
When maven does something I didn't expect, my debugging strategy is usually
more like "try to think of something in my bag of tricks".
Sometimes I sudden
27 matches
Mail list logo
