Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add a profile for debugging tests that run from Maven #11011

Merged
merged 1 commit into from
Feb 9, 2021

Conversation

chrisvest
Copy link
Contributor

Motivation:
In some cases, Intellij struggles to recreate the build and test
environment/configuration that Maven produces, and this can lead to tests
behaving differently when run from Intellij compared to when they run from
Maven.
This in turn can make debugging those tests harder.

Modification:
Add a profile to the Maven build, that will add the necessary command line
arguments for attaching the Intellij debugger to tests that are executed from
Maven.

Result:
It is now possible to debug the tests that Maven is running, from Intellij,
by enabling the -PijDebug Maven profile.

Motivation:
In some cases, Intellij struggles to recreate the build and test
environment/configuration that Maven produces, and this can lead to tests
behaving differently when run from Intellij compared to when they run from
Maven.
This in turn can make debugging those tests harder.

Modification:
Add a profile to the Maven build, that will add the necessary command line
arguments for attaching the Intellij debugger to tests that are executed from
Maven.

Result:
It is now possible to debug the tests that Maven is running, from Intellij,
by enabling the -PijDebug Maven profile.
@chrisvest chrisvest mentioned this pull request Feb 9, 2021
4 tasks
@chrisvest chrisvest merged commit 83895f0 into netty:4.1 Feb 9, 2021
@chrisvest chrisvest deleted the 4.1-ijdebug branch February 9, 2021 10:47
chrisvest added a commit to chrisvest/netty that referenced this pull request Feb 10, 2021
…11011)"

This reverts commit 83895f0

The same functionality is already natively available in surefire, by adding the `-Dmaven.surefire.debug` flag to Maven.
chrisvest added a commit that referenced this pull request Feb 10, 2021
* Revert "Add a profile for debugging tests that run from Maven (#11011)"

This reverts commit 83895f0

The same functionality is already natively available in surefire, by adding the `-Dmaven.surefire.debug` flag to Maven.

* Update surefire/failsafe version

These new versions copes better when our tests prints to STDOUT, and disturbs the progress processing that these plugins do.
chrisvest added a commit that referenced this pull request Feb 10, 2021
* Revert "Add a profile for debugging tests that run from Maven (#11011)"

This reverts commit 83895f0

The same functionality is already natively available in surefire, by adding the `-Dmaven.surefire.debug` flag to Maven.

* Update surefire/failsafe version

These new versions copes better when our tests prints to STDOUT, and disturbs the progress processing that these plugins do.
raidyue pushed a commit to raidyue/netty that referenced this pull request Jul 8, 2022
Motivation:
In some cases, Intellij struggles to recreate the build and test
environment/configuration that Maven produces, and this can lead to tests
behaving differently when run from Intellij compared to when they run from
Maven.
This in turn can make debugging those tests harder.

Modification:
Add a profile to the Maven build, that will add the necessary command line
arguments for attaching the Intellij debugger to tests that are executed from
Maven.

Result:
It is now possible to debug the tests that Maven is running, from Intellij,
by enabling the -PijDebug Maven profile.
raidyue pushed a commit to raidyue/netty that referenced this pull request Jul 8, 2022
* Revert "Add a profile for debugging tests that run from Maven (netty#11011)"

This reverts commit 83895f0

The same functionality is already natively available in surefire, by adding the `-Dmaven.surefire.debug` flag to Maven.

* Update surefire/failsafe version

These new versions copes better when our tests prints to STDOUT, and disturbs the progress processing that these plugins do.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants