Hi Developers, For those who subscribe to our 'dspace-change...@lists.sourceforge.net' listserv, you've surely noticed that all recent Trunk commits have thrown errors from Bamboo, as it attempts to build & test the latest code.
I've been trying to track down the exact cause of these errors, but honestly could use a fresh pair of eyes. So, I thought I'd write to describe what I've figured it out so far. (1) First off, this is a real error (it's not Bamboo being finicky, or a problem with a Bamboo agent). Something in our recent commits has actually broken a *portion* of our Maven build processes. Although most Maven build commands work fine (e.g. 'mvn clean package'), our DSpace build process can no longer successfully do both a *package* and a *unit test*. For example, the following will fail with errors: mvn package test -Dmaven.test.skip=false (Note the '-Dmaven.test.skip=false' is only necessary to ensure the tests are actually run -- since we decided to disable our unit tests by default. If tests were enabled by default, then 'mvn package test' would throw the same error) The error that is returned is the same one reported by recent Bamboo builds, for example: https://bamboo.duraspace.org/browse/DST-TRUNK-212 (2) Oddly enough, just doing 'mvn package' or just doing 'mvn test -Dmaven.test.skip=false' both work fine. It's the *combination* of packaging & unit testing that is failing. (3) As you can see from the reported Bamboo error (see the 'full build log' in the linked Bamboo report above), the failure seems to be that the 'dspace-discovery-xmlui-webapp' project fails to build as it cannot seem to copy over the necessary 'dspace-xmlui-api' dependency. Obviously, this all works fine if you just do a normal 'mvn package' -- it's only problematic when you do both a package and unit test. So, it seems that something is essentially 'locking' the 'dspace-xmlui-api' from being accessed -- possibly something in the unit testing. (4) As best as I can tell, this problem first started occurring around the time that we reworked all our pom.xml files to use the common 'dspace-pom' parent. So, it may be the result of some odd inheritance between pom.xml files, again possibly around the unit testing configs. Here's the commits where this issue seemed to have first begun: https://fisheye3.atlassian.com/changelog/dspace?cs=5796 https://fisheye3.atlassian.com/changelog/dspace?cs=5797 If anyone has any ideas, I'd be willing to entertain suggestions (I'll be on IRC most all day). In the meantime, I'll keep digging around in our pom.xml files to see if I can discover the root cause here. - Tim -- Tim Donohue Technical Lead for DSpace Project DuraSpace.org ------------------------------------------------------------------------------ Centralized Desktop Delivery: Dell and VMware Reference Architecture Simplifying enterprise desktop deployment and management using Dell EqualLogic storage and VMware View: A highly scalable, end-to-end client virtualization framework. Read more! http://p.sf.net/sfu/dell-eql-dev2dev _______________________________________________ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
