The vote is now closed and there were no objections, so I will proceed with the
release. Once there is a JIRA project for the plugin, then I will update the
issue tracking URL, tag the release and deploy to the repository.
Paul Gier wrote:
Thanks, as always, for the help Benjamin!
I did the following:
- Added the scm information
- Fixed the errors in dependency:analyze
- Removed calls to print stack trace and improved some of the error
handling code.
- Updated to mojo-parent 20.
- Fixed the artifactId in the usage page
I have deployed a new site and updated snapshot.
Benjamin Bentmann wrote:
Paul Gier wrote:
I would like to call a vote to promote the properties maven plugin
out of the sandbox and do a 1.0 alpha release.
+0, not using it. Notes:
The POM is missing the <scm> element.
mvn dependency:analyze reports discrepancies.
The code in AbstractWritePropertiesMojo.writeProperties() looks odd.
For instance, a possible FileNotFoundException is merely logged but
the control flow continues just to die on a NPE when calling
Properties.store(). Also, calls to printStackTrace() are inappropriate
in a mojo.
The site is at http://mojo.codehaus.org/properties-maven-plugin/
Once the mojo-parent:20 is syned on central, the JDK requirement on
the plugin-info.html could be fixed.
The usage.html states a wrong artifactId for the plugin. Also, the
<version> element points at 1.0-SNAPSHOT, this should eventually be
the released version.
Benjamin
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
