Elliotte Rusty Harold
Elliotte Rusty Harold
Why does Jaxen set packaging to bundle? Does this still make sense?
Specifically, what, if anything, needs to change in the public API. This is for Jaxen 3 or later.
Pull jaxen off of https://sourceforge.net/projects/jaxen/ It's obsolete and confusing search results.
Update docs for Jaxen 2.
Figure out how to release a new multimodule site and update RELEASING.md accordingly. See https://maven.apache.org/plugins/maven-site-plugin/examples/multimodule.html
Jaxen 2
There are some issues with the current code base in Java 9 and later. I'm thinking it's time to move forward. Specifically I'm thinking we should push a Jaxen 2.0...
[ERROR] protected Locale getLocale(Object value, Navigator navigator) [ERROR] ^ [ERROR] /Users/elharo/jaxen/src/java/main/org/jaxen/function/ext/LowerFunction.java:104: warning: no @return [ERROR] public static String evaluate(Object strArg, [ERROR] ^ [ERROR] /Users/elharo/jaxen/src/java/main/org/jaxen/function/ext/UpperFunction.java:103: warning: no @return [ERROR] public static...
somewhere in the code we reference Java 1.3 javadoc. Update this.