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

[Tim Donohue (DuraSpace JIRA)]

Title: Message Title

Tim Donohue commented on an issue   Re: ant_installer_dir needs to be set by inspecting the Maven pom.xml file, instead of hard-coded Here's a very "quick & dirty" grep and sed which can pull the version out of the parent "pom.xml". It's definitely a Unix-specific hack. But, it's better than what we currently have in vagrant-dspace (which is a hardcoded number): grep -E -m 1 -o "<version>(.*)</version>" pom.xml | sed -e 's,<version>\([^<]*\)</version>,\1,g' This will return "5.0-SNAPSHOT" for current "master". 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)

------------------------------------------------------------------------------
WatchGuard Dimension instantly turns raw network data into actionable 
security intelligence. It gives you real-time visual feedback on key
security issues and trends.  Skip the complicated setup - simply import
a virtual appliance and go from zero to informed in seconds.
http://pubads.g.doubleclick.net/gampad/clk?id=123612991&iu=/4140/ostg.clktrk
_______________________________________________
Dspace-devel mailing list
Dspace-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-devel