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 it's a problem with Bamboo (or how Bamboo is setup to 
run).  I think it's a problem with our Maven pom.xml files -- as I can 
achieve the same errors even without using Bamboo.

 From what I've been able to tell searching around online, it's possible 
Maven is getting confused about dependency management.  Digging into our 
pom.xml files, we have a ton of repetition between POMs -- where a child 
POM overwrites dependencies/settings with the same values as their 
parent POM.

I've done some cleaning of the Discovery POMs locally (which seem to be 
the messiest and most repetitive -- likely cause it used to be a totally 
separate module).  I *believe* I just succeeded in fixing the error 
reported in the building & testing of 'dspace-discovery-xmlui-webapp'. 
Unfortunately, now I'm getting the *exact same* error in the building & 
testing of 'dspace-xmlui-webapp' (again, based on 'dspace-xmlui-api' 
being unable to be copied properly).  So, this may not be a single 
problem caused by a single POM -- it may be a problem of how several of 
our POMs are currently interacting (especially those that depend on 
'dspace-xmlui-api').

After some more testing, I will commit some of my initial cleanup.  Even 
if it doesn't fix the entire problem yet, it seems to be getting closer 
to some sort of resolution.

Essentially, I believe our POMs need some overhaul -- we aren't taking 
advantage of inheritance in many places, and it seems like it may be 
confusing Maven to some extent.  The smaller we can make most of the 
POMs the better.

- Tim

On 11/11/2010 1:49 PM, Mark H. Wood wrote:
> 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.
>
>
>
>
> ------------------------------------------------------------------------------
> 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

------------------------------------------------------------------------------
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

Reply via email to