No problem.
--
James Mitchell
678.910.8017
On Dec 27, 2006, at 12:35 PM, Adam Koch wrote:
Sorry I just replied to an automated email before I saw this. I'll
go ahead and subscribe.
Thanks,
Adam
On 12/27/06, Mitchell James [EMAIL PROTECTED] wrote:
Well, first things first, you need
On 12/26/06, Rahul Akolkar [EMAIL PROTECTED] wrote:
On 12/26/06, Rahul Akolkar [EMAIL PROTECTED] wrote:
snip/
Back on track, will sign the pom, and will ask this list to verify it
before copying over. (BTW, is there a way to get m2 to sign?)
snap/
Done, I've added my signature to the
On 12/27/06, Wendy Smoak [EMAIL PROTECTED] wrote:
On 12/27/06, Craig McClanahan [EMAIL PROTECTED] wrote:
The md5 and sha1 checksums are fine. When I try to verify the signature,
though:
gpg --verify shale-master-2.pom.asc shale-master-2.pom
I get the Can't check signature: public
On 12/27/06, Rahul Akolkar [EMAIL PROTECTED] wrote:
On 12/27/06, Craig McClanahan [EMAIL PROTECTED] wrote:
snip/
Done, I've added my signature to the master pom v2 in the staging
repo. My key is here [1] amongst other places (I intend to add a
generic UID before 1.0.4).
Please
On 12/27/06, Craig McClanahan [EMAIL PROTECTED] wrote:
snip/
Yep ... that worked. I got the good signature and untrusted messages.
snap/
OK, so we're good to go on the master pom. Thanks.
I should have mentioned also what Wendy said ... we should follow the best
practice of maintaining
On 12/27/06, Wendy Smoak [EMAIL PROTECTED] wrote:
On 12/27/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
Author: craigmcc
Date: Wed Dec 27 14:33:45 2006
New Revision: 490580
URL: http://svn.apache.org/viewvc?view=revrev=490580
Log:
Add Dutch translations for the validator messages.
On 12/27/06, Craig McClanahan [EMAIL PROTECTED] wrote:
On 12/27/06, Wendy Smoak [EMAIL PROTECTED] wrote:
On 12/27/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
Author: craigmcc
Date: Wed Dec 27 14:33:45 2006
New Revision: 490580
URL: http://svn.apache.org/viewvc?view=revrev=490580
Few thoughts:
1) Why is the dependencies section in the parent pom commented out?
Tempted to remove it.
2) We probably want to move designtime into a profile (can wait post 1.0.4).
3) There is some other cruft in the parent and remoting poms that I
intend to remove.
Objections to 1 or 3?
Branching tomorrow. Please speak up now if you want more time.
-Rahul
On 12/27/06, Craig McClanahan [EMAIL PROTECTED] wrote:
On 12/27/06, Rahul Akolkar [EMAIL PROTECTED] wrote:
snip/
2) We probably want to move designtime into a profile (can wait post 1.0.4).
It should probably go back into the sandbox at the moment ... it's on my
list to work on in 2007,
On 12/27/06, Rahul Akolkar [EMAIL PROTECTED] wrote:
On 12/27/06, Craig McClanahan [EMAIL PROTECTED] wrote:
On 12/27/06, Rahul Akolkar [EMAIL PROTECTED] wrote:
snip/
2) We probably want to move designtime into a profile (can wait post
1.0.4).
It should probably go back into the sandbox
The permissions for the KEYS file [1] seem botched after being
restored from backup. Guess we'll need to ping #asfinfra ? (I'm never
on it though, anyone? TIA).
-Rahul
[1] http://www.apache.org/dist/shale/KEYS
For thread closure, this has been taken care of (thanks Craig).
-Rahul
On 12/28/06, Rahul Akolkar [EMAIL PROTECTED] wrote:
The permissions for the KEYS file [1] seem botched after being
restored from backup. Guess we'll need to ping #asfinfra ? (I'm never
on it though, anyone? TIA).
-Rahul
On 12/27/06, Rahul Akolkar [EMAIL PROTECTED] wrote:
For thread closure, this has been taken care of (thanks Craig).
Just in case someone else runs into something like this, here's the way I
worked around the issue without having to involve the infra folks. The
basic issue was that the KEYS
14 matches
Mail list logo
