Your best option of to use a configuration parameter that references an XML configuration and use decentxml[1] to read in that XML to preserve all whitespace and formatting.
I'm not changing the way the trimming behaviour works now would be the wisest thing to do after operating that way for so long, but I would agree that it should respect CDATA blocks if it's not. At any your first option using decentxml will get you to a solution that works faster. [1]: http://code.google.com/p/decentxml/ On Sep 12, 2011, at 3:09 PM, Laird Nelson wrote: > On Mon, Sep 12, 2011 at 2:57 PM, Laird Nelson <[email protected]> wrote: > >> Please vote for http://jira.codehaus.org/browse/MODELLO-256 and for >> http://jira.codehaus.org/browse/PLX-461. >> > > It looks to me like the Modello project, which generates the readers that > are capable of parsing a pom.xml, is at least capable of seeing if a field > can be trimmed. Unfortunately I can't tell how this determination is made. > There is a class in Modello somewhere called XmlFieldMetaData that has an > isTrim() method, and the reader that is generated does seem to obey this > directive. Now how you could possibly influence the pom.xml reader to obey > this directive when it's parsing the pom.xml for certain elements is > entirely beyond me. Help? > > Best, > Laird > > -- > http://about.me/lairdnelson Thanks, Jason ---------------------------------------------------------- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl --------------------------------------------------------- To do two things at once is to do neither. -—Publilius Syrus, Roman slave, first century B.C.
