For the additional requirement, getting into the pure Maven repo (The best), I really meant: build-able.
Me too, I don't really care what tool you use to build it as long as the tool is already checked in and you only use the attached metadata and the attached sources. But a tool like this, in my eyes is just another Maven plugin. Why care about being build-able? "Non-buildable source is fine as a gesture of goodwill, but I think if the public source isn't buildable, we're gonna end up with egg on our faces." Quote from: http://mail.opensolaris.org/pipermail/opensolaris-discuss/2005-February/002170.html On Fri, Sep 25, 2009 at 4:31 PM, Brian Fox <bri...@infinity.nu> wrote: > On Fri, Sep 25, 2009 at 12:44 PM, Albert Kurucz <albert.kur...@gmail.com> > wrote: >> Technically it is possible to manage 3 different OSS Maven repos. >> >> 1. The good enough >> This is the current "Maven Central" >> No rules, only "recommendations": >> http://maven.apache.org/guides/mini/guide-central-repository-upload.html >> Note: it is not a rule what is not enforced! > > > For what purpose? Again this is effectively a dead repo. >> >> 2. The good >> This would be the Maven Purgatory. >> Same rules applied as above, but rules enforced. >> Mistakes of rule-enforcements corrected by purge. >> > > Or this is the new data in Central. > >> 3. The best >> Call it the Maven Heaven >> Same rules, but only for Maven built projects. >> > > Pretty much useless. The tool used to build is completely irrelevant. > Such a repo would be so barren as to be hardly useful at all. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
