Re: What is the correct ?! - WAS Re: [VOTE] Release commons-exec-1.0.0 based on EXEC_1_0_0_RC2 did not pass ....

2009-01-04 Thread Brett Porter
On 29/12/2008, at 1:08 PM, Ralph Goers wrote: In short: 1. New projects should use org.apache.commons Yep, that's why I started commons-exec with o.a.commons as the group. I think it would be best to use that given the opportunity since there are no prior releases under commons-exec. Ch

Re: What is the correct ?! - WAS Re: [VOTE] Release commons-exec-1.0.0 based on EXEC_1_0_0_RC2 did not pass ....

2008-12-30 Thread Rahul Akolkar
On Sun, Dec 28, 2008 at 9:08 PM, Ralph Goers wrote: > The "correct" groupId with respect to what Maven recommends should be > org.apache.commons. However, if a groupId is changed and the package names > are not changed at the same time it will cause nothing but grief for users > of the project.

Re: [VOTE] Release commons-exec-1.0.0 based on EXEC_1_0_0_RC2 did not pass ....

2008-12-30 Thread Rahul Akolkar
On Sun, Dec 28, 2008 at 9:27 AM, Dennis Lundberg wrote: > Rahul Akolkar wrote: >> IMO ... >> >> On Sat, Dec 27, 2008 at 12:21 PM, Siegfried Goeschl >> wrote: >>> Hi folks, >>> >>> after more than one week I have to announce that the vote DID NOT PASS ... >>> >>> +) two +1 votes (Jörg, Sebastian)

Re: What is the correct ?! - WAS Re: [VOTE] Release commons-exec-1.0.0 based on EXEC_1_0_0_RC2 did not pass ....

2008-12-28 Thread Ralph Goers
The "correct" groupId with respect to what Maven recommends should be org.apache.commons. However, if a groupId is changed and the package names are not changed at the same time it will cause nothing but grief for users of the project. This is because to maven commons- exec:commons-exec:1.

What is the correct ?! - WAS Re: [VOTE] Release commons-exec-1.0.0 based on EXEC_1_0_0_RC2 did not pass ....

2008-12-28 Thread Siegfried Goeschl
Hi folks, can we get an agreement on that and put it into the wiki? If using "org.apache.commons.*" makes life easier I'm happy to use it but we should have a common understanding first ... Cheers, Siegfried Goeschl "As Thomas Hobbes observed in the 17th century, life under mob rule is solita

Re: [VOTE] Release commons-exec-1.0.0 based on EXEC_1_0_0_RC2 did not pass ....

2008-12-28 Thread Dennis Lundberg
Rahul Akolkar wrote: > IMO ... > > On Sat, Dec 27, 2008 at 12:21 PM, Siegfried Goeschl > wrote: >> Hi folks, >> >> after more than one week I have to announce that the vote DID NOT PASS ... >> >> +) two +1 votes (Jörg, Sebastian) >> +) two positive comments (Rahul, Oliver) which formally do not >

Re: [VOTE] Release commons-exec-1.0.0 based on EXEC_1_0_0_RC2 did not pass ....

2008-12-27 Thread Rahul Akolkar
IMO ... On Sat, Dec 27, 2008 at 12:21 PM, Siegfried Goeschl wrote: > Hi folks, > > after more than one week I have to announce that the vote DID NOT PASS ... > > +) two +1 votes (Jörg, Sebastian) > +) two positive comments (Rahul, Oliver) which formally do not > constitute a +1 > > Having said th

[VOTE] Release commons-exec-1.0.0 based on EXEC_1_0_0_RC2 did not pass ....

2008-12-27 Thread Siegfried Goeschl
Hi folks, after more than one week I have to announce that the vote DID NOT PASS ... +) two +1 votes (Jörg, Sebastian) +) two positive comments (Rahul, Oliver) which formally do not constitute a +1 Having said that a couple of issues were raised ... 1) [major] what is the correct groupId - "org

Re: [VOTE] Release commons-exec-1.0.0 based on EXEC_1_0_0_RC2

2008-12-22 Thread Rahul Akolkar
On Wed, Dec 17, 2008 at 4:17 PM, Rahul Akolkar wrote: > On Wed, Dec 17, 2008 at 4:12 PM, Oliver Heger > wrote: >> All looks good except for the folder name used in the source distribution: >> "commons-exec-2.4.1-src". I think this is caused by a Maven bug, I've seen >> this before... >> > > > Ha

Re: [VOTE] Release commons-exec-1.0.0 based on EXEC_1_0_0_RC2

2008-12-21 Thread sebb
On 16/12/2008, Siegfried Goeschl wrote: > Hi folks, > > after struggling with my and Maven's shortcomings (and wasting a release > candidate) it is time to call a vote to release commons-exec-1.0.0 > > Tag: > > https://svn.apache.org/repos/asf/commons/proper/exec/tags/EXEC_1_0_0_RC2 > Trivial

Re: [VOTE] Release commons-exec-1.0.0 based on EXEC_1_0_0_RC2

2008-12-20 Thread Jörg Schaible
Hi Sierfried, Siegfried Goeschl wrote: > Hi folks, > > after struggling with my and Maven's shortcomings (and wasting a release > candidate) it is time to call a vote to release commons-exec-1.0.0 > > Tag: > > https://svn.apache.org/repos/asf/commons/proper/exec/tags/EXEC_1_0_0_RC2 > > Site:

Re: [VOTE] Release commons-exec-1.0.0 based on EXEC_1_0_0_RC2

2008-12-17 Thread Rahul Akolkar
On Wed, Dec 17, 2008 at 5:09 PM, Siegfried Goeschl wrote: > Hi Rahul, > > +) I will double-check since I have also seen the problem before > +) would make a nice addition to the commons wiki > On item 2, absolutely, I think its atleast the 3rd RC bitten by this. TIA for wiki update. -Rahul >

Re: [VOTE] Release commons-exec-1.0.0 based on EXEC_1_0_0_RC2

2008-12-17 Thread Siegfried Goeschl
Hi Rahul, +) I will double-check since I have also seen the problem before +) would make a nice addition to the commons wiki Cheers, Siegfried Goeschl Rahul Akolkar wrote: > On Wed, Dec 17, 2008 at 4:12 PM, Oliver Heger > wrote: > >> All looks good except for the folder name used in the sou

Re: [VOTE] Release commons-exec-1.0.0 based on EXEC_1_0_0_RC2

2008-12-17 Thread Siegfried Goeschl
Good point - I will add that tomorrow ... Cheers, Siegfried Goeschl Oliver Heger wrote: > All looks good except for the folder name used in the source > distribution: "commons-exec-2.4.1-src". I think this is caused by a > Maven bug, I've seen this before... > > Another point is that I was not a

Re: [VOTE] Release commons-exec-1.0.0 based on EXEC_1_0_0_RC2

2008-12-17 Thread Rahul Akolkar
On Wed, Dec 17, 2008 at 4:12 PM, Oliver Heger wrote: > All looks good except for the folder name used in the source distribution: > "commons-exec-2.4.1-src". I think this is caused by a Maven bug, I've seen > this before... > Hardcoding version # in assembly source descriptor is perhaps the best

Re: [VOTE] Release commons-exec-1.0.0 based on EXEC_1_0_0_RC2

2008-12-17 Thread Oliver Heger
All looks good except for the folder name used in the source distribution: "commons-exec-2.4.1-src". I think this is caused by a Maven bug, I've seen this before... Another point is that I was not able to find your public key for verifying the signatures. It does not seem to be in KEYS [1].

Re: [VOTE] Release commons-exec-1.0.0 based on EXEC_1_0_0_RC2

2008-12-16 Thread Rahul Akolkar
Mostly OT with respect to vote, but might be useful for others to know in this context ... On Tue, Dec 16, 2008 at 6:40 PM, Siegfried Goeschl wrote: > Hi folks, > > after struggling with my and Maven's shortcomings (and wasting a release > candidate) it is time to call a vote to release commons-e

[VOTE] Release commons-exec-1.0.0 based on EXEC_1_0_0_RC2

2008-12-16 Thread Siegfried Goeschl
Hi folks, after struggling with my and Maven's shortcomings (and wasting a release candidate) it is time to call a vote to release commons-exec-1.0.0 Tag: https://svn.apache.org/repos/asf/commons/proper/exec/tags/EXEC_1_0_0_RC2 Site: http://people.apache.org/builds/commons/exec/1.0.0/RC2/site/