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
 64.233.166.182 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=ouflPRQZfUNo2cyhlz9lM2KBgpvaQL7wXqMw7E5TzHALHWGw7WB0tySVn+8NrN9vhD
         bZg1ckQxT+0wj/HY6fjmJMVrZQuWabIGAiE9lHEpj+a4NkkJugaA7ty0oPNQEMJXx2qP
         Q1KiyTScj+OrSPvTiyd6l/yUO5L3PMugIwRIQ=
Message-ID: <98d8c0860808290105w38fd1864te82a8a04f7b6a050@mail.gmail.com>
Date: Fri, 29 Aug 2008 10:05:45 +0200
From: "Pierre-Arnaud Marcelot" <pa@marcelot.net>
Sender: pajbam@gmail.com
To: "Apache Directory Developers List" <dev@directory.apache.org>,
	elecharny@nextury.com
Subject: Re: [Shared] How to avoid some breakage in Studio when modifying
 shared
In-Reply-To: <48B7AAB8.6020302@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_16205_1749745.1219997145724"
References: <48B7AAB8.6020302@gmail.com>

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

Hi Emmanuel,

On Fri, Aug 29, 2008 at 9:52 AM, Emmanuel Lecharny <elecharny@gmail.com>wrote:

> I guys,
>
> yesturday, as I modified shared, I broke Studio. The reason is that we have
> a DSML sub-project in Studio which depends on the Message API in shared.
>
> Here are some ideas to avoid such breakage in the near future :
> - the DSML subproject should become a shared-dsml sub-project


I completely agree with that. And I think, the project needs to be reworked
to avoid using the Message API from shared.
In my opinion, the use of this API makes it harder for the developer to use
the shared-dsml library. Writing DSML Requests/Responses is not very
intuitive.
The Message API is perfect for internal server use but not really for
end-users I think. Even more now, since it's using the Entry class.


> - we should depend on tagged versions of shared in studio, as we are
> modifying shared pretty enough


Well, as we need to fix some bugs in Shared from time to time, we need to
use the snapshot version. However when we would release a new version of
Studio, a release of Shared would be a prerequisite before releasing Studio
itself.

- if we do that, it means we have to release shared more often


When the server and/or the studio need it.


> - otherwise, we have to build studio each time we do a modification in
> shared, which will be overkilling, IMHO


Yes, it would be very overkilling... Since we have this nightly builds
server, I think we can use it as a way to alert us if something goes wrong
with a commit in Shared that affects Studio. Just like it did today.

Regards,
Pierre-Arnaud

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

<div dir="ltr">Hi Emmanuel,<br><br><div class="gmail_quote">On Fri, Aug 29, 2008 at 9:52 AM, Emmanuel Lecharny <span dir="ltr">&lt;<a href="mailto:elecharny@gmail.com">elecharny@gmail.com</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;">
I guys,<br>
<br>
yesturday, as I modified shared, I broke Studio. The reason is that we have a DSML sub-project in Studio which depends on the Message API in shared.<br>
<br>
Here are some ideas to avoid such breakage in the near future :<br>
- the DSML subproject should become a shared-dsml sub-project</blockquote><div><br>I completely agree with that. And I think, the project needs to be reworked to avoid using the Message API from shared. <br>In my opinion, the use of this API makes it harder for the developer to use the shared-dsml library. Writing DSML Requests/Responses is not very intuitive.<br>
The Message API is perfect for internal server use but not really for end-users I think. Even more now, since it&#39;s using the Entry class.<br>&nbsp;</div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
- we should depend on tagged versions of shared in studio, as we are modifying shared pretty enough</blockquote><div><br>Well, as we need to fix some bugs in Shared from time to time, we need to use the snapshot version. However when we would release a new version of Studio, a release of Shared would be a prerequisite before releasing Studio itself.<br>
<br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">- if we do that, it means we have to release shared more often</blockquote><div><br>
When the server and/or the studio need it.<br>&nbsp;</div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">- otherwise, we have to build studio each time we do a modification in shared, which will be overkilling, IMHO</blockquote>
<div><br>Yes, it would be very overkilling... Since we have this nightly builds server, I think we can use it as a way to alert us if something goes wrong with a commit in Shared that affects Studio. Just like it did today.<br>
<br>Regards,<br>Pierre-Arnaud<br></div></div><br></div>

------=_Part_16205_1749745.1219997145724--