Re: svn commit: r430653 - /jakarta/jakarta-build/trunk/pom.xml

2006-08-11 Thread Henri Yandell
On Fri, 11 Aug 2006, Dennis Lundberg wrote: Phil Steitz wrote: Thanks, Dennis. That helps and I agree with your arguments for inheritence in genera;. But why a Jakarta parent? I'll leave that one for Henri to answer. Do I look like I know what I'm doing? :) The Jakarta pom is there be

Re: Opening up the PMC

2006-08-11 Thread Martin van den Bemt
Torsten Curdt wrote: But if you argue into that direction -no matter how often this has been discussed already- I would rather question the idea of an umbrella PMC then... (*ducks*) Time and energy to express the ideas you have in that direction ? Mvgr, Martin -

Re: svn commit: r430653 - /jakarta/jakarta-build/trunk/pom.xml

2006-08-11 Thread Dennis Lundberg
Phil Steitz wrote: Thanks, Dennis. That helps and I agree with your arguments for inheritence in genera;. But why a Jakarta parent? I'll leave that one for Henri to answer. And can you answer the second question about addressing? I am -0 on doing anything that cements "Jakarta" into the

RE: svn commit: r430653 - /jakarta/jakarta-build/trunk/pom.xml

2006-08-11 Thread Phil Steitz
Thanks, Dennis. That helps and I agree with your arguments for inheritence in genera;. But why a Jakarta parent? And can you answer the second question about addressing? I am -0 on doing anything that cements "Jakarta" into the namespace above commons artifacts. Sorry if this has been disc

Re: svn commit: r430653 - /jakarta/jakarta-build/trunk/pom.xml

2006-08-11 Thread Dennis Lundberg
Phil Steitz wrote: Henri Yandell wrote: First few commit messages bounced on this btw, until I fixed that up. It's a maven2 Hen, Can you enlighten the rest of us as to what this is for and what, if any, implications it has on how we address maven2 artifacts originating in jakarta projects? Ph

Re: svn commit: r430653 - /jakarta/jakarta-build/trunk/pom.xml

2006-08-11 Thread Phil Steitz
Henri Yandell wrote: > > First few commit messages bounced on this btw, until I fixed that up. > It's a maven2 Hen, Can you enlighten the rest of us as to what this is for and what, if any, implications it has on how we address maven2 artifacts originating in jakarta projects? Phil > parent pom f