Author: baerrach
Date: Tue May  8 04:53:30 2012
New Revision: 1335337

URL: http://svn.apache.org/viewvc?rev=1335337&view=rev
Log:
[MECLIPSE-721] Improve documentation to explain why Eclipse sometimes does not 
import projects with correct project names.

o Updated FAQ and trouble shooting to explain the problem with links to the 
Eclipse bugs and the steps to work around the issue.


Modified:
    
maven/plugins/trunk/maven-eclipse-plugin/src/site/apt/trouble-shooting/index.apt
    maven/plugins/trunk/maven-eclipse-plugin/src/site/fml/faq.fml

Modified: 
maven/plugins/trunk/maven-eclipse-plugin/src/site/apt/trouble-shooting/index.apt
URL: 
http://svn.apache.org/viewvc/maven/plugins/trunk/maven-eclipse-plugin/src/site/apt/trouble-shooting/index.apt?rev=1335337&r1=1335336&r2=1335337&view=diff
==============================================================================
--- 
maven/plugins/trunk/maven-eclipse-plugin/src/site/apt/trouble-shooting/index.apt
 (original)
+++ 
maven/plugins/trunk/maven-eclipse-plugin/src/site/apt/trouble-shooting/index.apt
 Tue May  8 04:53:30 2012
@@ -36,3 +36,6 @@ Trouble Shooting
 
   See {{{./jdk-being-used-is-different-than-expected.html}jdk being used is 
different than expected}}.
 
+* The Eclipse project is not named correctly
+
+  Please see the FAQ 
{{{../faq.html#import-project-incorrect-project-name}Eclipse is not using the 
correct project name and is using the directory name instead}}.

Modified: maven/plugins/trunk/maven-eclipse-plugin/src/site/fml/faq.fml
URL: 
http://svn.apache.org/viewvc/maven/plugins/trunk/maven-eclipse-plugin/src/site/fml/faq.fml?rev=1335337&r1=1335336&r2=1335337&view=diff
==============================================================================
--- maven/plugins/trunk/maven-eclipse-plugin/src/site/fml/faq.fml (original)
+++ maven/plugins/trunk/maven-eclipse-plugin/src/site/fml/faq.fml Tue May  8 
04:53:30 2012
@@ -37,6 +37,18 @@ under the License.
        <p>You may also need to import the project created by Maven Eclipse 
Plugin. More information can be found <a href="usage.html#Simple 
Project">here</a>.</p>
      </answer>
    </faq>
+   <faq id="import-project-incorrect-project-name">
+     <question>Eclipse is not using the correct project name and is using the 
directory name instead</question>
+     <answer>
+       <p>See the Eclipse bug <a 
href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=225754#c38";>225754</a>.</p>
+       <p>Essentially if the folder:</p>
+          <ul>
+            <li>is directly below the default workspace then it IGNORES the 
.project/name element on the import and uses the directory name instead</li>
+            <li>is NOT directly below the default workspace then it correctly 
uses .project/name</li>
+          </ul>
+       <p>This may be why the current Eclipse recommendation is to create a 
workspace that has NO projects kept underneath it, which will mean correctly 
named projects.</p>
+     </answer>
+   </faq>
    <faq id="use-add-maven-repo">
      <question>After running <i>mvn eclipse:eclipse</i>, the generated 
dependencies are pointing to a non-existing file. What needs to be 
done?</question>
      <answer>


Reply via email to