| commit | a20bd852417c4c8c241c2a20d0b258385ffc6784 | [log] [tgz] |
|---|---|---|
| author | Lorenzo Bettini <lorenzo.bettini@gmail.com> | Wed Sep 08 09:30:01 2021 +0200 |
| committer | Michael Osipov <1983-01-06@gmx.net> | Wed Sep 08 09:45:01 2021 +0200 |
| tree | 8713cab76155617314af0880a84d0b02cd5d19b5 | |
| parent | bd9079d291b83afb33f37abef7d7206716c27ffa [diff] |
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
diff --git a/src/it/mcompiler-21_class-remove/pom.xml b/src/it/mcompiler-21_class-remove/pom.xml index 9c1ac32..e04756a 100644 --- a/src/it/mcompiler-21_class-remove/pom.xml +++ b/src/it/mcompiler-21_class-remove/pom.xml
@@ -28,9 +28,9 @@ <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>