From dev-return-22391-apmail-directory-dev-archive=directory.apache.org@directory.apache.org Mon Nov 05 18:31:08 2007
Return-Path:
Delivered-To: apmail-directory-dev-archive@www.apache.org
Received: (qmail 16354 invoked from network); 5 Nov 2007 18:31:08 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2)
by minotaur.apache.org with SMTP; 5 Nov 2007 18:31:08 -0000
Received: (qmail 91108 invoked by uid 500); 5 Nov 2007 18:29:46 -0000
Delivered-To: apmail-directory-dev-archive@directory.apache.org
Received: (qmail 91075 invoked by uid 500); 5 Nov 2007 18:29:46 -0000
Mailing-List: contact dev-help@directory.apache.org; run by ezmlm
Precedence: bulk
List-Help:
List-Unsubscribe:
List-Post:
List-Id:
Reply-To: "Apache Directory Developers List"
Delivered-To: mailing list dev@directory.apache.org
Received: (qmail 91064 invoked by uid 99); 5 Nov 2007 18:29:46 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 05 Nov 2007 10:29:46 -0800
X-ASF-Spam-Status: No, hits=1.2 required=10.0
tests=SPF_NEUTRAL
X-Spam-Check-By: apache.org
Received-SPF: neutral (athena.apache.org: local policy)
Received: from [213.46.255.22] (HELO viefep23-int.chello.at) (213.46.255.22)
by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 05 Nov 2007 18:29:48 +0000
Received: from felixknecht.ch ([217.162.149.243]) by viefep23-int.chello.at
(InterMail vM.7.08.02.00 201-2186-121-20061213) with ESMTP
id <20071105182911.JIBI13784.viefep23-int.chello.at@felixknecht.ch>
for ; Mon, 5 Nov 2007 19:29:11 +0100
Received: (qmail 22826 invoked by uid 210); 5 Nov 2007 18:29:10 -0000
Received: from 192.168.1.97 by odin (envelope-from , uid 201) with qmail-scanner-2.01st
(clamdscan: 0.91.2/4672. perlscan: 2.01st.
Clear:RC:1(192.168.1.97):.
Processed in 0.024633 secs); 05 Nov 2007 18:29:10 -0000
Received: from unknown (HELO ?192.168.1.97?) (192.168.1.97)
by 192.168.1.11 with SMTP; 5 Nov 2007 18:29:10 -0000
Message-ID: <472F60F6.4050005@apache.org>
Date: Mon, 05 Nov 2007 19:29:10 +0100
From: Felix Knecht
Organization: apache.org
User-Agent: Thunderbird 2.0.0.6 (X11/20070802)
MIME-Version: 1.0
To: Apache Directory Developers List
Subject: Re: Maven plugins for Apache Directory
References: <472F1E3E.6020206@otego.com>
In-Reply-To:
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Virus-Checked: Checked by ClamAV on apache.org
Alex Karasulu schrieb:
>
> On 11/5/07, *Felix Knecht* > wrote:
>
> For the maven build of the Studio I also created some functionality
> in a maven plugin.
>
> So we do have now within 3 subprojects of Apache Directory maven
> plugin functionality:
>
> apacheds:
> - apacheds-bootstrap-plugin
> - apacheds-core-plugin
>
> daemon:
> - daemon-plugin
>
> studio:
> - maven-studio-plugin (or whatever it'll be named)
>
> I just wonder if it would make sense to centralize the maven plugin
> functionality for the Apache Directory project in a
> new subproject e.g. directory-maven-plugin containing all maven
> plugin related functionality?
>
>
> The idea did occur to me a couple times. Sometimes I was just about to
> do that when it
> just seemed to fan out dependencies across subprojects. Meaning right
> now we have a
> good breakdown where shared is independent. apacheds depends on shared
> and studio
> depends on shared. This new subprject would then have dependencies all
> over. May not
> be a bad thing if it gives us other benefits.
>
> In terms of benefits it may allow us to release the plugins
> independently but because the
> plugins depend on other projects this may be a false benefit in reality.
I think about
- A subproject 'shared' exists to have shared stuff in one place - even if not everything is used in each project (I
didn't checked this). A projects maven-plugin is a kind of the same, isn't it?
- After a short search I haven't found any documentation about the existing maven-plugins. Having them in an own
subproject will give a chance to do the documentation in one place.
- You'll have 1 plugin name instead of already 4 (which IMO makes it more concise (maybe translation is wrong but if
overviewable is better?)).
- The Apache Directory Project has 1 maven plugin with different goals and not different (distributed) maven plugins in
the subprojects each containing hardly more than one goal.
- But yes, your right I haven't seen the dependencies to shared/apacheds.For the studio-plugin I created I haven't so
far any dependencies to another apache directory project.
And finally I'm also asking - maybe sometimes stupid - questions to get some more knowledge about and to understand
better why things are done in this or that way in the past.
So please stop me the questions are just too stupid, already discussed and a decision has been made or I open old sores.
Felix
>
> Just curious, what benefits do you foresee in doing this?
>
> Thanks,
> Alex
>