I discussed with jason and there is no such an requirement (transitive closure only in maven central) but that is a good practice that they promovate and they wanna guide everyone in doing so. For now, we can just have the poms as till now and later on once the dependent artifacts are published we can step by step remove th e<repository> from poms.
On Sun, Apr 5, 2009 at 5:29 AM, Niclas Hedhman <nic...@hedhman.org> wrote: > On Fri, Apr 3, 2009 at 11:19 PM, Alin Dreghiciu <adreghi...@gmail.com> wrote: > >> http://repository.ops4j.org/mvn-releases - ops4j releases; should >> contain only released maven artifacts for the groups starting with >> org.ops4j > > Well, I don't think this is sufficient. > > Maven central repo artifacts are required to not depend on artifacts > not present in the central repo. This requirement is something that we > can not abide by that easily, hence /m2release being fairly empty > (relatively speaking), but should get fuller if we only focus on the > issue. > > Did Jason mention anything about how to deal with such issue? > > > Cheers > -- > Niclas Hedhman, Software Developer > http://www.qi4j.org - New Energy for Java > > I live here; http://tinyurl.com/2qq9er > I work here; http://tinyurl.com/2ymelc > I relax here; http://tinyurl.com/2cgsug > > _______________________________________________ > general mailing list > general@lists.ops4j.org > http://lists.ops4j.org/mailman/listinfo/general > -- Alin Dreghiciu http://www.ops4j.org - New Energy for OSS Communities - Open Participation Software. http://www.qi4j.org - New Energy for Java - Domain Driven Development. Looking for a job. Sent from Cluj-Napoca, CJ, Romania _______________________________________________ general mailing list general@lists.ops4j.org http://lists.ops4j.org/mailman/listinfo/general
