Title: Message Title
|
|
|
|
Hi Hilton,
Not sure I understand your suggestion. You seem to be suggesting we build into the *installation* directory (e.g. [dspace]) rather than the source directory (e.g. [dspace-src]). Since the installation is actually performed by Ant (and not by Maven), this would potentially confuse things (as it is possible to build with Maven, and then tweak the "dspace.dir" setting in dspace.cfg before running 'ant fresh_install').
I'll also note that the reason we use the "target/" directory hierarchy is that it is a Maven best practice. It's possible to change that 'target' directory name, but I'm not sure that it's recommended.
So, for the time being, I'd still lean towards using "[src]/dspace/target/dspace-installer/" as the build location. If there's a really good reason to change that, we could. But, it seems the most logical to me still, as the "[src]/dspace/" directory is the Maven Module which actually *assembles* the Ant-based DSpace installer.
|
|
|
|
|
|
|
As we all know, when you build DSpace (mvn package) it gets built into a directory at:
[src]/dspace/target/dspace-[version]-build/
Unfortunately, when using IT/infrastructure automation software (e.g. Puppet or Chef or similar), this build location can be very difficult to dynamically determine because it includes the Maven <version>. For example, wha...
|
|
|
|
------------------------------------------------------------------------------
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
