Hi guys, Let's say I would like to release a project done with qi4j. I would like to push it on a public maven repository. Maven central seems to be the easiest thanks to oss.sonatype.org. But it's a bad maven practice to host a project on a repo that depends on another repo but central.
I can read in qi4j-core base pom that there have been efforts in this direction already. The main issue I can see is projects using third parties repositories. Central prefer artifacts that do not depends on others not present in central. I have listed the projects dependencies to external repos, here is the list: qi4j-extensions (javanet & aduna repos) qi4j-entitystore-gae (gae repo) qi4j-entitystore-neo4j (neo4j repo) qi4j-entitystore-rest (restlet repo) qi4j-entitystore-voldemort (clojars & oracle repos) qi4j-lib-rdf (aduna repo) qi4j-script-groovy (codehaus repo) qi4j-lib-spring (spring external bundles repo) qi4j-dddsample (javanet repo) qi4j-entitystore-jclouds (jclouds repo) qi4j-entitystore-jgroups (jboss repo) qi4j-tests-gae (maven-gae-plugin repo) Twelve, that's a lot of external repositories. This makes quite clear that we cannot go central easily. I wonder what we could do about it. OPS4J repository is currently mirrored to oss.s.o so maybe someone here know what to do for the qi4j case.. For reference, here are the two options oss.sonatype.org offers: - ask for mirroring the existing repository to central (simpler) - use oss.sonatype.org and get release staging for free (no more repo work) The two options are described here: https://docs.sonatype.org/display/Repository/Sonatype+OSS+Maven+Repository+Usage+Guide Getting the Qi4j artifacts on maven central can ease their use, ease projects using Qi4j and by so ease adoption. Qu'en pensez-vous ? WDYT ? Paul _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
