You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by Martin Ritchie <ri...@apache.org> on 2008/10/03 10:27:45 UTC

Re: [discussion] Qman location

2008/10/3 Arnaud Simon <as...@redhat.com>:
>
> ----- "Robert Greig" <ro...@gmail.com> wrote:
>
>> 2008/10/2 Arnaud Simon <as...@redhat.com>:
>>
>> > When we'll provide any additional tool like a command line or WSM
>> imp we'll put those tools under java/tools.
>>
>> Do you mean java/management/tools ?
>>
>> RG
>
> Yes, sorry java/management/tools.
>
> So to summarize the plan is to have:
>
> java
>  |
>  +management
>       |
>       + broker
>       |
>       + client
>       |
>       + common
>       |
>       + tools
>
> Qman current code would be split between java/management/client and java/management/common and the package structure would be:
> org\apache\qpid\management\client
> and
> org\apache\qpid\management\transport
>
> I would also like to move the existing eclipse-plugin from java/management to java/management/tools
>
> So, to summarize the vote is about tow things:
>
> a) []: move Qman code in java/management/client and java/management/common
> b) []: move eclipse-plugin in java/management/tools
>
> Arnaud

If we are going to have a management/tools would the QMan application
not sit better in there? So you would have the shared transport in
common, the client library in client and the QMan tool in tool?

Also think that if we are going to have a vote thread it should be for
a single resolution and not gain additional items as we go along. I
have no problem moving the eclipse-plugin but don't think the '[vote]
QMan location' thread is quite the right place to do that.

just a thought.

Martin

-- 
Martin Ritchie