You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by Henrib <hb...@gmail.com> on 2009/11/13 17:38:39 UTC
Help cutting JEXL-2.0 RC1 needed
I'm stuck trying to create an RC1 for JEXL-2.0.
I've followed each step of the procedure described at
http://wiki.apache.org/commons/CreatingReleases .
When performing the mvn -prc release:prepare , it gets stuck on [gpg:sign
{execution: sign-artifacts}] with commons-parent version 12; with
commons-parent version 11, it gets further but stops at:
[ERROR] BUILD FAILURE
...
svn: Commit failed (details follow):
svn: File
'/repos/asf/commons/proper/jexl/tags/JEXL_2_0_RC1/src/main/assembly/src.xml'
already exists
Any hint/advice/help ?
Thanks
Henrib
(PS: for info, Java 5 running on OSX 10.6.2:
Hornet:jexl-2.0 henri$ java -version
java version "1.5.0_19"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_19-b02-304)
Java HotSpot(TM) Client VM (build 1.5.0_19-137, mixed mode, sharing)
Hornet:jexl-2.0 henri$ uname -a
Darwin Hornet.local 10.2.0 Darwin Kernel Version 10.2.0: Tue Nov 3 10:37:10
PST 2009; root:xnu-1486.2.11~1/RELEASE_I386 i386
Hornet:jexl-2.0 henri$
)
--
View this message in context: http://old.nabble.com/Help-cutting-JEXL-2.0-RC1-needed-tp26339499p26339499.html
Sent from the Commons - Dev mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: Help cutting JEXL-2.0 RC1 needed
Posted by Ralph Goers <ra...@dslextreme.com>.
I ran mvn site on my Mac and target/site/ looks just like what is at your link. Did you upload it to p.a.o using site:deploy? BTW - the instructions say to use mvn site-deploy. Where does that plugin come from? The standard maven plugin is site:deploy.
Ralph
On Nov 16, 2009, at 4:16 PM, Niall Pemberton wrote:
> On Mon, Nov 16, 2009 at 10:38 PM, Henrib <hb...@gmail.com> wrote:
>>
>> I thought this might be related to the lack of commons-parent and/or
>> commons-build; even tried to ln -s those in the target as peers of checkout/
>> between prepare and perform to no avail.
>> Did cut an RC2 that has the same site formatting / styling problem, it's
>> here: http://people.apache.org/builds/commons/jexl/2.0/RC2/site/
>> Dont know what else I can do... :-(
>
> I just tried generating JEXL site from trunk and it looks OK to me:
>
> http://people.apache.org/~niallp/jexl/
>
> Looking at your version, seems that site.css is different:
> http://people.apache.org/builds/commons/jexl/2.0/RC2/site/css/site.css
>
> from mine:
> http://people.apache.org/~niallp/jexl/css/site.css
>
> site.css and the menus are pulled in from commons-site via
> commons-parent during the build process. For some reason it doesn't
> seemed to have done that for you when you built. Sorry not sure why
>
> Niall
>
>> Henrib wrote:
>>>
>>> I'm now able to publish releases but...
>>> 'mvn site' locally generates a different version than the one that ends up
>>> being published; the local version does generate the reports menu & seems
>>> to be styled correctly but the published version lacks the reports and
>>> styling is non-existent...
>>> Anyone with a similar experience ?
>>>
>>
>> --
>> View this message in context: http://old.nabble.com/Help-cutting-JEXL-2.0-RC1-needed-tp26339499p26379919.html
>> Sent from the Commons - Dev mailing list archive at Nabble.com.
>>
>>
>> ---------------------------------------------------------------------
>> 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
Re: Help cutting JEXL-2.0 RC1 needed
Posted by Henrib <hb...@gmail.com>.
Niall Pemberton-2 wrote:
>
> ...
> I just tried generating JEXL site from trunk and it looks OK to me:
>
> http://people.apache.org/~niallp/jexl/
>
> Looking at your version, seems that site.css is different:
> http://people.apache.org/builds/commons/jexl/2.0/RC2/site/css/site.css
>
> from mine:
> http://people.apache.org/~niallp/jexl/css/site.css
>
> site.css and the menus are pulled in from commons-site via
> commons-parent during the build process. For some reason it doesn't
> seemed to have done that for you when you built. Sorry not sure why
>
> Niall
>
Thank for taking the time to check it out.
This seems to indicate that the procedure I'm following (
http://wiki.apache.org/commons/CreatingReleases ) is not correct.
Out of these links, can you point the correct one to build commons-jexl ?
http://maven.apache.org/developers/release/apache-release.html
http://commons.apache.org/building.html
http://commons.apache.org/releases/prepare.html
http://commons.apache.org/releases/release.html
http://wiki.apache.org/commons/CreatingReleases
Thanks
Henrib
--
View this message in context: http://old.nabble.com/Help-cutting-JEXL-2.0-RC1-needed-tp26339499p26385717.html
Sent from the Commons - Dev mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: Help cutting JEXL-2.0 RC1 needed
Posted by Henrib <hb...@gmail.com>.
....the navigation.xml...
This might be one of the causes as explained in
http://maven.apache.org/guides/mini/guide-site.html .
I'll dig into this.
--
View this message in context: http://old.nabble.com/Help-cutting-JEXL-2.0-RC1-needed-tp26339499p26385994.html
Sent from the Commons - Dev mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: Help cutting JEXL-2.0 RC1 needed
Posted by Henrib <hb...@gmail.com>.
sebb-2-2 wrote:
>
> ...
> I don't know if these are due to site build problems or data problems;
> most likely the latter.
> ...
>
I'll correct the data related ones. Albeit I wish it would be a data problem
only; the navigation.xml for instance does not generate the expected html.
The only way to get it generated correctly was to add:
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-site-plugin</artifactId>
> <version>2.0.1</version>
> <configuration>
> <!-- Exclude the navigation file for Maven 1 sites
> and the changes file used by the changes-plugin,
> as they interfere with the site generation. -->
> <moduleExcludes>
> <xdoc>navigation.xml,changes.xml</xdoc>
> </moduleExcludes>
> </configuration>
> </plugin>
>
I removed this for RC2 trying to reduce entropy...
--
View this message in context: http://old.nabble.com/Help-cutting-JEXL-2.0-RC1-needed-tp26339499p26385813.html
Sent from the Commons - Dev mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: Help cutting JEXL-2.0 RC1 needed
Posted by sebb <se...@gmail.com>.
On 17/11/2009, Niall Pemberton <ni...@gmail.com> wrote:
> On Mon, Nov 16, 2009 at 10:38 PM, Henrib <hb...@gmail.com> wrote:
> >
> > I thought this might be related to the lack of commons-parent and/or
> > commons-build; even tried to ln -s those in the target as peers of checkout/
> > between prepare and perform to no avail.
> > Did cut an RC2 that has the same site formatting / styling problem, it's
> > here: http://people.apache.org/builds/commons/jexl/2.0/RC2/site/
> > Dont know what else I can do... :-(
>
>
> I just tried generating JEXL site from trunk and it looks OK to me:
>
> http://people.apache.org/~niallp/jexl/
The Javadoc is headed "Commons JEXL 2.0-SNAPSHOT API" which does not
look correct.
Also, the front page still has Javadoc for 1.0, and none for 2.0 at
the top of the lh menu
Releases and Builds section does not include 2.0
Building says that Jexl uses Maven or Ant, but Jexl 2 only uses Maven.
I don't know if these are due to site build problems or data problems;
most likely the latter.
> Looking at your version, seems that site.css is different:
> http://people.apache.org/builds/commons/jexl/2.0/RC2/site/css/site.css
>
> from mine:
> http://people.apache.org/~niallp/jexl/css/site.css
>
> site.css and the menus are pulled in from commons-site via
> commons-parent during the build process. For some reason it doesn't
> seemed to have done that for you when you built. Sorry not sure why
>
>
> Niall
>
>
> > Henrib wrote:
> >>
> >> I'm now able to publish releases but...
> >> 'mvn site' locally generates a different version than the one that ends up
> >> being published; the local version does generate the reports menu & seems
> >> to be styled correctly but the published version lacks the reports and
> >> styling is non-existent...
> >> Anyone with a similar experience ?
> >>
> >
> > --
> > View this message in context: http://old.nabble.com/Help-cutting-JEXL-2.0-RC1-needed-tp26339499p26379919.html
> > Sent from the Commons - Dev mailing list archive at Nabble.com.
> >
> >
> > ---------------------------------------------------------------------
> > 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
Re: Help cutting JEXL-2.0 RC1 needed
Posted by Niall Pemberton <ni...@gmail.com>.
On Mon, Nov 16, 2009 at 10:38 PM, Henrib <hb...@gmail.com> wrote:
>
> I thought this might be related to the lack of commons-parent and/or
> commons-build; even tried to ln -s those in the target as peers of checkout/
> between prepare and perform to no avail.
> Did cut an RC2 that has the same site formatting / styling problem, it's
> here: http://people.apache.org/builds/commons/jexl/2.0/RC2/site/
> Dont know what else I can do... :-(
I just tried generating JEXL site from trunk and it looks OK to me:
http://people.apache.org/~niallp/jexl/
Looking at your version, seems that site.css is different:
http://people.apache.org/builds/commons/jexl/2.0/RC2/site/css/site.css
from mine:
http://people.apache.org/~niallp/jexl/css/site.css
site.css and the menus are pulled in from commons-site via
commons-parent during the build process. For some reason it doesn't
seemed to have done that for you when you built. Sorry not sure why
Niall
> Henrib wrote:
>>
>> I'm now able to publish releases but...
>> 'mvn site' locally generates a different version than the one that ends up
>> being published; the local version does generate the reports menu & seems
>> to be styled correctly but the published version lacks the reports and
>> styling is non-existent...
>> Anyone with a similar experience ?
>>
>
> --
> View this message in context: http://old.nabble.com/Help-cutting-JEXL-2.0-RC1-needed-tp26339499p26379919.html
> Sent from the Commons - Dev mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> 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
Re: Help cutting JEXL-2.0 RC1 needed
Posted by Henrib <hb...@gmail.com>.
I thought this might be related to the lack of commons-parent and/or
commons-build; even tried to ln -s those in the target as peers of checkout/
between prepare and perform to no avail.
Did cut an RC2 that has the same site formatting / styling problem, it's
here: http://people.apache.org/builds/commons/jexl/2.0/RC2/site/
Dont know what else I can do... :-(
Henrib wrote:
>
> I'm now able to publish releases but...
> 'mvn site' locally generates a different version than the one that ends up
> being published; the local version does generate the reports menu & seems
> to be styled correctly but the published version lacks the reports and
> styling is non-existent...
> Anyone with a similar experience ?
>
--
View this message in context: http://old.nabble.com/Help-cutting-JEXL-2.0-RC1-needed-tp26339499p26379919.html
Sent from the Commons - Dev mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: Help cutting JEXL-2.0 RC1 needed
Posted by Henrib <hb...@gmail.com>.
I'm now able to publish releases but...
'mvn site' locally generates a different version than the one that ends up
being published; the local version does generate the reports menu & seems to
be styled correctly but the published version lacks the reports and styling
is non-existent...
Anyone with a similar experience ?
--
View this message in context: http://old.nabble.com/Help-cutting-JEXL-2.0-RC1-needed-tp26339499p26375531.html
Sent from the Commons - Dev mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: Help cutting JEXL-2.0 RC1 needed
Posted by Henrib <hb...@gmail.com>.
Thanks for the offer; how should/can we proceed so we can capture this info
for the next project release? I'd hate to come back for help again and bug
you all when the release vote goes thru. :-)
Siegfried Goeschl wrote:
>
> Hi Henrib,
>
> if needed I can lend you a hand and help you through the M2 release
> around Saturday or Sunday evening (e.g. 22:00 CET+1)
>
> Cheers
>
> PS: I remember my first release too well ... ;-)
>
>
--
View this message in context: http://old.nabble.com/Help-cutting-JEXL-2.0-RC1-needed-tp26339499p26345266.html
Sent from the Commons - Dev mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: Help cutting JEXL-2.0 RC1 needed
Posted by Siegfried Goeschl <si...@it20one.at>.
Hi Henrib,
if needed I can lend you a hand and help you through the M2 release
around Saturday or Sunday evening (e.g. 22:00 CET+1)
Cheers
PS: I remember my first release too well ... ;-)
Henrib wrote:
> Thanks for the info; not sure how to perform step 5 though...
> Trying to cut a release is a tad stressfull for a newbie. :-)
>
> Niall Pemberton-2 wrote:
>
>> ...
>> 5) Upload the artifacts for review
>> ...
>>
>>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: Help cutting JEXL-2.0 RC1 needed
Posted by Phil Steitz <ph...@gmail.com>.
sebb wrote:
> On 14/11/2009, Christian Grobmeier <gr...@gmail.com> wrote:
>> >
>> > > I'm sure glad there is help; there are a few project that are just going
>> > /
>> > > went through that process (commons-exec for instance) . Is there anyone
>> > > involved willing to share their successful publishing process ?
>> >
>> > We definitely need to do that and it is on my todo list to document
>> > the "manual" process that I follow. Basically, we have two ways to
>> > do releases now - using the maven release plugin (more or less
>> > documented on the Wiki) and "manually" doing the tagging and file
>> > movement via the command line. Personally, I prefer the command line
>> > approach.
>>
>>
>>
>> I have used the M2 approach for compress. It worked, but I sometime felt
>> that the process had control bout me and not otherwise. I also run into
>> several problems, from which most were based on my own enviroment. However,
>> it was no fun at all. Currently I try to build up the release plugin for
>> Log4php project, but this is pretty hard too. At the moment, I am tending to
>> a proper command line plan. There are too much problems I don't understand
>> with M2.
>>
>> @Henri: I don't know what why the error here happened, but I know that you
>> need a clean checkout to make release plugin work proberly. Its not working
>> if you have some kind of files from your IDE in your project.
>
> Seems to me one should _always_ work from a clean check-out,
> regardless of the build process. Otherwise the process may not be
> repeatable by others, and it's far too easy to accidentally include
> spurious files.
+1. This is another reason I like the "manual" approach outlined by
Niall above. You know what you are tagging, the tags are immutable
and you build the artifacts from a fresh checkout of the tag.
Phil
>
>> Cheers
>>
>> Christian
>>
>
> ---------------------------------------------------------------------
> 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
Re: Help cutting JEXL-2.0 RC1 needed
Posted by sebb <se...@gmail.com>.
On 14/11/2009, Christian Grobmeier <gr...@gmail.com> wrote:
> >
> >
> > > I'm sure glad there is help; there are a few project that are just going
> > /
> > > went through that process (commons-exec for instance) . Is there anyone
> > > involved willing to share their successful publishing process ?
> >
> > We definitely need to do that and it is on my todo list to document
> > the "manual" process that I follow. Basically, we have two ways to
> > do releases now - using the maven release plugin (more or less
> > documented on the Wiki) and "manually" doing the tagging and file
> > movement via the command line. Personally, I prefer the command line
> > approach.
>
>
>
> I have used the M2 approach for compress. It worked, but I sometime felt
> that the process had control bout me and not otherwise. I also run into
> several problems, from which most were based on my own enviroment. However,
> it was no fun at all. Currently I try to build up the release plugin for
> Log4php project, but this is pretty hard too. At the moment, I am tending to
> a proper command line plan. There are too much problems I don't understand
> with M2.
>
> @Henri: I don't know what why the error here happened, but I know that you
> need a clean checkout to make release plugin work proberly. Its not working
> if you have some kind of files from your IDE in your project.
Seems to me one should _always_ work from a clean check-out,
regardless of the build process. Otherwise the process may not be
repeatable by others, and it's far too easy to accidentally include
spurious files.
> Cheers
>
> Christian
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: Help cutting JEXL-2.0 RC1 needed
Posted by Christian Grobmeier <gr...@gmail.com>.
>
>
> > I'm sure glad there is help; there are a few project that are just going
> /
> > went through that process (commons-exec for instance) . Is there anyone
> > involved willing to share their successful publishing process ?
>
> We definitely need to do that and it is on my todo list to document
> the "manual" process that I follow. Basically, we have two ways to
> do releases now - using the maven release plugin (more or less
> documented on the Wiki) and "manually" doing the tagging and file
> movement via the command line. Personally, I prefer the command line
> approach.
I have used the M2 approach for compress. It worked, but I sometime felt
that the process had control bout me and not otherwise. I also run into
several problems, from which most were based on my own enviroment. However,
it was no fun at all. Currently I try to build up the release plugin for
Log4php project, but this is pretty hard too. At the moment, I am tending to
a proper command line plan. There are too much problems I don't understand
with M2.
@Henri: I don't know what why the error here happened, but I know that you
need a clean checkout to make release plugin work proberly. Its not working
if you have some kind of files from your IDE in your project.
Cheers
Christian
Re: Help cutting JEXL-2.0 RC1 needed
Posted by Phil Steitz <ph...@gmail.com>.
Henrib wrote:
> Thanks Phil.
> My first hurdle is the signing part which I'm just discovering and have yet
> to understand...
> And information is hard to find: the public_html directory is not the most
> documented thing you ought to know. What should be in there exactly ?
As Rahul pointed out, people.apache.org:/home/henrib/public_html is
essentially the doc root of the web site available at
http://people.apache.org/~henrib
so you put things there that you want to make publicly available.
>
> I'm sure glad there is help; there are a few project that are just going /
> went through that process (commons-exec for instance) . Is there anyone
> involved willing to share their successful publishing process ?
We definitely need to do that and it is on my todo list to document
the "manual" process that I follow. Basically, we have two ways to
do releases now - using the maven release plugin (more or less
documented on the Wiki) and "manually" doing the tagging and file
movement via the command line. Personally, I prefer the command line
approach. I will update the docs here:
http://commons.apache.org/releases/release.html
once I complete the pool and dbcp releases that I am working on.
The link above includes links to info on how to set up a signing
key, which you need to do in either case (whether you have maven
generate the sigs or do it manually). Also mentioned there are some
tools in /committers/tools for signing files in a directory and
verifying signatures.
Sorry the docs are not where they need to be.
Phil
>
> Many thanks.
> Henrib
>
>
> Phil Steitz wrote:
>> ...
>> I always just tar up the files from /target and ~/.m2/repository/...
>> and then scp them to my home directory and unpack them in public_html.
>>
>> Phil
>>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: Help cutting JEXL-2.0 RC1 needed
Posted by Rahul Akolkar <ra...@gmail.com>.
Attempts at answering any specific questions below ...
On Fri, Nov 13, 2009 at 6:11 PM, Henrib <hb...@gmail.com> wrote:
>
> Thanks Phil.
> My first hurdle is the signing part which I'm just discovering and have yet
> to understand...
<snip/>
The m2 gpg-plugin should do it fairly effortlessly (once its set up,
which may present a catch or two). It should generate the .asc files
as needed.
> And information is hard to find: the public_html directory is not the most
> documented thing you ought to know. What should be in there exactly ?
>
<snap/>
Yes, some of the information is hard to find. WRT the above question, see:
http://www.apache.org/dev/new-committers-guide.html#public_html
(ssh into people.a.o, create public_html in your ~ if needed, chmod it
755, then visit http://people.apache.org/~henrib and it won't 404
anymore)
-Rahul
> I'm sure glad there is help; there are a few project that are just going /
> went through that process (commons-exec for instance) . Is there anyone
> involved willing to share their successful publishing process ?
>
> Many thanks.
> Henrib
>
>
> Phil Steitz wrote:
>>
>> ...
>> I always just tar up the files from /target and ~/.m2/repository/...
>> and then scp them to my home directory and unpack them in public_html.
>>
>> Phil
>>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: Help cutting JEXL-2.0 RC1 needed
Posted by Henrib <hb...@gmail.com>.
Thanks Phil.
My first hurdle is the signing part which I'm just discovering and have yet
to understand...
And information is hard to find: the public_html directory is not the most
documented thing you ought to know. What should be in there exactly ?
I'm sure glad there is help; there are a few project that are just going /
went through that process (commons-exec for instance) . Is there anyone
involved willing to share their successful publishing process ?
Many thanks.
Henrib
Phil Steitz wrote:
>
> ...
> I always just tar up the files from /target and ~/.m2/repository/...
> and then scp them to my home directory and unpack them in public_html.
>
> Phil
>
>
--
View this message in context: http://old.nabble.com/Help-cutting-JEXL-2.0-RC1-needed-tp26339499p26345042.html
Sent from the Commons - Dev mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: Help cutting JEXL-2.0 RC1 needed
Posted by Phil Steitz <ph...@gmail.com>.
Henrib wrote:
> Thanks for the info; not sure how to perform step 5 though...
> Trying to cut a release is a tad stressfull for a newbie. :-)
The stress never goes away, but neither does the help :)
>
> Niall Pemberton-2 wrote:
>> ...
>> 5) Upload the artifacts for review
>> ...
>>
>
I always just tar up the files from /target and ~/.m2/repository/...
and then scp them to my home directory and unpack them in public_html.
Phil
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: Help cutting JEXL-2.0 RC1 needed
Posted by Henrib <hb...@gmail.com>.
Thanks for the info; not sure how to perform step 5 though...
Trying to cut a release is a tad stressfull for a newbie. :-)
Niall Pemberton-2 wrote:
>
> ...
> 5) Upload the artifacts for review
> ...
>
--
View this message in context: http://old.nabble.com/Help-cutting-JEXL-2.0-RC1-needed-tp26339499p26339766.html
Sent from the Commons - Dev mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: Help cutting JEXL-2.0 RC1 needed
Posted by Niall Pemberton <ni...@gmail.com>.
On Fri, Nov 13, 2009 at 4:38 PM, Henrib <hb...@gmail.com> wrote:
>
> I'm stuck trying to create an RC1 for JEXL-2.0.
> I've followed each step of the procedure described at
> http://wiki.apache.org/commons/CreatingReleases .
I never use the release plugin for components (only parent pom) - so I
would give up on that and just do it manually.
1) Commit updates to the version numbers in pom.xml, build.xml,
project.xml from 2.0-SNAPSHOT to 2.0
2) Tag JEXL_2.0_RC1
3) Check out the JEXL_2.0_RC1 tag
4) Run the following maven command:
mvn -Prc install
5) Upload the artifacts for review
[Note: using "install" rather than "package" in the m2 command causes
the md5/sha files to get created and put in your local repo - target
has everything else except that]
Niall
> When performing the mvn -prc release:prepare , it gets stuck on [gpg:sign
> {execution: sign-artifacts}] with commons-parent version 12; with
> commons-parent version 11, it gets further but stops at:
> [ERROR] BUILD FAILURE
> ...
> svn: Commit failed (details follow):
> svn: File
> '/repos/asf/commons/proper/jexl/tags/JEXL_2_0_RC1/src/main/assembly/src.xml'
> already exists
>
> Any hint/advice/help ?
> Thanks
> Henrib
>
> (PS: for info, Java 5 running on OSX 10.6.2:
> Hornet:jexl-2.0 henri$ java -version
> java version "1.5.0_19"
> Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_19-b02-304)
> Java HotSpot(TM) Client VM (build 1.5.0_19-137, mixed mode, sharing)
> Hornet:jexl-2.0 henri$ uname -a
> Darwin Hornet.local 10.2.0 Darwin Kernel Version 10.2.0: Tue Nov 3 10:37:10
> PST 2009; root:xnu-1486.2.11~1/RELEASE_I386 i386
> Hornet:jexl-2.0 henri$
> )
>
>
> --
> View this message in context: http://old.nabble.com/Help-cutting-JEXL-2.0-RC1-needed-tp26339499p26339499.html
> Sent from the Commons - Dev mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> 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
Re: Help cutting JEXL-2.0 RC1 needed
Posted by Henrib <hb...@gmail.com>.
Henrib wrote:
>
> Using the manual procedure, generated
> http://people.apache.org/~henrib/jexl-2.0rc3/site/staging/ which is styled
> correctly but has the site links wrong like:
> http://people.apache.org/~henrib/jexl-2.0rc3/Users/people.apache.org/home/henrib/public_html/jexl-2.0rc3/site
>
Similar symptoms in http://jira.codehaus.org/browse/MSITE-404 ...
--
View this message in context: http://old.nabble.com/Help-cutting-JEXL-2.0-RC1-needed-tp26339499p26396488.html
Sent from the Commons - Dev mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: Help cutting JEXL-2.0 RC1 needed
Posted by Niall Pemberton <ni...@gmail.com>.
On Tue, Nov 17, 2009 at 6:41 PM, Henrib <hb...@gmail.com> wrote:
>
> Tried an RC3 after cleansing the xdoc related elements.
> From a clean svn checkout, the 'mvn site' works as expected.
>
> Using the manual procedure, generated
> http://people.apache.org/~henrib/jexl-2.0rc3/site/staging/ which is styled
> correctly but has the site links are wrong:
> http://people.apache.org/~henrib/jexl-2.0rc3/Users/people.apache.org/home/henrib/public_html/jexl-2.0rc3/site
I'm guessing, but probably something to do with
distributionManagement/site/url is causing this. The site isn't
actually part of the distrinbution, so its not being voted on and is
just there for people's convenience - so you could check out the tag
and generate it simply using "mvn clean site" and upload it manually.
I find maven's automated stuff too painful and I don't like some of
the side effects which is why I use a manual method for the whole
release process.
Niall
> Using the automated procedure, generated
> http://people.apache.org/builds/commons/jexl/2.0/RC3/site/ which has correct
> links but is not styled correctly and misses the extra-menus (reports, etc).
>
> Hints welcome as usual.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: Help cutting JEXL-2.0 RC1 needed
Posted by Henrib <hb...@gmail.com>.
Tried an RC3 after cleansing the xdoc related elements.
>From a clean svn checkout, the 'mvn site' works as expected.
Using the manual procedure, generated
http://people.apache.org/~henrib/jexl-2.0rc3/site/staging/ which is styled
correctly but has the site links are wrong:
http://people.apache.org/~henrib/jexl-2.0rc3/Users/people.apache.org/home/henrib/public_html/jexl-2.0rc3/site
Using the automated procedure, generated
http://people.apache.org/builds/commons/jexl/2.0/RC3/site/ which has correct
links but is not styled correctly and misses the extra-menus (reports, etc).
Hints welcome as usual.
--
View this message in context: http://old.nabble.com/Help-cutting-JEXL-2.0-RC1-needed-tp26339499p26395243.html
Sent from the Commons - Dev mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: Help cutting JEXL-2.0 RC1 needed
Posted by Henrib <hb...@gmail.com>.
More progress: perform succeeded!
When trying to perform, maven starts with a warning:
> [WARNING] Maven will be executed in interactive mode, but no input stream
> has been configured for this MavenInvoker instance.
>
This lead to http://jira.codehaus.org/browse/MRELEASE-424 ; I applied the
fix but had also provide the username / password to get it to work.
In the parent pom.xml, I did:
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-release-plugin</artifactId>
> <version>2.0-beta-9</version>
> <configuration>
> <username>henrib</username>
> <password>mypassword</password>
> <mavenExecutorId>forked-path</mavenExecutorId>
> </configuration>
> </plugin>
>
The command line I used was:
> mvn -Prc -Dgpg.passphrase=mygkgkey -Dpassword=mypassword release:perform
> -e
>
The settings.xml also contained the username / password for good measure...
Dont know how much is redundant but this finally made it work.
I'll send out the vote momentarily.
Thanks to all for helping out!
--
View this message in context: http://old.nabble.com/Help-cutting-JEXL-2.0-RC1-needed-tp26339499p26362268.html
Sent from the Commons - Dev mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: Help cutting JEXL-2.0 RC1 needed
Posted by Rahul Akolkar <ra...@gmail.com>.
On Sun, Nov 15, 2009 at 9:21 AM, Henrib <hb...@gmail.com> wrote:
>
>
> Using the trunk in the <scm> tag and -Dpassword allowed to successfully
> prepare!
<snip/>
Progress. The <scm> section should have trunk URLs (in trunk :-) so
that must have got out of sync somewhere along the way here.
> The release:perform is getting stuck in the deploy:deploy...
>
<snap/>
Whats the commons.deployment.protocol value you're using? (if you
don't know, its "scp").
Check if you can otherwise ssh into people.a.o using ssh-agent (or Pageant).
Check if you have something like the following in your
$USER_HOME/.m2/settings.xml :
<server>
<id>apache.snapshots</id>
<username>henrib</username>
<directoryPermissions>755</directoryPermissions>
<filePermissions>644</filePermissions>
<!-- add configuration if needed (e.g. PuTTY) -->
</server>
Finally, try mvn with debug (-X) and/or traces (-e) to see if there is
more information.
-Rahul
>
> Christian Grobmeier wrote:
>>
>> I think you hould mention the trunk instead of RC1 in the <scm> tag - but
>> thats just a guess. I had the same idea before a few days with log4php.
>>
>> However, I also figured out that I need to -Dpassword to make this work
>> correctly - did you manage it to run a commit with certificate?
>>
>> Cheers
>> Christian
>>
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: Help cutting JEXL-2.0 RC1 needed
Posted by Henrib <hb...@gmail.com>.
Using the trunk in the <scm> tag and -Dpassword allowed to successfully
prepare!
The release:perform is getting stuck in the deploy:deploy...
Christian Grobmeier wrote:
>
> I think you hould mention the trunk instead of RC1 in the <scm> tag - but
> thats just a guess. I had the same idea before a few days with log4php.
>
> However, I also figured out that I need to -Dpassword to make this work
> correctly - did you manage it to run a commit with certificate?
>
> Cheers
> Christian
>
>
--
View this message in context: http://old.nabble.com/Help-cutting-JEXL-2.0-RC1-needed-tp26339499p26359505.html
Sent from the Commons - Dev mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: Help cutting JEXL-2.0 RC1 needed
Posted by Christian Grobmeier <gr...@gmail.com>.
>
>
> [INFO] Tagging release with the label JEXL_2_0_RC1...
> [INFO] Executing: /bin/sh -c cd
> /Users/henri/Java/apache-commons/rc1/commons/jexl-2.0 && svn
> --non-interactive copy --file
>
> /var/folders/Ya/YaSJZzgsHu4O4NXovx-nNE+++TI/-Tmp-/maven-scm-1545582656.commit
> --revision 836226
> https://svn.apache.org/repos/asf/commons/proper/jexl/tags/JEXL_2_0_RC1
> https://svn.apache.org/repos/asf/commons/proper/jexl/tags/JEXL_2_0_RC1
>
> The source & destination of the svn copy are the same...
> I suspect the pom.xml should carry somewhere the 'trunk' information; may
> be
> the <scm> should mention the trunk rather than RC1 ?
>
> I think you hould mention the trunk instead of RC1 in the <scm> tag - but
thats just a guess. I had the same idea before a few days with log4php.
However, I also figured out that I need to -Dpassword to make this work
correctly - did you manage it to run a commit with certificate?
Cheers
Christian
Re: Help cutting JEXL-2.0 RC1 needed
Posted by Henrib <hb...@gmail.com>.
Made some progress; by adding an 'rc' profile in my maven / settings.xml
containing the gpg.passphrase, using commons-parent-12, I'm able to sign the
artifacts.
My input is:
What is the release version for "Commons JEXL"?
(org.apache.commons:commons-jexl) 2.0: : 2.0-RC1
What is SCM release tag or label for "Commons JEXL"?
(org.apache.commons:commons-jexl) commons-jexl-2.0: : JEXL_2_0_RC1
What is the new development version for "Commons JEXL"?
(org.apache.commons:commons-jexl) 2.1-SNAPSHOT: : 2.0-SNAPSHOT
The new pb is related to svn, the svn copy fails:
[INFO] Trace
org.apache.maven.BuildFailureException: Unable to tag SCM
Provider message:
The svn tag command failed.
Command output:
svn: No such revision 836226
With the following trace:
[INFO] Tagging release with the label JEXL_2_0_RC1...
[INFO] Executing: /bin/sh -c cd
/Users/henri/Java/apache-commons/rc1/commons/jexl-2.0 && svn
--non-interactive copy --file
/var/folders/Ya/YaSJZzgsHu4O4NXovx-nNE+++TI/-Tmp-/maven-scm-1545582656.commit
--revision 836226
https://svn.apache.org/repos/asf/commons/proper/jexl/tags/JEXL_2_0_RC1
https://svn.apache.org/repos/asf/commons/proper/jexl/tags/JEXL_2_0_RC1
The source & destination of the svn copy are the same...
I suspect the pom.xml should carry somewhere the 'trunk' information; may be
the <scm> should mention the trunk rather than RC1 ?
Hints welcome.
Henrib
--
View this message in context: http://old.nabble.com/Help-cutting-JEXL-2.0-RC1-needed-tp26339499p26351941.html
Sent from the Commons - Dev mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: Help cutting JEXL-2.0 RC1 needed
Posted by Henrib <hb...@gmail.com>.
Good info; will try that.
Thanks
Rahul Akolkar wrote:
>
>
> Perhaps a hint is that the error message seems similar to the one at
> the end of this page (scroll all the way down, see first message in
> "Trouble Shooting"):
>
> http://maven.apache.org/developers/release/apache-release.html
> ...
>
--
View this message in context: http://old.nabble.com/Help-cutting-JEXL-2.0-RC1-needed-tp26339499p26345087.html
Sent from the Commons - Dev mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: Help cutting JEXL-2.0 RC1 needed
Posted by Rahul Akolkar <ra...@gmail.com>.
On Fri, Nov 13, 2009 at 11:38 AM, Henrib <hb...@gmail.com> wrote:
>
> I'm stuck trying to create an RC1 for JEXL-2.0.
> I've followed each step of the procedure described at
> http://wiki.apache.org/commons/CreatingReleases .
>
> When performing the mvn -prc release:prepare , it gets stuck on [gpg:sign
> {execution: sign-artifacts}] with commons-parent version 12; with
> commons-parent version 11, it gets further but stops at:
> [ERROR] BUILD FAILURE
> ...
> svn: Commit failed (details follow):
> svn: File
> '/repos/asf/commons/proper/jexl/tags/JEXL_2_0_RC1/src/main/assembly/src.xml'
> already exists
>
> Any hint/advice/help ?
<snip/>
Perhaps a hint is that the error message seems similar to the one at
the end of this page (scroll all the way down, see first message in
"Trouble Shooting"):
http://maven.apache.org/developers/release/apache-release.html
Not everyone at Commons uses the exact same release recipe. At some
point, we'll need to align the Commons m2 release procedure to the
above (yes, a pain point has been that its been a moving target and as
one would therefore expect, its moved again :-).
-Rahul
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org