change the android tests to use simpler process (no longer needs to use android Assets), instead us this.getClass().getResource(...). The same mechanism now works in Java an Android.
Update the build process to include the 'android' target which loads an Android main and test project with the JDOM unit tests. See https://github.com/hunterhacker/jdom/wiki/JDOM2-and-Android
…ing the unit test jar unless it has the working test resources. References to resources are now done through ClassLoader.getSystemResource*
Convert them to 'DOS' format end-of-line. Update copyright to 2012 Update README.txt content
Remove redundant JavaDoc
Deprecation in junit code - still produces javac deprecation message. Somehow contrib code 'schema' was never included in my eclipse path, it was never 'generified'. This is now resolved.
Also build 'junit' after 'contrib' so now tests in junit may test contrib code.
after remove(). Includes a bunch more test cases, and fixes some redundancy in Element/Document.
This target builds three bundles that are signed and ready to be loaded to sonatype-nexus staging area. It builds an effectively empty javadoc jar for the junit and contrib jars. The three maven-bundle jars in build/maven folder can be loaded up to the nexus using the 'bundle upload' mechanism in your oss.sonatype web-page.
'filter' copy of the code from core/src/java
Remove dependency on AllTests.java which is a JUnit3 throwback. Rename all tests named 'Test*Exception' to 'Test*Exceptn' because eclipse/ant hooks in to the *Exception name and makes thinks 'clickable' and they are not in fact Exception classes. Update the junit ant task to produce HTML reports. Make the coverage process work with the new report style.
This commit includes a replacement org.jaxen.jdom.DocumentNavigator implementation. This new Navigator understands the jdom2 class names. Lots of issues to fix, and not all tests are passing. There are a number of bugs in jaxen's DocumentNavigator. 1. Can only set an XPath context to Document or Element (not other content). 2. Attribute axis does not appear to return Attributes in document order. Other minor issues.
new coverage test run. This solves some occasional issues when the HTML coverage Reports are out-of-sync with the actual code. It also seems to make the process faster.
This target will create a .classpath file which tells eclipse where all the source/jar dependencies are. If you run 'ant eclipse' or use eclipse to run the 'eclipse' target, then refresh your project, you will be all set up. Add a description to the 'coverage' ant target
Add JDOMAbout class to jdom jar.
Current org.jdom2 coverage is 42%/41% run ant coverage, and inspect build/coverage/index.html
This is intended as a starting-point only. It's enough to build the core and contrib jars.