Mailing-List: contact dev-help@directory.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache Directory Developers List" <dev@directory.apache.org>
Received-SPF: pass (athena.apache.org: domain of pajbam@gmail.com designates
 209.85.200.172 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:sender:to:subject:in-reply-to:mime-version
         :content-type:references:x-google-sender-auth;
        b=YStT9snh8L0f7kxeAGFp3cnEBQM5tEysu5Lmi0x7nOYR3YvR3KZ+KKe1RUwOMOX6AM
         hCeV8OVTVR+M5rAXnouCkpzmBnF7Xy1ShUCn6DEgorlNO4fUcbZiPjHzQfCYRit2ZMXN
         wOl+JdfncFi9i4y3IHm25D/RXqRgeONc5vkjs=
Message-ID: <98d8c0860810010102g1e75838fg262131967eec5d7e@mail.gmail.com>
Date: Wed, 1 Oct 2008 10:02:59 +0200
From: "Pierre-Arnaud Marcelot" <pa@marcelot.net>
Sender: pajbam@gmail.com
To: "Apache Directory Developers List" <dev@directory.apache.org>
Subject: Re: [Studio] Using the Maven Release Plugin
In-Reply-To: <48E293C9.7020003@apache.org>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_38787_11036260.1222848179732"
References: <98d8c0860809190454q4a3356d1q9b45e6b9e735f197@mail.gmail.com>
	 <98d8c0860809230300vee65f60uedbdc2390e2024e@mail.gmail.com>
	 <19a9f6be0809230315s16dcc2e0mc1d20eee01660004@mail.gmail.com>
	 <48D8C3A0.6040105@apache.org> <48D8D4CA.30603@apache.org>
	 <98d8c0860809230500v534936a5yd1f49a35c7a825c@mail.gmail.com>
	 <48D8DC0E.70407@apache.org>
	 <98d8c0860809230515m336efc7dhf9f4bbe2b4843b93@mail.gmail.com>
	 <98d8c0860809300307i2f218264r353155658ff0b4f3@mail.gmail.com>
	 <48E293C9.7020003@apache.org>

------=_Part_38787_11036260.1222848179732
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Hi Stefan,

On Tue, Sep 30, 2008 at 11:02 PM, Stefan Seelmann <seelmann@apache.org>wrote:

> Perhaps a better option is to exclude the integraton-ui and
> integration-core plugins from the release?
>
> WDYT?


Yeah, this could be a good idea.
Actually, it does not make sense to release those plugins on the maven
repositories.
This is for our testing only.

What we could do is associate them to a special "integration-test" profile.
They would be run only on demand.
Which would also speed up our build.

WDOT ?

Regards,
Pierre-Arnaud

------=_Part_38787_11036260.1222848179732
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

<div dir="ltr">Hi Stefan,<br><br><div class="gmail_quote">On Tue, Sep 30, 2008 at 11:02 PM, Stefan Seelmann <span dir="ltr">&lt;<a href="mailto:seelmann@apache.org" target="_blank">seelmann@apache.org</a>&gt;</span> wrote:<br>

<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Perhaps a better option is to exclude the integraton-ui and<br>
integration-core plugins from the release?<br>
<br>
WDYT?</blockquote><div><br>Yeah, this could be a good idea.<br>Actually, it does not make sense to release those plugins on the maven repositories.<br>This is for our testing only.<br><br>What we could do is associate them to a special &quot;integration-test&quot; profile.<br>
They would be run only on demand.<br>Which would also speed up our build.<br><br>WDOT ?<br><br>Regards,<br>Pierre-Arnaud<br></div></div><br></div>

------=_Part_38787_11036260.1222848179732--