Return-Path: Delivered-To: apmail-directory-dev-archive@www.apache.org Received: (qmail 49753 invoked from network); 21 May 2007 15:17:39 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 21 May 2007 15:17:39 -0000 Received: (qmail 43666 invoked by uid 500); 21 May 2007 15:17:44 -0000 Delivered-To: apmail-directory-dev-archive@directory.apache.org Received: (qmail 43632 invoked by uid 500); 21 May 2007 15:17:44 -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 43621 invoked by uid 99); 21 May 2007 15:17:44 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 21 May 2007 08:17:44 -0700 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 (herse.apache.org: domain of akarasulu@gmail.com designates 66.249.92.170 as permitted sender) Received: from [66.249.92.170] (HELO ug-out-1314.google.com) (66.249.92.170) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 21 May 2007 08:17:35 -0700 Received: by ug-out-1314.google.com with SMTP id 71so953287ugh for ; Mon, 21 May 2007 08:17:12 -0700 (PDT) DKIM-Signature: a=rsa-sha1; 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; b=UQ0DvVH5PGv1VoO1iVFJj/cIRlOQ0djXyIxm9FZcwvWZjxxbJC7EiGXIBPOhrMXi9XeRBflZFtSo5v7MuoAyRV5t3nt0G+KDWBOLZf6YbY7VI+o+v0WzIgErGw8yJtZqGujjOzL4a10tFkjZ0FHOwm59zV1+/wdeQFM9HLBy10A= 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=iUM/MDyPT4Wm8UoRrkM7nyMDDKeGSK2c13HkuKDTIGRfsOhipNJRJRSRrfJ8Tn6tYNyCPoLCUdZimArZ6YtH+/oumuqGZS4yeIKf2r9ktfwZaSaixSpf/DGIyw+JqSYLU5fpvPGO9V9yK9Rx5FpUCjKN/VW72olVl43kyDPk0BA= Received: by 10.67.27.15 with SMTP id e15mr3466378ugj.1179760632357; Mon, 21 May 2007 08:17:12 -0700 (PDT) Received: by 10.66.235.5 with HTTP; Mon, 21 May 2007 08:17:12 -0700 (PDT) Message-ID: Date: Mon, 21 May 2007 11:17:12 -0400 From: "Alex Karasulu" Sender: akarasulu@gmail.com To: "Apache Directory Developers List" , elecharny@iktek.com Subject: Re: [ApacheDS] Problems building the installers In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_86657_25402945.1179760632267" References: <4651624C.4000000@labeo.de> <46517C4F.5040105@labeo.de> <43b026c70705210805o7c9a3cffp1919988513dd1617@mail.gmail.com> X-Google-Sender-Auth: ee7dab71ece255f2 X-Virus-Checked: Checked by ClamAV on apache.org ------=_Part_86657_25402945.1179760632267 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Yeah we're not there 100% yet. Yet another thing to do. I will file a JIR= A on doign this so we finally get to it. Alex On 5/21/07, Emmanuel Lecharny wrote: > > I think this is already done, and if not, then this should be done. > > On 5/21/07, Alex Karasulu wrote: > > > > I think this was due not to the SNAPSHOT repos but to the fact that we > > do not use > > a specific revision for all the plugins involved. > > > > If we disable the SNAPSHOT repos there will be other negative effects. > > For example > > when we are on a SNAPSHOT like say 1.5.1-SNAPSHOT then the snapshot jar= s > > are > > deployed to the apache snapshot repo. If a user checks out the apached= s > > trunk and > > tries to build that instead of building the svn area with the dependent > > projects then > > those snapshots from shared and daemon will not be resolved. Even wors= e > > if a user > > checks out apacheds/trunk/server-installers and tries to build that the= n > > it will fail if > > the SNAPSHOT repos are not visible. > > > > I think we just have to make sure we assign a specific revision to all > > the plugins we > > use instead of not including a revision for a plugin. This will preven= t > > the use of > > SNAPSHOT plugins I hope. > > > > There is also a pluginManagement section in the pom that we need to > > populate so > > we lock all plugins to a specific revision instead of allowing the use > > of SNAPSHOTs. > > > > Alex > > > > On 5/21/07, Chris Custine < chris.custine@gmail.com> wrote: > > > > > > Do you guys think that these problems are from having the SNAPSHOT > > > repos (regular maven repo and plugin repo) in the maven repo stack? = I am > > > basically in the habit of disabling the SNAPSHOT repos in any project= I > > > build because it does stuff like this. And yes I always disable the > > > SNAPSHOT repo in ApacheDS pom as well :-) > > > > > > Its always been in the back of my mind to ask why it is enabled, but = I > > > figured that it allowed someone to build part of the SVN project with= out > > > building the entire thing or something along those lines. > > > > > > Chris > > > > > > On 5/21/07, Alex Karasulu < akarasulu@apache.org> wrote: > > > > > > > > Ahhh the unpredictability of Maven strikes again! > > > > > > > > Alex > > > > > > > > On 5/21/07, Stefan Zoerner < stefan@labeo.de> wrote: > > > > > > > > > > Emmanuel Lecharny wrote: > > > > > > I have tested it again after having removed the repo, and still > > > > > working ... > > > > > > > > > > Hi Emmanuel, > > > > > > > > > > I have removed the repo from my machine, rebuilt it all and you > > > > > are > > > > > right: I just came back from lunch and now I have fresh > > > > > installers. > > > > > > > > > > Thanks for your help, > > > > > Stefan > > > > > > > > > > > > > > > > > > > > > > -- > Regards, > Cordialement, > Emmanuel L=E9charny > www.iktek.com > ------=_Part_86657_25402945.1179760632267 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Yeah we're not there 100% yet.  Yet another thing to do.  I w= ill file a JIRA on
doign this so we finally get to it.

Alex
<= br>
On 5/21/07, Emmanuel Lecharny <elecharny@gmail.com>= wrote:
I t= hink this is already done, and if not, then this should be done.


On 5/21/07, Alex Karasulu < akarasulu@apache.org > wrote:
I think this was due not to the SNAPSHOT repos but to the fact that we= do not use=20
a specific revision for all the plugins involved.

If we disable = the SNAPSHOT repos there will be other negative effects.  For example
when we are on a SNAPSHOT like say 1.5.1-SNAPSHOT then the snapshot jar= s are
deployed to the apache snapshot repo.  If a user checks out = the apacheds trunk and
tries to build that instead of building the svn = area with the dependent projects then=20
those snapshots from shared and daemon will not be resolved.  Even= worse if a user
checks out apacheds/trunk/server-installers and tries t= o build that then it will fail if
the SNAPSHOT repos are not visible.
I think we just have to make sure we assign a specific revision to all = the plugins we
use instead of not including a revision for a plugin.&nb= sp; This will prevent the use of
SNAPSHOT plugins I hope.

There = is also a pluginManagement section in the pom that we need to populate so
we lock all plugins to a specific revision instead of allowing the use = of SNAPSHOTs.

Alex


On 5/21/07,=20 Chris Custine < chris.custine@gmail.com> wrote:
Do you guys think that these problems are from = having the SNAPSHOT repos (regular maven repo and plugin repo) in the maven= repo stack?  I am basically in the habit of disabling the SNAPSHOT re= pos in any project I build because it does stuff like this.  And yes I= always disable the SNAPSHOT repo in ApacheDS pom as well  :-)

Its always been in the back of my mind to ask why it is enabled, bu= t I figured that it allowed someone to build part of the SVN project withou= t building the entire thing or something along those lines.

Chris


On 5/21/07, Alex Karasulu < akarasulu@apache.org> wrote:
Ahhh the unpredictability of Maven strikes again!

Alex

=
On 5/21/07, Stefan Zoerner < stefan@labeo.de> wrote:
Emmanuel Lecharny wrote:
> I have tested it again after havin= g removed the repo, and still working ...

Hi Emmanuel,

I have removed the repo from my machine, rebuil= t it all and you are
right: I just came back from lunch and now I have f= resh installers.

Thanks for your help,
     S= tefan







--
Regards,
Cordialem= ent,
Emmanuel L=E9charny
www.iktek.com

------=_Part_86657_25402945.1179760632267--