You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@olingo.apache.org by sk...@apache.org on 2013/12/10 10:44:31 UTC
svn commit: r1549799 -
/incubator/olingo/site/trunk/content/doc/eclipse.mdtext
Author: sklevenz
Date: Tue Dec 10 09:44:31 2013
New Revision: 1549799
URL: http://svn.apache.org/r1549799
Log:
CMS commit to olingo by sklevenz
Modified:
incubator/olingo/site/trunk/content/doc/eclipse.mdtext
Modified: incubator/olingo/site/trunk/content/doc/eclipse.mdtext
URL: http://svn.apache.org/viewvc/incubator/olingo/site/trunk/content/doc/eclipse.mdtext?rev=1549799&r1=1549798&r2=1549799&view=diff
==============================================================================
--- incubator/olingo/site/trunk/content/doc/eclipse.mdtext (original)
+++ incubator/olingo/site/trunk/content/doc/eclipse.mdtext Tue Dec 10 09:44:31 2013
@@ -21,15 +21,11 @@ Notice: Licensed to the Apache Softwa
---
[Eclipse](http://eclipse.org) (in version `Juno` and `Kepler`) is supported by the project.
-For full support it is necessary to have [Maven](http://maven.apache.org/) properly integrated into Eclipse (i.e. at least `M2_REPO` has to be set correctly as `Classpath Variable`).
-Recommended is to install the `m2e - Maven Integration for Eclipse` via the _Help -> Eclipse Marketplace..._ menu.
-With the Maven Eclipse plugin necessary project files can be generated with:
+With the Maven project files can be generated with:
```
mvn eclipse:clean eclipse:eclipse
```
As result each Maven module will get a consistent `.project`, `.classpath` and `.settings` file with which each module can be imported as existing project to Eclipse.
-There are also [code style templates](https://git-wip-us.apache.org/repos/asf?p=incubator-olingo-odata2.git;a=tree;f=src/eclipse;h=420ec7b716ea24ccd66f4bfddf2c08ccf8c86f6c;hb=HEAD) available which can be used
-to configure an Eclipse workspace.
\ No newline at end of file