How about we download the OSMF swc during the release build stage and
package it with the SDK artifact like we do other third party dependencies
like Batik, Velocity and Xerces?

Pros:
* Since we resolve this dependency during build time, end users don't get
affected by Sourceforge downtimes
* If Sourceforge is down when we make the build, we just get the dependency
from our previous good build.  OSMF has not changed for a while
* Our Installer already has a way to force users to accept the license for
OSMF.  So very little change required to the Installer.

Cons (?):
* OSMF would have to be made a 'required' component instead of 'optional'.
Since it is a small, single file, I don't think this is quite a problem.
* Installer needs to be reworked a bit, to eliminate the optional OSMF
download path.  Should not be a major change.

What do folks think of this proposal?

Thanks,
Om

Reply via email to