I think that sounds reasonable and necessary. We ought to draw a clear distinction between development environments (which should usually be using the latest available) and production environments (where a release means a specific set of versions). We ought to be making full use of local Maven settings to shape behavior for the development environment. And wherever it makes sense we ought to push configuration up the project tree toward or into the root, so that it can be shared and thus consistent.
We do need to keep in mind that there is movement to more fully
modularize the product, with projects that depend on the tree but are
not part of it and meant to be dropped into installed builds.
Otherwise there is the possibility of making common configuration
which shouldn't be. We are going to wind up with multiple project
trees, each with its own needs, all chasing each other. Their needs
will tend toward rough consistency but will vary among them from
time to time. We could look at the idea of a "corporate POM" which
configures a few things that absolutely must be consistent across
trees (if there are such).
This is going to mean a little more work for developers, but not much
I think.
--
Mark H. Wood, Lead System Programmer mw...@iupui.edu
Balance your desire for bells and whistles with the reality that only a
little more than 2 percent of world population has broadband.
-- Ledford and Tyler, _Google Analytics 2.0_
pgpZKu8dYSPR0.pgp
Description: PGP signature
------------------------------------------------------------------------------ Sell apps to millions through the Intel(R) Atom(Tm) Developer Program Be part of this innovative community and reach millions of netbook users worldwide. Take advantage of special opportunities to increase revenue and speed time-to-market. Join now, and jumpstart your future. http://p.sf.net/sfu/intel-atom-d2d
_______________________________________________ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
