[
https://issues.apache.org/jira/browse/AMBARI-20609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16075622#comment-16075622
]
Hadoop QA commented on AMBARI-20609:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12870771/AMBARI-20609.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/11723//console
This message is automatically generated.
> Fix Install Wizard data attribute
> ----------------------------------
>
> Key: AMBARI-20609
> URL: https://issues.apache.org/jira/browse/AMBARI-20609
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
> Affects Versions: 3.0.0
> Reporter: Antonenko Alexander
> Assignee: Antonenko Alexander
> Priority: Critical
> Fix For: 3.0.0
>
> Attachments: AMBARI-20609_additional-fix.patch,
> AMBARI-20609-assign.patch, AMBARI-20609-back-next.patch, AMBARI-20609.patch,
> AMBARI-20609.patch, AMBARI-20609_review.patch, AMBARI-20609-step4.patch,
> AMBARI-20609_step7.patch, AMBARI-20609-step9.patch,
> AMBARI-20609-steps0-3.patch
>
>
> There have been a lot of frontend changes committed to trunk in preparation
> for Ambari 3.0's new look and feel.
> Obviously, this makes our current XPaths incompatible for trunk.
> For starters, we need to make changes to XPaths and other changes necessary
> so that we can at least run Install Wizard against the trunk code base. Also,
> we need to make sure that Ambari Web's code itself is using best practices
> with use of specific IDs and class names, etc.
> We will implement special data attribute for XPaths
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
