+1! On Wed, 2002-05-22 at 14:36, Vincent Massol wrote: > Hi, > > What do you think about removing unnecessary build comments from Maven > build files. After all, if I use Maven it is because I don't want to > care how it generates the stuff. They would only appear in VERBOSE or > DEBUG modes. > > For example : > > project-properties: > Trying to override old definition of task project-properties > Creating classpath reference ... > Creating dependency.set ... > Creating source set reference ... > Adding Reference maven.src.set with a value of > E:\Vma\Projets\Encours\ICOM\Icom\development\iceberg\ > src\core > Creating aspect source set reference ... > Adding Reference maven.src.aspect.set with a value of > [project-properties] mpsd => null > Adding Reference maven.compile.src.set with a value of > E:\Vma\Projets\Encours\ICOM\Icom\development\ > iceberg\src\core > Creating unit test class entries reference ... > Trying to override old definition of task update-properties > Checking for old properties ... > > Will actually generate the following in normal mode (i.e . not verbose > nor debug) : > > project-properties: > > > What do you think ? If we agree I can submit a patch for this (using the > "level" attribute of the echo task would be nice but it is only > supported in Ant 1.5 I think and I guess we want to support previous > versions). What we can do is include the Ant 1.5 echo task in the Maven > source tree and use it with a taskdef. > > Shall I go ahead ? > Thanks > > -Vincent > > > -- > 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]>
