Tobias,
On 3/12/12 3:30 AM, Tobias Wunden wrote:
Hi,
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?
Not that I know of, but awhile back a few of us were poking around mvn
overlays. The idea is that basically you have an untouched MH mvn repo
and the overlays get copied over from your other local repo at build
time. Never followed up more on this as I left it to our operations
group, who (I believe) just maintains a branch similar to what you're
doing.
There is really no need to stick new workflow operations into the conductor
bundle, they may as well live in their own bundle, e.g
matterhorn-comductor-myinstitution.
I like this idea but I don't understand what you mean by their own
bundle. Would this be a replacement for matterhorn-conductor or live
alongside it? What would the new bundle include in it? Thanks for
helping me to understand this better.
-Chris Colvard
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?
Releases get pushed immediately when the are approved, it's the last
step. Each release candidate gets pushed too. Snapshots don't get
pushed at all to my knowledge - this would require an svn hook to push
a snapshot to mvn everytime a change was made. I don't think anyone
would be against this, just that no one has had time to set this up.
I agree that our build server should be pushing snapshots to the maven
repository. I'll take care of this soon.
Tobias
_______________________________________________
Matterhorn-users mailing list
[email protected]
http://lists.opencastproject.org/mailman/listinfo/matterhorn-users
_______________________________________________
Matterhorn-users mailing list
[email protected]
http://lists.opencastproject.org/mailman/listinfo/matterhorn-users
