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.176 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=XRN0AHABZy54O6jp0vRj7V01hqlAN3J+oC6EVuBN82HKy/K/f6qUBs4+2NiOhARq/N
         M6qd1guZOjWqsWg6HVrNHnCX5h7KDsgESqSwNWQPGSUswU/HcWN/N+iXuyP1fHKrGBtV
         3qRNh8kWYvaH5PgeCVQitrg326wFBlK090pnQ=
Message-ID: <98d8c0860809110147u4fc39393u3298038943791e9b@mail.gmail.com>
Date: Thu, 11 Sep 2008 10:47:51 +0200
From: "Pierre-Arnaud Marcelot" <pa@marcelot.net>
Sender: pajbam@gmail.com
To: "Apache Directory Developers List" <dev@directory.apache.org>
Subject: Re: [Studio] Eclipse plugin snapshot update
In-Reply-To: <48C8DA53.1020002@apache.org>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_39719_16352119.1221122871973"
References: <48C8C898.6000905@otego.com> <48C8CD44.1090709@apache.org>
	 <98d8c0860809110127m72f8e4f0va2b859cb42e85667@mail.gmail.com>
	 <48C8D7DD.60406@apache.org>
	 <98d8c0860809110139i4ff8f679le3d17ba43b20d25e@mail.gmail.com>
	 <48C8DA53.1020002@apache.org>

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

Well, I was thinking we could tell our users they need to copy/paste the
content of the 'plugins' and 'features' folders of the ZIP on the
corresponding folders of their Eclipse installation.

That's not a very difficult task, so I think they can do it easily.

Pierre-Arnaud

On Thu, Sep 11, 2008 at 10:44 AM, Felix Knecht <felixk@apache.org> wrote:

> Pierre-Arnaud Marcelot schrieb:
> > Hi Felix,
> >
> > On Thu, Sep 11, 2008 at 10:33 AM, Felix Knecht <felixk@apache.org
> > <mailto:felixk@apache.org>> wrote:
> >
> >
> >     > Unfortunately, Eclipse won't be able to find an update between two
> >     > builds of this nightly update site (as the version number will stay
> >     > the same). The solution would be to uninstall Studio's features and
> >     > plugins before re-installing them with the update site.
> >     IMO this is too complex for a 'normal' user. Thus I'd vote only for
> 2.
> >
> >
> > Yeah, but I don't think a "normal" user would try to use a nightly
> > version of Studio. ;)
> >
> > However, I think solution 2 is enough and as we already have the zip
> > generated at each build.
> Nope. This zip must have another directory structure to make it work. It
> must look like
>
> eclipse
>  \ plugins
>  \ features
>
> Otherwise it won't work :-(
>
>
> > We just need to deploy it aside the other already available downloads.
> >
> > Pierre-Arnaud
>
>

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

<div dir="ltr">Well, I was thinking we could tell our users they need to copy/paste the content of the &#39;plugins&#39; and &#39;features&#39; folders of the ZIP on the corresponding folders of their Eclipse installation.<br>
<br>That&#39;s not a very difficult task, so I think they can do it easily.<br><br>Pierre-Arnaud<br><br><div class="gmail_quote">On Thu, Sep 11, 2008 at 10:44 AM, Felix Knecht <span dir="ltr">&lt;<a href="mailto:felixk@apache.org">felixk@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;">Pierre-Arnaud Marcelot schrieb:<br>
<div class="Ih2E3d">&gt; Hi Felix,<br>
&gt;<br>
&gt; On Thu, Sep 11, 2008 at 10:33 AM, Felix Knecht &lt;<a href="mailto:felixk@apache.org">felixk@apache.org</a><br>
</div><div class="Ih2E3d">&gt; &lt;mailto:<a href="mailto:felixk@apache.org">felixk@apache.org</a>&gt;&gt; wrote:<br>
&gt;<br>
&gt;<br>
&gt; &nbsp; &nbsp; &gt; Unfortunately, Eclipse won&#39;t be able to find an update between two<br>
&gt; &nbsp; &nbsp; &gt; builds of this nightly update site (as the version number will stay<br>
&gt; &nbsp; &nbsp; &gt; the same). The solution would be to uninstall Studio&#39;s features and<br>
&gt; &nbsp; &nbsp; &gt; plugins before re-installing them with the update site.<br>
&gt; &nbsp; &nbsp; IMO this is too complex for a &#39;normal&#39; user. Thus I&#39;d vote only for 2.<br>
&gt;<br>
&gt;<br>
&gt; Yeah, but I don&#39;t think a &quot;normal&quot; user would try to use a nightly<br>
&gt; version of Studio. ;)<br>
&gt;<br>
&gt; However, I think solution 2 is enough and as we already have the zip<br>
&gt; generated at each build.<br>
</div>Nope. This zip must have another directory structure to make it work. It<br>
must look like<br>
<br>
eclipse<br>
 &nbsp;\ plugins<br>
 &nbsp;\ features<br>
<br>
Otherwise it won&#39;t work :-(<br>
<div><div></div><div class="Wj3C7c"><br>
<br>
&gt; We just need to deploy it aside the other already available downloads.<br>
&gt;<br>
&gt; Pierre-Arnaud<br>
<br>
</div></div></blockquote></div><br></div>

------=_Part_39719_16352119.1221122871973--