The most prominent --illegal-access
warn messages that appear on each and every build are excluded by us.
However, the ivy-core does not yet work with java modules
, but with a OSGI bundles
. Therefore, it's almost impossible to prevent each and every access warning that might arise in a dependency of the ivy-core.
Nevertheless, it's indeed a good idea to record warnings in build processes and get rid of the false positives. I do this with blacklisting. In my 'Jenkinsfile' build pipelines it looks as follows:
stages{
stage('build')
..
post {
always {
recordIssues tools: [mavenConsole()], unstableTotalAll: 1, filters: [
excludeMessage('.*-illegal-access=warn.*'), // java11
]
junit '**/target/*-reports/**/*.xml'
}
}`