Re: svn commit: r430653 - /jakarta/jakarta-build/trunk/pom.xml
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 because it seemed like a good idea to share things between Jakarta m2 projects and not just Commons ones - or at least to try and encourage that sharing. Though I had thought that the mailing lists in the parent would appear in the children and that's not happened. It didn't seem like it would be damaging to represent the current structure and Brett didn't run screaming when I asked him :) I'm not tied to it though - just throwing energy at the commons to m2 problems. Hen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Opening up the PMC
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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: svn commit: r430653 - /jakarta/jakarta-build/trunk/pom.xml
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 namespace above commons artifacts. Sorry if this has been discussed and agreed and I just missed it. As it is currently done the namespace for commons artifacts is and will be org.apache.commons, so there's no jakarta in there. The pom for commons does have a parent which is currently the jakarta pom. If Jakarta would be dissolved, that could easily be changed to something else, say the ASF pom. Phil From: Dennis Lundberg [mailto:[EMAIL PROTECTED] Sent: Fri 8/11/2006 9:36 AM To: Jakarta General List Subject: Re: svn commit: r430653 - /jakarta/jakarta-build/trunk/pom.xml 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? Phil The purpose of having a parent pom is to reduce the amount of information you need to put in the pom of a specific project. It also makes sure that all projects us the *same* information for certain things. These things are put in the parent. An example of this is which plugins *all* projects must use. Each project can then add more plugins if they so desire. Now I know some of you are preparing to throw in arguments about how we tried to do this with Maven 1 and it failed. Before you do there is one crucial difference. In Maven 1 the parent had to reside somewhere within the same file system as your project. In Maven 2 the parent pom is published to a Maven repository. It is then downloaded like any other artifact by Maven automatically. So there will be no need to check out jakarta-build from svn and putting it in the exact correct location on your own machine. -- Dennis Lundberg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Dennis Lundberg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: svn commit: r430653 - /jakarta/jakarta-build/trunk/pom.xml
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 discussed and agreed and I just missed it. Phil From: Dennis Lundberg [mailto:[EMAIL PROTECTED] Sent: Fri 8/11/2006 9:36 AM To: Jakarta General List Subject: Re: svn commit: r430653 - /jakarta/jakarta-build/trunk/pom.xml 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? > > Phil The purpose of having a parent pom is to reduce the amount of information you need to put in the pom of a specific project. It also makes sure that all projects us the *same* information for certain things. These things are put in the parent. An example of this is which plugins *all* projects must use. Each project can then add more plugins if they so desire. Now I know some of you are preparing to throw in arguments about how we tried to do this with Maven 1 and it failed. Before you do there is one crucial difference. In Maven 1 the parent had to reside somewhere within the same file system as your project. In Maven 2 the parent pom is published to a Maven repository. It is then downloaded like any other artifact by Maven automatically. So there will be no need to check out jakarta-build from svn and putting it in the exact correct location on your own machine. -- Dennis Lundberg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: svn commit: r430653 - /jakarta/jakarta-build/trunk/pom.xml
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? Phil The purpose of having a parent pom is to reduce the amount of information you need to put in the pom of a specific project. It also makes sure that all projects us the *same* information for certain things. These things are put in the parent. An example of this is which plugins *all* projects must use. Each project can then add more plugins if they so desire. Now I know some of you are preparing to throw in arguments about how we tried to do this with Maven 1 and it failed. Before you do there is one crucial difference. In Maven 1 the parent had to reside somewhere within the same file system as your project. In Maven 2 the parent pom is published to a Maven repository. It is then downloaded like any other artifact by Maven automatically. So there will be no need to check out jakarta-build from svn and putting it in the exact correct location on your own machine. -- Dennis Lundberg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: svn commit: r430653 - /jakarta/jakarta-build/trunk/pom.xml
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 for Jakarta projects. Created under advice from Brett on > #maven :) > > Hen > > On Fri, 11 Aug 2006 [EMAIL PROTECTED] wrote: > >> Author: bayard >> Date: Thu Aug 10 21:03:21 2006 >> New Revision: 430653 >> >> URL: http://svn.apache.org/viewvc?rev=430653&view=rev >> Log: >> not released yet, so giving it a dev version of 1-SNAPSHOT >> >> Modified: >>jakarta/jakarta-build/trunk/pom.xml >> >> Modified: jakarta/jakarta-build/trunk/pom.xml >> URL: >> http://svn.apache.org/viewvc/jakarta/jakarta-build/trunk/pom.xml?rev=430653&r1=430652&r2=430653&view=diff >> >> == >> >> --- jakarta/jakarta-build/trunk/pom.xml (original) >> +++ jakarta/jakarta-build/trunk/pom.xml Thu Aug 10 21:03:21 2006 >> @@ -10,7 +10,7 @@ >> jakarta-parent >> pom >> >> - 1 >> + 1-SNAPSHOT >> Apache Jakarta >> http://jakarta.apache.org/ >> 1999 >> >> >> >> - >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
