> The argument for parent refs is to define many things at one place. > The version is not really the reason, because it is defined in the > parent ref. > Without parent refs you have to define the > <issueManagement> > <ciManagement> > <developers> > <reports> > .... > in every pom.
Ok then we definitely want the parent ref! I thought that those were inherited when you used <module>. I didn't realize you had to specify that you were the child of a particular POM. Does this mean that if you build the child, it asks the parent to build? If so, then that is interesting (not a problem - just unexpected.) > A legitimate question: > Is the core pom a parent of the tomahawk pom, this depends on the > differences of the poms. If tomahawk has a different groupId it can't be > a child of core. I would say tomahawk and core are independent of one another. Actually all of the "top" level POMS would be independent of one another. So you would have 3 separate group ids. org.apache.myfaces.core org.apache.myfaces.tomahawk org.apache.myfaces.commons What is the significance of the group id? I know that your repository will have one folder for each but what else does it mean? Underneath the group id folder is the version right? If each of these 3 can have their own release cycle then I think we *must* have 3 group ids right? > > commons > > ======= > > myfaces/commons/trunk > > I think commons should have a parent ref to myfaces. What do you mean by this? > TODO find a better name for assembly +1 > > maven-tools > > ========= > > > > custom maven plugins, etc. > > Not only maven tools. I would suggest myfaces-tools or myfaces-build-tools? What else goes in here besides plugins? > I think the experimental stuff should only released as a nighly build. I'm ok with your suggestion but a while back there seemed to be support for including it in tomahawk. I can't remember the arguments off the top of my head. I will do an archive search ... > and tobago is released :-) Of course, we shouldn't forget tobago ;-) Its good to have you guys on board. Your Maven experience is already coming in handy. [snip] > A continuum server updates automatically the myfaces snapshot repository. > If an other developer perform an update of tomahawk, the next call of > mvn fetch the new snapshot of commons into his local repository from the > myfaces snapshot repository. > > TODO setup continuum > TODO define the snapshot repository OK I think I see what you mean. We can come back to your suggestion later when we get the SVN stuff done. I was interested in continuum before this explanation but now I am *very* interested. Bill Dudney has also expressed interest and now that we have our zone we can do this! First things first though. Lets get *re*organized and get the POMs the way we want them. Thanks for your excellent ideas ... Sean Sean
