A few questions to the MyFaces maven gurus: (Sorry if some of these questions already have been asked or discussed - I did what I could to search in my mail archives for the right answers ;-)
Q1. Regarding the maven sub-project: Why do build-tools and master-pom have no parent relationship to the maven-project pom? Q2. What exactly is the build-tools module for? Checkstyle is not used yet, right? Q3. Why does the site pom have no parent relationship to the myfaces-master pom? Seems to contain lots of redundant information which could be derived from master pom. Q4. What is commons/src/site? Is this zombie code? Q5. The module name "wagon-maven-plugin" is a bit confusing IMHO. Should't we call it "myfaces-maven-wagon-plugin" or something like that to point out that this is no standard or codehaus sandbox plugin? Q6. Why do assembly sub-modules exist? Is there any issue that prevents us from adding the assembly configuration into the modules pom itself? Q7. AFAIK the scm config is not needed within sub-modules. Maven calculates the right SVN URLs. So, any objections against removing scm config from core/api, core/impl, tomahawk/core etc. ? What I currently try to achieve is a simple way to deploy a snapshot or release version to a corporate maven repository. Therefore I'm exploring simple ways to make the distributionManagement config overwritable by the user. Not really difficult with profile properties. Will check that in soon. Maven rocks and I want to thank all of you guys that helped to mavenize MyFaces. However, the current numer of POMs in MyFaces is slaying me. So we should try to simplify things in some places I think. I will try to help out where I can. Manfred
