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,
I note that the build seems to start in [DSpace-source] rather than
[DSpace-source]/dspace. Strange things happen when doing that. I've
never worked out why. It definitely makes the Reactor build in a
different order.
--
Mark H. Wood, Lead System Programmer mw...@iupui.edu
Balance your
Hi Mark W,
Unfortunately, your suggestion to change directories doesn't seem to
matter. Locally, on my own machine, I can achieve the same error
messages whether I run this command from [dspace-source] or
[dspace-source]/dspace/
mvn package test -Dmaven.test.skip=false
So, I don't think
On 11/11/2010 2:07 PM, Mark Diggory wrote:
I'm researching if I can get the artifact properly registered in the
maven reactor. Alternatives are...
1.) move the dspace-ui-share dependencies out of dspace-jspui-webapp
and dspace-xmlui-webapp and only build at [dspace-source] with
-Paddons
On Thu, Nov 11, 2010 at 12:06 PM, Tim Donohue tdono...@duraspace.org wrote:
Hi Mark W,
Unfortunately, your suggestion to change directories doesn't seem to
matter. Locally, on my own machine, I can achieve the same error
messages whether I run this command from [dspace-source] or
