THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
- Are the NOTICE and LICENSE files included in the root directory?
- Are the NOTICE and LICENSE files included in jar?
- Is the jar's manifest file correct?
- Check the component version number is correct.
- Check the title and vendor.
- Check the JDK version.
- if the JDK version is higher than expected (e.g. JDK 1.4 rather than JDK 1.3) does the maven build have the compatibility option set?
- Check the documentation
- Is the style in keeping with other Commons components
- Is there adequate information on:
- Releases
- Mailing Lists
- Dependencies
- Are all dependencies appropriately licensed?
- Are all dependencies released versions?
Wiki Markup Dependency *comments* are good (indicating whether its required/optional/for testing/for the site generation) e.g. \[http://jakarta.apache.org/commons/resources/dependencies.html Resources\]
Wiki Markup *Issue Tracking* - there are some good examples of custom issue tracking pages (see \[http://jakarta.apache.org/commons/validator/issue-tracking.html Validator\] or \[http://jakarta.apache.org/commons/io/issue-tracking.html IO\]).
- Project License
- Do the JavaDocs look OK?
- Are there any check style or javadoc warnings
- Is a Simian report included? If so has the component obtained a license for Simian?
Wiki Markup See \[http://www.redhillconsulting.com.au/products/simian/get_it_now.html Simian Web site\]
- See the following threads:
Wiki Markup \[http://www.mail-archive.com/commons-dev%40jakarta.apache.org/msg70746.html VOTE Release Configuration 1.2\]
Wiki Markup \[http://www.mail-archive.com/commons-dev%40jakarta.apache.org/msg70942.html VOTE Release Configuration 1.2\]
Wiki Markup \[http://www.mail-archive.com/commons-dev%40jakarta.apache.org/msg71449.html Checking Release Candidates - Wiki Page\]
- Do all the links work for the local copy of the documentation?
- If you're a user of the component - can you give the RC a test run?
...