Hello all,
A while back I suggested that the Maven team delegate some of the
reponsibility of maintaining the ibiblio repo to volunteers (as in the linux
equivalent, as Jerome has noted earlier in the thread). Each such voluteer
can maintain a specific area in the repo; so, someone who uses hibernate
frequently can maintain its poms, until the hibernate team agrees to do it
for us.
The idea was generally accepted by brett, with a slight modification that
volunteers go through a screening process, just like normal commit access is
provisioned (someone who submits enough pom patches will slowly be given
commit access to ibiblio).
for more info, see
http://www.nabble.com/critique-of-maven-2.0.2-tf1052845.html#a2738495
perhaps it is time to move this forward?
On 7/5/06, jerome lacoste <[EMAIL PROTECTED]> wrote:
On 7/5/06, Steve Loughran <[EMAIL PROTECTED]> wrote:
> Ralph Goers wrote:
> >
> >
> > Carlos Sanchez wrote:
> >>
> >> Yes you can, it's not the best way to do it but you can, by adding
> >> explicitly the dependency with the versoin you want to your pom. In
> >> the very worst case you have to add all transitive deendencies to
your
> >> pom, like in Maven 1.
[..]
I've been following this thread with interest.
It makes me think of the various problems Linux distribution have to
deal with when making their own repositories. It took 10 years for
these solutions to be what they are today. I really think some ideas
should be reused, even though the goals are slightly different.
Some features/ways of working that may or may not be applicable:
- they typically use a versionning similar to x.y.z-n sometimes
adding. -n can be used to fix packaging issues (POM in the case of
maven). Vendor fixes are also accepted and version names reflect the
vendor name.
- the distributions with the best repositories typically require the
package to be buildable from source. The build is tested in a separate
environment where all the required build dependencies are listed, to
make sure that the dependency list is accepted. Something similar
should maybe be done before accepting a project on a POM, setting up a
build environment based on the given pom.
- number of versions of a particular package in a repo is reduced to a
minimum. users are adviced to upgrade to the latest & greatest to make
sure that fixes are always present in the last released versions
- responsibilities of preparing packages is spread around 10s of
people. Packages are orphaned when no one is taking care of them.
People can reuse tricks/scripts learned by former packagers to go on
with the job.
- use of provides and various other dependency markers (that's coming
in m2 2.1 if I got it right)
Cheers,
Jerome
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
______________________________________
Cheers,
Arik Kfir [EMAIL PROTECTED]
Linux user, number 415067 - http://counter.li.org/
http://corleon.dnsalias.org
