I like this idea. Which version of felix are you thinking of using? I changed the README to say felix 3.2.2 since we know that works (and 4.0 doesn't), so if we use a different version then the README should be updated.
And to be honest, this is pretty much what I've been doing for a while now. Download felix, uncompress, checkout the felix directory from our tree overtop. Keeps the config files up to date :) G On 12-03-19 11:02 AM, Tobias Wunden wrote: > As of today, when doing a checkout of Matterhorn, the first step for > developers is to download a specific version of Felix and then build the > Matterhorn sources, adding a -DdeployTo switch to make sure the Matterhorn > artifacts end up in the correct place. > > Even though Matterhorn is intended to work with *any* OSGi container, I > propose to integrate a suitable version of Felix into the source tree such > that: > > a) there is a start script that will - after building Matterhorn - start > Matterhorn without the need to install Felix, copy configuraiton files around > etc. > > b) building Matterhorn without the -DdeployTo switch will result in the > artifacts deployed into the integrated Felix directory structure. > > The old way of deploying will still be working, it will just be much easier > to get started from scratch. > > Tobias > _______________________________________________ > Matterhorn mailing list > [email protected] > http://lists.opencastproject.org/mailman/listinfo/matterhorn > > > To unsubscribe please email > [email protected] > _______________________________________________
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Matterhorn mailing list [email protected] http://lists.opencastproject.org/mailman/listinfo/matterhorn To unsubscribe please email [email protected] _______________________________________________
