Hi Paul! Thanks for doing the research on this one.
On 2010-11-01 17.58, Paul Merlin wrote:
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.
This is a bit beyond my own grasp, so I don't really have an opinion on what would be the best option.
But what is the real issue? Since our POM's reference the repositories I don't quite understand why it's so important that the others are also centralized. Why is that?
/Rickard _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
