Hi Martin, sorry for delay.Well, I'm generating that artifact running (from
java/management/client directory) :
> ant
> ant gzip-release
After that, under java/management/client/release/ I have that file (tar &
zip archives are in the same folder too).
I'm not really sure about this procedure; I
On Tue, 2009-05-05 at 18:01 -0400, Steve Huston wrote:
> I've been working on building the ACL plugin on Windows. The plugin
> links against the broker library to pick up the qmf-gen-generated
> ACL-related classes/events. This is failing on Windows because the
> qmf-gen stuff isn't inserting expor
2009/5/4 Andrea Gazzarini :
> Hi Martin, the filename is qpid-management-client-0.5.tar.gz.I saw
> https://issues.apache.org/jira/browse/QPID-1753
> Should I update that issue? I saw that all its siblings are left empty...
Hi Andrea,
Was looking to do an RC2 today but I don't see a
qpid-managemen
I've been working on building the ACL plugin on Windows. The plugin
links against the broker library to pick up the qmf-gen-generated
ACL-related classes/events. This is failing on Windows because the
qmf-gen stuff isn't inserting export directives.
Much more than just the ACL stuff gets generated
Except for a very small set of issues I believe that the cmake Win32/VC9
build is as good or better than the hard coded build with checked in
project files.
I propose that we remove the .sln and .vcproj files after the weekend
and stop having to maintain 3 different build systems.
Andrew
-
[
https://issues.apache.org/jira/browse/QPID-1731?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Huston resolved QPID-1731.
Resolution: Fixed
Pete's patches and additions have been integrated at trunk r771776.
> Need to add
Hi,
Pete McKinnon's contribution of a VS project and code to help the qmf
agent library build on Windows triggered some build warnings and I'm
not sure what the original intent of this code is. I'm hoping someone
can help me understand it.
The problems arise because qpid/agent/ManagementAgent.h de
Rajith Attapattu wrote:
Hi All,
I have prototyped a new configuration for the JMS Destination
abstraction, that addresses some of the issues associated with our
previous binding URL format.
The proposal is organized as follows.
1. Design concepts/notes
2. Configuration format with examples
3. C
I'm not sure that the form you have is more conveniant. It's harder to
parse from a qpid pov and somewhat more error prone to write,
primarily due to (users) having to keep count of quotes etc. The
client has to have a parser, which if it was just flat props we'd get
for free. I know properties fil
Conceptually it is what you put down in the more verbose format.
The more compact form is just a convenient way of expressing it in the
JNDI props file which is the only config mechanism we support.
So in some other config source the more verbose form could be used.
Regards,
Rajith
On Mon, May 4
[
https://issues.apache.org/jira/browse/QPID-1838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gordon Sim reassigned QPID-1838:
Assignee: Joshua Kramer
> Create ACL Plugin based on SELinux
> --
>
Aidan Skinner wrote:
On Mon, May 4, 2009 at 8:15 PM, Steve Huston wrote:
Hi Josh,
Can someone please assign QPID-1838 to joshuak ?
Your name doesn't show up on the list of people to which the issue can
be assigned. I'm not a JIRA expert, but maybe someone knowledgable can
say what this mean
12 matches
Mail list logo