Title: Message Title
|
|
|
|
Mark, I like that idea, and will see if I can work with it. The path Maven would need to write to is /vagrant/config, we'd have to add another level at the top of the :hierarchy: in the hiera.yaml file in the vagrant-dspace project root, probably call it '- dspace_version'. Though, this would be changing the dspace build... are we sure we want to go there?
I've also come up with this code snippet, which will allow puppet to directly query the information it needs, though your idea would not slow down the build process:
mvn dependency:list | grep dspace-api:jar | head -n 1 | sed 's/.*jar:\(.*\):compile.*/\1/'
This would add a maven command and a sed command (both a tad slow) to the pile of things to be done before ant can even run. However, I don't think the first 'vagrant up' would be noticeably slower (it's already pretty slow).
|
|
|
|
|
|
|
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...
|
|
|
|
------------------------------------------------------------------------------
Rapidly troubleshoot problems before they affect your business. Most IT
organizations don't have a clear picture of how application performance
affects their revenue. With AppDynamics, you get 100% visibility into your
Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!
http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk
_______________________________________________
Dspace-devel mailing list
Dspace-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-devel
