Extensive testing of 1.0.0.Beta2 found only a handful of minor issues, so we're comfortable pressing on without another Beta release.
Obviously, not a whole lot new went into this. Check out the full list of bugfixes: Release Notes - JBoss Issue Tracker. We did, however, sneak in a couple of enhancements:
- [ARTIF-728] Add upload endpoint that takes a local file path - JBoss Issue Tracker
If you're using an Artificer client that's co-located with the server, or a file is visible to both (network storage, etc.), there's no reason to pass the entire content stream through HTTP (as you would remotely). So, we've added new endpoints that simply take an absolute file path as the means to "upload" an artifact.
- [ARTIF-733] Improve expansion/derivation relationship lookups - JBoss Issue Tracker
A performance enhancement that reduced the number of trips to the database during batch processing.
- [ARTIF-737] Execute batch persist in single transaction - JBoss Issue Tracker
Batch uploads are now processed within a single transaction. Therefore, if any item fails, the entire set of artifacts are rolled back. This makes sense for most use cases, otherwise you'd have to manually deal with cleanup and synchronization.
A big "thank you" to everyone who contributed to Overlord S-RAMP 0.x and Artificer 1.0, as well as all the alpha/beta testers! We're excited to see the Artificer community and project continue to grow and innovate. Looking forward to the next steps on the roadmap -- onward!