[
https://issues.apache.org/jira/browse/SUREFIRE-1788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17150310#comment-17150310
]
Alexander Kriegisch edited comment on SUREFIRE-1788 at 7/2/20, 2:31 PM:
------------------------------------------------------------------------
_(Damn it, when starting to edit in "Text" mode and clicking on "Visual" all my
text was lost, not for the first time.)_
Funny, I just opened this page again because I wanted to report hat I found out
that {{<useModulePath>false</useModulePath>}} actually helps mitigate the
problem and my build no longer freezes, only to find out that you had written
the same. 😉
But now my build logs look quite messy, content from different lines mixed into
one, even mixed up between stdLog and stdErr output. Fore example, something
like that should be my own logging on stdOut and some ByteBuddy logging on
stdErr becomes:
{code}
[Byte Buddy] RESET
net.bytebuddy.agent.builder.AgentBuilder$Default$ExecutingTransformer$ByteBuddy$ModuleSupport@6179e425
on sun.instrument.InstrumentationImpl@70cf32e3
[Byte Buddy] BEFORE_INSTALL
net.bytebuddy.agent.builder.AgentBuilder$Default$ExecutingTransformer$ByteBuddy$ModuleSupport@1fcb4808
on sun.instrument.InstrumentationImpl@70cf32e3
Mock closed
Closing Mock
{code}
{code}
M[Byte Buddy] RESET
net.bytebuddy.agent.builder.AgentBuilder$Default$ExecutingTransformer$ByteBuddy$ModuleSupport@6179e425
on sun.instrument.InstrumentationImpl@70cf32e3
Byte Buddy] BEFORE_INSTALL
net.bytebuddy.agent.builder.AgentBuilder$Default$ExecutingTransformer$ByteBuddy$ModuleSupport@1fcb4808
on sun.instrumeClosing Mock
ock closed
nt.InstrumentationImpl@70cf32e3
{code}
In M4 everything looked normal. The new console output handler seems to be a
very asynchronous guy...
{quote}The fix goes to M6.{quote}
Okay, more waiting for me then.
was (Author: kriegaex):
_(Damn it, when starting to edit in "Text" mode and clicking on "Visual" all my
text was lost, not for the first time.)_
Funny, I just opened this page again because I wanted to report hat I found out
that {{<useModulePath>false</useModulePath>}} actually helps mitigate the
problem and my build no longer freezes, only to find out that you had written
the same. 😉
But now my build logs look quite messy, content from different lines mixed into
one, even mixed up between stdLog and stdErr output. Fore example, something
like that should be my own logging on stdOut and some ByteBuddy logging on
stdErr becomes:
{code}
[Byte Buddy] RESET
net.bytebuddy.agent.builder.AgentBuilder$Default$ExecutingTransformer$ByteBuddy$ModuleSupport@6179e425
on sun.instrument.InstrumentationImpl@70cf32e3
[Byte Buddy] BEFORE_INSTALL
net.bytebuddy.agent.builder.AgentBuilder$Default$ExecutingTransformer$ByteBuddy$ModuleSupport@1fcb4808
on sun.instrument.InstrumentationImpl@70cf32e3
Mock closed
Closing Mock
{code}
{code}
M[Byte Buddy] RESET
net.bytebuddy.agent.builder.AgentBuilder$Default$ExecutingTransformer$ByteBuddy$ModuleSupport@6179e425
on sun.instrument.InstrumentationImpl@70cf32e3
Byte Buddy] BEFORE_INSTALL
net.bytebuddy.agent.builder.AgentBuilder$Default$ExecutingTransformer$ByteBuddy$ModuleSupport@1fcb4808
on sun.instrumeClosing Mock
ock closed
nt.InstrumentationImpl@70cf32e3
{code}
In M4 everything looked normal. The new console output handler seems to be a
very asynchronous guy...
{quote}The fix goes to M6.{quote}
Okay, more waiting for me then.
*Update:* The output mix-up also happens without {{<forkNode
implementation=...}}, it does not seem to be related only to that but to the
new release in general. Is this also a know issue?
> Unhandled native logs in SurefireForkChannel
> --------------------------------------------
>
> Key: SUREFIRE-1788
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1788
> Project: Maven Surefire
> Issue Type: Task
> Components: Maven Failsafe Plugin, Maven Surefire Plugin, process
> forking
> Reporter: Tibor Digana
> Assignee: Tibor Digana
> Priority: Major
> Fix For: 3.0.0-M5
>
>
> This is related only to the internal change of the version 3.0.0-M5 itself.
> The
> [stdOut|https://github.com/apache/maven-surefire/blob/master/maven-surefire-common/src/main/java/org/apache/maven/plugin/surefire/extensions/SurefireForkChannel.java#L153]
> should be printed to INFO on the console.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
