<rant>
Well, let me add the "why are we doing this?" view.
Both by its name ("build.properties") and by its usage (by Maven) this
file ought to contain only information that Maven needs to build the
product. It should contain nothing which only matters during
installation. Which is just about all of it. Taking a quick look, I
don't see *any* properties which should have significance to Maven or
our POMs.build.properties has the wrong name and is in the wrong place. It belongs to the installation process. It should be called "install.properties" and it should be used and/or applied by Ant, or whatever tool we use to drive installation. In that position it could be thought of as a saved-installer-answers file for replaying an installation (although you could hand-craft one beforehand, or edit as needed). We could even have a simple "wizard" to lead people through the questions and file the answers. Is that at all helpful? -- Mark H. Wood, Lead System Programmer mw...@iupui.edu Machines should not be friendly. Machines should be obedient.
signature.asc
Description: Digital signature
------------------------------------------------------------------------------ October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60134071&iu=/4140/ostg.clktrk
_______________________________________________ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
