[Lucene-java Wiki] Update of "DeveloperTips" by UweSchindler

[Apache Wiki <wi...@apache.org>]

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Lucene-java Wiki" for change notification.

The "DeveloperTips" page has been changed by UweSchindler:
https://wiki.apache.org/lucene-java/DeveloperTips?action=diff&rev1=7&rev2=8

Comment:
fix url, remove outdated Subversion section, update Java versions

  
   * Code compatibility:
    * All code to be included in 3.X releases should be compatible with Java 5.
-   * All code to be included in 4.X releases should be compatible with Java 6.
+   * All code to be included in 4.0 to 4.7.x releases should be compatible with Java 6.
-   * All code to be included in trunk, from which 5.0 will be released, should be compatible with Java 7. As most code is currently committed also to the 4.x branch it is a good idea to only use Java 6 code features (no diamond operators instead of full generics,...) unless explicitly needed.
+   * All code to be included in 4.8 onwards and 5.x releases should be compatible with Java 7.
+   * All code to be included in 6.x releases and on master branch should be compatible with Java 8.
   * All public classes and methods should have informative [[http://www.oracle.com/technetwork/java/javase/documentation/index-137868.html|Javadoc comments]].
-  * Code should be formatted according to [[http://www.oracle.com/technetwork/java/codeconv-138413.html|Sun's conventions]] with one exception:
+  * Code should be formatted according to [[http://www.oracle.com/technetwork/java/codeconventions-150003.pdf|Sun's conventions]] with one exception:
    * indent two spaces per level, not four.
   * Contributions should pass existing unit tests.
   * New unit tests should be provided to demonstrate bugs and fixes (http://www.junit.org). Please make your test cases extend LuceneTestCase, which has additional checks including thread leaks for example and makes sure that assertions are enabled.
@@ -47, +48 @@

   * update documentation (e.g., ''package.html'' files, this wiki, etc.)
  
  Please use the ''LUCENE-NNNN.patch''  naming pattern when creating patches for uploading to JIRA.  Once you create a new JIRA issue, note its name and use that name when naming your patch file.  For example, if you are creating a patch for a JIRA issue named LUCENE-3456, then name your patch filename LUCENE-3456.patch.  If you are creating a new version of an existing patch, use the existing patch's file name.  JIRA will automatically "gray out" the old patch and clearly mark your newly uploaded patch as the latest.
- 
- == European SVN Mirror ==
- Depending on where you are located the European mirror might be faster or slower:
- 
- {{{
- svn checkout http://svn.eu.apache.org/repos/asf/lucene/dev/trunk/ lucene-trunk
- }}}
- <<Anchor(antivy)>>
  
  == Problems with Ivy? ==
  Some people have reported problems getting Ivy to work when installed in ${user.home}/.ant/lib