Besides the multi-module doc, my experience wishes for the POM entry descriptions - some are too vague. More detail (what is it for/why would you use it, how to use it), examples, valid values, etc. would help a lot.
I think the project descriptor has big potential as a solid reference vehicle, with the added info. I would value that more than many of the "guides". For a simple example, the <packaging> element doesn't describe valid values, so a search begins to learn them. Viewing the schema doesn't help, as the packaging type is "string". Additionally, I think the phrase "type of artifact" is not intuitive to newbies, so listing the valid values would bring contextual explanation, as well as their definition. HTH, and thanks for asking. -----Original Message----- From: Jason van Zyl [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 08, 2005 9:10 AM To: Maven Users List Subject: RE: [m2] Guide to creating archetypes [snip] Anything in particular that's missing from the guides or introductory material? Also check the JIRA components for documentation as I know there are guides like the multi-project guide that are in demand and it's noted in JIRA. You can also vote on issues which lets us know what you guys want most which lets us focus our time better on writing what's most desired. [snip] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
