+1, I agree that the plugin is mature enough for a 1.0 final version.
 
There are still some minor issues, something for a 1.0.1 :
- checkstyle has still a lot of errors
- examples/catalog.html has some escaping problems: ... the public id was 
--COUNTER-->> and the system id <<<http://www.example.com/sample.dtd.
 
-Robert
 
> Date: Mon, 14 Feb 2011 12:42:54 +0100
> From: [email protected]
> To: [email protected]
> Subject: [mojo-dev] [VOTE] Release xml-maven-plugin 1.0
> 
> Hi,
> 
> I'd like to cut a new release of the xml-maven-plugin. After going
> through three beta versions, I think the plugin is sufficiently mature
> for a version 1.0. All outstanding issues are closed.
> 
> The list of changes since 1.0-beta-3:
> 
> - Disabled proxy password logging. Also reduced logging level of proxy
> info from "info" to "debug". Fixes MOJO-1593. Thanks to Mykola
> Nikishov.
> - The ResourceManager is now used when loading stylesheets or
> resolving included files, thus enabling use of classpath resources.
> Fixes MOJO-735. Thanks to Mark Hobson.
> - Documentation fix: Replace ReplaceRegExpFileMapper with
> RegExpFileMapper. Fixes MOJO-1512. Thanks to Ramón Torres Bátiz.
> - Catalogs can now be specified as URL's, not only as files. Fixes
> MOJO-1471. Thanks to Andreas Eternach.
> - The resolver does now attempt to use the namespace URI and not only
> the public ID. Fixes MOJO-1470. Thanks to Andreas Eternach.
> - Add support for in-place transformation. Fixes MOJO-1447. Thanks to
> Luke W. Patterson.
> - Added catalog file example to the docs. Fixes MOJO-1413.
> - Using latest version of mojo parent POM.
> 
> The staging repository is here:
> 
> https://nexus.codehaus.org/content/repositories/orgcodehausmojo-051/
> 
> The site is updated:
> 
> http://mojo.codehaus.org/xml-maven-plugin
> 
> Thanks,
> 
> Jochen
> 
> -- 
> I Am What I Am And That's All What I Yam (Popeye)
> 
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
> 
> http://xircles.codehaus.org/manage_email
> 
> 
                                          

Reply via email to