Hi Dennis, Your email below was exactly what I needed. It also makes me ask this question "how do users know to look at the archiver plugin options for the packaging-type plugins?". E.g. my recent escapade into making a war (converting an M1 build to M2) - I was in the middle of trying to determine how to use an existing manifest file vs having Maven generate one when I read your below email. There are a number of nice examples of manifest file manipulation in the war plugin docs, but nothing on using a file. Same is true for the "Guide to Working with Manifests" page. So I visited the archiver docs, and there was my answer!
Nothing I found on the war plugin's docs leads the user to look at the archiver info (and with a quick glance at the EAR one I did not see anything on other packaging plugins; my guess is I will have similar questions on the EAR plugin). Assuming all of these packaging plugins use archiver (could be a wrong assumption!), I am thinking we should add to each of the packaging plugins a simple sentence or two stating to also refer to the Archiver docs for further configuration examples and a link to it. Otherwise, it takes "preexisting knowledge" to know to look there. WDYT? Additionally, the archiver plugin is not listed on the http://maven.apache.org/plugins/ page. This also leads me to wonder if different doc page(s) exist for a plugin list. I think probably not, and this is just a "doc maintenance issue", which hints to auto-generating a plugin list page with description and link to its page. That's a different issue of course! :-) <generalThought>Besides these specifics on archiver, the <configuration> element options per plugin seem a little bit elusive - we rely on examples on the plugin doc page, which I think the existing ones are good, just incomplete at times [cite above case]. Not knowing what would be the answer other than something like the M1 properties list pages (properties could still get overlooked, of course). One thing I miss with the <configuration> elements that we have with most of the POM is what XML schema provides for IDE smart completion.</generalThought> -----Original Message----- From: Dennis Lundberg [mailto:[EMAIL PROTECTED] Sent: Sunday, February 24, 2008 4:44 AM To: Maven Users List Subject: Re: manifest problem Please help Did you try following the documentation to the letter: http://maven.apache.org/shared/maven-archiver/examples/manifestFile.html http://maven.apache.org/shared/maven-archiver/examples/manifestEntries.html http://maven.apache.org/shared/maven-archiver/examples/classpath.html --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
