Robin, Tim,

IMO, It really seems to me that the test environment is only used in dspace-api. For 3.0 if we can move it there it would be best, we can address providing it to other modules as a future issue.


On Thu, Oct 25, 2012 at 11:13 AM, Tim Donohue <> wrote:

I actually wonder if this is caused by the fact that Unit Tests are
enabled by default in [dspace-src]/pom.xml?

This idea of including the "testEnvironment.xml" in the "binary release"
seems odd/wrong to me, as I'm not sure why you'd ever want to run Unit
Tests on a binary release (or whether you even could successfully).

However, I do think we should disable Unit Tests by default again (as
they were disabled in 1.8.x). Doing so may help the errors you're seeing
(but, then again, I could be wrong).

- Tim

On 10/25/2012 9:20 AM, Robin Taylor wrote:
> I've created a pull request to fix the issue with the binary release in
> line with Tim's suggested fix #2 (see Jira). It works ok following the
> existing instructions of building the binary release by running 'mvn
> package' from [dspace-release]/dspace, however given that the binary
> distro would now include the parent pom one level up at [dspace-release]
> it would be nice to be able to build from there as we can do with the
> dspace-src-release. Unfortunately when I tried running 'mvn package' at
> the top level I got the following error...
> ------------------------------------------------------------------------
> [INFO] Building DSpace Parent Project
> [INFO]    task-segment: [package]
> [INFO]
> ------------------------------------------------------------------------
> [INFO] [enforcer:enforce {execution: enforce-maven}]
> [INFO] [assembly:single {execution: default}]
> [INFO] Reading assembly descriptor: src/main/assembly/testEnvironment.xml
> [INFO]
> ------------------------------------------------------------------------
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Error reading assemblies: Error locating assembly descriptor:
> src/main/assembly/testEnvironment.xml
> Blindly I then copied src/main/assembly/testEnvironment.xml and
> src/main/filters/ into the binary release and
> the build then worked from the top level. I suspect we could just
> include these two files in the binary release to give us source and
> binary releases which had the same structure and shared the same build
> instructions, but I'm not too familiar with the test environment so I
> would appreciate any input.
> Cheers, Robin.

Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
Dspace-release mailing list

@mire Inc. 
Mark Diggory (Schedule a Meeting)
2888 Loker Avenue East, Suite 315, Carlsbad, CA. 92010
Esperantolaan 4, Heverlee 3001, Belgium