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

Hemanth Yamijala updated ATLAS-672:
-----------------------------------
    Attachment: ATLAS-672-1.patch

[~bergenholtz], in general +1 for the patch. I just made a few changes in this 
new patch (ATLAS-672-1.patch):

* Left the dashboard (v1) module settings in the pom under comments. That way, 
if someone wants to switch during transition period, they can do so easily.
* There was one failure in RAT checkin when I ran the build. This I fixed by 
making the following entry to RAT exclude files:
{code}
-                        <exclude>.bowerrc</exclude>
+                        <exclude>**/.bowerrc</exclude>
{code}

I tested the patch by building and deploying it. The new UI shows up. Most of 
the existing functionality is intact (with some minor issues that can easily be 
addressed in subsequent JIRAs). Indeed, the new UI looks sleeker at least to me.

If you can review my changes, we could go ahead committing it.

[~j...@nanthrax.net], you mentioned you were testing the new dashboard. Can you 
please let us know if there're any issues you'd like to see fixed in this 
patch, as opposed to taking them as improvements / fixes later? Will wait for a 
day to hear back from you before commit.

> UI: Make dashboard v2 the default UI implementation
> ---------------------------------------------------
>
>                 Key: ATLAS-672
>                 URL: https://issues.apache.org/jira/browse/ATLAS-672
>             Project: Atlas
>          Issue Type: Task
>    Affects Versions: 0.7-incubating
>            Reporter: Erik Bergenholtz
>            Assignee: Erik Bergenholtz
>             Fix For: 0.7-incubating
>
>         Attachments: ATLAS-672-1.patch, ATLAS-672.patch
>
>
> Now that dasboardv2 has been a part of the code base for some time, I propose 
> that we move to using this implementation in favor of the older dashboard 
> implementation.



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

Reply via email to