|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
------------------------------------------------------------------------------ LIMITED TIME SALE - Full Year of Microsoft Training For Just $49.99! 1,500+ hours of tutorials including VisualStudio 2012, Windows 8, SharePoint 2013, SQL 2012, MVC 4, more. BEST VALUE: New Multi-Library Power Pack includes Mobile, Cloud, Java, and UX Design. Lowest price ever! Ends 9/20/13. http://pubads.g.doubleclick.net/gampad/clk?id=58041151&iu=/4140/ostg.clktrk
_______________________________________________ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
Whether we add Google Analytics to build.properties depends on the"purpose" of the build.properties file.
* Is build.properties meant to just be the "base set/minimum" set of configs needed to get DSpace running (in which case, GA may not be applicable to add to build.properties)?
* OR, is build.properties meant to provide a way to quickly edit configs that 80-90% of institutions would want to tweak (in which case, GA may be worth adding)?
This seems to need some discussion.