Hi, On 26 November 2014 at 18:23, Svetoslav Neykov <[email protected]> wrote: >> the loss of copy-to-clipboard > I believe this functionality has been added as a workaround to the > disappearing selection problem. Currently the sensors tab is updated > constantly with the latest state coming from the server. Updating the html > clears any selection in it. It's possible to rewrite this code so it changes > only items which are really updated, avoiding the need for this component.
This is a very useful feature especially with the disappearing-selection problem. However I've just discovered any easy way to keep ZeroClipboard - it's available on a CDN so we can hotlink to that version instead of bundling it ourselves: http://cdnjs.com/libraries/zeroclipboard > I don't mind the tests being skipped, but don't really like the > release-as-a-subset-of-repository idea. What do you think of the approach to > move the test jar files as external projects? It's the same as depending on > testng for example. They can still live in the brooklyn repo as sources. It depends on what "external projects" means exactly. I'm concerned over what effects this would have on our release process, and on potentials contributors being able to modify and add these kinds of resources themselves. To be clear, what I am suggesting is not a good solution, but it is an acceptable (IMO) solution to allow us to get on with the business of releasing software, and to give us some breathing space to consider this problem some more at a later date. Richard.
