Mailing-List: contact dev-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Commons Developers List" <dev@commons.apache.org>
Received-SPF: pass (athena.apache.org: local policy)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
  s=s1024; d=yahoo.com;
  h=X-YMail-OSG:Received:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID;
  b=gCJfxTDBS+Dn1o5Gyv19aR1hww/lXgwHytF5F9B4fhtUxNbV38ZJXQ6PpfqyGnsZSSeDZRl1gF+OD38aG6z1Mxpw8eMqYsG781n64JaVMmvhlhPrQ4Jjuv8C/YYyjii+4uCFDJCQIPt/zMgRZMZ4EMD0KhNouMqxnUWFjiIcdQM=;
Date: Fri, 13 Jun 2008 10:28:20 -0700 (PDT)
From: Matt Benson <gudnabrsam@yahoo.com>
Subject: Re: RC attempts
To: Commons Developers List <dev@commons.apache.org>
In-Reply-To: <55afdc850806121750y432f4e22v3f633f560e21a9ea@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Message-ID: <683840.94096.qm@web55102.mail.re4.yahoo.com>


--- Niall Pemberton <niall.pemberton@gmail.com> wrote:

> On Fri, Jun 13, 2008 at 12:27 AM, Matt Benson
> <gudnabrsam@yahoo.com> wrote:
> > Update:  Luckily pquerna was available on
> #asfinfra
> > and retrieved the production site from www before
> it
> > got synched with the new content.  I couldn't get
> > JXPATH_1_2 to build the Maven 1 site... though I
> did
> > find an email trail where jcarman had had the same
> > problem before:
> >
> > Could not find the class:
> > org.apache.commons.jelly.tags.fmt.FmtTagLibrary
> >

It just occurred to me that I probably could have
retrieved a built site from a binary distro.  :)

> > I'll try the RC again tomorrow.
> 
> Personally I don't like the release plugin and I
> don't use it for
> component releases (only the poms). I just tag the
> RC, manually
> setting the actual version number. Then check out
> the release
> candidate tag and build the RC using "mvn -Prc
> install" (using
> "install" rather than "package" also causes the
> checksums to be
> created - but in you local m2 repo).

Thanks, I'll try this now.  :)

-Matt

> 
> Niall
> 
> > -Matt
> >
> > --- Matt Benson <gudnabrsam@yahoo.com> wrote:
> >
> >>
> >> --- James Carman <james@carmanconsulting.com>
> wrote:
> >>
> >> > You're right, imagining the profanity makes
> this
> >> > message much more
> >> > enjoyable! :)
> >>
> >> I don't know about that, but I know that writing
> it
> >> without felt awfully stifling.
> >>
> >> >
> >> > You need to use the "rc" profile when building
> a
> >> > release candidate.
> >> > The default profile shouldn't be updating the
> >> site.
> >> > We should have to
> >> > turn on a "release" profile or something for
> that
> >> to
> >> > happen.  What
> >> > command did you use?
> >> >
> >>
> >> Well, actually I think my problem is that I was
> >> trying
> >> to use _some_ of Rahul's proposed instructions on
> >> the
> >> CreatingReleases page on the wiki; I need to
> >> remember,
> >> apparently, that none of those commands are
> >> particularly safe as yet and that I should
> >> completely
> >> ignore them in favor of your commands farther
> down
> >> the
> >> page.  <sigh>
> >>
> >> -Matt
> >>
> >> >
> >> >
> >> > On Thu, Jun 12, 2008 at 6:44 PM, Matt Benson
> >> > <gudnabrsam@yahoo.com> wrote:
> >> > > Have I mentioned I HATE Maven?  I don't
> >> understand
> >> > how
> >> > > something that looks innocuous like building
> an
> >> RC
> >> > can
> >> > > go out and update the production website,
> which,
> >> > > AFAICT, isn't backed up anywhere, so I guess
> >> I'll
> >> > be
> >> > > trying to regen it from the previous release.
> >> Can
> >> > > anyone tell me simply exactly what commands
> will
> >> > > create an RC I can use without breaking all
> >> kinds
> >> > of
> >> > > stuff?
> >> > >
> >> > > -Matt
> >> > >
> >> > > P.S.  Please read this email as if it were
> >> fairly
> >> > > drenched in profanity.
> >> > >
> >> > >
> >> > >
> >> > >
> >> > >
> >> >
> >>
> >
>
---------------------------------------------------------------------
> >> > > To unsubscribe, e-mail:
> >> > dev-unsubscribe@commons.apache.org
> >> > > For additional commands, e-mail:
> >> > dev-help@commons.apache.org
> >> > >
> >> > >
> >> >
> >> >
> >>
> >
>
---------------------------------------------------------------------
> >> > To unsubscribe, e-mail:
> >> > dev-unsubscribe@commons.apache.org
> >> > For additional commands, e-mail:
> >> > dev-help@commons.apache.org
> >> >
> >> >
> >>
> >>
> >>
> >>
> >>
> >>
> >
>
---------------------------------------------------------------------
> >> To unsubscribe, e-mail:
> >> dev-unsubscribe@commons.apache.org
> >> For additional commands, e-mail:
> >> dev-help@commons.apache.org
> >>
> >>
> >
> >
> >
> >
> >
> >
>
---------------------------------------------------------------------
> > To unsubscribe, e-mail:
> dev-unsubscribe@commons.apache.org
> > For additional commands, e-mail:
> dev-help@commons.apache.org
> >
> >
> 
>
---------------------------------------------------------------------
> To unsubscribe, e-mail:
> dev-unsubscribe@commons.apache.org
> For additional commands, e-mail:
> dev-help@commons.apache.org
> 
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org