The next round
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
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/sandbox/example/pom.xml
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 makes sense we can
change it in a future version. (When the tomahawk pom is to different)
tools (org.apache.myfaces)
[no assembly but release on a maven repository]
=====
myfaces/tools/trunk/pom.xml
myfaces/tools/trunk/myfaces-archetype-plugin/pom.xml
myfaces/tools/trunk/build-tools(checkstyleandpmdconfiguration)/pom.xm
NOTE: The myfaces-archetype-plugin is an archetype-plugin for maven
currently in the test repository.
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 but the site is for everything
not just for core
Process for updating the site and publishing the nightly builds and the
snapshots:
=======
This is done by special task from the continuum server or by some
chron scripts invoked on the myfaces.zone.apache.org server?
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
NOTE: The links between the the top level site and the subprojects are
added manually in the site.xml. The svn version of the site plugin is
reactor aware(Then not all links between the subprojects must defined).
mvn deploy:deploy on all trunks for deploying all artifacts to the
snapshot repository
mvn assembly:assembly for the nightly build on core and tomahawk
NOTE: A release need some more steps, but maven has a plugin for this
and a best practice.
TODO find a better name for assembly (dist|build|bin)?
TODO use the myfaces solaris zone for publish the site, nightly build,
continuum..
TODO setup continuum
TODO define a snapshot repository
TODO define the process for updating the site and nightly build
Best Regards
Bernd
