Hey, Quoting Niclas Hedhman <[email protected]>: > It is related to that Sonatype is tired of Maven being blamed when > third-party repository fails, and causing builds to break. > > What Sonatype refuses to acknowledge is that the centralized model > doesn't work, since so much stuff that people like us depend on is > not, and will not be, available o repo1.maven.org. Many, many years > ago (pre-2005) I suggested to leverage Google search engine (et al) to > locate the needed artifacts, allowing multiple locations of those > artifacts independent of a centralized solution, to no prevail. > > I don't know if Qi4j (other than core) will have a chance of being > disted on repo1.maven.org any time soon, dur to all our dependencies > not being there. > > Cheers
I don't know what you think but the effort for pushing qi4j-core to central seems overkill if the rest of the platform is not (ie. libraries and extensions). The only issue remaining is for projects that wants to get to central without depending on another repo but ... like you said it's a drawback of the centralized model and it seems we'll have to live with it for now. Paul _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
