I am starting our upgrade from DSpace 4 to DSpace 5.
Our code base contains only the dspace folder rather than the full source
distribution (dspace, dspace-api, etc).
All of our custom code resides in dspace/modules including
dspace/modules/additions.
Our additions module has a compile dependency on dspace-api and will not
compile unless dspace-api-5.4-SNAPSHOT.jar has already been installed in
the maven repository.
I can work around this issue by building the full source instance of DSpace
with mvn install and then running mvn package on my code base. I do not
remember encountering this issue on prior upgrades.
Here is an excerpt from my additions pom.xml file. Should I convey this
dependency differently?
<dependency>
<groupId>org.dspace</groupId>
<artifactId>dspace-api</artifactId>
</dependency>
<dependency>
<groupId>org.dspace</groupId>
<artifactId>dspace-api-lang</artifactId>
</dependency>
<dependency>
<groupId>javax.servlet</groupId>
<artifactId>servlet-api</artifactId>
<scope>provided</scope>
</dependency>
Thanks, Terry
--
Terry Brady
Applications Programmer Analyst
Georgetown University Library Information Technology
https://www.library.georgetown.edu/lit/code
425-298-5498 (Seattle, WA)
------------------------------------------------------------------------------
_______________________________________________
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech
List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
