Re: Release 1.0 in Maven Central and its dependency tree
At a quick glance, that does't look quite good at all :O
The Java EE 8 samples project uses the API 1.0 pom without any issues. Both local and on a clean travis environment it could be resolved.
Payara 5 also used the 1.0 version, but includes both API and Implementation artefacts:
The workaround therefor may be to specify both API and Implementations dependencies in your pom. Not ideal, of course. But could you perhaps try that?