Introduction
As mentioned in the introductory blog post, one of the main reasons for the creation of Atbash initiative was the ability to release maven artifacts to Maven Central.
However, this will take some time as the package naming should ideally match the group and artifact names.
So this renaming/re-branding will take some time and in the main time the current Nexus maven repository, hosted on OpenShift by the company, needs to be replaced.
Temporary relocation
So there will be a temporary solution for the removal of the Nexus server. It will include the JCenter and GitHub platforms.
This is the case for the JSF Renderer Extensions and the Octopus projects.
JCenter for final artifacts
The final artifacts are made available on JCenter and can be included from there into your project. Add the following snippet or equivalent to your maven pom file.
<repositories>
<repository>
<id>Bintray_JCenter</id>
<url>https://jcenter.bintray.com</url>
</repository>
</repositories>
It contains the latest (amongst others) version of JSF Renderer extensions (0.4.1) and Octopus (0.9.7)
GitHub repository for snapshots
Since JCenter/Bintray doesn’t accept snapshots artifacts, they will be placed in a GitHub repository. With the following snippet, you can try out the work in progress for the projects.
<repositories>
<repository>
<id>atbash-mvn-repo</id>
<url>https://raw.github.com/atbashEE/mvn_repo/master/</url>
<releases><enabled>false</enabled></releases>
<snapshots><enabled>true</enabled></snapshots>
</repository>
</repositories>
Conclusion
The ultimate goal is maven central for all Atbash resources, but due to time restrictions there will be temporary repository locations for them.