On 11/06/2013 11:25 PM, Andrew Stitcher wrote:
On Wed, 2013-11-06 at 18:50 +0000, Gordon Sim wrote:
...
I realise after tracking this down that you did comment in JIRA, but to
me this would have warranted at least a brief email direct to the list
(since JIRA comments are easy to miss, at least in my experience).
Apologies, I was under the impression that the management spec was
*extremely* rarely changed.
Well, 10 times in 2013 so far and I have a pending change already on
review board... updates aren't frequent but it is continually evolving.
I think its a bad idea to have duplicated files. For the management spec
in particular this is bound to lead to confusion, especially since it
hasn't been clearly highlighted. I already spent some time trying to
figure out why changes to the spec had no effect.
I agree entirely.
The java broker no longer uses this. However I'm not sure whether the
Java based QMF API does?
I could find no references outside cpp to management-schema.xml, so I
assume the file is not used elsewhere.
It seems that assumption is correct, in which case there is no point in
leaving the old copy there where its only purpose can be to cause confusion.
If it does then having two separate copies is not in my view acceptable
and moving it without checking what works for the other component seems
unreasonable.
That is why it was duplicated (Justin's preference).
I would argue duplication - especially without any discussion to make
people aware of the issue - would be the worst approach even if
something else was using it, since it would likely result in undetected
divergence of components that previously shared the same file.
If it doesn't then I personally don't mind having this moved to the cpp
tree, but lets remove the other copy to avoid confusion.
I agree, however it is impossible to have a self contained c++ tree at
present without having this file in that tree.
I'll note in passing that the python release pulls in the (AMQP) spec
file without needing it to be copied in svn.
However, as far as the management spec goes it sounds like the cpp tree
might actually be the best place for it since that is the only component
left using it. Duplication of the other files is less serious perhaps.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
