Mailing-List: contact dev-help@myfaces.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "MyFaces Development" <dev@myfaces.apache.org>
Received-SPF: pass (nike.apache.org: domain of lu4242@gmail.com designates
 209.85.132.243 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :cc:content-type;
        b=SiXdUi8wCEpKwtjNJDIsFU/gjr/Axpgtv9NWwTx7PpwZovwnnVfJ0xhghPQCMljkHu
         hry9wGxEBdMC7yCaAbt4OaohoQTvLvBWpdUzopxXPLT32ob8SOX08j+9Qy13unPoVr40
         ShpZzmS2skTJP+fkFNHq2NqXsBYTVQVrdD2r0=
MIME-Version: 1.0
In-Reply-To: <71235db40908270554r3d790caelf4f4ceec6f428c19@mail.gmail.com>
References: <71235db40908270554r3d790caelf4f4ceec6f428c19@mail.gmail.com>
Date: Thu, 27 Aug 2009 08:05:23 -0500
Message-ID: <f6c92360908270605p632c57ceob37dbbfc610bbd75@mail.gmail.com>
Subject: Re: MyFaces nightly builds
From: Leonardo Uribe <lu4242@gmail.com>
To: Matthias Wessendorf <matzew@apache.org>
Cc: MyFaces Development <dev@myfaces.apache.org>
Content-Type: multipart/alternative; boundary=001636c5b3047495b204721f38fb

--001636c5b3047495b204721f38fb
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Hi

2009/8/27 Matthias Wessendorf <matzew@apache.org>

> Hello,
>
> can one of the continuum guys enable the 1.2.x branch to be scheduled
> via the nightly build cycle ?
>
> Currently we only build trunk (2.0), e.g.:
>
> http://people.apache.org/repo/m2-snapshot-repository/org/apache/myfaces/core/myfaces-api/2.0.0-SNAPSHOT/
>
> but after we made the 2.0 stuff become trunk there was no nightly
> build for the 1.1.x and 1.2.x stuff.
>
> Would be great if one with continuum access could fix that issue.
>

Unfortunately, I don't have continuum access. For now, I'm deploying
manually myfaces core 2.0.0 related artifacts to snapshots repo when there
are changes on trunk that break the build (changes in
myfaces-builder-plugin, myfaces-test20, shared-4.0.x).

regards

Leonardo Uribe


>
> Thanks!
> Matthias
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
>

--001636c5b3047495b204721f38fb
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi<br><br><div class=3D"gmail_quote">2009/8/27 Matthias Wessendorf <span di=
r=3D"ltr">&lt;<a href=3D"mailto:matzew@apache.org">matzew@apache.org</a>&gt=
;</span><br><blockquote class=3D"gmail_quote" style=3D"border-left: 1px sol=
id rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hello,<br>
<br>
can one of the continuum guys enable the 1.2.x branch to be scheduled<br>
via the nightly build cycle ?<br>
<br>
Currently we only build trunk (2.0), e.g.:<br>
<a href=3D"http://people.apache.org/repo/m2-snapshot-repository/org/apache/=
myfaces/core/myfaces-api/2.0.0-SNAPSHOT/" target=3D"_blank">http://people.a=
pache.org/repo/m2-snapshot-repository/org/apache/myfaces/core/myfaces-api/2=
.0.0-SNAPSHOT/</a><br>

<br>
but after we made the 2.0 stuff become trunk there was no nightly<br>
build for the 1.1.x and 1.2.x stuff.<br>
<br>
Would be great if one with continuum access could fix that issue.<br>
</blockquote><div><br>Unfortunately, I don&#39;t have continuum access. For=
 now, I&#39;m deploying manually myfaces core 2.0.0 related artifacts to sn=
apshots repo when there are changes on trunk that break the build (changes =
in myfaces-builder-plugin, myfaces-test20, shared-4.0.x).<br>
<br>regards<br><br>Leonardo Uribe<br>=A0</div><blockquote class=3D"gmail_qu=
ote" style=3D"border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0p=
t 0.8ex; padding-left: 1ex;"><br>
Thanks!<br>
Matthias<br>
<font color=3D"#888888"><br>
--<br>
Matthias Wessendorf<br>
<br>
blog: <a href=3D"http://matthiaswessendorf.wordpress.com/" target=3D"_blank=
">http://matthiaswessendorf.wordpress.com/</a><br>
sessions: <a href=3D"http://www.slideshare.net/mwessendorf" target=3D"_blan=
k">http://www.slideshare.net/mwessendorf</a><br>
twitter: <a href=3D"http://twitter.com/mwessendorf" target=3D"_blank">http:=
//twitter.com/mwessendorf</a><br>
</font></blockquote></div><br>

--001636c5b3047495b204721f38fb--