Also, I notice that there is no cdi artifact in Maven Central (whereas, for example, there is a jta artifact)—its source would appear to be here: https://github.com/jbosstm/narayana/blob/27e1778636aabc3b1214e50aa58edd3253f48a15/ArjunaJTA/cdi/pom.xml#L22. Is there any reason it is not released (https://search.maven.org/classic/#search%7Cga%7C1%7Cg%3A%22org.jboss.narayana.jta%22%20AND%20a%3A%22cdi%22)?
It appears to my untrained eye that narayana-jta just bundles a bunch of "atomic" artifacts (https://github.com/jbosstm/narayana/blob/27e1778636aabc3b1214e50aa58edd3253f48a15/ArjunaJTA/narayana-jta/pom.xml#L57-L70). I'd be happy if either (a) the cdi artifact were released to Maven Central (at version 5.9.1.Final or greater) or (b) narayana-jta were released to Maven Central (at version 5.9.1.Final or greater) or (c) all of the above.
ljnelson strange. It really seems there was some error during the 5.9.1.Final release. I've just deployed the narayana-jta artifact to the jboss nexus repository. The artifact should be mirrored to the maven central during the day. If you configure your maven with repository it should be working for you already now.
Releasing the cdi artifact sounds reasonable to me, just I need to check what are general belief in the team.
<repository> <id>jboss-public-repository</id> <url>http://repository.jboss.org/nexus/content/repositories/public/</url> <releases> <enabled>true</enabled> </releases> <snapshots> <enabled>false</enabled> </snapshots> </repository>
+1 - lets deploy the CDI artifact if it helps
Regarding the missing narayana-jta Jar I did have problems with the release and thought I had covered it but seems I missed one - thanks for the report. Let's get CDI PR in and then we can do a 5.9.2.Final - might be cleaner that way