I just saw this show up on previously working pom's this afternoon. Removing the ${reports} will eliminate the error but mess up the index.html page. I'm guessing this is due to something gone terribly wrong on a component upgrade in Maven, but I haven't checked out their lists yet.
Nothing obvious on their list traffic or jira. I posted a question on [EMAIL PROTECTED] I checked the documentation and it was supposed to be ${ reports} instead of {$reports} and I have again let CR's instead of LF's into a file, but neither had previously caused a problem and fixing them didn't make the problem go away. Will wait to hear what the Maven gurus have to say.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
