From dev-return-22385-apmail-directory-dev-archive=directory.apache.org@directory.apache.org Mon Nov 05 16:55:23 2007 Return-Path: Delivered-To: apmail-directory-dev-archive@www.apache.org Received: (qmail 57714 invoked from network); 5 Nov 2007 16:55:23 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 5 Nov 2007 16:55:23 -0000 Received: (qmail 19232 invoked by uid 500); 5 Nov 2007 16:55:11 -0000 Delivered-To: apmail-directory-dev-archive@directory.apache.org Received: (qmail 19190 invoked by uid 500); 5 Nov 2007 16:55:10 -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 19179 invoked by uid 99); 5 Nov 2007 16:55:10 -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 08:55:10 -0800 X-ASF-Spam-Status: No, hits=2.0 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of akarasulu@gmail.com designates 209.85.198.189 as permitted sender) Received: from [209.85.198.189] (HELO rv-out-0910.google.com) (209.85.198.189) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 05 Nov 2007 16:55:14 +0000 Received: by rv-out-0910.google.com with SMTP id g11so1269054rvb for ; Mon, 05 Nov 2007 08:54:51 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:references:x-google-sender-auth; bh=Epv/cGcUNprYlcz+BfMw2bovftcKlHlEKTAN29u0FpE=; b=HLEHDx4xQSt/Ctmck82hekBnncGsF3DPrsoxLAtX8+5Nx7Dp+n9piVCcIcGwBJKgsu3ks+MP8Ldo6OfJjBianPswoZy4o+pVhcNYLbz6Bp43hsv8/r7ccumttTExHirp/0di6XRp7Omn4OyCQ3CqNI1+aDPBPQKaAksnYqHYdHY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:references:x-google-sender-auth; b=Np3BKHI9vDeOlQ3jRea7SUy+0/ex2UXBWEtCyrRdOlf0fLjNqcnyoJHX2faOXu1T9uj2wMdQFnewCAggpAIzhFGwN6pqQHnshSBvYuu2noIZ/+PRPdlnK/ChDb9gsDPdtShlN/v9Nb/jAiwZ3m0KHbP5jHhgv2cH0y7N9BitOXw= Received: by 10.114.76.1 with SMTP id y1mr5312758waa.1194281691169; Mon, 05 Nov 2007 08:54:51 -0800 (PST) Received: by 10.115.18.12 with HTTP; Mon, 5 Nov 2007 08:54:51 -0800 (PST) Message-ID: Date: Mon, 5 Nov 2007 11:54:51 -0500 From: "Alex Karasulu" Sender: akarasulu@gmail.com To: "Apache Directory Developers List" Subject: Re: Maven plugins for Apache Directory In-Reply-To: <472F1E3E.6020206@otego.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_31058_21693227.1194281691165" References: <472F1E3E.6020206@otego.com> X-Google-Sender-Auth: 344bc58fe1c81d68 X-Virus-Checked: Checked by ClamAV on apache.org ------=_Part_31058_21693227.1194281691165 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline 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. Just curious, what benefits do you foresee in doing this? Thanks, Alex ------=_Part_31058_21693227.1194281691165 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline
On 11/5/07, Felix Knecht <felix@otego.com> 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.

Just curious, what benefits do you foresee in doing this?

Thanks,
Alex

------=_Part_31058_21693227.1194281691165--