AnsweredAssumed Answered

Maven 3 Build Warnings in almost all projects

Question asked by bardioc on Oct 21, 2011
Hello,

I've checked out the code for activity and built it using the current version 3.0.3, getting a lot of warnings in the project like:


21.10.11 09:53:18 CEST: [WARN] 'build.plugins.plugin.version' for org.apache.maven.plugins:maven-compiler-plugin is missing. @ org.activiti:activiti-root:5.9-SNAPSHOT, C:\ws\activiti\pom.xml, line 470, column 15
21.10.11 09:53:18 CEST: [WARN] The expression ${version} is deprecated. Please use ${project.version} instead.
21.10.11 09:53:18 CEST: [WARN] The expression ${version} is deprecated. Please use ${project.version} instead.
21.10.11 09:53:18 CEST: [WARN] The expression ${version} is deprecated. Please use ${project.version} instead.
21.10.11 09:53:18 CEST: [WARN] The expression ${version} is deprecated. Please use ${project.version} instead.
21.10.11 09:53:18 CEST: [WARN] 'reporting.plugins.plugin.version' for org.apache.maven.plugins:maven-javadoc-plugin is missing. @ line 122, column 12
21.10.11 09:53:18 CEST: [WARN]
21.10.11 09:53:18 CEST: [WARN] It is highly recommended to fix these problems because they threaten the stability of your build.
21.10.11 09:53:18 CEST: [WARN]
21.10.11 09:53:18 CEST: [WARN] For this reason, future Maven versions might no longer support building such malformed projects.
21.10.11 09:53:18 CEST: [WARN]
21.10.11 09:53:18 CEST: [WARN] Using platform encoding (Cp1252 actually) to copy filtered resources, i.e. build is platform dependent!
21.10.11 09:53:18 CEST: [INFO] skip non existing resourceDirectory C:\ws\activiti\modules\activiti-cxf\src\main\resources
21.10.11 09:53:18 CEST: [INFO] Nothing to compile - all classes are up to date
21.10.11 09:53:18 CEST: [WARN] Using platform encoding (Cp1252 actually) to copy filtered resources, i.e. build is platform dependent!

These are really easy to correct so my question is, if this can be done, as it hides potential important warnings. I could support here and correct the maven configuration of the files, attach these changes to a JIRA Issue created. However, I'm unsure if I shall create one or not for this task.

Thanks,

Heiko

Outcomes