And, to come back to the first issue, when changing a pom you should also wipe out the opencast branch in your maven repository to see if everything builds.
Christoph Am 08.10.2011 um 05:28 schrieb Greg Logan: > Hi folks, > > I noticed this when I did a full rebuild of trunk to do some merging: > All of the OAIPMH integration tests fail. This is caused by the fix for > MH-8214: the module was incorrectly included in the admin profile, but > removing it from the admin profile removes it from the build completely. > If you are running the integration tests and see those tests (and those > tests alone!) fail then don't worry. If you are not seeing them fail > then you likely have that bundle built and in felix already. > > Since this does not break the functionality of trunk I'm not going to > revert the change, but I'm surprised that no one aside from me has > noticed this. I see a lot of commits in svn, but not a whole lot of > complaining. Perhaps a new rule: If you change a pom file you must > rebuild everything from scratch after wiping your $FELIX_HOME/matterhorn > directory. That way we don't run into this kind of situation again. > > G > > _______________________________________________ > Matterhorn mailing list > [email protected] > http://lists.opencastproject.org/mailman/listinfo/matterhorn > > > To unsubscribe please email > [email protected] > _______________________________________________ _______________________________________________ Matterhorn mailing list [email protected] http://lists.opencastproject.org/mailman/listinfo/matterhorn To unsubscribe please email [email protected] _______________________________________________
