Looks pretty good. One minor change and a few questions. @Martin: Any comments on this before we go ahead? (We will keep your resource structure for now and try to find a solution for that later.)
> The next try: > > core (org.apache.myfaces) > [This has a own release cycle] > ==== > myfaces/core/trunk/pom.xml > myfaces/core/trunk/myfaces-api/pom.xml > myfaces/core/trunk/myfaces-impl/pom.xml > myfaces/core/trunk/assembly/pom.xml > > <modules> > <module>myfaces-api</module> > <module>myfaces-impl</module> > <module>assembly</module> > <modules> > > > commons (org.apache.myfaces) > [This has a own release cycle] > ======= > myfaces/commons/trunk/pom.xml > myfaces/commons/trunk/src/main > myfaces/commons/trunk/src/test > myfaces/commons/trunk/src/site > [myfaces/commons/assembly/pom.xml] > NOTE: own assembly not really needed > if released as part of the assembly of core and tomahawk OK. Now I understand why you skipped assembly for this one. > > tomahawk & sandbox > (org.apache.myfaces.tomahawk or org.apache.myfaces) > [This has a own release cycle] > [Sandbox is not released only in nightly build] > ======= > myfaces/tomahawk/trunk/pom.xml > myfaces/tomahawk/trunk/src/main > myfaces/tomahawk/trunk/src/test > myfaces/tomahawk/trunk/src/site > myfaces/tomahawk/trunk/example/pom.xml > myfaces/tomahawk/trunk/sandbox/pom.xml > myfaces/tomahawk/trunk/sandbox/src/main > myfaces/tomahawk/trunk/sandbox/src/test > myfaces/tomahawk/trunk/sandbox/src/site > myfaces/tomahawk/trunk/assembly/pom.xml > > NOTE: If tomahawk has a different groupid the pom is not inherited > Maybe we can start which the same groupid, if it make sense we can > change it in a future version. (The tomahawk pom is to different) One more change ... myfaces/tomahawk/trunk/sandbox/example <-- add this Sandbox examples will depend on sandbox components and the sandbox.jar. So they should probably be broken out separately. > tools (org.apache.myfaces) > [no assembly but release on a maven repository] > ===== > myfaces/tools/trunk/pom.xml > myfaces/tools/trunk/maven-myfaces-plugin/pom.xml > myfaces/tools/trunk/build-tools(checkstyleandpmdconfiguration)/pom.xm > > NOTE: The maven-myfaces-plugin is an archtype-plugin for maven currently > in the test repository. Oh yes Bruno's archtype plugin. Yes that should go there. > site (org.apache.myfaces) > [never released only for publishing the main site and the content of the > main site] > ===== > myfaces/site/trunk/pom.xml > NOTE: The main site can be part of core It could be part of core but I think your initial idea (as its own top level) is better. The site is for everything (not just core.) > > Process for updateing the site and publishing the nightly build and the > snapshots: > This is done by spezial task from the continuum server or by some > scripts invoked on the myfaces.zone.apache.org server? I was thinking chron script on the zone. > The idea is: We call some maven goals on some poms. > mvn site:deploy in the site trunk for the main site > mvn site:deploy in the core, commons and tomahawk trunk Sounds good. The one thing is that I would like links in the top level site for the module sites (and also in the reverse direction.) Do we just add those manually to the nav contents of each of the sites? Is there a way to do this in Maven? > mvn deploy:deploy on all trunks for the shapshots And this will make the snapshots available to our own projects as well as those of our users right? Sounds good. > mvn assembly:assembly for the nightly build on core and tomahawk Right. And maybe also for the official release? > NOTE: I don't expect one spezial pom for this. I guess you're right. There isn't anything in Maven that will pull it all together for you. > TODO find a better name for assembly We can try ;-) Build is already taken. Maybe publish? > TODO setup solaris zone Its been setup. Nothing has been done with it yet. Once we get the builds working that will be the next step. > TODO setup continuum > TODO define a snapshot repository > TODO define the process for updating the site and nightly buid Yes. This looks great Bernd. I like what we are settling on. > > Best Regards > > Bernd > Sean
