----- Original Message ----- From: "bob mcwhirter" <[EMAIL PROTECTED]> To: "Turbine Maven Developers List" <[EMAIL PROTECTED]> Sent: Friday, July 05, 2002 7:42 AM Subject: Re: [idea] extending the maven command...
<snip> > I'd just like to avoid adding anything for a specific plugin/goal to > the general maven framework. If we can make all of this part of a > plugin, that'd be my goal. > Yep, I have the same concern. Binding a commandline option for a plugin without specifyng the plugin is a bad idea. The two phase idea Bob has seems like a good approach that is already being used in other software. Gets my vote. Also I'd like to see a way similar to ant's -find option to dig down and find a maven.xml or project.xml if present in parent dirs. Although I never liked the -find option explicitly, it should be implied. So I'm in a project subdir of src/java and that dir has a maven.xml. I type maven compile --include *.foopackage maven would be smart enough to use the maven.xml in the src/java dir and the project.xml in ../.. and compile all sources under the foopackage This allows me to break out java source specific pre/post goals and such in a maven.xml in the src/java dir. The fact you can't type 'maven' unless you are in a dir with a project.xml has caught me a few times. -Peter > -bob > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
