Hi, how is the fulcrum site be prepared to get it up to date again ( http://turbine.apache.org/fulcrum/ ) ?
This has be done probably the last time from the trunk. I think, if we update now the site the released components get the Javadocs from the current trunk. Is this ok? A tagged version should then be generated for the entire fulcrum tree (?). Some more updates seem to the necessary (xdocs7navigation.xml, pom.xml...). I have some more concerns to do this right now: 1) Dependencies: Building the site fails due to the fact, that a lot of fulcrum (cache, bsf, commonsmail, crypto) components depend on fulcrum-parent v1 (current version is v2-SNAPSHOT). Changing the version to v2-SNAPSHOT the site build seems to execute successfully. But the parent fulcrum-parent v2-SNAPSHOT depends on turbine-parent v2 not the current turbine-parent v3. Do we not need another fulcrum-parent, which does depend on turbine-parent version 3? 2) Labeling: In the current fulcrum site there is no section for non released components or components in development. Shouldn´t be the dormant components renamed to components in development? This could include old "dormant" and new not released components. Best regards, Georg --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@turbine.apache.org For additional commands, e-mail: dev-h...@turbine.apache.org
