|
||||||||
|
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 |
||||||||
------------------------------------------------------------------------------ Get your SQL database under version control now! Version control is standard for application code, but databases havent caught up. So what steps can you take to put your SQL databases under version control? Why should you start doing it? Read more to find out. http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk
_______________________________________________ Dspace-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-devel
In general, that's probably the "best practice" to avoid these sorts of incompatibility issues -- i.e. avoid managing versions of common libraries in each individual module (as they are likely going get out-of-sync), and instead do the version management in 'dspace-parent' POM for any shared/common libraries used across multiple modules.
So, I think PR#242 (as it currently stands) is a good start, but may not go far enough yet... best to get this all cleaned up at once.