[Dspace-devel] [DuraSpace JIRA] (DS-1760) ant_installer_dir needs to be set by inspecting the Maven pom.xml file, instead of hard-coded

[Mark H. Wood (DuraSpace JIRA)]

Title: Message Title

Mark H. Wood commented on an issue   Re: ant_installer_dir needs to be set by inspecting the Maven pom.xml file, instead of hard-coded We could perhaps create a new filterable YAML template and have Maven drop the filtered version somewhere convenient. Maven knows what it's going to call the artifacts. See what is done in dspace-api with src/main/resources/maven.properties and scm.properties. Add Comment   DSpace / DS-1760 ant_installer_dir needs to be set by inspecting the Maven pom.xml file, instead of hard-coded Currently, the /config/common.yaml file includes this setting for ant_installer_dir: ant_installer_dir : '/home/vagrant/dspace-src/dspace/target/dspace-4.0-SNAPSHOT-build' Which was correct for pre DSpace 4.0-RC1 builds, it now needs to be set to: ant_installer_dir : '/home/vagrant/dspace-src/dspace/target/dspace-4.0-rc2-SNAPSHOT-build' Howeve... This message was sent by Atlassian JIRA (v6.1.1#6155-sha1:7188aee)

------------------------------------------------------------------------------
November Webinars for C, C++, Fortran Developers
Accelerate application performance with scalable programming models. Explore
techniques for threading, error checking, porting, and tuning. Get the most 
from the latest Intel processors and coprocessors. See abstracts and register
http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk
_______________________________________________
Dspace-devel mailing list
Dspace-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-devel