Mailing-List: contact users-help@maven.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Maven Users List" <users@maven.apache.org>
Received-SPF: pass (nike.apache.org: domain of albert.kurucz@gmail.com
 designates 209.85.219.207 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type:content-transfer-encoding;
        b=FI6/S5i6QykCh0ETDmHACZ9y+aw374zUlEJF5BhbrKWu/YFtiYXA/cziaVeQqVNA8X
         4wcfVDVTke91sOj61Y0GQGoVW7MmBvoGrz1PMTMoEsXyR3Wrv7SroJcWDYbtKt3cXo6d
         IMismycdB5GECKagiS2/SL58Xs4N+jSPi9GV8=
MIME-Version: 1.0
In-Reply-To: <200909261514.54177.herve.boutemy@free.fr>
References: <d0e91d130909240740q1fde18a8t76623d11cb66ae49@mail.gmail.com>
	 <eb0f802d0909251431h6443e428yc789a047b9eb4feb@mail.gmail.com>
	 <d0e91d130909251935n70eb45dcwdf8c71aa35114c23@mail.gmail.com>
	 <200909261514.54177.herve.boutemy@free.fr>
Date: Tue, 29 Sep 2009 07:21:00 -0500
Message-ID: <d0e91d130909290521q35fa1023m6a4258ceb1bcd2e0@mail.gmail.com>
Subject: Re: Maven Central Repository - Cleanup Efforts
From: Albert Kurucz <albert.kurucz@gmail.com>
To: Maven Users List <users@maven.apache.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

> Do you really mean that you would like to enforce such -source-release.zi=
p
> 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=C3=A9 BOUTEMY <herve.boutemy@free.fr>=
 wrote:
> Le samedi 26 septembre 2009, Albert Kurucz a =C3=A9crit :
>> For the additional requirement, getting into the pure Maven repo =C2=A0(=
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 sam=
e
> thing.
>
> -sources.jar artefacts usually attached to the main artefact are not mean=
t to
> be buildable, but used for IDEs. You can't build with that, since it's on=
ly 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.zi=
p
> 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 t=
he
>> 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 <brianf@infinity.nu> wrote:
>> > On Fri, Sep 25, 2009 at 12:44 PM, Albert Kurucz <albert.kurucz@gmail.c=
om>
> 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.h=
tml
>> >> 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-unsubscribe@maven.apache.org
>> > For additional commands, e-mail: users-help@maven.apache.org
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org