*Hi Corneau,*

*I guess you are right as that is exactly what is happening in my case. I
got a successful install that made me happy but the web app at 8080 serves
a blank page.*
*I reinstalled in a fresh folder and found the same error. However, I
noticed that a lot of error messages are generated when installing npm. A
snapshot is given below:*

[INFO]
------------------------------------------------------------------------
[INFO] Building Zeppelin: web Application 0.6.0-incubating-SNAPSHOT
[INFO]
------------------------------------------------------------------------
[INFO]
[INFO] --- maven-checkstyle-plugin:2.13:check (checkstyle-fail-build) @
zeppelin-web ---
[INFO]
[INFO]
[INFO] --- maven-resources-plugin:2.7:copy-resources (copy-resources) @
zeppelin-web ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 17 resources
[INFO]
[INFO] --- maven-enforcer-plugin:1.3.1:enforce (enforce) @ zeppelin-web ---
[INFO]
[INFO] --- frontend-maven-plugin:0.0.23:install-node-and-npm (install node
and npm) @ zeppelin-web ---
[INFO] Installing node version v0.10.22
[INFO] Creating temporary directory
/usr/local/incubator-zeppelin/zeppelin-web/node_tmp
[INFO] Downloading Node.js from
http://nodejs.org/dist/v0.10.22/node-v0.10.22-linux-x64.tar.gz to
/usr/local/incubator-zeppelin/zeppelin-web/node_tmp/node.tar.gz
[INFO] No proxy was configured, downloading directly
[INFO] Extracting Node.js files in node_tmp
[INFO] Unpacking
/usr/local/incubator-zeppelin/zeppelin-web/node_tmp/node.tar.gz into
/usr/local/incubator-zeppelin/zeppelin-web/node_tmp
[INFO] Moving node binary to
/usr/local/incubator-zeppelin/zeppelin-web/node/node
[INFO] Deleting temporary directory
/usr/local/incubator-zeppelin/zeppelin-web/node_tmp
[INFO] Installed node locally.
[INFO] Installing npm version 1.3.8
[INFO] Downloading NPM from http://registry.npmjs.org/npm/-/npm-1.3.8.tgz
to /usr/local/incubator-zeppelin/zeppelin-web/npm.tar.gz
[INFO] No proxy was configured, downloading directly
[INFO] Extracting NPM files in node/
[INFO] Unpacking /usr/local/incubator-zeppelin/zeppelin-web/npm.tar.gz into
/usr/local/incubator-zeppelin/zeppelin-web/node
[INFO] Installed NPM locally.
[INFO]
[INFO] --- frontend-maven-plugin:0.0.23:npm (npm install) @ zeppelin-web ---
[INFO] Running 'npm install --color=false' in
/usr/local/incubator-zeppelin/zeppelin-web
[ERROR] npm http GET https://registry.npmjs.org/bower
[ERROR] npm http GET https://registry.npmjs.org/grunt-autoprefixer
[ERROR] npm http GET https://registry.npmjs.org/grunt
[ERROR] npm http GET https://registry.npmjs.org/grunt-concurrent
[ERROR] npm http GET https://registry.npmjs.org/grunt-contrib-clean
[ERROR] npm http GET https://registry.npmjs.org/grunt-contrib-concat
[ERROR] npm http GET https://registry.npmjs.org/grunt-contrib-connect
[ERROR] npm http GET https://registry.npmjs.org/grunt-contrib-copy
[ERROR] npm http GET https://registry.npmjs.org/grunt-contrib-htmlmin
[ERROR] npm http GET https://registry.npmjs.org/grunt-contrib-cssmin
[ERROR] npm http GET https://registry.npmjs.org/grunt-contrib-uglify
[ERROR] npm http GET https://registry.npmjs.org/grunt-contrib-jshint
[ERROR] npm http GET https://registry.npmjs.org/grunt-filerev
[ERROR] npm http GET https://registry.npmjs.org/grunt-contrib-watch
[ERROR] npm http GET https://registry.npmjs.org/grunt-ng-annotate
[ERROR] npm http GET https://registry.npmjs.org/grunt-svgmin



*.... many more such errors.*
*But bower components get successfully loaded after this. After bower when
grunt build starts the problem begins and we get*

[INFO] Running "connect:test" (connect) task
[INFO] Started connect web server on http://localhost:9001
[INFO]
[INFO] Running "karma:unit" (karma) task
[INFO] INFO [karma]: Karma v0.12.37 server started at http://localhost:9002/
[INFO] INFO [launcher]: Starting browser PhantomJS
[INFO] INFO [PhantomJS 1.9.8 (Linux 0.0.0)]: Connected on socket
lJCtJXUKw8w8Ux_VV-HQ with id 36245844
[INFO] Warning: Task "karma:unit" failed. Use --force to continue.
[INFO]
[INFO] Aborted due to warnings.
[INFO]
[INFO]
[INFO] Execution Time (2015-10-28 02:47:28 UTC)
[INFO] jshint:all         900ms  ▇▇▇▇▇▇▇ 16%
[INFO] jshint:test         90ms  ▇ 2%
[INFO] wiredep:app        197ms  ▇▇ 3%
[INFO] concurrent:test     1.6s  ▇▇▇▇▇▇▇▇▇▇▇▇▇ 29%
[INFO] autoprefixer:dist  288ms  ▇▇▇ 5%
[INFO] karma:unit          2.4s  ▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇ 43%
[INFO] Total 5.7s
[INFO]
[INFO]
------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] Zeppelin ........................................... SUCCESS [
7.668 s]
[INFO] Zeppelin: Interpreter .............................. SUCCESS [
7.885 s]
[INFO] Zeppelin: Zengine .................................. SUCCESS [
2.731 s]
[INFO] Zeppelin: Spark dependencies ....................... SUCCESS [
28.139 s]
[INFO] Zeppelin: Spark .................................... SUCCESS [
31.584 s]
[INFO] Zeppelin: Markdown interpreter ..................... SUCCESS [
0.396 s]
[INFO] Zeppelin: Angular interpreter ...................... SUCCESS [
0.302 s]
[INFO] Zeppelin: Shell interpreter ........................ SUCCESS [
0.243 s]
[INFO] Zeppelin: Hive interpreter ......................... SUCCESS [
4.099 s]
[INFO] Zeppelin: Apache Phoenix Interpreter ............... SUCCESS [
4.672 s]
[INFO] Zeppelin: Apache Geode interpreter ................. SUCCESS [06:09
min]
[INFO] Zeppelin: PostgreSQL interpreter ................... SUCCESS [
0.599 s]
[INFO] Zeppelin: Tajo interpreter ......................... SUCCESS [
1.037 s]
[INFO] Zeppelin: Flink .................................... SUCCESS [
11.354 s]
[INFO] Zeppelin: Apache Ignite interpreter ................ SUCCESS [
0.787 s]
[INFO] Zeppelin: Kylin interpreter ........................ SUCCESS [
0.348 s]
[INFO] Zeppelin: Lens interpreter ......................... SUCCESS [
7.210 s]
[INFO] Zeppelin: Cassandra ................................ SUCCESS [
51.598 s]
[INFO] Zeppelin: web Application .......................... FAILURE [09:34
min]
[INFO] Zeppelin: Server ................................... SKIPPED
[INFO] Zeppelin: Packaging distribution ................... SKIPPED
[INFO]
------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 18:25 min
[INFO] Finished at: 2015-10-28T08:17:34+05:30
[INFO] Final Memory: 122M/423M
[INFO]
------------------------------------------------------------------------
[ERROR] Failed to execute goal
com.github.eirslett:frontend-maven-plugin:0.0.23:grunt (grunt build) on
project zeppelin-web: Failed to run task: 'grunt --no-color' failed. (error
code 3) -> [Help 1]



*I feel that grunt build error is linked to the earlier http errors. *
*Looking forward to your inputs*



On Wed, Oct 28, 2015 at 2:17 AM, Corneau Damien <cornead...@gmail.com>
wrote:

> If normal grunt build didn't pass iin zeppelin-web, then there is no way
> the mvn clean package in incubator-zeppelin will since it call grunt build
>
> On Tue, Oct 27, 2015 at 6:53 PM, Pablo Torre <pablotorr...@gmail.com>
> wrote:
>
>> I am using a virtual machine with Ubuntu 14.04
>>
>>
>> $ npm -v
>>
>> 1.4.28
>>
>> $ node -v
>>
>> v0.10.40
>>
>> $ java -version
>>
>> java version "1.7.0_79"
>>
>> OpenJDK Runtime Environment (IcedTea 2.5.6) (7u79-2.5.6-0ubuntu1.14.04.1)
>>
>> OpenJDK 64-Bit Server VM (build 24.79-b02, mixed mode)
>>
>>
>> Apache Maven 3.1.1 (0728685237757ffbf44136acec0402957f723d9a; 2013-09-17
>> 15:22:22+0000)
>>
>> Maven home: /usr/local/maven
>>
>> Java version: 1.7.0_79, vendor: Oracle Corporation
>>
>> Java home: /usr/lib/jvm/java-7-openjdk-amd64/jre
>>
>> Default locale: en_US, platform encoding: UTF-8
>>
>> OS name: "linux", version: "3.19.0-25-generic", arch: "amd64", family:
>> "unix"
>>
>>
>> The logs:
>>
>>
>> [INFO]
>> ------------------------------------------------------------------------
>>
>> [INFO] Reactor Summary:
>>
>> [INFO]
>>
>> [INFO] Zeppelin .......................................... SUCCESS
>> [10.919s]
>>
>> [INFO] Zeppelin: Interpreter ............................. SUCCESS
>> [15.539s]
>>
>> [INFO] Zeppelin: Zengine ................................. SUCCESS
>> [5.762s]
>>
>> [INFO] Zeppelin: Spark dependencies ...................... SUCCESS
>> [57.376s]
>>
>> [INFO] Zeppelin: Spark ................................... SUCCESS
>> [5:17.924s]
>>
>> [INFO] Zeppelin: Markdown interpreter .................... SUCCESS
>> [6.517s]
>>
>> [INFO] Zeppelin: Angular interpreter ..................... SUCCESS
>> [0.897s]
>>
>> [INFO] Zeppelin: Shell interpreter ....................... SUCCESS
>> [0.789s]
>>
>> [INFO] Zeppelin: Hive interpreter ........................ SUCCESS
>> [17.743s]
>>
>> [INFO] Zeppelin: Apache Phoenix Interpreter .............. SUCCESS
>> [15.154s]
>>
>> [INFO] Zeppelin: Apache Geode interpreter ................ SUCCESS
>> [18.203s]
>>
>> [INFO] Zeppelin: PostgreSQL interpreter .................. SUCCESS
>> [2.916s]
>>
>> [INFO] Zeppelin: Tajo interpreter ........................ SUCCESS
>> [3.508s]
>>
>> [INFO] Zeppelin: Flink ................................... SUCCESS
>> [1:50.128s]
>>
>> [INFO] Zeppelin: Apache Ignite interpreter ............... SUCCESS
>> [16.485s]
>>
>> [INFO] Zeppelin: Kylin interpreter ....................... SUCCESS
>> [3.318s]
>>
>> [INFO] Zeppelin: Lens interpreter ........................ SUCCESS
>> [1:26.327s]
>>
>> [INFO] Zeppelin: Cassandra ............................... SUCCESS
>> [9:07.738s]
>>
>> [INFO] Zeppelin: web Application ......................... FAILURE
>> [23:25.153s]
>>
>> [INFO] Zeppelin: Server .................................. SKIPPED
>>
>> [INFO] Zeppelin: Packaging distribution .................. SKIPPED
>>
>> [INFO]
>> ------------------------------------------------------------------------
>>
>> [INFO] BUILD FAILURE
>>
>> [INFO]
>> ------------------------------------------------------------------------
>>
>> [INFO] Total time: 44:06.492s
>>
>> [INFO] Finished at: Tue Oct 27 17:49:16 UTC 2015
>>
>>
>>
>>
>> [INFO] Final Memory: 119M/432M
>>
>> [INFO]
>> ------------------------------------------------------------------------
>>
>> [ERROR] Failed to execute goal
>> com.github.eirslett:frontend-maven-plugin:0.0.23:grunt (grunt build) on
>> project zeppelin-web: Failed to run task: 'grunt --force --no-color'
>> failed. (error code 137) -> [Help 1]
>>
>> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
>> goal com.github.eirslett:frontend-maven-plugin:0.0.23:grunt (grunt build)
>> on project zeppelin-web: Failed to run task
>>
>> at
>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
>>
>> at
>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
>>
>> at
>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
>>
>> at
>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
>>
>> at
>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
>>
>> at
>> org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
>>
>> at
>> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
>>
>> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:317)
>>
>> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:152)
>>
>> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:555)
>>
>> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:214)
>>
>> at org.apache.maven.cli.MavenCli.main(MavenCli.java:158)
>>
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>
>> at
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>>
>> at
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>
>> at java.lang.reflect.Method.invoke(Method.java:606)
>>
>> at
>> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
>>
>> at
>> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
>>
>> at
>> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
>>
>> at
>> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
>>
>> Caused by: org.apache.maven.plugin.MojoFailureException: Failed to run
>> task
>>
>> at
>> com.github.eirslett.maven.plugins.frontend.mojo.GruntMojo.execute(GruntMojo.java:71)
>>
>> at
>> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:106)
>>
>> at
>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
>>
>> ... 19 more
>>
>> Caused by:
>> com.github.eirslett.maven.plugins.frontend.lib.TaskRunnerException: 'grunt
>> --force --no-color' failed. (error code 137)
>>
>> at
>> com.github.eirslett.maven.plugins.frontend.lib.NodeTaskExecutor.execute(NodeTaskExecutor.java:38)
>>
>> at
>> com.github.eirslett.maven.plugins.frontend.mojo.GruntMojo.execute(GruntMojo.java:69)
>>
>> ... 21 more
>>
>>
>>
>> I don't understand it because the error is this: Failed to execute goal
>> com.github.eirslett:frontend-maven-plugin:0.0.23:grunt (grunt build) on
>> project zeppelin-web and I was able to execute manually "grunt force"
>> inside zeppelin-web
>>
>>
>>
>>
>> 2015-10-27 18:01 GMT+01:00 rohit choudhary <rconl...@gmail.com>:
>>
>>> Hi Pablo,
>>>
>>> Some more logs please? The most recent errors are? Also, what's your dev
>>> setup - mac/linux? Versions of npm/node/java?
>>>
>>> Thanks,
>>> Rohit.
>>>
>>> On Tue, Oct 27, 2015 at 10:21 PM, Pablo Torre <pablotorr...@gmail.com>
>>> wrote:
>>>
>>>> I executed mvn clean package -Pspark-1.4 -Dhadoop.version=2.2.0
>>>> -Phadoop-2.2 -DskipTests but I still have the same problem:
>>>>
>>>> INFO]
>>>> ------------------------------------------------------------------------
>>>>
>>>> [INFO] BUILD FAILURE
>>>>
>>>> [INFO]
>>>> ------------------------------------------------------------------------
>>>>
>>>> [INFO] Total time: 42:11.317s
>>>>
>>>> [INFO] Finished at: Tue Oct 27 16:03:13 UTC 2015
>>>>
>>>> [INFO] Final Memory: 122M/422M
>>>>
>>>> [INFO]
>>>> ------------------------------------------------------------------------
>>>>
>>>> [ERROR] Failed to execute goal
>>>> com.github.eirslett:frontend-maven-plugin:0.0.23:grunt (grunt build) on
>>>> project zeppelin-web: Failed to run task: 'grunt --force --no-color'
>>>> failed. (error code 137) -> [Help 1]
>>>>
>>>> 2015-10-27 17:08 GMT+01:00 rohit choudhary <rconl...@gmail.com>:
>>>>
>>>>> Hi Rick,
>>>>>
>>>>> What are the things that you have in mind? I was thinking of this
>>>>> myself, including some items such as making npm/node etc be strictly local
>>>>> instead of global, a single script that abstracts some of these steps. I
>>>>> will be happy to help.
>>>>>
>>>>> Thanks,
>>>>> Rohit.
>>>>>
>>>>> On Tue, Oct 27, 2015 at 8:40 PM, Rick Moritz <rah...@gmail.com> wrote:
>>>>>
>>>>>> From my experience, that will not work unless you -DskipTests, since
>>>>>> the tests require you have a dist-file available.
>>>>>> Even CI runs two builds at the moment.
>>>>>> So, if you need a tested (NB: tests will fail anyway, until
>>>>>> ZEPPELIN-346 gets merged) distributable, you have to first clean package
>>>>>> with -DskipTests, then package with tests to verify your build.
>>>>>> Oh, you'll also need the ability to pass the selenium tests, which
>>>>>> isn't a given on every platform.
>>>>>>
>>>>>> I'm currently looking into cleaning the build up progressively, but
>>>>>> am also looking for any kind of support. A major refactoring is 
>>>>>> necessary,
>>>>>> in my opinion, to move this project forward from a stability and
>>>>>> repeatability standpoint.
>>>>>>
>>>>>> On Tue, Oct 27, 2015 at 4:04 PM, Pablo Torre <pablotorr...@gmail.com>
>>>>>> wrote:
>>>>>>
>>>>>>> Now, should I try to run mvn clean package inside
>>>>>>> incubador-zeppelin?
>>>>>>>
>>>>>>> 2015-10-27 15:50 GMT+01:00 Pablo Torre <pablotorr...@gmail.com>:
>>>>>>>
>>>>>>>> I tried "./grunt --force" right now and it works
>>>>>>>>
>>>>>>>> 2015-10-27 15:39 GMT+01:00 naveen xavier <naveen.xav...@gmail.com>:
>>>>>>>>
>>>>>>>>> Hi Pablo,
>>>>>>>>>
>>>>>>>>> Were you able to build grunt within the zeppelin-web folder? Use
>>>>>>>>> the following command
>>>>>>>>> ./grunt --force
>>>>>>>>>
>>>>>>>>> On Tue, Oct 27, 2015 at 8:05 PM, Pablo Torre <
>>>>>>>>> pablotorr...@gmail.com> wrote:
>>>>>>>>>
>>>>>>>>>> Hi guys,
>>>>>>>>>>
>>>>>>>>>> I was taking a look to this thread because I wasn't able to fix
>>>>>>>>>> my issue. I followed your suggestions:
>>>>>>>>>>
>>>>>>>>>> Inside zeppelin-web:
>>>>>>>>>>
>>>>>>>>>> Remove node_modules and bower_components
>>>>>>>>>> rm -rf ~/.npm
>>>>>>>>>> npm cache clear
>>>>>>>>>> mvn clean install
>>>>>>>>>>
>>>>>>>>>> And after this inside incubator-zeppelin I executed:
>>>>>>>>>>
>>>>>>>>>> mvn clean package -Pspark-1.4 -Dhadoop.version=2.2.0 -Phadoop-2.2
>>>>>>>>>> -DskipTests
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> But I get the error:
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> BUILD FAILURE
>>>>>>>>>>
>>>>>>>>>> [INFO]
>>>>>>>>>> ------------------------------------------------------------------------
>>>>>>>>>>
>>>>>>>>>> [INFO] Total time: 31:53.919s
>>>>>>>>>>
>>>>>>>>>> [INFO] Finished at: Tue Oct 27 14:32:13 UTC 2015
>>>>>>>>>>
>>>>>>>>>> [INFO] Final Memory: 124M/428M
>>>>>>>>>>
>>>>>>>>>> [INFO]
>>>>>>>>>> ------------------------------------------------------------------------
>>>>>>>>>>
>>>>>>>>>> [ERROR] Failed to execute goal
>>>>>>>>>> com.github.eirslett:frontend-maven-plugin:0.0.23:grunt (grunt build) 
>>>>>>>>>> on
>>>>>>>>>> project zeppelin-web: Failed to run task: 'grunt --force --no-color'
>>>>>>>>>> failed. (error code 137) -> [Help 1]
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> 2015-10-27 14:15 GMT+01:00 rohit choudhary <rconl...@gmail.com>:
>>>>>>>>>>
>>>>>>>>>>> Naveen,
>>>>>>>>>>>
>>>>>>>>>>> Glad! Look forward to your use cases with Zeppelin.
>>>>>>>>>>>
>>>>>>>>>>> Thanks,
>>>>>>>>>>> Rohit.
>>>>>>>>>>>
>>>>>>>>>>> On Tue, Oct 27, 2015 at 4:37 PM, naveen xavier <
>>>>>>>>>>> naveen.xav...@gmail.com> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> Hi Guys
>>>>>>>>>>>>
>>>>>>>>>>>> Yipee Did it
>>>>>>>>>>>>
>>>>>>>>>>>> I just figured that grunt is building only when I give the
>>>>>>>>>>>> --force switch. So I edited the pom.xml in zeppelin-web folder as 
>>>>>>>>>>>> given
>>>>>>>>>>>> below and added it as an argument
>>>>>>>>>>>>
>>>>>>>>>>>> <execution>
>>>>>>>>>>>>             <id>grunt build</id>
>>>>>>>>>>>>             <goals>
>>>>>>>>>>>>               <goal>grunt</goal>
>>>>>>>>>>>>             </goals>
>>>>>>>>>>>>
>>>>>>>>>>>>             <configuration>
>>>>>>>>>>>>               <arguments>*--force*</arguments>
>>>>>>>>>>>>             </configuration>
>>>>>>>>>>>>  </execution>
>>>>>>>>>>>>
>>>>>>>>>>>> Then I did a maven package and presto it worked. Thanks a lot
>>>>>>>>>>>> guys will now try and run Zeppelin which has been delayed by ONE 
>>>>>>>>>>>> day
>>>>>>>>>>>>
>>>>>>>>>>>> Thanks Rohit, Corneau and Renjith for all the help
>>>>>>>>>>>>
>>>>>>>>>>>> Regards,
>>>>>>>>>>>>
>>>>>>>>>>>> Naveen
>>>>>>>>>>>>
>>>>>>>>>>>> On Tue, Oct 27, 2015 at 4:14 PM, naveen xavier <
>>>>>>>>>>>> naveen.xav...@gmail.com> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>> Hi all,
>>>>>>>>>>>>>
>>>>>>>>>>>>> Just another update. On carrying out activities suggested by
>>>>>>>>>>>>> Renjith finally my ./grunt build error has been cleared. It gave 
>>>>>>>>>>>>> some
>>>>>>>>>>>>> warnings but ran with --force switch. Apparently phantomjs has 
>>>>>>>>>>>>> been
>>>>>>>>>>>>> successfully installed.
>>>>>>>>>>>>> The current versions displayed are
>>>>>>>>>>>>> npm: 1.4.21
>>>>>>>>>>>>> node: 0.10.25
>>>>>>>>>>>>> phantomjs: 1.9.0
>>>>>>>>>>>>>
>>>>>>>>>>>>> However on performing a mvn install in zeppelin-web folder....
>>>>>>>>>>>>> I end up with the same grunt --no-color failed error as part of 
>>>>>>>>>>>>> installing
>>>>>>>>>>>>> the eirslett frontend plugin.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Adamant error.Any inputs will be most appreciated.
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Tue, Oct 27, 2015 at 3:31 PM, Renjith Kamath <
>>>>>>>>>>>>> renjith.kam...@gmail.com> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>> Tried again on a new vm "Ubuntu *15.04 x86_64*". This time
>>>>>>>>>>>>>> everything worked fine just by doing "mvn clean install" in 
>>>>>>>>>>>>>> zeppelin-web
>>>>>>>>>>>>>> java 1.8.0_66
>>>>>>>>>>>>>> maven 3.3.3
>>>>>>>>>>>>>> npm is supposed to install karma and other karma related deps
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> may be you can delete node_modules and bower_components from
>>>>>>>>>>>>>> zeppelin-web
>>>>>>>>>>>>>> rm -rf ~/.npm
>>>>>>>>>>>>>> npm cache clear
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> and finally mvn clean install. frontend-maven-plugin should
>>>>>>>>>>>>>> take care of all npm and bower deps
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Thanks & Regards,
>>>>>>>>>>>>>> RK
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Tue, Oct 27, 2015 at 2:54 PM, naveen xavier <
>>>>>>>>>>>>>> naveen.xav...@gmail.com> wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Hi Renjith,
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Just installed nodesjs legacy as suggested by you. Now on
>>>>>>>>>>>>>>> giving the command nodejs -v I am getting v0.10.25
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Secondly fontconfig is installed and is the latest version.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> The problem on running ./grunt in the zeppelin-web folder
>>>>>>>>>>>>>>> seems to be in the karma-phantomjs-launcher module. The 
>>>>>>>>>>>>>>> node-modules folder
>>>>>>>>>>>>>>> does not have this folder in it. I searched and found it in the 
>>>>>>>>>>>>>>> temp folder
>>>>>>>>>>>>>>> with a folder named as - (ie hypen). Any help on how to get the 
>>>>>>>>>>>>>>> phantomjs
>>>>>>>>>>>>>>> problem sorted out.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Thanks again
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> On Tue, Oct 27, 2015 at 2:35 PM, Renjith Kamath <
>>>>>>>>>>>>>>> renjith.kam...@gmail.com> wrote:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> I was able to see the earlier phantomjs error on a new vm
>>>>>>>>>>>>>>>> and resolve it by installing libfontconfig.
>>>>>>>>>>>>>>>> Can you check if "fontconfig" package is installed or not?
>>>>>>>>>>>>>>>> sudo apt-get install fontconfig
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Thanks & Regards,
>>>>>>>>>>>>>>>> RK
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> On Tue, Oct 27, 2015 at 2:28 PM, rohit choudhary <
>>>>>>>>>>>>>>>> rconl...@gmail.com> wrote:
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Naveen,
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Looks like there's some issue with your NodeJS
>>>>>>>>>>>>>>>>> installation. I looked up some links, there was a breaking 
>>>>>>>>>>>>>>>>> change in the
>>>>>>>>>>>>>>>>> package manager, and I think this would work for you sudo
>>>>>>>>>>>>>>>>> apt-get install nodejs-legacy.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> http://stackoverflow.com/questions/21168141/can-not-install-packages-using-node-package-manager-in-ubuntu
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>>>>>> Rohit.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> On Tue, Oct 27, 2015 at 1:02 PM, naveen xavier <
>>>>>>>>>>>>>>>>> naveen.xav...@gmail.com> wrote:
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Hi Renjith,
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Did as you suggested, it seems to already exist
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Reading package lists... Done
>>>>>>>>>>>>>>>>>> Building dependency tree
>>>>>>>>>>>>>>>>>> Reading state information... Done
>>>>>>>>>>>>>>>>>> Note, selecting 'libfontconfig1' instead of
>>>>>>>>>>>>>>>>>> 'libfontconfig'
>>>>>>>>>>>>>>>>>> libfontconfig1 is already the newest version.
>>>>>>>>>>>>>>>>>> The following packages were automatically installed and
>>>>>>>>>>>>>>>>>> are no longer required:
>>>>>>>>>>>>>>>>>>   libarmadillo4 libarpack2 libdap11 libdapclient3
>>>>>>>>>>>>>>>>>> libepsilon1 libfreexl1 libgdal1h libgeos-3.4.2 libgeos-c1
>>>>>>>>>>>>>>>>>> libhawtjni-runtime-java
>>>>>>>>>>>>>>>>>>   libhdf4-0-alt libhdf5-8 libjansi-java
>>>>>>>>>>>>>>>>>> libjansi-native-java libkml0 libmysqlcppconn7 libnetcdfc7 
>>>>>>>>>>>>>>>>>> libodbc1
>>>>>>>>>>>>>>>>>> libogdi3.2 libopenjp2-7
>>>>>>>>>>>>>>>>>>   libpq5 libproj0 libspatialite5 liburiparser1
>>>>>>>>>>>>>>>>>> libvsqlitepp3 libxerces-c3.1 linux-headers-3.19.0-15
>>>>>>>>>>>>>>>>>> linux-headers-3.19.0-15-generic
>>>>>>>>>>>>>>>>>>   linux-image-3.19.0-15-generic
>>>>>>>>>>>>>>>>>> linux-image-extra-3.19.0-15-generic mysql-utilities 
>>>>>>>>>>>>>>>>>> mysql-workbench-data
>>>>>>>>>>>>>>>>>> odbcinst odbcinst1debian2
>>>>>>>>>>>>>>>>>>   proj-bin proj-data python-mysql.connector
>>>>>>>>>>>>>>>>>> python-pexpect python-pyodbc python-pysqlite2 scala-library
>>>>>>>>>>>>>>>>>> Use 'apt-get autoremove' to remove them.
>>>>>>>>>>>>>>>>>> 0 upgraded, 0 newly installed, 0 to remove and 50 not
>>>>>>>>>>>>>>>>>> upgraded.
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Any reason libfontconfig1 needs to be replaced???
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> On Tue, Oct 27, 2015 at 12:55 PM, Renjith Kamath <
>>>>>>>>>>>>>>>>>> renjith.kam...@gmail.com> wrote:
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> Hey Naveen,
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> The issue is in PhantomJs dep. Please try "sudo apt-get
>>>>>>>>>>>>>>>>>>> install libfontconfig"
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> Thanks & Regards,
>>>>>>>>>>>>>>>>>>> RK
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> On Tue, Oct 27, 2015 at 12:32 PM, naveen xavier <
>>>>>>>>>>>>>>>>>>> naveen.xav...@gmail.com> wrote:
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> Hi Corneau & Rohit,
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> Just as suggested I did a ./grunt in the zeppelin-web
>>>>>>>>>>>>>>>>>>>> folder. It ran successfully and then prompted to use the 
>>>>>>>>>>>>>>>>>>>> following command
>>>>>>>>>>>>>>>>>>>> as the module is missing:
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> install karma-phantomjs-launcher --save-dev
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> On attempting to install the same I received the
>>>>>>>>>>>>>>>>>>>> following error:
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> > phantomjs@1.9.18 install
>>>>>>>>>>>>>>>>>>>> /usr/local/incubator-zeppelin/zeppelin-web/node_modules/phantomjs
>>>>>>>>>>>>>>>>>>>> > node install.js
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> sh: 1: node: not found
>>>>>>>>>>>>>>>>>>>> npm WARN This failure might be due to the use of legacy
>>>>>>>>>>>>>>>>>>>> binary "node"
>>>>>>>>>>>>>>>>>>>> npm WARN For further explanations, please read
>>>>>>>>>>>>>>>>>>>> /usr/share/doc/nodejs/README.Debian
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> npm ERR! phantomjs@1.9.18 install: `node install.js`
>>>>>>>>>>>>>>>>>>>> npm ERR! Exit status 127
>>>>>>>>>>>>>>>>>>>> npm ERR!
>>>>>>>>>>>>>>>>>>>> npm ERR! Failed at the phantomjs@1.9.18 install script.
>>>>>>>>>>>>>>>>>>>> npm ERR! This is most likely a problem with the
>>>>>>>>>>>>>>>>>>>> phantomjs package,
>>>>>>>>>>>>>>>>>>>> npm ERR! not with npm itself.
>>>>>>>>>>>>>>>>>>>> npm ERR! Tell the author that this fails on your system:
>>>>>>>>>>>>>>>>>>>> npm ERR!     node install.js
>>>>>>>>>>>>>>>>>>>> npm ERR! You can get their info via:
>>>>>>>>>>>>>>>>>>>> npm ERR!     npm owner ls phantomjs
>>>>>>>>>>>>>>>>>>>> npm ERR! There is likely additional logging output
>>>>>>>>>>>>>>>>>>>> above.
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> npm ERR! System Linux 3.19.0-30-generic
>>>>>>>>>>>>>>>>>>>> npm ERR! command "/usr/bin/nodejs" "/usr/bin/npm"
>>>>>>>>>>>>>>>>>>>> "install" "karma-phantomjs-launcher" "--save-dev"
>>>>>>>>>>>>>>>>>>>> npm ERR! cwd /usr/local/incubator-zeppelin/zeppelin-web
>>>>>>>>>>>>>>>>>>>> npm ERR! node -v v0.10.25
>>>>>>>>>>>>>>>>>>>> npm ERR! npm -v 1.4.21
>>>>>>>>>>>>>>>>>>>> npm ERR! code ELIFECYCLE
>>>>>>>>>>>>>>>>>>>> npm ERR!
>>>>>>>>>>>>>>>>>>>> npm ERR! Additional logging details can be found in:
>>>>>>>>>>>>>>>>>>>> npm ERR!
>>>>>>>>>>>>>>>>>>>> /usr/local/incubator-zeppelin/zeppelin-web/npm-debug.log
>>>>>>>>>>>>>>>>>>>> npm ERR! not ok code 0
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> I read in some post that the temp files of phantomjs
>>>>>>>>>>>>>>>>>>>> could create a problem, so I deleted the same... but got 
>>>>>>>>>>>>>>>>>>>> the same error. I
>>>>>>>>>>>>>>>>>>>> am now trying to build phantomjs from source after cloning 
>>>>>>>>>>>>>>>>>>>> it from github.
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> Let me know if I am on the right path.
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> Thanks again for your interest.
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> On Tue, Oct 27, 2015 at 2:04 AM, naveen xavier <
>>>>>>>>>>>>>>>>>>>> naveen.xav...@gmail.com> wrote:
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> Hi Rohit,
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> Thank you so much for your quick response.
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> Did exactly as you suggested and successfully
>>>>>>>>>>>>>>>>>>>>> installed npm inside zeppelin-web folder. Now when I give 
>>>>>>>>>>>>>>>>>>>>> the command: *npm
>>>>>>>>>>>>>>>>>>>>> -v*
>>>>>>>>>>>>>>>>>>>>> I get:  *1.4.21*
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> However the command: *mvn package*
>>>>>>>>>>>>>>>>>>>>> within the zeppelin-web folder gives the same grunt
>>>>>>>>>>>>>>>>>>>>> build error:
>>>>>>>>>>>>>>>>>>>>> *'grunt --no-color' failed. (error code 3).*
>>>>>>>>>>>>>>>>>>>>> I also again tried the command: *mvn package
>>>>>>>>>>>>>>>>>>>>> -DskipTests* from incubator-zeppelin folder and
>>>>>>>>>>>>>>>>>>>>> received the same error!!!
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> Also went through your trail mail with Pablo who has
>>>>>>>>>>>>>>>>>>>>> been graduating to new problems but my error message has 
>>>>>>>>>>>>>>>>>>>>> just not changed.
>>>>>>>>>>>>>>>>>>>>> I have tried every possible combination and end up with 
>>>>>>>>>>>>>>>>>>>>> the same grunt
>>>>>>>>>>>>>>>>>>>>> error. Please help.
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> On Mon, Oct 26, 2015 at 11:20 PM, rohit choudhary <
>>>>>>>>>>>>>>>>>>>>> rconl...@gmail.com> wrote:
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> Hi Naveen,
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> Can you run npm install inside you /zeppelin-web/
>>>>>>>>>>>>>>>>>>>>>> directory? If that is successful you can run - mvn 
>>>>>>>>>>>>>>>>>>>>>> package -Dskiptest
>>>>>>>>>>>>>>>>>>>>>> -Phadoop-2.3 -Ppyspark (or whatever else you want to 
>>>>>>>>>>>>>>>>>>>>>> configure your
>>>>>>>>>>>>>>>>>>>>>> zeppelin with). You might be missing on some npm 
>>>>>>>>>>>>>>>>>>>>>> libraries.
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>>>>>>>>>>> Rohit
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> On Mon, Oct 26, 2015 at 11:00 PM, naveen xavier <
>>>>>>>>>>>>>>>>>>>>>> naveen.xav...@gmail.com> wrote:
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> Hi,
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> My configuration is as follows:
>>>>>>>>>>>>>>>>>>>>>>> Ubuntu 15.04
>>>>>>>>>>>>>>>>>>>>>>> Spark 1.4.1
>>>>>>>>>>>>>>>>>>>>>>> Hadoop 2.7
>>>>>>>>>>>>>>>>>>>>>>> Maven 3.3.3
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> I am trying to install Apache Zeppelin using the
>>>>>>>>>>>>>>>>>>>>>>> following command
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> mvn clean package -DskipTests
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> Despite several attempts, I am getting the following
>>>>>>>>>>>>>>>>>>>>>>> error.
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> [ERROR] Failed to execute goal
>>>>>>>>>>>>>>>>>>>>>>> com.github.eirslett:frontend-maven-plugin:0.0.23:grunt 
>>>>>>>>>>>>>>>>>>>>>>> (grunt build) on
>>>>>>>>>>>>>>>>>>>>>>> project zeppelin-web: Failed to run task: 'grunt 
>>>>>>>>>>>>>>>>>>>>>>> --no-color' failed. (error
>>>>>>>>>>>>>>>>>>>>>>> code 3) -> [Help 1]
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> Any help will be highly appreciated. Thanks in
>>>>>>>>>>>>>>>>>>>>>>> advance
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> Regards,
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> Naveen Xavier
>>>>>>>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>>>>>>>> Regards,
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> Naveen Xavier
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>>>>>> Regards,
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> Naveen Xavier
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>>>>> Regards,
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> Naveen Xavier
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>>> Regards,
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Naveen Xavier
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>> Regards,
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Naveen Xavier
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> --
>>>>>>>>>>>>> Regards,
>>>>>>>>>>>>>
>>>>>>>>>>>>> Naveen Xavier
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> --
>>>>>>>>>>>> Regards,
>>>>>>>>>>>>
>>>>>>>>>>>> Naveen Xavier
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> Pablo Torre.
>>>>>>>>>> Freelance software engineer and Ruby on Rails developer.
>>>>>>>>>> Oleiros (Coruña)
>>>>>>>>>> *Personal site <http://www.pablotorrerodriguez.com>*
>>>>>>>>>> My blog <http://www.aboutechnologies.com>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Regards,
>>>>>>>>>
>>>>>>>>> Naveen Xavier
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Pablo Torre.
>>>>>>>> Freelance software engineer and Ruby on Rails developer.
>>>>>>>> Oleiros (Coruña)
>>>>>>>> *Personal site <http://www.pablotorrerodriguez.com>*
>>>>>>>> My blog <http://www.aboutechnologies.com>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Pablo Torre.
>>>>>>> Freelance software engineer and Ruby on Rails developer.
>>>>>>> Oleiros (Coruña)
>>>>>>> *Personal site <http://www.pablotorrerodriguez.com>*
>>>>>>> My blog <http://www.aboutechnologies.com>
>>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Pablo Torre.
>>>> Freelance software engineer and Ruby on Rails developer.
>>>> Oleiros (Coruña)
>>>> *Personal site <http://www.pablotorrerodriguez.com>*
>>>> My blog <http://www.aboutechnologies.com>
>>>>
>>>
>>>
>>
>>
>> --
>> Pablo Torre.
>> Freelance software engineer and Ruby on Rails developer.
>> Oleiros (Coruña)
>> *Personal site <http://www.pablotorrerodriguez.com>*
>> My blog <http://www.aboutechnologies.com>
>>
>
>


-- 
Regards,

Naveen Xavier

Reply via email to