February 2015 Summaries

Jose Maria Arranz shares his experience with the challenges of publishing on Maven Central and how using Bintray, recommended by JFrog employee @jbaruch, provided a simpler alternative. Arranz highlights the difficulties of the Sonatype process and praises Bintray for its user-friendly interface that allows for easy uploading and signing of artifacts using GnuPG keys. This solution enabled him to release his project, RelProxy, on both JCenter and Maven Central with greater ease. He acknowledges that while some steps could be further automated, the current process with Bintray's auto-signing and uploading is sufficient for his needs, especially since releasing occurs infrequently. Arranz also notes that JCenter offers additional benefits, such as being a pre-configured repository in some environments, implying a successful publishing experience overall.

Steve Button's blog post on The Buttso Blathers details his experience with the newly released JFrog Artifactory 3.5.1, highlighting its compatibility with the Oracle Maven Repository. The update involved configuring a remote repository using a straightforward process, which required setting up a proxy for firewall navigation, adding a remote repository with specific credentials, and adjusting advanced settings for proper host authentication and cookie management. After configuring these settings, Button tested the setup with a Maven project, confirming that dependencies were successfully fetched through the Artifactory server and locally cached for future use. He also discovered that the Artifactory Web UI provides useful features such as search functionality and a repository browser for navigating the Oracle Maven Repository. Button appreciated the quick support from the JFrog Artifactory team and suggested enabling password encryption to secure credentials stored in configuration files.

The transition from Maven Central to JCenter as the default repository in Android Studio was driven by several factors, including performance improvements and secure connections. JCenter, a Java repository in Bintray, became favored due to its extensive library offerings and secure HTTPS connections, contrasting with Maven Central's earlier HTTP-only support. The change was notable during the Android Studio 0.8 release, where developers experienced issues with Maven Central, such as large indexing that consumed significant disk space, which JCenter addressed with its efficient handling. Additionally, JCenter's broader repository coverage and ease of integration with Maven Central for legacy support were appealing, enhancing Android Studio's performance and user experience. The migration has sparked ongoing discussions and interest in further exploring its benefits among developers and advocates within the Android development community.