maven-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject svn commit: r1335337 - in /maven/plugins/trunk/maven-eclipse-plugin/src/site: apt/trouble-shooting/index.apt fml/faq.fml
Date Tue, 08 May 2012 04:53:31 GMT
Author: baerrach
Date: Tue May  8 04:53:30 2012
New Revision: 1335337

[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/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
+* 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
--- 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>
+   <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="">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
+          </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>

View raw message