Author: maartenc
Date: Thu Oct 23 12:53:34 2008
New Revision: 707460

URL: http://svn.apache.org/viewvc?rev=707460&view=rev
Log:
Updated release notes with IVY-955

Modified:
    ant/ivy/core/branches/2.0.0-rc2/RELEASE_NOTES
    ant/ivy/core/branches/2.0.0-rc2/doc/release-notes.html

Modified: ant/ivy/core/branches/2.0.0-rc2/RELEASE_NOTES
URL: 
http://svn.apache.org/viewvc/ant/ivy/core/branches/2.0.0-rc2/RELEASE_NOTES?rev=707460&r1=707459&r2=707460&view=diff
==============================================================================
--- ant/ivy/core/branches/2.0.0-rc2/RELEASE_NOTES (original)
+++ ant/ivy/core/branches/2.0.0-rc2/RELEASE_NOTES Thu Oct 23 12:53:34 2008
@@ -217,5 +217,6 @@
 - FIX: Maven pom license url can contain xml entities (IVY-950)
 - FIX: Maven pom license has name as optional element (IVY-949)
 - FIX: Ivy doesn't throw an error when the parent POM cannot be loaded 
(IVY-931)
+- FIX: Maven pom parser is not handling pom property ${project.parent.version} 
(IVY-955)
 
 - DOCUMENTATION: Filesystem resolver: talks about "patterns" but does not 
mention these must become absolute file paths (IVY-910)
\ No newline at end of file

Modified: ant/ivy/core/branches/2.0.0-rc2/doc/release-notes.html
URL: 
http://svn.apache.org/viewvc/ant/ivy/core/branches/2.0.0-rc2/doc/release-notes.html?rev=707460&r1=707459&r2=707460&view=diff
==============================================================================
--- ant/ivy/core/branches/2.0.0-rc2/doc/release-notes.html (original)
+++ ant/ivy/core/branches/2.0.0-rc2/doc/release-notes.html Thu Oct 23 12:53:34 
2008
@@ -221,6 +221,7 @@
 - FIX: Maven pom license url can contain xml entities (IVY-950)
 - FIX: Maven pom license has name as optional element (IVY-949)
 - FIX: Ivy doesn't throw an error when the parent POM cannot be loaded 
(IVY-931)
+- FIX: Maven pom parser is not handling pom property ${project.parent.version} 
(IVY-955)
 
 - DOCUMENTATION: Filesystem resolver: talks about "patterns" but does not 
mention these must become absolute file paths (IVY-910)
 </textarea>


Reply via email to