Infrastructure

The current architecture documentation and javadocs that are published on mule1 only represent the HEAD/Trunk of development, and not the released versions of APIs and software. MN developers and ITK developers that want their software to work with current and prior versioned releases have no place to view this documentation. This story encompasses creating:

1) build systems that automate the production of architecture and javadocs for each released version using hudson
2) a standard URL for released versions of documentation
-- I suggest that released versions of documentation should be published to https://releases.dataone.org in the appropriate subdirectories (an online browsable version in 'online')

For example, for the R client release documentation, we have published:

@https://releases.dataone.org
/dist/dataone_1.0.0-manual.pdf
/online/dataone_r/index.html (overview page for product, with browsable links to documentation for current and prior released versions)
@

I think we should do something similar for libclient, common, architecture, etc. Need to add individual tasks to this story for completing this for each of our products.