Title: Message Title
|
|
|
|
jmockit 1.6, OTOH, is much too new. 1.1 seems to be the latest we can use without extensive changes.
Already the required jmockit changes dwarf the version enforcement changes. Should "Update JMockit" be made a separate ticket, with this depending on it?
https://github.com/DSpace/DSpace/pull/499
|
|
|
|
|
|
|
|
Stated prerequisites for DSpace 4.x include JDK/JRE 1.7 and Maven 3. The pom.xml in dspace-parent is enforcing Java 1.6 and does not specify the Maven version. The former prevents use of Java 1.7 features in development, and the latter is lurking to create mysteries for those running older versions of Maven.
|
|
|
|
------------------------------------------------------------------------------
Subversion Kills Productivity. Get off Subversion & Make the Move to Perforce.
With Perforce, you get hassle-free workflows. Merge that actually works.
Faster operations. Version large binaries. Built-in WAN optimization and the
freedom to use Git, Perforce or both. Make the move to Perforce.
http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk
_______________________________________________
Dspace-devel mailing list
Dspace-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-devel
