directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex Karasulu" <>
Subject RE: [vote] Nominate Ibiblio Content Manager
Date Sat, 13 Mar 2004 20:14:46 GMT
Phil, Noel & Mark,

I'm not talking about pushing out and pulling them back in.  Take 
for example the ldap project which has a common jar for both clients
and servers.  Eve (server) needs that jar.  Rather than have the user 
have to build the common jar and the Eve jar its better to have common 
up on some site we all can access.

Noel's idea is a good one.  Since we cannot control the fact that any
project in the incubator can set the version to something other than
SNAPSHOT and upload it we need to enforce the use of a repo that had
incubator in the URL somewhere.  It's just an additional repo that 
all in the incubator have access to.  It's just in one place.

The bottom line is xyz-SNAPSHOT.jar != release but you cannot enforce
this unless you restrict publishing (loosely termed) to a specific 
repo.  It should be a rule of the incubator actually to keep things here
and only here.

I personally use a repo in my home account to manage these jars because when I
move to a new machine I don't want everything to have to rebuild over again.
Plus I can manage snapshot's I expose to the other members of the team.  
Its for internal use really.  BTW I would really love to blow this directory away.

It would be nice to have an additional incubator based maven repo for
projects under incubation.  That way I don't have to replicate jars and
others don't either off their own user accounts or yet another site all


> -----Original Message-----
> From: Phil Steitz []
> Sent: Saturday, March 13, 2004 2:41 PM
> To: Apache Directory Developers List
> Subject: Re: [vote] Nominate Ibiblio Content Manager
> Alex Karasulu wrote:
> >>I am not a maven expert, but I don't think that anything other than
> >>external jars needs to be externally hosted -- i.e., you can install
> >>internally generated jars to the local maven repo to get multi-project
> >>builds to work. I think you can get maven to do that automatically using
> >>install goals.  That's how the directory-naming build works now. See
> >>
> >
> >
> > Already have the reactor in use for this but can't do another
> indirection.
> > Plus we have multiple subprojects some of which depend on another.
> >
> > Alex
> >
> >
> I don't get this.  At the very least, you could generate the jars
> individually and them jar:install them into the local repo or just put
> them in the expected locations in .maven/repsitory.  It does not make
> sense to me that an external repo should be required to push out and pull
> back jars as part of the build process.
> Brett can probably help with this.
> Phil

View raw message