Below are some notes I took after installing DSpace 1.7.0 on Windows 7 using
Maven 3.0.2:
1. Use mvn install instead of mvn package. Note, mvn install will download a
whole bucketload of stuff, you need to have a good internet connection.
2. Also, incase of any issues, do mvn -eX install > log.txt
Mark,
Excellent, thanks so much for the confirmation here. It wasn't a significant
issue in that 2.2.1 worked fine, but I wanted to make sure that I wasn't
missing anything for my tutorials / guides.
Cheers
- Patrick E.
On Mon, Mar 7, 2011 at 3:16 PM, Mark Diggory wrote:
> Patrick,
>
> this
Patrick,
this is a known issue with Maven 3, we are working on some project
restructuring in DSpace trunk to alleviate this, for now, if you can build
with the latest version of maven 2, that would be recommended. I think you
can choose the maven installation in the m2eclipse plugin so you are not
Elliot (et al),
Many thanks for the reply. You might have to say that I am both using and
not using Eclipse, though the part where I am may be interfering with the
part where I am not. I'm attempting to setup both a local development
environment through Eclipse as well as a non-Eclipse (command-li
Hi Patrick,
Are you using Eclipse? I was getting very similar errors when I didn’t have my
projects set up correctly. I never had any trouble using Maven 3.02 via command
line. With a bit of searching I found out it looks like the Maven option to
“Enable Nested Modules” isn’t supported in the l
DSpace Techies and Devs -
I wanted to see whether anyone had had success setting up DSpace 1.7.0 using
Maven 3.0.2. I ask because I'm attempting to put together a guide / tutorial
/ how-to for establishing a solid and streamlined workflow for maintaining
multiple development and production dspace
6 matches
Mail list logo
