From 9699eceea7ab1d4a9c5cdbff5944ed958d4cee3e Mon Sep 17 00:00:00 2001 From: samskivert Date: Wed, 8 Sep 2010 21:28:27 +0000 Subject: [PATCH] First entry into "Why Maven sucks" journal: 1. Warnings and deprecations are not shown by default. 2. Documentation shows use of with mulitple arguments in a single element: -foo -bar which is a bald-faced lie. Only a single argument is allowed inside a element. Web search turns up "helpful" advice to use multiple elements: -foo -bar Fair enough, and also a bald-faced lie. After spending a bunch of time debugging why my compiler arguments were not working, I discovered that Maven was just (silently) using the last one and ignoring/overwriting all of the previous arguments. I had noticed while poring over the documentation that it was also possible to use the so-called "Map version" (whatever that means), which uses this completely fucking stupid syntax: Why is that syntax completely fucking stupid, you might ask? Well, dear reader, because the arguments that I'm actually passing end up looking like this: which is a case study in how not to represent information in XML. I didn't even try that originally because I was sure that it would not work, given the wacky non-[a-zA-z]+ nature of the argument I needed to supply. The fact that it does work gives me the fear. You might wonder if the following form would provide satisfaction: -Xlint -Xlint:-serial Other than being absurdly verbose, it seems right in line with The Maven Way (tm). However, that results in -compilerArgument=-Xlint and -compilerArgument=-Xlint:-serial being passed to the compiler. Hilarity naturally ensues. git-svn-id: https://samskivert.googlecode.com/svn/trunk@2859 6335cc39-0255-0410-8fd6-9bcaacd3b74c --- pom.xml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/pom.xml b/pom.xml index 9c5e897d..1d3c4056 100644 --- a/pom.xml +++ b/pom.xml @@ -85,6 +85,9 @@ 1.5 1.5 + true + true + com/samskivert/velocity/** com/samskivert/xml/**