Repository: incubator-zeppelin
Updated Branches:
  refs/heads/master 781a700dd -> 58cb48a24


[HOTFIX] ZEPPELIN-959: Fix odd code block in writingzeppelininterpreter.md

### What is this PR for?
Currently some code blocks in 
[docs/development/writingzeppelininterpreter.html](https://zeppelin.apache.org/docs/0.6.0-SNAPSHOT/development/writingzeppelininterpreter.html)
 & 
[docs/storage/storage.html#S3](https://zeppelin.apache.org/docs/0.6.0-SNAPSHOT/storage/storage.html)
 are broken.

But it seems the broken code block  in `docs/storage/storage.html` is already 
handled in #962. So I just updated in 
`docs/development/writingzeppelininterpreter.html`

### What type of PR is it?
Hot Fix

### Todos

### What is the Jira issue?
[ZEPPELIN-959](https://issues.apache.org/jira/browse/ZEPPELIN-959)

### How should this be tested?
See the attached images :)

### Screenshots (if appropriate)
- Before
![docs-before2](https://cloud.githubusercontent.com/assets/10060731/15812570/6d70ba16-2b6b-11e6-8486-86052e8ceeed.gif)

- After
<img width="1077" alt="screen shot 2016-06-05 at 7 38 50 pm" 
src="https://cloud.githubusercontent.com/assets/10060731/15812563/4b36e696-2b6b-11e6-8f14-f4572331eec6.png";>

### Questions:
* Does the licenses files need update? No
* Is there breaking changes for older versions? No
* Does this needs documentation? No

Author: AhyoungRyu <[email protected]>

Closes #969 from AhyoungRyu/ZEPPELIN-959 and squashes the following commits:

8f8cc70 [AhyoungRyu] ZEPPELIN-959: Fix odd code block in 
writingzeppelininterpreter.md
879b8f9 [AhyoungRyu] Revert "ZEPPELIN-959: Fix odd code blocks in some 
documentations"
967b2fa [AhyoungRyu] ZEPPELIN-959: Fix odd code blocks in some documentations


Project: http://git-wip-us.apache.org/repos/asf/incubator-zeppelin/repo
Commit: 
http://git-wip-us.apache.org/repos/asf/incubator-zeppelin/commit/58cb48a2
Tree: http://git-wip-us.apache.org/repos/asf/incubator-zeppelin/tree/58cb48a2
Diff: http://git-wip-us.apache.org/repos/asf/incubator-zeppelin/diff/58cb48a2

Branch: refs/heads/master
Commit: 58cb48a24a72c62ef22da9bc730dcc05fc75fb60
Parents: 781a700
Author: AhyoungRyu <[email protected]>
Authored: Sun Jun 5 22:30:20 2016 -0700
Committer: Lee moon soo <[email protected]>
Committed: Mon Jun 6 11:25:27 2016 -0700

----------------------------------------------------------------------
 docs/development/writingzeppelininterpreter.md | 4 ++++
 1 file changed, 4 insertions(+)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/incubator-zeppelin/blob/58cb48a2/docs/development/writingzeppelininterpreter.md
----------------------------------------------------------------------
diff --git a/docs/development/writingzeppelininterpreter.md 
b/docs/development/writingzeppelininterpreter.md
index 04b2bb9..a024fca 100644
--- a/docs/development/writingzeppelininterpreter.md
+++ b/docs/development/writingzeppelininterpreter.md
@@ -39,11 +39,13 @@ Creating a new interpreter is quite simple. Just extend 
[org.apache.zeppelin.int
 You can include `org.apache.zeppelin:zeppelin-interpreter:[VERSION]` artifact 
in your build system. And you should your jars under your interpreter directory 
with specific directory name. Zeppelin server reads interpreter directories 
recursively and initializes interpreters including your own interpreter.
 
 There are three locations where you can store your interpreter group, name and 
other information. Zeppelin server tries to find the location below. Next, 
Zeppelin tries to find `interpareter-setting.json` in your interpreter jar. 
+
 ```
 {ZEPPELIN_INTERPRETER_DIR}/{YOUR_OWN_INTERPRETER_DIR}/interpreter-setting.json
 ```
 
 Here is an example of `interpareter-setting.json` on your own interpreter.
+
 ```json
 [
   {
@@ -72,11 +74,13 @@ Here is an example of `interpareter-setting.json` on your 
own interpreter.
 ```
 
 Finally, Zeppelin uses static initialization with the following:
+
 ```
 static {
     Interpreter.register("MyInterpreterName", MyClassName.class.getName());
   }
 ```
+
 **Static initialization is deprecated and will be supported until 0.6.0.**
 
 The name will appear later in the interpreter name option box during the 
interpreter configuration process.

Reply via email to