Author: mibo
Date: Mon May 4 11:19:27 2015
New Revision: 1677585
URL: http://svn.apache.org/r1677585
Log:
CMS commit to olingo by mibo
Modified:
olingo/site/trunk/content/doc/odata4/tutorials/read/tutorial_read.mdtext
Modified:
olingo/site/trunk/content/doc/odata4/tutorials/read/tutorial_read.mdtext
URL:
http://svn.apache.org/viewvc/olingo/site/trunk/content/doc/odata4/tutorials/read/tutorial_read.mdtext?rev=1677585&r1=1677584&r2=1677585&view=diff
==============================================================================
--- olingo/site/trunk/content/doc/odata4/tutorials/read/tutorial_read.mdtext
(original)
+++ olingo/site/trunk/content/doc/odata4/tutorials/read/tutorial_read.mdtext
Mon May 4 11:19:27 2015
@@ -145,23 +145,24 @@ On the second wizard page, choose the a
On the next page, enter the following information:
- - Project Name: *DemoService*
- - Groupd Id: *my.group.id*
- - Artifact Id: *DemoService*
- - Version: *0.0.1*
- - Package: *myservice.mynamespace.service*
+
+ * Project Name: *DemoService*
+ * Groupd Id: *my.group.id*
+ * Artifact Id: *DemoService*
+ * Version: *0.0.1*
+ * Package: *myservice.mynamespace.service*
> Note:
> If youâre using this wizard for the first time, it might take some time,
> as maven needs to download the archetype itself to your local maven-repo.
-After finishing the wizard, the next step is to edit the pom.xml file.
+After finishing the wizard, the next step is to edit the *pom.xml* file.
**Edit pom file**
In our project, weâll be using several libraries, e.g. the Olingo libraries.
In the pom.xml file, we specify the dependencies and Maven will take care to
download them to our local maven repository.
-Furthermore, the pom.xml file tells Maven which output we want to have as
result of our build. In our case, this is a war file.
+Furthermore, the *pom.xml* file tells Maven which output we want to have as
result of our build. In our case, this is a war file.
In our example, the pom.xml file looks as follows:
