Skip to content
This repository

Apr 22, 2012

  1. Rolf

    Issue #75 - change Resource paths to be absolute.

    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.
    rolfl authored

Apr 19, 2012

  1. Rolf

    Issue #75 - 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
    rolfl authored

Apr 11, 2012

  1. Rolf

    Copy test resources to be part of the junit jar. No real point in hav…

    …ing the unit test jar unless it has the working test resources. References to resources are now done through ClassLoader.getSystemResource*
    rolfl authored

Apr 06, 2012

  1. Rolf

    Include the JDOM License directly in the POM

    rolfl authored

Apr 05, 2012

  1. Rolf

    Update Package to contain LICENSE.txt and README.txt

    Convert them to 'DOS' format end-of-line.
    Update copyright to 2012
    Update README.txt content
    rolfl authored

Mar 26, 2012

  1. Rolf

    change the name from JDOM2 to JDOM

    rolfl authored

Mar 19, 2012

  1. Rolf

    Tidy up the eclipse ant task.

    rolfl authored

Mar 13, 2012

  1. Rolf

    JavaDoc tidyup

    rolfl authored

Feb 17, 2012

  1. Rolf

    Tidy up maven processes

    rolfl authored

Feb 15, 2012

  1. Rolf

    Make it easier to test JDOM on different Java versions.

    rolfl authored

Feb 14, 2012

  1. Rolf

    Make samples build after contrib

    Remove redundant JavaDoc
    rolfl authored
  2. Rolf

    Tidy up build messages.

    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.
    rolfl authored

Feb 11, 2012

  1. Rolf

    Change the build order and classpaths to include Xalan libraries.

    Also build 'junit' after 'contrib' so now tests in junit may test contrib code.
    rolfl authored

Dec 07, 2011

  1. Rolf

    Smaller Package zip file (exclude dev-only jars).

    rolfl authored
  2. Rolf

    Add coverage, and thus junit results to be build, makes syncing the j…

    …dom-pages easier
    rolfl authored

Nov 06, 2011

  1. Rolf

    Create a 'package' properly

    rolfl authored

Oct 17, 2011

  1. Rolf

    Remove calls to deprecated deltree task and replace with 'delete'

    rolfl authored

Oct 11, 2011

  1. Rolf

    Fixes #24 - Descendant iterator (and by proxy, FilterIterator) broken

    after remove().
    Includes a bunch more test cases, and fixes some redundancy in
    Element/Document.
    rolfl authored

Sep 30, 2011

  1. Rolf

    Include Maven target in build.

    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.
    rolfl authored

Sep 27, 2011

  1. Rolf

    Remove default-package classes (JDOMAbout) from main jar.

    Fixes #6
    rolfl authored

Sep 26, 2011

  1. Rolf

    Clean up the build again. Fix compile-time warnings, and remove the

    'filter' copy of the code from core/src/java
    rolfl authored

Sep 20, 2011

  1. Rolf

    Tidy up the ant junit process.

    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.
    rolfl authored

Sep 19, 2011

  1. Rolf

    Add implementation o Jaxen XPath library Navigator for supporting JDOM2.

    rolfl authored
  2. Rolf

    Include testing for org.jdom2.xpath.*

    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.
    rolfl authored

Sep 10, 2011

  1. Rolf

    Perform cleanup of the previous Cobertura artifacs before performing a

    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.
    rolfl authored

Sep 05, 2011

  1. Rolf

    Add xml-apis to eclipse path

    rolfl authored

Aug 15, 2011

  1. Rolf

    Include xml-apis jar in classpath for junit/eclipse targets.

    rolfl authored

Aug 08, 2011

  1. Jason Hunter

    Made the README.txt a bit more modern. Added the new usage commands t…

    …o build.xml.
    authored
  2. Jason Hunter

    Let's name the JARs jdom2.jar and jdom2-contrib.jar.

    -jh-
    authored

Aug 03, 2011

  1. Rolf

    create an 'eclipse' target for ant.

    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
    rolfl authored
  2. Rolf

    Clean up build artifacts.

    Add JDOMAbout class to jdom jar.
    rolfl authored

Aug 02, 2011

  1. Rolf

    Include JUnit ant target and code coverage tool cobertura.

    Current org.jdom2 coverage is 42%/41%
    run ant coverage, and inspect build/coverage/index.html
    rolfl authored
  2. Rolf

    Create an initial build.xml for the combined core/contrib/test code.

    This is intended as a starting-point only. It's enough to build the core
    and contrib jars.
    rolfl authored
Something went wrong with that request. Please try again.