[maven-site] branch master updated: update IDE instructions (#138)

[el...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

elharo pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/maven-site.git


The following commit(s) were added to refs/heads/master by this push:
     new bb9fac4  update IDE instructions (#138)
bb9fac4 is described below

commit bb9fac4b862ce96a9c40cceabf812c068c90eb6a
Author: Elliotte Rusty Harold <el...@users.noreply.github.com>
AuthorDate: Sat Mar 7 08:53:41 2020 -0500

    update IDE instructions (#138)
    
    @michael-o
---
 content/apt/developers/conventions/code.apt | 14 ++++++--------
 1 file changed, 6 insertions(+), 8 deletions(-)

diff --git a/content/apt/developers/conventions/code.apt b/content/apt/developers/conventions/code.apt
index 1976330..edcd50e 100644
--- a/content/apt/developers/conventions/code.apt
+++ b/content/apt/developers/conventions/code.apt
@@ -143,15 +143,13 @@ public class MyMojo
  The following sections show how to set up the code style for Maven in IDEA and Eclipse.
  It is strongly preferred that patches use this style before they are applied.
 
-*** IntelliJ IDEA 4.5+
+*** IntelliJ IDEA
 
- Download <<<{{{../../developers/maven-idea-codestyle.xml}maven-idea-codestyle.xml}}>>> and copy it to
- <<<~/.IntelliJIDEA/config/codestyles>>> then restart IDEA. On Windows, try
- <<<C:\Documents and Settings\<username>\.IntelliJIDEA\config\codestyles>>>
+ Download <<<{{{../../developers/maven-idea-codestyle.xml}maven-idea-codestyle.xml}}>>>
+ and import it into IDEA using File > Settings > Editor > Code Style > Gear icon >
+ Import Scheme > IntelliJ IDEA Code Style XML
 
- After this, restart IDEA and open the settings to select the new code style.
-
-*** Eclipse 3.2+
+*** Eclipse
 
  Download <<<{{{../../developers/maven-eclipse-codestyle.xml}maven-eclipse-codestyle.xml}}>>>.
 
@@ -176,7 +174,7 @@ public class MyMojo
  * <<Documentation>>: Document public interfaces well, i.e. all non-trivial public and
  protected functions should include Javadoc that indicates what they do.
 
- * <<Testing>>: All non-trivial public classes should corresponding unit or
+ * <<Testing>>: All non-trivial public classes should have corresponding unit or
  integration tests.
 
  []