You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@atlas.apache.org by "Sanjay Patel (JIRA)" <ji...@apache.org> on 2015/12/11 04:01:11 UTC
[jira] [Comment Edited] (ATLAS-199) webapp build fails (grunt +
tests)
[ https://issues.apache.org/jira/browse/ATLAS-199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15052070#comment-15052070 ]
Sanjay Patel edited comment on ATLAS-199 at 12/11/15 3:00 AM:
--------------------------------------------------------------
[~suma.shivaprasad] We did tried following solutions:
According to http://maven.apache.org/guides/introduction/introduction-to-profiles.html we can not use ${project.build.directory} in <missing>/<exists> tag,
here we have to hard code target path.
So for that i have tried following solutions:
1. Directly hard coding target path
2. I have used ${basedir} - this also not worked as we can't use ${project.build.directory}
3. I had tried by defining property in root pom.xml but in this also we have to use ${property} which will not work again as per http://maven.apache.org/guides/introduction/introduction-to-profiles.html
In first solution everything works fine but after mvn clean install when I am doing mvn clean package -Pdist at that time the
dashboard module does fails with error that it can not find local node and at this time it was executing profile with id grunt-task.
this happens because mvn clean is not completed for dashboard module and it is able to find node, node_modules and dist/lib directories in dashboard/target
folder so it is not activating profiles with ids install-node, install-node_modules and bower-install. Now when maven execution comes to execute profile with ID grunt-task at that time mvn clean for dashboard module is completed and it can't able to find
node as its profile is not executed.
Second and Third option also not working as per http://maven.apache.org/guides/introduction/introduction-to-profiles.html
Other possible solutions in progress:
1. Activate profiles using environment variables
2. Plugin execution(<execution></execution>) as per phase
3. Use ant-run plugin and define a task/target for different execution
was (Author: sanjayp):
[~suma.shivaprasad] We did tried following solutions:
According to http://maven.apache.org/guides/introduction/introduction-to-profiles.html we can not use ${project.build.directory} in <missing>/<exists> tag,
here we have to hard code target path.
So for that i have tried following solutions:
1. Directly hard coding target path
2. I have used ${basedir} - this also not worked as we can't use ${project.build.directory}
3. I had tried by defining property in root pom.xml but in this also we have to use ${property} which will not work again as per http://maven.apache.org/guides/introduction/introduction-to-profiles.html
In first solution everything works fine but after mvn clean install when I am doing mvn clean package -Pdist at that time the
dashboard module does fails with error that it can not find local node and at this time it was executing profile with id grunt-task.
this happens because mvn clean is not completed for dashboard module and it is able to find node, node_modules and dist/lib directories in dashboard/target
folder so it is not activating profiles with ids install-node, install-node_modules and bower-install. Now when maven execution comes to execute profile with ID grunt-task at that time mvn clean for dashboard module is completed and it can't able to find
node as its profile is not executed.
Second and Third option also not working as per http://maven.apache.org/guides/introduction/introduction-to-profiles.html
Other possible solutions in progress:
1. Activate profiles using environment variables
2. Plugin execution(<execution></execution>) as per phase
3. Use ant-run plugin and define a task/target
> 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: Sanjay Patel
> Priority: Critical
> Labels: ATLAS-UI-BUGS
> 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)