directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex Karasulu" <akaras...@apache.org>
Subject Re: [VOTE] Policy for Managing TLP POM
Date Wed, 23 May 2007 16:32:26 GMT
Yes you got it :).

Alex

On 5/23/07, Emmanuel Lecharny <elecharny@gmail.com> wrote:
>
> Hi Chris,
>
> I was puzzled too, but I put it first on my unablility to understand
> complex engish sentences, because I'm not a native english...
>
> Ok, here is some explaination :
> - the TLP pom.xml was just intended to gather very common infos like
> remote maven repos, nothing more
> - it was used (misused would be a better term) to build ADS as a
> whole, and this was *not* a good idea.
>
> So this TLP pom.xml is still usefull, but must be pointed only by
> subprojects, and not been used to build the server.
>
> To build the server, there is another pom.xml which can be found in
> apacheds-XXX-with-dependencies (where XXX is the version).
>
> Hope it helps.
>
> Alex, did I understood what you told me ?
>
> Emmanuel
>
>
> On 5/23/07, Chris Custine <chris.custine@gmail.com> wrote:
> > I fall into the "dazed and confused" camp at the moment so I need to do
> some
> > more reading to fully understand.  One part in particular that I don't
> > understand is this line:
> > "This causes it's misuse to facilitate building ApacheDS and all it's
> > dependencies in one big build. This must stop because this usage makes
> it
> > inconvenient to use for building other projects like Triplesec and LDAP
> > Studio once it moves to Maven."
> > I actually LIKE it this way  :-)  I don't think this actually causes any
> > harm anyway, because if you build a project that references this pom as
> a
> > parent, the modules section is ignored IIRC.  Are you talking about some
> > other issue with the parent pom?
> >
> > These maven setups are definitely a complex issue so I find myself
> wanting
> > to take a cautious approach...
> >
> > Chris
> >
> >
> > On 5/22/07, Alex Karasulu <akarasulu@apache.org> wrote:
> > > Hi all,
> > >
> > > I compiled some documentation talking about how we should handle a
> parent
> > POM for our TLP
> > > so all subprojects can inherit from it.  We have been using it
> incorrectly
> > and have been loosing
> > > track of it. I explain all this and expose some simple policy (6
> rules)
> > that will help us keep this
> > > all straight [1].
> > >
> > > Please read this and let's vote on it make it official.
> > >
> > > [  ] +1 Apply this policy/process for TLP POM management
> > > [  ] +/-0 Abstain - don't understand or don't care
> > > [  ] -1 Do *NOT* apply this policy for TLP POM management
> > >
> > > -- Alex
> > >
> > > -------
> > > [1] -
> > http://cwiki.apache.org/DIRxDEV/top-level-pom-management-policy.html
> > >
> > >
> > >
> >
> >
>
>
> --
> Regards,
> Cordialement,
> Emmanuel L├ęcharny
> www.iktek.com
>

Mime
View raw message