betwixt 0.5 release jars
the new betwixt 0.5 is ready and will be announced soon. i've uploaded the jar (together with signature and md5) to my home directory on minotaur (http://www.apache.org/~rdonkin/commons-betwixt/). it'd probably be best if one of the repo team copied them into the repository but i'd be willing to execute this myself if some instructions were be provided. TIA - robert
RE: betwixt 0.5 release jars
Title: RE: betwixt 0.5 release jars Hi Robert, Do you build the final release with Maven or Ant? If it is Maven, the commons build would need to be changed to automate this, but it's pretty easy. Change: /www/jakarta.apache.org/builds/jakarta-commons To: www.apache.org /www/www.apache.org/dist/java-repository/ In /commons-build/project.xml (This is my understanding of the current place for releases of JARs to all be published to - correct me if I'm wrong) Then from the betwixt checkout of 0.5, run "maven jar:deploy" Cheers, Brett > -Original Message- > From: robert burrell donkin [mailto:[EMAIL PROTECTED]] > Sent: Sunday, 27 June 2004 8:01 PM > To: [EMAIL PROTECTED] > Subject: betwixt 0.5 release jars > > > the new betwixt 0.5 is ready and will be announced soon. i've > uploaded > the jar (together with signature and md5) to my home directory on > minotaur (http://www.apache.org/~rdonkin/commons-betwixt/). it'd > probably be best if one of the repo team copied them into the > repository but i'd be willing to execute this myself if some > instructions were be provided. > > TIA > > - robert >
Re: betwixt 0.5 release jars
On 27 Jun 2004, at 23:59, Brett Porter wrote: Hi Robert, hi brett Do you build the final release with Maven or Ant? maven If it is Maven, the commons build would need to be changed to automate this, but it's pretty easy. i have a feeling that henri looked into this before - it might even be working already (but see below). Change: /www/jakarta.apache.org/builds/jakarta- commons To: www.apache.org /www/www.apache.org/dist/java-repository/ In /commons-build/project.xml (This is my understanding of the current place for releases of JARs to all be published to - correct me if I'm wrong) i'm a little sensitive to the needs for supervision at the moment (after being strongly reminded on this list before by members who know about these issues). the jar's i've posted have been approved for release. i don't really want to have to run a second vote (again) for a release of different jars to the repo. i'm sure that once the process is better understood and documented we'll be able to move toward automation without too many people screaming. until then, i'd feel better if some member of the repo committee moved the stuff into place. - robert
RE: betwixt 0.5 release jars
Title: RE: betwixt 0.5 release jars > i'm a little sensitive to the needs for supervision at the moment > (after being strongly reminded on this list before by members > who know > about these issues). the jar's i've posted have been approved for > release. i don't really want to have to run a second vote > (again) for a > release of different jars to the repo. If you have a controlled environment and build from a clean checkout of a tag... There shouldn't be a problem? > i'm sure that once the process is better understood and documented > we'll be able to move toward automation without too many people > screaming. until then, i'd feel better if some member of the repo > committee moved the stuff into place. I think anyone who can commit to CVS can put a jar into /www/www.apache.org/dist/java-repository/commons-betwixt/jars, so you should be good to go. I'm just here out of interest - I'm not sure I form part of the "repo committee"? :) Cheers, Brett
Re: betwixt 0.5 release jars
Yes, pretty much the case. The big thing is to make sure you set group write permissions and make sure the group is apcvs. I can look into setting the deployment dir to be /www/www.apache.org/dist/java-repository/ but I remember requests from the mirror folks to make sure that deployment happened in a working/scratch directory and the copied into the dist this way the md5 checksum scipts that test the contents of dist wouldn't bark during the upload process. -Mark Brett Porter wrote: > i'm a little sensitive to the needs for supervision at the moment > (after being strongly reminded on this list before by members > who know > about these issues). the jar's i've posted have been approved for > release. i don't really want to have to run a second vote > (again) for a > release of different jars to the repo. If you have a controlled environment and build from a clean checkout of a tag... There shouldn't be a problem? > i'm sure that once the process is better understood and documented > we'll be able to move toward automation without too many people > screaming. until then, i'd feel better if some member of the repo > committee moved the stuff into place. I think anyone who can commit to CVS can put a jar into /www/www.apache.org/dist/java-repository/commons-betwixt/jars, so you should be good to go. I'm just here out of interest - I'm not sure I form part of the "repo committee"? :) Cheers, Brett begin:vcard fn:Mark Diggory n:Diggory;Mark org:Harvard University;Harvard MIT Data Center adr:Harvard University;;G-6 Littauer Center (North Yard);Cambridge;Ma;02138-2901;United States email;internet:[EMAIL PROTECTED] title:Software Engineer tel;work:617 496 7246 tel;fax:617 495 0438 tel;home:617 718 2033 tel;cell:617 285 4106 url:http://www.hmdc.harvard.edu version:2.1 end:vcard
RE: betwixt 0.5 release jars
Title: RE: betwixt 0.5 release jars Thanks for clarifying that Mark - makes sense. While Maven uploads directly, I make a habit of doing it on a machine with a fast connection so shouldn't have a problem with our releases, however this could still be a concern. Are there any filenames that the mirrors don't pick up (eg . Prefixed files) that we could use to upload as a temporary file then move to the correct location when done? I can build that into Maven's upload support, and would prefer it to using /tmp or user's home directories if possible. Thanks, Brett > -Original Message- > From: Mark R. Diggory [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, 30 June 2004 2:39 AM > To: [EMAIL PROTECTED] > Subject: Re: betwixt 0.5 release jars > > > Yes, pretty much the case. The big thing is to make sure you > set group > write permissions and make sure the group is apcvs. > I can look into setting the deployment dir to be > /www/www.apache.org/dist/java-repository/ but I remember > requests from > the mirror folks to make sure that deployment happened in a > working/scratch directory and the copied into the dist this > way the md5 > checksum scipts that test the contents of dist wouldn't bark > during the > upload process. > -Mark
RE: betwixt 0.5 release jars
Apologies for continually sending in HTML format BTW - Outlook at work insists on "deciding the best format" for me despite setting the email address to plain text only. I'll resubscribe from a different email address and use webmail :) - Brett -Original Message- From: Brett Porter Sent: Wednesday, 30 June 2004 8:51 AM To: '[EMAIL PROTECTED]' Subject: RE: betwixt 0.5 release jars Thanks for clarifying that Mark - makes sense. While Maven uploads directly, I make a habit of doing it on a machine with a fast connection so shouldn't have a problem with our releases, however this could still be a concern. Are there any filenames that the mirrors don't pick up (eg . Prefixed files) that we could use to upload as a temporary file then move to the correct location when done? I can build that into Maven's upload support, and would prefer it to using /tmp or user's home directories if possible. Thanks, Brett > -Original Message- > From: Mark R. Diggory [mailto:[EMAIL PROTECTED] > Sent: Wednesday, 30 June 2004 2:39 AM > To: [EMAIL PROTECTED] > Subject: Re: betwixt 0.5 release jars > > > Yes, pretty much the case. The big thing is to make sure you > set group > write permissions and make sure the group is apcvs. > I can look into setting the deployment dir to be > /www/www.apache.org/dist/java-repository/ but I remember > requests from > the mirror folks to make sure that deployment happened in a > working/scratch directory and the copied into the dist this > way the md5 > checksum scipts that test the contents of dist wouldn't bark > during the > upload process. > -Mark
Re: betwixt 0.5 release jars
Brett Porter wrote: Apologies for continually sending in HTML format BTW - Outlook at work insists on "deciding the best format" for me despite setting the email address to plain text only. I'll resubscribe from a different email address and use webmail :) I use Thunderbird and am very happy with it. MAybe you can use that for discussing in Opensource projects. Webmail is annoying to say the least for this (I sis the same thing once, from Outlook to webmail, etc ;-) -- Nicola Ken Barozzi [EMAIL PROTECTED] - verba volant, scripta manent - (discussions get forgotten, just code remains) -
Re: betwixt 0.5 release jars
I definitely use thunderbird from home... but I can't use it at work because I need the outlook calendar, etc. I'm certainly tempted though :) - Brett On Wed, 30 Jun 2004 08:52:42 +0200, Nicola Ken Barozzi <[EMAIL PROTECTED]> wrote: > > Brett Porter wrote: > > > Apologies for continually sending in HTML format BTW - Outlook at work > > insists on "deciding the best format" for me despite setting the email > > address to plain text only. I'll resubscribe from a different email address > > and use webmail :) > > I use Thunderbird and am very happy with it. MAybe you can use that for > discussing in Opensource projects. Webmail is annoying to say the least > for this (I sis the same thing once, from Outlook to webmail, etc ;-) > > -- > Nicola Ken Barozzi [EMAIL PROTECTED] > - verba volant, scripta manent - > (discussions get forgotten, just code remains) > - >
Re: betwixt 0.5 release jars
On 29 Jun 2004, at 00:08, Brett Porter wrote: > i'm a little sensitive to the needs for supervision at the moment > (after being strongly reminded on this list before by members > who know > about these issues). the jar's i've posted have been approved for > release. i don't really want to have to run a second vote > (again) for a > release of different jars to the repo. If you have a controlled environment and build from a clean checkout of a tag... There shouldn't be a problem? i thought that last time :) > i'm sure that once the process is better understood and documented > we'll be able to move toward automation without too many people > screaming. until then, i'd feel better if some member of the repo > committee moved the stuff into place. I think anyone who can commit to CVS can put a jar into /www/www.apache.org/dist/java-repository/commons-betwixt/jars, so you should be good to go. yep. i've taken care of betwixt manually but i'll probably use maven build next time. I'm just here out of interest - I'm not sure I form part of the "repo committee"? :) thanks for the reply. FWIW i'd say that you'd make a good addition to that committee. - robert
