Page History

...

• Examples of existing implementations of such features: Confluence, Hudson, ...
• We could(should) also evaluate OSGi, although my feeling is that it is very complex and bulky, and will incur more cost than bring benefits. Somehow I hope I'm wrong.
• We might also want to evaluate how to re-use the Maven infrastructure. This might be particularly interesting since our builds already deploy to Maven repositories, we might not have to invent much as far as getting new modules goes ! The current effort is going into "Mercury", which as far as I understand, will be a foundation block for Maven 3:
  • http://svn.magnolia-cms.com/svn/internal/testing-mercury/
  • http://www.sonatype.com/people/2008/11/what-is-mercury/
  • http://maven.apache.org/mercury/index.html
  • http://docs.codehaus.org/display/MAVEN/Mercury
  • http://docs.codehaus.org/display/MAVEN/HowTo+use+Mercury+for+accessing+repositories
  • http://repo2.maven.org/maven2/org/apache/maven/mercury/ (1.0-alpha-5 is available at the time of writing)
  • http://svn.eu.apache.org/viewvc/maven/mercury/trunk/

GUI

We'll want to display decent module descriptions etc, maybe even screenshots. This implies we might need to add some features to the module descriptor.