v5.1.0

What's Changed

• Update API to work with latest logbooks server by @slominskir in #4

Upgrade Notes

• Now requires Java 11 as he minimum version to run due to use of java.net.HttpClient

Full Changelog: v5.0.0...v5.1.0

v5.0.0

• Renamed package from org.jlab.elog to org.jlab.jlog to match project name included in package name convention
• Replaced Travis CI with GitHubAction CI
• Replaced Bintray with GitHubPackage, OSSRH (Maven Central)
• Configuration can now be overridden via properties in user home directory
• Upgraded to Gradle 6.6.1 in wrapper

v4.0.1

• Fix bug with base64 decoder - now uses Mime flavored decoder. Didn't realize there were flavors until now.
• Separated Integration tests from Unit tests with class name suffix
• Travis CI now uses Gradle build
• Removed Ant build
• Code cleanup

v4.0.0

This version of jlog requires Java 8+

• Removed javax.xml.bind.DatatypeConverter dependency since no longer ships in Java 11 and replaced with Java 8 Base64 class dependency
• Add Gradle build (will eventually replace Ant build)
• Re-organize code to match Gradle preferences
• Release info no longer hard-coded - now comes from build.gradle via release.properties file

v3.3.1

• Fixed issue where power users (services) could no longer specify the Author field - it was always overwritten on submit (but not forced queue) to be whatever was in the client certificate.

v3.3.0

• Added support for automatically setting author to user in client certificate and other tweaks (Thanks Bobby) #1

v3.2.0

Disable forced schema validation.

v3.1.0

• Updated default configuration properties to reflect recent logbook server SSL requirement
• Added configuration property for server certificate check

v3.0.0

Upgraded to require Java 7, which address many issues. Starting with the "3" series of the library users must have at least Java 7. This seems reasonable since two newer versions (Java 8 and 9) are available and the previously supported Java 6 is now extremely old and has many warts. Issues fixed by using Java 7 features include:

1. We can now set the "Expect" HTTP header with value "100-Continue" to avoid flooding the web server during an SSL renegotiation (internal issue # ELOGAPI-19).
2. Many bugs in earlier versions of the Java 6 JVM are now sidestepped including the javax.xml.bind.DatatypeConverter NPE (internal issue # ELOGAPI-23) and insecure SSL renegotiation (internal issue # ELOGAPI-26)
3. Java 7 allows using the try-with-resources feature, which easily solves the swallowed close exception (internal issue # ELOGAPI-34)

Other changes include:
4. Default Windows queue path updated from M drive to O drive due to recent CUE security changes
5. Ignore certificates errors when downloading attachments (internal issue # ELOGAPI-27)

v2.9.0

Initial release on github