You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Yusaku Sako (JIRA)" <ji...@apache.org> on 2014/01/07 02:02:06 UTC
[jira] [Reopened] (AMBARI-3567) Make provisions for
ambari-web/public content to be read from a static location
[ https://issues.apache.org/jira/browse/AMBARI-3567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Yusaku Sako reopened AMBARI-3567:
---------------------------------
Reopening since this is breaking the mvn build process.
It seems that the patch changes the build order.
Before the patch:
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Build Order:
[INFO]
[INFO] Ambari Main
[INFO] Apache Ambari Project POM
[INFO] Ambari Web
[INFO] Ambari Server
[INFO] Ambari Agent
[INFO] Ambari Client
[INFO]
After the patch:
[INFO] Reactor Build Order:
[INFO]
[INFO] Ambari Main
[INFO] Apache Ambari Project POM
[INFO] Ambari Server
[INFO] Ambari Agent
[INFO] Ambari Client
[INFO] Ambari Web
Since the order was changed, it causes the following error:
[INFO] Reactor Summary:
[INFO]
[INFO] Ambari Main ....................................... SUCCESS [1.981s]
[INFO] Apache Ambari Project POM ......................... SUCCESS [0.930s]
[INFO] Ambari Server ..................................... FAILURE [1:04.833s]
[INFO] Ambari Agent ...................................... SKIPPED
[INFO] Ambari Client ..................................... SKIPPED
[INFO] Ambari Web ........................................ SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 1:08.920s
[INFO] Finished at: Mon Jan 06 16:56:12 PST 2014
[INFO] Final Memory: 36M/162M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.codehaus.mojo:rpm-maven-plugin:2.0.1:rpm (default-cli) on project ambari-server: Source location /root/ambari/ambari-server/../ambari-web/public does not exist -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR] mvn <goals> -rf :ambari-server
> Make provisions for ambari-web/public content to be read from a static location
> -------------------------------------------------------------------------------
>
> Key: AMBARI-3567
> URL: https://issues.apache.org/jira/browse/AMBARI-3567
> Project: Ambari
> Issue Type: Improvement
> Components: build
> Affects Versions: 1.4.1
> Environment: Fedora 19
> Reporter: Trevor McKay
> Assignee: Trevor McKay
> Fix For: 1.4.3
>
> Attachments: static-web.patch
>
>
> Nodejs dependencies add to the number of things that have to be packaged in order to include Ambari in Fedora (and potentially other distributions).
> If the content in ambari-web/public can be added to the Ambari source tree and read from that location by ambari-server at build time, then nodejs will not be a required dependency on Fedora. Static web content can be generated as needed and updated in the Ambari source tree.
> To this end, the current maven build system should support an option to skip the ambari-web module at build time.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)