[jira] [Commented] (ATLAS-199) webapp build fails (grunt + tests)

2015-10-09 Thread Suma Shivaprasad (JIRA) 

[ 
https://issues.apache.org/jira/browse/ATLAS-199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14951604#comment-14951604
 ] 

Suma Shivaprasad commented on ATLAS-199:


[~Darshan Kumar] Refer 
https://builds.apache.org/job/apache-atlas-nightly/87/console for build 
failures and command that is run

> webapp build fails (grunt + tests)
> --
>
> Key: ATLAS-199
> URL: https://issues.apache.org/jira/browse/ATLAS-199
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.6-incubating
>Reporter: Erik Bergenholtz
>Assignee: Darshan Kumar
>Priority: Critical
>  Labels: patch-available
> Fix For: 0.6-incubating
>
> Attachments: ATLAS-199-v0.patch
>
>
> When building Atlas webapp, I see the following issues:
> mvn clean install:
> {code}
> [INFO] Running 'grunt bower --no-color' in 
> /Users/ebergenholtz/git3/incubator-atlas/dashboard
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time: 34.282 s
> [INFO] Finished at: 2015-09-30T13:55:30-05:00
> [INFO] Final Memory: 35M/420M
> [INFO] 
> 
> [ERROR] Failed to execute goal 
> com.github.eirslett:frontend-maven-plugin:0.0.23:grunt (install bower) on 
> project atlas-webapp: Failed to run task: 'grunt bower --no-color' failed. 
> java.io.IOException: Cannot run program 
> "/Users/ebergenholtz/git3/incubator-atlas/dashboard/node/node" (in directory 
> "/Users/ebergenholtz/git3/incubator-atlas/dashboard"): error=2, No such file 
> or directory -> [Help 1]
> {code}
> Also, if I bypass the grunt task some of the tests fail.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ATLAS-199) webapp build fails (grunt + tests)

2015-10-09 Thread Darshan Kumar (JIRA) 

[ 
https://issues.apache.org/jira/browse/ATLAS-199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14951619#comment-14951619
 ] 

Darshan Kumar commented on ATLAS-199:
-

Thanks, I see the log and I find this command --  export 'MAVEN_OPTS=-Xmx4096m 
-XX:MaxPermSize=1024m -Dfile.encoding=UTF-8 -noverify

I will run the build and update you. Thank you

> webapp build fails (grunt + tests)
> --
>
> Key: ATLAS-199
> URL: https://issues.apache.org/jira/browse/ATLAS-199
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.6-incubating
>Reporter: Erik Bergenholtz
>Assignee: Darshan Kumar
>Priority: Critical
>  Labels: patch-available
> Fix For: 0.6-incubating
>
> Attachments: ATLAS-199-v0.patch
>
>
> When building Atlas webapp, I see the following issues:
> mvn clean install:
> {code}
> [INFO] Running 'grunt bower --no-color' in 
> /Users/ebergenholtz/git3/incubator-atlas/dashboard
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time: 34.282 s
> [INFO] Finished at: 2015-09-30T13:55:30-05:00
> [INFO] Final Memory: 35M/420M
> [INFO] 
> 
> [ERROR] Failed to execute goal 
> com.github.eirslett:frontend-maven-plugin:0.0.23:grunt (install bower) on 
> project atlas-webapp: Failed to run task: 'grunt bower --no-color' failed. 
> java.io.IOException: Cannot run program 
> "/Users/ebergenholtz/git3/incubator-atlas/dashboard/node/node" (in directory 
> "/Users/ebergenholtz/git3/incubator-atlas/dashboard"): error=2, No such file 
> or directory -> [Help 1]
> {code}
> Also, if I bypass the grunt task some of the tests fail.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: Review Request 39157: Configure Consumer Groups for Notifications

2015-10-09 Thread Suma Shivaprasad 

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/39157/#review102064
---



notification/src/main/java/org/apache/atlas/kafka/KafkaNotification.java (line 
223)


consumerConnector need to be shutdown


- Suma Shivaprasad


On Oct. 9, 2015, 1:40 a.m., Tom Beerbower wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/39157/
> ---
> 
> (Updated Oct. 9, 2015, 1:40 a.m.)
> 
> 
> Review request for atlas, John Speidel and Shwetha GS.
> 
> 
> Bugs: ATLAS-215
> https://issues.apache.org/jira/browse/ATLAS-215
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> Currently with the notification framework we set the properties so that all 
> consumers are created in a single group...
> 
> //todo take group id as argument to allow multiple consumers??
> properties.put(ConsumerConfig.GROUP_ID_CONFIG, ATLAS_GROUP);
> 
> Having Kafka consumers for both the HOOK and ENTITIES topics in a single 
> group causes this issue ...
> 
> java.lang.IllegalArgumentException: requirement failed: Round-robin 
> assignment is allowed only if all consumers in the group subscribe to the 
> same topics, AND if the stream counts across topics are identical for a given 
> consumer instance.
> Topic ATLAS_ENTITIES has the following available consumer streams: 
> Set(atlas_c6401.ambari.apache.org-1443714948705-e518b690-0)
> Topic ATLAS_HOOK has the following available consumer streams: 
> Set(atlas_c6401.ambari.apache.org-1443714214755-8fd9a5f8-0)
> 
> We shouldn't have HOOK consumers and ENTITIES consumers in the same group.
> 
> 
> Diffs
> -
> 
>   notification/pom.xml 2e12520 
>   notification/src/main/java/org/apache/atlas/kafka/KafkaNotification.java 
> 7b3cf89 
>   
> notification/src/main/java/org/apache/atlas/notification/NotificationHookConsumer.java
>  29194a4 
>   
> notification/src/main/java/org/apache/atlas/notification/NotificationInterface.java
>  d4be07b 
>   
> notification/src/test/java/org/apache/atlas/kafka/KafkaNotificationTest.java 
> 735655c 
> 
> Diff: https://reviews.apache.org/r/39157/diff/
> 
> 
> Testing
> ---
> 
> new unit test added
> 
> mvn clean test
> 
> [INFO] 
> 
> [INFO] BUILD SUCCESS
> [INFO] 
> 
> [INFO] Total time: 12.246 s
> [INFO] Finished at: 2015-10-08T21:37:55-04:00
> [INFO] Final Memory: 40M/605M
> [INFO] 
> 
> 
> 
> Thanks,
> 
> Tom Beerbower
> 
>

[jira] [Commented] (ATLAS-199) webapp build fails (grunt + tests)

2015-10-09 Thread Darshan Kumar (JIRA) 

[ 
https://issues.apache.org/jira/browse/ATLAS-199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14950786#comment-14950786
 ] 

Darshan Kumar commented on ATLAS-199:
-

Result of this command :  mvn findbugs:gui
[INFO] 
[INFO] apache-atlas ... SUCCESS [19:10 min]
[INFO] Apache Atlas Typesystem  SUCCESS [02:33 min]
[INFO] Apache Atlas Common  SUCCESS [04:03 min]
[INFO] Apache Atlas Client  SUCCESS [ 35.076 s]
[INFO] Apache Atlas Notification .. SUCCESS [ 24.271 s]
[INFO] Apache Atlas Repository  SUCCESS [02:52 min]
[INFO] Apache Atlas Web Application ... SUCCESS [01:34 min]
[INFO] Apache Atlas Documentation . SUCCESS [01:36 min]
[INFO] Apache Atlas Hive Bridge ... SUCCESS [ 59.990 s]
[INFO] Apache Atlas Distribution .. SUCCESS [02:06 min]
[INFO] 
[INFO] BUILD SUCCESS
[INFO] 
[INFO] Total time: 36:06 min
[INFO] Finished at: 2015-10-09T22:37:16+05:30
[INFO] Final Memory: 32M/68M
[INFO] 

[~suma.shivaprasad] I get the GUI with zero bugs in the folder and I close the 
GUI firebug,after which I see success. Please let me know.

> webapp build fails (grunt + tests)
> --
>
> Key: ATLAS-199
> URL: https://issues.apache.org/jira/browse/ATLAS-199
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.6-incubating
>Reporter: Erik Bergenholtz
>Assignee: Darshan Kumar
>Priority: Critical
>  Labels: patch-available
> Fix For: 0.6-incubating
>
> Attachments: ATLAS-199-v0.patch
>
>
> When building Atlas webapp, I see the following issues:
> mvn clean install:
> {code}
> [INFO] Running 'grunt bower --no-color' in 
> /Users/ebergenholtz/git3/incubator-atlas/dashboard
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time: 34.282 s
> [INFO] Finished at: 2015-09-30T13:55:30-05:00
> [INFO] Final Memory: 35M/420M
> [INFO] 
> 
> [ERROR] Failed to execute goal 
> com.github.eirslett:frontend-maven-plugin:0.0.23:grunt (install bower) on 
> project atlas-webapp: Failed to run task: 'grunt bower --no-color' failed. 
> java.io.IOException: Cannot run program 
> "/Users/ebergenholtz/git3/incubator-atlas/dashboard/node/node" (in directory 
> "/Users/ebergenholtz/git3/incubator-atlas/dashboard"): error=2, No such file 
> or directory -> [Help 1]
> {code}
> Also, if I bypass the grunt task some of the tests fail.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (ATLAS-216) UI: showing invalid date and time values for hive table

2015-10-09 Thread Ayub Khan (JIRA) 

 [ 
https://issues.apache.org/jira/browse/ATLAS-216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ayub Khan updated ATLAS-216:

Attachment: Invalid_Timestamps_for_hivetables.png

UI snapshot attached with invalid date entries

> UI: showing invalid date and time values for hive table
> ---
>
> Key: ATLAS-216
> URL: https://issues.apache.org/jira/browse/ATLAS-216
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.6-incubating
>Reporter: Ayub Khan
> Attachments: Invalid_Timestamps_for_hivetables.png
>
>
> While viewing the hive tables metadata in Atlas UI, I see invalid time values 
> for createTime and transient_lastDdlTime entries. Please check the attached 
> UI snapshot.
> The same query through API results in correct timestamps. Below is the API 
> response.
> {code}
> curl 
> http://localhost:21000/api/atlas/entity/f286e5d3-0514-4f28-9cef-373473cd
> {"requestId":"qtp186909238-384 - 
> 71055c83-f290-4370-a279-24412918fb58","GUID":"f286e5d3-0514-4f28-9cef-373473cd","definition":"{\n
>   
> \"jsonClass\":\"org.apache.atlas.typesystem.json.InstanceSerialization$_Reference\",\n
>   \"id\":{\n
> \"jsonClass\":\"org.apache.atlas.typesystem.json.InstanceSerialization$_Id\",\n
> \"id\":\"f286e5d3-0514-4f28-9cef-373473cd\",\n\"version\":0,\n
> \"typeName\":\"hive_table\"\n  },\n  \"typeName\":\"hive_table\",\n  
> \"values\":{\n\"tableType\":\"MANAGED_TABLE\",\n
> \"name\":\"primary.default.t\",\n\"viewExpandedText\":null,\n
> \"createTime\":1444395991,\n\"description\":null,\n
> \"temporary\":false,\n\"db\":{\n  
> \"jsonClass\":\"org.apache.atlas.typesystem.json.InstanceSerialization$_Id\",\n
>   \"id\":\"cca28963-f7b1-44fd-a631-f4b6f3b09612\",\n  
> \"version\":0,\n  \"typeName\":\"hive_db\"\n},\n
> \"viewOriginalText\":null,\n\"retention\":0,\n\"tableName\":\"t\",\n  
>   \"columns\":[\n  {\n
> \"jsonClass\":\"org.apache.atlas.typesystem.json.InstanceSerialization$_Reference\",\n
> \"id\":{\n  
> \"jsonClass\":\"org.apache.atlas.typesystem.json.InstanceSerialization$_Id\",\n
>   \"id\":\"5f89e208-a9ff-40eb-912b-b4394f8d8c0e\",\n  
> \"version\":0,\n  \"typeName\":\"hive_column\"\n},\n
> \"typeName\":\"hive_column\",\n\"values\":{\n  
> \"comment\":null,\n  
> \"qualifiedName\":\"primary.default.t.salary\",\n  
> \"type\":\"string\",\n  \"name\":\"salary\"\n},\n
> \"traitNames\":[\n  \n],\n\"traits\":{\n  \n  
>   }\n  },\n  {\n
> \"jsonClass\":\"org.apache.atlas.typesystem.json.InstanceSerialization$_Reference\",\n
> \"id\":{\n  
> \"jsonClass\":\"org.apache.atlas.typesystem.json.InstanceSerialization$_Id\",\n
>   \"id\":\"14870ed2-f596-46a3-9500-c720e559703e\",\n  
> \"version\":0,\n  \"typeName\":\"hive_column\"\n},\n
> \"typeName\":\"hive_column\",\n\"values\":{\n  
> \"comment\":null,\n  
> \"qualifiedName\":\"primary.default.t.integer\",\n  
> \"type\":\"int\",\n  \"name\":\"integer\"\n},\n
> \"traitNames\":[\n  \n],\n\"traits\":{\n  \n  
>   }\n  },\n  {\n
> \"jsonClass\":\"org.apache.atlas.typesystem.json.InstanceSerialization$_Reference\",\n
> \"id\":{\n  
> \"jsonClass\":\"org.apache.atlas.typesystem.json.InstanceSerialization$_Id\",\n
>   \"id\":\"535e002f-f7ed-4e6e-a363-4cc38ebc3b46\",\n  
> \"version\":0,\n  \"typeName\":\"hive_column\"\n},\n
> \"typeName\":\"hive_column\",\n\"values\":{\n  
> \"comment\":null,\n  
> \"qualifiedName\":\"primary.default.t.number\",\n  
> \"type\":\"int\",\n  \"name\":\"number\"\n},\n
> \"traitNames\":[\n  \n],\n\"traits\":{\n  \n  
>   }\n  }\n],\n\"comment\":null,\n\"lastAccessTime\":0,\n  
>   \"owner\":\"apathan\",\n\"sd\":{\n  
> \"jsonClass\":\"org.apache.atlas.typesystem.json.InstanceSerialization$_Reference\",\n
>   \"id\":{\n
> \"jsonClass\":\"org.apache.atlas.typesystem.json.InstanceSerialization$_Id\",\n
> \"id\":\"168ba76f-c5db-4398-bded-ed25bb626785\",\n
> \"version\":0,\n\"typeName\":\"hive_storagedesc\"\n  },\n  
> \"typeName\":\"hive_storagedesc\",\n  \"values\":{\n
> \"location\":\"hdfs:\/\/localhost:9000\/user\/hive\/warehouse\/t\",\n
> \"serdeInfo\":{\n  
> \"jsonClass\":\"org.apache.atlas.typesystem.json.InstanceSerialization$_Struct\",\n
>   \"typeName\":\"hive_serde\",\n

[jira] [Comment Edited] (ATLAS-188) Provide Ability to Add Tag to Entity

2015-10-09 Thread Sanjay Patel (JIRA) 

[ 
https://issues.apache.org/jira/browse/ATLAS-188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14950931#comment-14950931
 ] 

Sanjay Patel edited comment on ATLAS-188 at 10/9/15 6:26 PM:
-

[~suma.shivaprasad] I have attached Updated patch ATLAS-188.v2.patch


was (Author: sanjayp):
[~suma.shivaprasad] I have attached Updated patch *ATLAS-188.v2.patch*

> Provide Ability to Add Tag to Entity
> 
>
> Key: ATLAS-188
> URL: https://issues.apache.org/jira/browse/ATLAS-188
> Project: Atlas
>  Issue Type: Task
>Affects Versions: 0.6-incubating
>Reporter: Erik Bergenholtz
>Assignee: Sanjay Patel
>Priority: Critical
> Fix For: 0.6-incubating
>
> Attachments: ATLAS-188.v1.patch, ATLAS-188.v2.patch
>
>
> Atlas UI needs to provide the ability to add a tag to an existing entity (see 
> attached mocks). 
> User Story:
> - User Searches for an entity (i.e. hive_table) from the main search screen
> - User identifies an entity that will get a tag associated with it
> - The user selects 'Add Tag' from the detailed entity screen and fills out 
> the necessary fields based on the tag definition.
> - The tag is attached to the Entity



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: Review Request 39157: Configure Consumer Groups for Notifications

2015-10-09 Thread Suma Shivaprasad 


> On Oct. 9, 2015, 4 p.m., Suma Shivaprasad wrote:
> > notification/src/main/java/org/apache/atlas/kafka/KafkaNotification.java, 
> > line 226
> > 
> >
> > consumerConnector need to be shutdown

This seems to be taken care of in close() already


- Suma


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/39157/#review102064
---


On Oct. 9, 2015, 1:40 a.m., Tom Beerbower wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/39157/
> ---
> 
> (Updated Oct. 9, 2015, 1:40 a.m.)
> 
> 
> Review request for atlas, John Speidel and Shwetha GS.
> 
> 
> Bugs: ATLAS-215
> https://issues.apache.org/jira/browse/ATLAS-215
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> Currently with the notification framework we set the properties so that all 
> consumers are created in a single group...
> 
> //todo take group id as argument to allow multiple consumers??
> properties.put(ConsumerConfig.GROUP_ID_CONFIG, ATLAS_GROUP);
> 
> Having Kafka consumers for both the HOOK and ENTITIES topics in a single 
> group causes this issue ...
> 
> java.lang.IllegalArgumentException: requirement failed: Round-robin 
> assignment is allowed only if all consumers in the group subscribe to the 
> same topics, AND if the stream counts across topics are identical for a given 
> consumer instance.
> Topic ATLAS_ENTITIES has the following available consumer streams: 
> Set(atlas_c6401.ambari.apache.org-1443714948705-e518b690-0)
> Topic ATLAS_HOOK has the following available consumer streams: 
> Set(atlas_c6401.ambari.apache.org-1443714214755-8fd9a5f8-0)
> 
> We shouldn't have HOOK consumers and ENTITIES consumers in the same group.
> 
> 
> Diffs
> -
> 
>   notification/pom.xml 2e12520 
>   notification/src/main/java/org/apache/atlas/kafka/KafkaNotification.java 
> 7b3cf89 
>   
> notification/src/main/java/org/apache/atlas/notification/NotificationHookConsumer.java
>  29194a4 
>   
> notification/src/main/java/org/apache/atlas/notification/NotificationInterface.java
>  d4be07b 
>   
> notification/src/test/java/org/apache/atlas/kafka/KafkaNotificationTest.java 
> 735655c 
> 
> Diff: https://reviews.apache.org/r/39157/diff/
> 
> 
> Testing
> ---
> 
> new unit test added
> 
> mvn clean test
> 
> [INFO] 
> 
> [INFO] BUILD SUCCESS
> [INFO] 
> 
> [INFO] Total time: 12.246 s
> [INFO] Finished at: 2015-10-08T21:37:55-04:00
> [INFO] Final Memory: 40M/605M
> [INFO] 
> 
> 
> 
> Thanks,
> 
> Tom Beerbower
> 
>

Re: Review Request 39157: Configure Consumer Groups for Notifications

2015-10-09 Thread Tom Beerbower 


> On Oct. 9, 2015, 4:23 p.m., Suma Shivaprasad wrote:
> > Where is consumer group for entity notifications from ATLAS taken care of?

Thanks for the review!

For entity notification, some other application (i.e. Ranger) is the consumer.  
The usage would be something like this ...


// Obtain provider through injection…
EntityNotificationConsumerProvider consumerProvider;

EntityNotificationConsumer consumer = consumerProvider.get();

…

while(consumer.hasNext()) {
EntityNotification notification = consumer.next();


Entity entity = notification.getEntity();
…
}

The consumer group would be specified in the application.properties 
configuration along with the other kafka specific configs ...

atlas.kafka.bootstrap.servers=c6401.ambari.apache.org:6667
atlas.kafka.zookeeper.connect=c6401.ambari.apache.org:2181
atlas.kafka.group.id=entityConsumer

... and would be passed into the call to createConsumers() when the 
EntityNotificationConsumer is obtained.

I'll have to merge to read the configuration and pass the consumer group id in 
the entity notification patch https://reviews.apache.org/r/38341/ (which is 
still pending) if this change is pushed first.


- Tom


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/39157/#review102073
---


On Oct. 9, 2015, 1:40 a.m., Tom Beerbower wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/39157/
> ---
> 
> (Updated Oct. 9, 2015, 1:40 a.m.)
> 
> 
> Review request for atlas, John Speidel and Shwetha GS.
> 
> 
> Bugs: ATLAS-215
> https://issues.apache.org/jira/browse/ATLAS-215
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> Currently with the notification framework we set the properties so that all 
> consumers are created in a single group...
> 
> //todo take group id as argument to allow multiple consumers??
> properties.put(ConsumerConfig.GROUP_ID_CONFIG, ATLAS_GROUP);
> 
> Having Kafka consumers for both the HOOK and ENTITIES topics in a single 
> group causes this issue ...
> 
> java.lang.IllegalArgumentException: requirement failed: Round-robin 
> assignment is allowed only if all consumers in the group subscribe to the 
> same topics, AND if the stream counts across topics are identical for a given 
> consumer instance.
> Topic ATLAS_ENTITIES has the following available consumer streams: 
> Set(atlas_c6401.ambari.apache.org-1443714948705-e518b690-0)
> Topic ATLAS_HOOK has the following available consumer streams: 
> Set(atlas_c6401.ambari.apache.org-1443714214755-8fd9a5f8-0)
> 
> We shouldn't have HOOK consumers and ENTITIES consumers in the same group.
> 
> 
> Diffs
> -
> 
>   notification/pom.xml 2e12520 
>   notification/src/main/java/org/apache/atlas/kafka/KafkaNotification.java 
> 7b3cf89 
>   
> notification/src/main/java/org/apache/atlas/notification/NotificationHookConsumer.java
>  29194a4 
>   
> notification/src/main/java/org/apache/atlas/notification/NotificationInterface.java
>  d4be07b 
>   
> notification/src/test/java/org/apache/atlas/kafka/KafkaNotificationTest.java 
> 735655c 
> 
> Diff: https://reviews.apache.org/r/39157/diff/
> 
> 
> Testing
> ---
> 
> new unit test added
> 
> mvn clean test
> 
> [INFO] 
> 
> [INFO] BUILD SUCCESS
> [INFO] 
> 
> [INFO] Total time: 12.246 s
> [INFO] Finished at: 2015-10-08T21:37:55-04:00
> [INFO] Final Memory: 40M/605M
> [INFO] 
> 
> 
> 
> Thanks,
> 
> Tom Beerbower
> 
>

[jira] [Commented] (ATLAS-199) webapp build fails (grunt + tests)

2015-10-09 Thread Darshan Kumar (JIRA) 

[ 
https://issues.apache.org/jira/browse/ATLAS-199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14950512#comment-14950512
 ] 

Darshan Kumar commented on ATLAS-199:
-

ok will look into it. Thanks 

> webapp build fails (grunt + tests)
> --
>
> Key: ATLAS-199
> URL: https://issues.apache.org/jira/browse/ATLAS-199
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.6-incubating
>Reporter: Erik Bergenholtz
>Assignee: Darshan Kumar
>Priority: Critical
>  Labels: patch-available
> Fix For: 0.6-incubating
>
> Attachments: ATLAS-199-v0.patch
>
>
> When building Atlas webapp, I see the following issues:
> mvn clean install:
> {code}
> [INFO] Running 'grunt bower --no-color' in 
> /Users/ebergenholtz/git3/incubator-atlas/dashboard
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time: 34.282 s
> [INFO] Finished at: 2015-09-30T13:55:30-05:00
> [INFO] Final Memory: 35M/420M
> [INFO] 
> 
> [ERROR] Failed to execute goal 
> com.github.eirslett:frontend-maven-plugin:0.0.23:grunt (install bower) on 
> project atlas-webapp: Failed to run task: 'grunt bower --no-color' failed. 
> java.io.IOException: Cannot run program 
> "/Users/ebergenholtz/git3/incubator-atlas/dashboard/node/node" (in directory 
> "/Users/ebergenholtz/git3/incubator-atlas/dashboard"): error=2, No such file 
> or directory -> [Help 1]
> {code}
> Also, if I bypass the grunt task some of the tests fail.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)