On Thu, 13 Nov 2008, Benjamin Bentmann wrote:
David wrote:
Could we proceed with a 1.0 release baesd on the latest
1.0-alpha-3-SNAPSHOT.
0, not using it.
The parameter generatedSourcesDirectory is @required while
generatedResourcesDirectory is not, although both mojos treat them the same,
i.e. don't support null values for them. I would assume that either both are
@required or none are (considering that they have defaults, i.e. the plugin
works without the user specifying them explicitly, i.e. setting them is
optional)
Hmm, yes they have default values - so the user doesn't have to do
anything - and should usually be happy with the default ones - but I need
*some* value. What is best practice?
There's an undeclared dependency on maven-model.
Oup - must have been to eager when I was removing excessive ones.
Note I ran mvn docck:check and got:
[ERROR] There are no example files in your site directory (in
apt|html|xml[.vm] format). They should either be called
'example*.(apt|html|xml)[.vm]' or they should be located in the 'examples'
directory.
I'm a fan of (sensible) conventions but there is really no point in strictly
adhering to something if it just doesn't fit. When there are simply no
interesting examples to give, that's not an error condition. I'm always
amused by plugin sites with a FAQ that merely says "Question - Answer"
because an automated tool told to do so... So, you shouldn't be worried too
much about this "[ERROR]" ;-)
Yes exactly - that's why I'm pointing out that it's "not docck ok"
accoring to the guidelines - but also no value in adding it.
As always, thank you for your input.
Dave
--
David J. M. Karlsen - +47 90 68 22 43
http://www.davidkarlsen.com
http://mp3.davidkarlsen.com
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
