Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

Android Support #75

Closed
rolfl opened this Issue Apr 19, 2012 · 0 comments

Comments

Projects
None yet
1 participant
Collaborator

rolfl commented Apr 19, 2012

Get as much of JDOM working on Android as possible, and document those items which 'deviate' from regular JDOM

rolfl added a commit that referenced this issue Apr 19, 2012

Issue #75 - Android support
Android does not implement the (mandatory) XMLSchema (XSD) specification. This is 'broken', and it throws IllegalArgumentException.
This fix catches the IllegalArgumentException which means that the XMLReaders enum is able to initialize. (without this fix, the entire enum crashes, and any external references throw ClassNotFoundErrors in Android).

rolfl added a commit that referenced this issue Apr 19, 2012

Issue #75 - Android support.
The class-build order appears to be subtly different for Android, which, in this enum, causes the items to become available at a different time (compated to regular Java). By restructring the 'DEFAULT' enum build process we end up with a better solution for both regular Java and Android.

rolfl added a commit that referenced this issue Apr 19, 2012

Issue #75 - Android.
Use new FidoFetch mechanism for getting test resources. This 'abstracts' the process so that it can be different between regular Java testing and Android testing.

rolfl added a commit that referenced this issue Apr 19, 2012

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 added a commit that referenced this issue Apr 20, 2012

rolfl added a commit that referenced this issue Apr 20, 2012

Issue #75 - Replace JUnit 'Assume' directives with plain code to hand…
…le these conditions in Android test layer

rolfl added a commit that referenced this issue Apr 20, 2012

Issue #75 - Android's e.printStackTrace() is not useful because there…
… is no accessible STDERR (or STDOUT). Instead 'chain' the problem.

rolfl added a commit that referenced this issue Apr 20, 2012

Issue #75 - Create URLs at runtime, not class construct time. This fi…
…xes a broken context in Android where the base directory is not populated correctly.

rolfl added a commit that referenced this issue Apr 20, 2012

rolfl added a commit that referenced this issue Apr 22, 2012

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 rolfl closed this in 01c0d67 Apr 23, 2012

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment