MAVEN-1755 : Backward Incompability : Usage of xml entities in the POM doesn't work in maven 1.1 beta 1 & 2

Upgrade to a maven-model 3.0.2 SNAPSHOT which allow us to read the POM from an URL with DOM4J
It fixes the problem of relative entities. We have to check if it doesn't reduce significantly performances.


git-svn-id: https://svn.apache.org/repos/asf/maven/maven-1/plugins/trunk@454415 13f79535-47bb-0310-9956-ffa450edef68

multiproject/xdocs/changes.xml

@@ -25,6 +25,7 @@
   </properties>
   <body>
     <release version="1.6-SNAPSHOT" date="in SVN">
+      <action dev="aheritier" type="update" issue="MAVEN-1769">Upgrade maven-model to version 3.0.2</action>
       <action dev="aheritier" type="update">Use a custom build of velocity (1.5-20060721.044818) to wait for a release of velocity 1.5 which will fix the issue VELOCITY-193 (The horrible error : "log4j:ERROR Attempted to append to closed appender named [null]").</action>
       <action dev="ltheussl" type="fix" issue="MPMULTIPROJECT-68" due-to="Shinobu Kawai">Only register the dependency convergence report if there are child projects.</action>
       <action dev="ltheussl" type="fix" issue="MPMULTIPROJECT-67" due-to="Shinobu Kawai">maven-multiproject-plugin:deregister does not work.</action>