For some start-ups, this could mean a business opportunity!
Nobody said, that the quality info should be given away free.

On Tue, Sep 29, 2009 at 7:21 AM, Albert Kurucz <albert.kur...@gmail.com> wrote:
>> Do you really mean that you would like to enforce such -source-release.zip
>> artefacts to be published?
> Not any qualities of the code should be enforced.
> But I very much want to be able to find those gems from the big pile of ...
>
> Therefore the artifacts on Central should be search-able and filter-able.
> Some people want to add more metadata to support this.
> My opinion is that this approach will not work, it just opens the door
> for more corruption.
>
> There should be independent software quality certifications agencies,
> which issue issue their lists certifying that artifacts on that list
> fulfill certain well specified minimum quality measures.
>
> Maven should be able to use the output from these agencies (for
> filtering or search).
> I hope agencies will maintain high quality of their database, because
> credibility can be lost only once.
>
> On Sat, Sep 26, 2009 at 8:14 AM, Hervé BOUTEMY <herve.bout...@free.fr> wrote:
>> Le samedi 26 septembre 2009, Albert Kurucz a écrit :
>>> 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.
>> I need some clarifications to be sure that we are all speaking of the same
>> thing.
>>
>> -sources.jar artefacts usually attached to the main artefact are not meant to
>> be buildable, but used for IDEs. You can't build with that, since it's only a
>> part of the sources, and does not honour directories expected in pom.xml.
>>
>> Since a few months, -source-release.zip artefacts were added to latest
>> Apache's artefacts (at least Maven's ones) to provide buildable source.
>> See [1] for example.
>>
>> Do you really mean that you would like to enforce such -source-release.zip
>> artefacts to be published?
>>
>> [1] http://repo2.maven.org/maven2/org/apache/maven/plugins/maven-invoker-
>> plugin/1.4/
>>
>>> 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/002
>>>170.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
>>
>>
>>
>> ---------------------------------------------------------------------
>> 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

Reply via email to