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 later versions of m2eclipse. So
I set up one project per DSpace module and it all seemed to work. The m2eclipse
dependency management then was able to correctly identify the modules as
separate Java projects. I hope this helps (obviously not if you’re not using
eclipse).
Elliot
From: Patrick Etienne [via DSpace]
[mailto:[email protected]]
Sent: Monday, March 07, 2011 7:57 AM
To: Elliot Dawson
Subject: DSpace 1.7.0 & Maven 3.0.2 - DuplicateProjectException / Missing
pom.xml properties
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 environments (we have a grant
project where we will be hosting several institutions' dspace repositories).
To make a long story short, it seems as though installation works fine on maven
2.2.1 but fails on 3.0.2 with the following [ERROR]:
"Two or more projects in the reactor have the same identifier, please make sure
that <groupId>:<artifactId>:<version> is unique for each project: (...)"
(goes on to list all dspace maven projects)
In effort to investigate the problem, I put together a google
spreadsheet<https://spreadsheets.google.com/ccc?key=0AgxlFEYcNkPzdC13N3V1cXdPdDRuYWdWRVJWTFo4Q0E&hl=en&authkey=CNqj2pAG>
listing all the dspace maven project pom.xml files as well as (manually
checking their) <groupId>:<artifactId>:<version> strings. Unfortunately (or
fortunately?) there were no duplicate project identifiers. However, after some
more searching I found that it's likely not a problem with an actual duplicate
project identifier as much as it is having two pom.xml files referencing the
same maven <module/>. There's information on the net about possibly changing
this error message so it better reflects the actual cause of the problem (jira
over at Sonatype<https://issues.sonatype.org/browse/TYCHO-531>), but I couldn't
find a maven specific bug report. Note, the bug would only be about the
information the error message provides; referencing the same maven <module/>
from two different pom.xml files is still a valid problem (or so it seems) in
3.0.2
Specifically, the two pom.xml files that seem to be contributing to the problem
are the {dspace-1.7.0-src-release}/pom.xml and the
{dspace-1.7.0-src-release}/dspace/pom.xml. Both files make references to the
following project <modules/>:
dspace-ap
dspace-stats
dspace-discovery
dspace-oai
dspace-jspui
dspace-sword
dspace-xmlui
dspace-lni
This is probably a good point at which to say that I'm not terribly familiar
with maven. I'm not sure why exactly it seems to be within spec to reference
the same <module/> with two different pom.xml files within 2.2.1 but not with
3.0.2. However, it does seem to be the source of the error I listed above (or
at least, from what I can tell). If anyone has any tips, hints, resources, or
suggestions related to getting maven 3.0.2 to play nice with dspace (or
vice-versa) please let me know!
- Patrick E.
--
Patrick K. Etienne
Systems Analyst
Georgia Institute of Technology
Library & Information Center
(404) 385-8121
------------------------------------------------------------------------------
What You Don't Know About Data Connectivity CAN Hurt You
This paper provides an overview of data connectivity, details
its effect on application quality, and explores various alternative
solutions. http://p.sf.net/sfu/progress-d2d
_______________________________________________
DSpace-tech mailing list
[hidden email]</user/SendEmail.jtp?type=node&node=3339149&i=0&by-user=t>
https://lists.sourceforge.net/lists/listinfo/dspace-tech
________________________________
If you reply to this email, your message will be added to the discussion below:
http://dspace.2283337.n4.nabble.com/DSpace-1-7-0-Maven-3-0-2-DuplicateProjectException-Missing-pom-xml-properties-tp3339149p3339149.html
To start a new topic under DSpace - Tech, email
[email protected]<mailto:[email protected]>
To unsubscribe from DSpace - Tech, click
here<http://dspace.2283337.n4.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=3276945&code=ZWRhd3NvbkBtYWYub3JnfDMyNzY5NDV8LTE0OTM1MzcyODk=>.
--
View this message in context:
http://dspace.2283337.n4.nabble.com/DSpace-1-7-0-Maven-3-0-2-DuplicateProjectException-Missing-pom-xml-properties-tp3339149p3339268.html
Sent from the DSpace - Tech mailing list archive at Nabble.com.------------------------------------------------------------------------------
What You Don't Know About Data Connectivity CAN Hurt You
This paper provides an overview of data connectivity, details
its effect on application quality, and explores various alternative
solutions. http://p.sf.net/sfu/progress-d2d
_______________________________________________
DSpace-tech mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-tech