Diffusion¶

Current state¶

Capsis is not really distributed.¶

• A demo version can be downloaded on the website. This version is not up to date and cannot be extended. It contains only free modules.
• Modelers have access to the SVN and all the modules
• Users depends on modelers. Modelers distributes a partial copy of capsis. Users cannot update their version on their own.

Capsis distribution model¶

• Capsis is based on a centralized approach. All the modelers work on the same SVN repository and thus share their source code.

Some solutions¶

• Models are packaged in Jars. Thus a user can get a particular jar of a model and put it in his system.

• It may lead to version and dependency problems
• Model need particular extension which are packaged with the kernel

• Capsis is lauched from Java web start ensuring that the user get the latest version.

• User doesn't control model version.

• Capsis is distributed via SVN and an authentifcation / rights management

• User have a restricted access to the SVN repository (depending of their privileges)
• Nothing guaranty that the user download a functional version
• Version of several modules are not synchronized
• User must recompile capsis and thus download the JDK (intead of using standard jre)

• Capsis is distributed in a zip file or in a standalone installer

• Use IzPack and ant to create installer (ant installer -Dmodules=mymodule/**)
• Modeler publish the release on redmine
• Modeler can create a subproject to restrict and control file access
• User download package on redmine and install it on its computer