You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by "Mark R. Diggory" <md...@latte.harvard.edu> on 2003/07/14 04:07:26 UTC
Undocumented properties (was: Re: Keeping your test source code ...)
Sorry, I made it sound like I was poking holes in the project in that
last thread, while in reality, I really appreciate Maven as a tool and
use it regularly.
I want to clarify that I understand that there are project.xml elements
that can be set ( unitTestSourceDirectory,
integrationUnitTestSourceDirectory, ...). And, these elements as well as
all the plug properties are well documented. I didn't want to make it
seem that there was a "lack of documentation" for Maven, there certainly
is alot of documentation going around.
My primary question is if there are undocumented properties that can be
set in project.properties or used in maven.xml that are not actually
defined by the plugins, but actually by the base architecture of Maven
itself? Like for instance properties used by werkz plugin or maven
plugin base?
This actually flows back to an earlier discussion about documentation
and the werkz plugin.
http://www.mail-archive.com/users@maven.apache.org/msg00751.html
thanks,
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Undocumented properties
Posted by di...@multitask.com.au.
Maybe someone could integrate this into the Maven user's guide.
--
dIon Gillard, Multitask Consulting
Blog: http://blogs.codehaus.org/people/dion/
Work: http://www.multitask.com.au
Ben Walding <be...@walding.com> wrote on 15/07/2003 12:35:12 AM:
>
> >>This actually flows back to an earlier discussion about documentation
> >>and the werkz plugin.
> >>
> >>
> >
> >I post some quicky docs to the list regarding Werkz and Ben challenged
> >the user to make an xdoc of it. It's in the archive if you want to
> >document it.
> >
> >
> >
> >>http://www.mail-archive.com/users@maven.apache.org/msg00751.html
> >>
> >>
>
> Surprisingly, they rose to the challenge!
>
> http://wiki.codehaus.org/maven/WerkzTagDocumentation
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
Re: Undocumented properties
Posted by Ben Walding <be...@walding.com>.
>>This actually flows back to an earlier discussion about documentation
>>and the werkz plugin.
>>
>>
>
>I post some quicky docs to the list regarding Werkz and Ben challenged
>the user to make an xdoc of it. It's in the archive if you want to
>document it.
>
>
>
>>http://www.mail-archive.com/users@maven.apache.org/msg00751.html
>>
>>
Surprisingly, they rose to the challenge!
http://wiki.codehaus.org/maven/WerkzTagDocumentation
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Undocumented properties (was: Re: Keeping your test source
code ...)
Posted by Jason van Zyl <ja...@zenplex.com>.
On Sun, 2003-07-13 at 22:07, Mark R. Diggory wrote:
> Sorry, I made it sound like I was poking holes in the project in that
> last thread, while in reality, I really appreciate Maven as a tool and
> use it regularly.
Fear not, I have a very, very thick skin :-)
> I want to clarify that I understand that there are project.xml elements
> that can be set ( unitTestSourceDirectory,
> integrationUnitTestSourceDirectory, ...). And, these elements as well as
> all the plug properties are well documented. I didn't want to make it
> seem that there was a "lack of documentation" for Maven, there certainly
> is alot of documentation going around.
The documentation is still lacking and that is for the most part my
doing. I do much of it in bursts when I get the time.
> My primary question is if there are undocumented properties that can be
> set in project.properties or used in maven.xml that are not actually
> defined by the plugins, but actually by the base architecture of Maven
> itself? Like for instance properties used by werkz plugin or maven
> plugin base?
Most of the base properties are in driver/default.properties. Some of
those actually belong in their respective plugins which I have done in
the refactoring I have which will be shoved into CVS soon.
> This actually flows back to an earlier discussion about documentation
> and the werkz plugin.
I post some quicky docs to the list regarding Werkz and Ben challenged
the user to make an xdoc of it. It's in the archive if you want to
document it.
> http://www.mail-archive.com/users@maven.apache.org/msg00751.html
>
> thanks,
> Mark
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
--
jvz.
Jason van Zyl
jason@zenplex.com
http://tambora.zenplex.org
In short, man creates for himself a new religion of a rational
and technical order to justify his work and to be justified in it.
-- Jacques Ellul, The Technological Society
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org