I've updated the wiki page with the current status of all Commons Proper
sites (and some of the sandbox sites). See:
http://nagoya.apache.org/wiki/apachewiki.cgi? CreatingStandardWebPresence
The main thing that struck me, when putting this together, is the number
of components that have both Maven and non-Maven sites. In all such cases,
the non-Maven site is the one linked to from the main Commons page. The
components in this state are:
BeanUtils Collections Digester Discovery Jexl Lang Logging Modeler
Is there any reason why we should not switch over to the Maven sites as the main sites right now, and "deprecate" the non-Maven versions?
-1
for most of these components, the existing sites are the primary maintained versions. the mavenized sites are secondary versions which have been posted up but are not actively maintained by the committers responsible for these components. it's important that the current websites for these components are not replaced by outdated and possible inaccurate information.
all components need to be given the chance to update their maven builds and transfer their existing content before the existing sites are removed. (i think that mandating maven as the build system for all components is quite a big change. i've often had to run custom patched versions of maven and i'd prefer to wait until a proper 1.0 release before we force everyone to use it.)
there are also some features that many of these web sites use that are not (easily) available through maven. in particular, maven javadocs are created from head whereas the javadocs for the latest release are made available at the moment. time is needed to resolve issues like this.
- robert
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
