There are three primary things: SDO, DAS and SCA. For each of those
there are different artifacts we are releasing:
* the source distro (zip and tgz)
* the binary distro (zip and tgz)
* the maven artifacts that will loaded into the m2-incubator-
repository (jar and pom for each)
The first
Any other votes on this?
--
Jeremy
On Oct 2, 2006, at 8:28 AM, Jeremy Boynes wrote:
The parent pom and buildtools are pre-reqs for all other Java
projects in the M2 release. These are distributed through the maven
repo rather than as a end-user distribution. Please vote to approve
the
+1 from me.
Thanks,
Raymond
- Original Message -
From: Jeremy Boynes [EMAIL PROTECTED]
To: tuscany-dev@ws.apache.org
Sent: Thursday, October 05, 2006 4:39 PM
Subject: Re: [VOTE] Release parent pom and buildtools for M2
Any other votes on this?
--
Jeremy
On Oct 2, 2006, at 8:28 AM
+1 from me.
On 10/5/06, Raymond Feng [EMAIL PROTECTED] wrote:
+1 from me.
Thanks,
Raymond
- Original Message -
From: Jeremy Boynes [EMAIL PROTECTED]
To: tuscany-dev@ws.apache.org
Sent: Thursday, October 05, 2006 4:39 PM
Subject: Re: [VOTE] Release parent pom and buildtools for M2
Subject: Re: [VOTE] Release parent pom and buildtools for M2
Any other votes on this?
--
Jeremy
On Oct 2, 2006, at 8:28 AM, Jeremy Boynes wrote:
The parent pom and buildtools are pre-reqs for all other Java
projects in the M2 release. These are distributed through the maven
+1
Jeremy Boynes wrote:
The parent pom and buildtools are pre-reqs for all other Java
projects in the M2 release. These are distributed through the maven
repo rather than as a end-user distribution. Please vote to approve
the release content:
parent-pom
[tag]
I'd like to vote on this, and have spent 15 mins perusing all the files. I
saw that you have addressed Dan's point on signatures. To be honest I don't
have sufficient experience in this area to make criticism. I wonder if
there are others feeling the same way, and hence the slowness on this
I agree with Kelvin (although I'd prefer the extra detail to be on the
mailing list not IRC). Also, I'm not sure I understand the big picture of
this M2 release or why we would vote on this bit now, I guess I thought
there would be a single vote for the final thing we were releasing, not lots
of
+1 to what Kelvin has mentioned. I would also like to know more about what
has gone into this..
Thanks
- Venkat
On 10/4/06, ant elder [EMAIL PROTECTED] wrote:
I agree with Kelvin (although I'd prefer the extra detail to be on the
mailing list not IRC). Also, I'm not sure I understand the
I just tried it and the stuff does verify with your public key from the public
keyrings. You should get someone to sign your key eventually (next week
at ApacheCon, we should all sign each others keys). For those without keys
(like myself), it's probably a good idea to create ones ahead
On Wednesday October 04 2006 12:02 pm, Daniel Kulp wrote:
I just tried it and the stuff does verify with your public key from the
public keyrings. You should get someone to sign your key eventually
(next week at ApacheCon, we should all sign each others keys). For those
without keys
Jeremy,
I have to give it a -1 right now.
Lately, the incubator PMC's have been requiring ALL artifacts to be properly
digitally signed, including those going into the maven repository. Thus, you
need to sign all the stuff you put up there and then add a KEYS file or
similar into svn with
+1 from me.
Jim
On Oct 2, 2006, at 8:28 AM, Jeremy Boynes wrote:
The parent pom and buildtools are pre-reqs for all other Java
projects in the M2 release. These are distributed through the maven
repo rather than as a end-user distribution. Please vote to approve
the release content:
The parent pom and buildtools are pre-reqs for all other Java
projects in the M2 release. These are distributed through the maven
repo rather than as a end-user distribution. Please vote to approve
the release content:
parent-pom
[tag]
14 matches
Mail list logo