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

Fixed the comment in the POM #66

Merged
merged 1 commit into from
Sep 8, 2021
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Fixed the comment in the POM
The comment in the POM wrongly describes the tested scenario. I guess this was due to a copy and paste from another IT, https://github.com/apache/maven-compiler-plugin/blob/master/src/it/mcompiler-21_methodname-change/pom.xml
  • Loading branch information
LorenzoBettini committed Sep 8, 2021
commit 01601c1cbed423397d527895f0d713b6cb7cbe73
6 changes: 3 additions & 3 deletions src/it/mcompiler-21_class-remove/pom.xml
Original file line number Diff line number Diff line change
Expand Up @@ -28,9 +28,9 @@ under the License.
<version>1.0-SNAPSHOT</version>

<description>
This IT tests what happens if the method name in a single class BeanA gets changed.
In this case 'mvn compile' (without a clean) should fail as BeanA2
still uses the old method of BeanA.
This IT tests what happens if a single class BeanA is removed.
In this case 'mvn compile' (without a clean) should fail as BeanA2
still uses the removed class BeanA.
</description>

<build>
Expand Down