You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jdo-commits@db.apache.org by mb...@apache.org on 2022/07/24 19:32:48 UTC
[db-jdo] 02/02: JDO-817 removing compiler warnings: added a new paragraph about wraings to the readme
This is an automated email from the ASF dual-hosted git repository.
mbo pushed a commit to branch tck-compiler-warnings
in repository https://gitbox.apache.org/repos/asf/db-jdo.git
commit 99a995a06af1779ab31d1156bd71dfc0b67f1ff4
Author: Michael Bouschen <Mi...@akquinet.de>
AuthorDate: Sun Jul 24 21:32:38 2022 +0200
JDO-817 removing compiler warnings: added a new paragraph about wraings to the readme
---
README.md | 11 +++++++++++
1 file changed, 11 insertions(+)
diff --git a/README.md b/README.md
index 95525407..b56a5ec3 100644
--- a/README.md
+++ b/README.md
@@ -150,4 +150,15 @@ While running the TCK, maven uses the following configuration files in src/conf:
* jdo.tck.mapping : The file designator that maven.xml uses to build a javax.jdo.option.Mapping value and corresponding schema name (required)
* exclude.list : A list of test classes NOT to execute during a TCK test run
+### Warnings
+There is a profile called `warnings` that configures the maven-compiler-plugin to show compiler warnings and passes
+`-Xlint:all,-try,-rawtypes` as argument to javac. Activate the warnings profile to enable compiler warnings.
+Please note, the tck enables the profile `jdori` per default and this default is disabled when specifying the profile
+`warnings`. So if you want to run the tck with the jdori with warnings enabled please use the following:
+
+ mvn -Pwarings,jdori clean install
+
+You can pass different compiler arguments using the -D option:
+
+ mvn -Pwarings,jdori -DcompilerArgument=-Xlint:all clean install