You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@olingo.apache.org by bu...@apache.org on 2013/12/10 10:44:34 UTC
svn commit: r889834 - in /websites/staging/olingo/trunk/content: ./
doc/eclipse.html
Author: buildbot
Date: Tue Dec 10 09:44:34 2013
New Revision: 889834
Log:
Staging update by buildbot for olingo
Modified:
websites/staging/olingo/trunk/content/ (props changed)
websites/staging/olingo/trunk/content/doc/eclipse.html
Propchange: websites/staging/olingo/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Tue Dec 10 09:44:34 2013
@@ -1 +1 @@
-1549798
+1549799
Modified: websites/staging/olingo/trunk/content/doc/eclipse.html
==============================================================================
--- websites/staging/olingo/trunk/content/doc/eclipse.html (original)
+++ websites/staging/olingo/trunk/content/doc/eclipse.html Tue Dec 10 09:44:34 2013
@@ -73,14 +73,10 @@
<h1 id="eclipse-ide-support">Eclipse IDE Support</h1>
<hr />
-<p><a href="http://eclipse.org">Eclipse</a> (in version <code>Juno</code> and <code>Kepler</code>) is supported by the project.
-For full support it is necessary to have <a href="http://maven.apache.org/">Maven</a> properly integrated into Eclipse (i.e. at least <code>M2_REPO</code> has to be set correctly as <code>Classpath Variable</code>).
-Recommended is to install the <code>m2e - Maven Integration for Eclipse</code> via the <em>Help -> Eclipse Marketplace...</em> menu. </p>
-<p>With the Maven Eclipse plugin necessary project files can be generated with:</p>
+<p><a href="http://eclipse.org">Eclipse</a> (in version <code>Juno</code> and <code>Kepler</code>) is supported by the project.</p>
+<p>With the Maven project files can be generated with:</p>
<p><code>mvn eclipse:clean eclipse:eclipse</code></p>
-<p>As result each Maven module will get a consistent <code>.project</code>, <code>.classpath</code> and <code>.settings</code> file with which each module can be imported as existing project to Eclipse.
-There are also <a href="https://git-wip-us.apache.org/repos/asf?p=incubator-olingo-odata2.git;a=tree;f=src/eclipse;h=420ec7b716ea24ccd66f4bfddf2c08ccf8c86f6c;hb=HEAD">code style templates</a> available which can be used
-to configure an Eclipse workspace.</p>
+<p>As result each Maven module will get a consistent <code>.project</code>, <code>.classpath</code> and <code>.settings</code> file with which each module can be imported as existing project to Eclipse. </p>