[
https://issues.apache.org/jira/browse/ZOOKEEPER-678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Colin Goodheart-Smithe updated ZOOKEEPER-678:
---------------------------------------------
Attachment: ZooInspector.zip
The submitted zip file contains the updates Patrick asked for. The zip
contains the zooinspector folder for the contrib folder. It also contains the
findbugs report and the RAT report. The RAT report identifies 3 files without
licence headers. These are the EPL licence file and two .cfg files. These
files are generated by the application and are used for setting the defaults to
use for connection settings and for the nodeviewers used on first start up. Do
these need licence headers since they are generated by the application? The
reason they need to be submitted is so that the defaults can be determined the
first time the application is run.
> Browser application to view and edit the contents of a zookeeper instance
> -------------------------------------------------------------------------
>
> Key: ZOOKEEPER-678
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-678
> Project: Zookeeper
> Issue Type: New Feature
> Affects Versions: 3.3.0
> Reporter: Colin Goodheart-Smithe
> Assignee: Colin Goodheart-Smithe
> Fix For: 3.3.0
>
> Attachments: zooInspector.sh, ZooInspector.zip, ZooInspector.zip,
> ZooInspector.zip
>
>
> An application which shows a tree view of the nodes currently in a zookeeper
> instance and allow the user to view and update the contents of the nodes as
> well as allowing users to add and remove nodes from the tree, similar in use
> to the Luke application in the Lucene project.
> I have a list of other features that I want to add to this application but I
> wanted to gauge the response before I implemented them all. I have found
> this useful when debugging my application and thought that it may be useful
> to others.
> I was going to submit this as a patch file but I have used some icon files
> and one library which isn't available in the maven/ivy repositories and these
> don't seem to work when creating a patch file using subversion. Because of
> this I have attached a zip containing this application to this issue. If
> there is a better way to submit this please let me know.
> The zip contains two directories, the src directory contains the source as it
> would be added to the contrib folder and the build folder contains a build
> version of the with a runnable jar.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
