Posted by gouessej on Sep 19, 2011; 10:02am
URL: https://forum.jogamp.org/New-Deployment-FHS-Filesystem-Hierarchy-Standard-tp3334675p3348147.html

Hi!

It is important to keep atomic JARs and to modularize the APIs which compose JogAmp because:
- Java Web Start on Oracle JVM (not on OpenJDK) does not show the details of downloaded JARs. The progress bar is not updated during a download, the user can think that the installation has failed. If you use smaller JARs, the progress bar is updated more often which gives a better feedback
- some high level APIs and engines will not use some components of JOGL, for example the new text API. They should not have to use the biggest JAR
- the most direct competitor of JogAmp claims to be lightweight. If the APIs of Jogamp become bigger, some people might have the feeling that they have to download too much things or useless things, that is why a proper modularization is important for deployment too.