I tried maven-b3, then moved several of our projects to a CVS-head about maven-b4 and a few things (that used to work) no longer work. I suspected the problem was with project.xml, so I tried to check the file against its XML schema with an appropriate tool (yeah, not open source, I'm afraid...). This rose several problems: - the suppression of <sourceDirectories/> in the new schema: if I remove it (as the schema prescribes) when migrating the project.xml file, I get an error when trying to get the CheckStyle report:
/home/team/maven/plugins/core/build.xml:1435: Unable to create a Checker When I put this XML clause back, I get no error, do-env gives all correct parameters including CLASSPATH, but nothing is generated. So definitely there is a problem with that part of the schema :-( - I have another problem with the dependencies: theoretically (I mean, according to the XML schema) and practically I am forced to use the jakarta versioning scheme for all libraries. This is a change from b3, and though I like the idea, it is a real nuisance. If I try to omit the <version>, ant looks for mylib-null.jar and obviously does not find it/them. Also, there is a bug in the schema at this level, since the definition of <version> is (id, name, tag) (from <versions>).
