Open Bug 1173223 Opened 6 years ago Updated 6 years ago
Maven warnings when building parser
User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:38.0) Gecko/20100101 Firefox/38.0 Build ID: 20150511103818 Steps to reproduce: 1. Get latest mercurial trunk: "hg clone https://hg.mozilla.org/projects/htmlparser" 2. Run "mvn clean source:jar javadoc:jar repository:bundle-create" Actual results: There were warnings generated by Apache Maven complaining about unspecified plugin versions: [WARNING] [WARNING] Some problems were encountered while building the effective model for nu.validator.htmlparser:htmlparser:bundle:1.4 [WARNING] 'build.plugins.plugin.version' for org.codehaus.mojo:rpm-maven-plugin is missing. @ line 165, column 15 [WARNING] 'build.plugins.plugin.version' for org.apache.maven.plugins:maven-compiler-plugin is missing. @ line 79, column 15 [WARNING] 'build.plugins.plugin.version' for org.apache.maven.plugins:maven-surefire-plugin is missing. @ line 140, column 15 [WARNING] [WARNING] It is highly recommended to fix these problems because they threaten the stability of your build. [WARNING] [WARNING] For this reason, future Maven versions might no longer support building such malformed projects. [WARNING] The bundle was still built successfully though. Expected results: There should not have been any warnings of this form.
Added a patch to fix the Maven warnings
Attachment #8617704 - Flags: review+
Severity: normal → trivial
OS: Unspecified → All
Hardware: Unspecified → All
Comment on attachment 8617704 [details] [diff] [review] Patch to add version numbers to Maven plugins used It's been a long time since I've looked at Maven, so this is basically a rubber-stamp from me.
Attachment #8617704 - Flags: review?(hsivonen) → review+
(In reply to Henri Sivonen (:hsivonen) from comment #2) > Comment on attachment 8617704 [details] [diff] [review] > Patch to add version numbers to Maven plugins used > > It's been a long time since I've looked at Maven, so this is basically a > rubber-stamp from me. Thank you! Although I now see that I made a mistake: the POM file said I was actually supposed to submit this patch to Validator.nu's Bugzilla. Should I copy this bug over? My apologies!
You need to log in before you can comment on or make changes to this bug.