I've written a simple distribution workflow step and gotten it working
but I have a question about how other people manage their custom code.
1) In order for the workflow conductor to see my distribution service,
I added its OSGi definition to
matterhorn-conductor/src/main/resources/OSGI-INF/operations/ and added a
reference to this file in the felix bundle part of
matterhorn-conductor's pom file. I don't really want to maintain a
local copy of matterhorn-conductor nor do I want to have to remember to
make these changes before building/deploying matterhorn-conductor. Is
there any better way to handle this?
2) I want to keep my custom modules outside of the matterhorn source
and not need the matterhorn source in order to build it. I've tried
adding the repositories mentioned in base's pom file, but the opencast
maven repository appears to be really outdated for snapshots. It only
has 1.1-SNAPSHOT and nothing newer than that. I will probably work from
released versions but would like to have my CI server run builds that
test the snapshots to see if my module ever becomes incompatible with
trunk. Are there any plans for updating snapshots? Do releases get
pushed to the maven repo in a reliable time frame? Anything else I
should be aware of when attempting this approach?
Any help would be appreciated.
Thanks,
Chris Colvard
Variations on Video
Indiana University
_______________________________________________
Matterhorn-users mailing list
[email protected]
http://lists.opencastproject.org/mailman/listinfo/matterhorn-users
