Re: [m2 config] was: Re: svn commit: r430653 - /jakarta/jakarta-build/trunk/pom.xml
On 8/27/06, Phil Steitz <[EMAIL PROTECTED]> wrote: Dennis Lundberg wrote: I don't think so. After I had deployed the pom, Maven wanted to deploy *all* of the sandbox components. At this point I simply canceled the rest of the deploy. By the way, there is a technique to avoid this problem .. "mvn -N deploy" will only deploy the POM in the directory you're executing the command from, while "mvn deploy" does that POM and all its modules. Craig Thanks again, Dennis. Let's take this to commons-dev now. Sorry, all, about all the noise. Phil >> Still in learning mode here... >> >> Phil > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[m2 config] was: Re: svn commit: r430653 - /jakarta/jakarta-build/trunk/pom.xml
Dennis Lundberg wrote: I don't think so. After I had deployed the pom, Maven wanted to deploy *all* of the sandbox components. At this point I simply canceled the rest of the deploy. Thanks again, Dennis. Let's take this to commons-dev now. Sorry, all, about all the noise. Phil >> Still in learning mode here... >> >> Phil > > - 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: Dennis Lundberg wrote: Phil Steitz wrote: Henri Yandell wrote: 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. Can someone less m2-newbie than me pls publish the jakarta and commons parents to the m2-snapshot-repo? The sandbox parent appears to be there, but the others are not and they have to be manually installed to get any commons m2 builds to work. That makes it pretty hard for the non-initiate to build the components (e.g. [pipeline]) that are dropping m1 poms. Done. I have deployed the poms jakarta, commons and commons-sandbox. Thanks, Dennis! Now I am confused, though, since we seem to have both commons-sandbox and commons-sandbox-parent and the sanbox m2 builds seem to be evenly split between them, though all (other than pipeline) are listed as modules of commons-sandbox. Are these for different purposes? commons-sandbox-parent was set up by Brett when he introduced the Maven 2 build in the sandbox. commons-sandbox was set up by Henri as part of the Jakarta Maven 2 setup. So I guess we should be moving from commons-sandbox-parent to commons-sandbox. Perhaps Henri can comment on this. Also, do we really want to have the individual components set up as modules? I don't think so. After I had deployed the pom, Maven wanted to deploy *all* of the sandbox components. At this point I simply canceled the rest of the deploy. Still in learning mode here... Phil -- 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
Dennis Lundberg wrote: > Phil Steitz wrote: >> Henri Yandell wrote: >>> >>> 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. >> Can someone less m2-newbie than me pls publish the jakarta and commons >> parents to the m2-snapshot-repo? The sandbox parent appears to be >> there, but the others are not and they have to be manually installed to >> get any commons m2 builds to work. That makes it pretty hard for the >> non-initiate to build the components (e.g. [pipeline]) that are dropping >> m1 poms. > > Done. > I have deployed the poms jakarta, commons and commons-sandbox. > Thanks, Dennis! Now I am confused, though, since we seem to have both commons-sandbox and commons-sandbox-parent and the sanbox m2 builds seem to be evenly split between them, though all (other than pipeline) are listed as modules of commons-sandbox. Are these for different purposes? Also, do we really want to have the individual components set up as modules? Still in learning mode here... Phil - 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: 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. Can someone less m2-newbie than me pls publish the jakarta and commons parents to the m2-snapshot-repo? The sandbox parent appears to be there, but the others are not and they have to be manually installed to get any commons m2 builds to work. That makes it pretty hard for the non-initiate to build the components (e.g. [pipeline]) that are dropping m1 poms. Done. I have deployed the poms jakarta, commons and commons-sandbox. -- Dennis Lundberg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
svn commit: r437442 - /jakarta/jakarta-build/trunk/pom.xml
Author: dennisl Date: Sun Aug 27 12:41:36 2006 New Revision: 437442 URL: http://svn.apache.org/viewvc?rev=437442&view=rev Log: Remove duplicate maven-pmd-plugin. 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=437442&r1=437441&r2=437442&view=diff == --- jakarta/jakarta-build/trunk/pom.xml (original) +++ jakarta/jakarta-build/trunk/pom.xml Sun Aug 27 12:41:36 2006 @@ -90,10 +90,6 @@ org.apache.maven.plugins -maven-pmd-plugin - - -org.apache.maven.plugins maven-checkstyle-plugin config/sun_checks.xml - 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: > > > 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. Can someone less m2-newbie than me pls publish the jakarta and commons parents to the m2-snapshot-repo? The sandbox parent appears to be there, but the others are not and they have to be manually installed to get any commons m2 builds to work. That makes it pretty hard for the non-initiate to build the components (e.g. [pipeline]) that are dropping m1 poms. Thanks! Phil > > Hen > > - > 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]
