Hi, Thanks for your feedback.
> -Maven does not handle XML properly! I do not have a clue > what its doing inside but maybe some developers might think > that XML ist just some little ASCII standard extension > (quite a point of view). Please refrain from insulting the developer's intelligence :) Usually these bugs arise due to a double transformation of XML (eg project.xml -> index.xml -> index.html), and they are often in Jelly rather than Maven. For the specific test cases for something not working, file a bug in JIRA. > -Maven exception handling is sometimes inconvenient because > it does not give you a clue what the actual problem is. I've tried to help this in RC3, but if you have a specific example then file a bug and I'd be happy to look into it. > -Maven documentation is a nice thing to start, but when doing > something more it gets really hard. This is on the 1.0 TODO list which is about to start. I plan a documentation overhaul. > -when using subprojects that extend a parent POM then This is the way inheritence is specified for POMv3. Again, if this goes into JIRA we might look at it for Maven 1.1. > -Why does maven not know about scm:svn and I have to set > maven.changelog.factory=org.apache.maven.svnlib.SvnChangeLogFactory > when using a subversion repository connection? Yes, I know. Too many cvs junkies. I have been meaning to file a JIRA issue to get this fixed, but perhaps you could do that along with the others. It's a changelog plugin issue. > However dont wory be happy and thanks for doing maven You're welcome. Regards, Brett
