I'm tracking down reasons for unexpected consequences of what should be minor POM tweaking, and I'm puzzled by some of the dependency declarations.
For one thing, XMLUI (at least) seems to get most of its dependencies set up in dspace/modules/xmlui. Shouldn't the stock dependencies be in dspace-xmlui and its subprojects? I thought that dspace/modules** was supposed to be essentially empty scaffolding to be filled locally as needed. For another, 'mvn dependency:analyze' shows a *lot* of "used undeclared" and "unused declared" dependencies throughout the tree. Shouldn't we try to keep these cleaned up as much as possible, and document the reasons for the rest? I'm a mere apprentice w.r.t. things Maven, so before I plunge into this I wanted to stir up some discussion among those more experienced. -- Mark H. Wood, Lead System Programmer mw...@iupui.edu Friends don't let friends publish revisable-form documents.
pgp0WJVPthao3.pgp
Description: PGP signature
------------------------------------------------------------------------------ Enter the BlackBerry Developer Challenge This is your chance to win up to $100,000 in prizes! For a limited time, vendors submitting new applications to BlackBerry App World(TM) will have the opportunity to enter the BlackBerry Developer Challenge. See full prize details at: http://p.sf.net/sfu/Challenge
_______________________________________________ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
