Hello, so far I'm happily using maven to buil our fairly complex j2ee application and now I trying to move forward and configure maven to perform release & build and deploy site hand by hand.
I didn't found much documentation about those topics, so I was looking for some best practices. I did checkout of myfaces tobago and orchestra from svn and looked out how they do the things, but only to see same shortcomings I've already met. At the and I'm expecting to have cvs tagged release ears inside our local repository and release site somewhere. I can easily do mvn release:prepare perfectly, but I can't correctly build multimodule site. Even with mvn site:stage I've allways ended with separated sites in different staging dirs with broken links. So my questions are 1. What are benefits and shotcomings of having separated "project pom" (in parent directory of submodules) and "parent pom" (in subdirectory named parent or maven). Maven-archetype-j2ee-simple archetype uses common project&parent and same case in Maven definitive guide (http://www.sonatype.com/book/) I've found unpleasant censequences of this and every project I've looked at does not use this. 2. Is it better to have parent pom associated with parent site and use project pom only to agregate modules? Or inverse? 3. Why are my modules and project sites after mvn site:stage in separated dirs with broken links beetween them? 4. What is correct sequence of commands to perform release with site correctly built? 5(optional:) Why build from svn dump site build so hugely differs from what can be found at http://myfaces.apache.org/tobago/index.html Thanks for any hints and advices, Martin Vanek --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
