Noel O'Connor created QPID-4166:
---
Summary: Add all possible qpidd configuration settings to
/etc/qpidd.conf
Key: QPID-4166
URL: https://issues.apache.org/jira/browse/QPID-4166
Project: Qpid
Alex Rudyy created QPID-4167:
Summary: Queue attributes are ignored on queue creation with web
management console
Key: QPID-4167
URL: https://issues.apache.org/jira/browse/QPID-4167
Project: Qpid
On Jul 24, 2012, at 5:19 PM, Rajith Attapattu wrote:
On Tue, Jul 24, 2012 at 4:56 PM, Joseph Ottinger j...@enigmastation.com
wrote:
There *are* ways to turn that off - but the easiest is to run once
While this might solve the developer headaches, it still doesn't solve
the issue with
[
https://issues.apache.org/jira/browse/QPID-4167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Rudyy updated QPID-4167:
-
Status: Ready To Review (was: In Progress)
Queue attributes are ignored on queue creation with web
[
https://issues.apache.org/jira/browse/QPID-4167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Rudyy updated QPID-4167:
-
Attachment: 0001-QPID-4167-Fix-setting-of-queue-attributes-via-web-ma.patch
Attached a patch fixxing the
[
https://issues.apache.org/jira/browse/QPID-4167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Rudyy reassigned QPID-4167:
Assignee: Robbie Gemmell (was: Alex Rudyy)
Robbie,
Could you please review and commit the patch
Hi,
It looks for me that the structure of proton-j sub-project will be
quite simple and will not require the creation of complicated building
scripts similar to what we have in qpid java tree right now. I believe
that we can have 2 building systems for proton-j at least on first
stages of the
Umm, I would say the main priority is that Joseph creates the pom such
that proton builds via mvn clean install OOTB (as any good Maven
project should.) As long as he's met that threshold, I don't see a need
anymore for maintaining two sources of records for builds.
Maven is really
Incidentally, since we've talked about it, here's the pom.xml
(attached); this is not a patch (since the patch will need to move
directories). It also targets Java 7 by default; that's easily
changed. (I don't know the target VM yet; IMO, it SHOULD be 7, since 6
is at the end of its support
Rafael Schloming wrote:
The other big issue we had was with integration of the maven built
software into other environments. I don't know if this has changed, but
maven didn't really have a concept of configuration. Rather than
adapting the software to build within the host environment, e.g. use
That should do it, just change the url to Qpid. But before proceeding
with a patch, I would certainly configure the tests in (I guess the
patch doesn't need to include the moved files/folders, just the pom.xml
and instructions on the file movements a committer needs to do for the
pom.xml to
Well, as far as I could tell, there *are* no tests yet - which worries
me. But that's part of what motivated my desire to move to Maven; we
can configure Arquillian to crank up a Qpid instance so that we can
run tests as part of the build without too much fuss.
And sure, if there're any things we
OK, another possible bell-and-whistle to look at: Configuring in
checkstyle (http://checkstyle.sourceforge.net/) and possibly PMD
(http://pmd.sourceforge.net/pmd-5.0.0/) so the project won't build if
there's any code formatting errors. CXF uses both so feel free to raid
its poms. I just
Hi Everyone,
I believe this has been mentioned in a few threads now, but in order to
release Proton, it needs to have it's own JIRA project. (I tried
managing this with a component within the Qpid JIRA project, but
versions are scoped to projects not components, so this simply won't
work.) As I'd
[X] Yes, create a JIRA project for Proton.
[ ] No, bah, humbug, Proton can suck it.
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[X] Yes, create a JIRA project for Proton.
Rajith
On Wed, Jul 25, 2012 at 1:39 PM, Gordon Sim g...@redhat.com wrote:
[X] Yes, create a JIRA project for Proton.
[ ] No, bah, humbug, Proton can suck it.
-
To unsubscribe,
[X] Yes, create a JIRA project for Proton.
[ ] No, bah, humbug, Proton can suck it.
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
On Wed, Jul 25, 2012 at 01:34:52PM -0400, Rafael Schloming wrote:
Hi Everyone,
I believe this has been mentioned in a few threads now, but in order to
release Proton, it needs to have it's own JIRA project. (I tried
managing this with a component within the Qpid JIRA project, but
versions
[X] Yes, create a JIRA project for Proton.
[ ] No, bah, humbug, Proton can suck it.
Andrew
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
On Wed, 2012-07-25 at 12:50 -0400, Joseph Ottinger wrote:
Well, as far as I could tell, there *are* no tests yet - which worries
me. But that's part of what motivated my desire to move to Maven; we
can configure Arquillian to crank up a Qpid instance so that we can
run tests as part of the
On 07/25/2012 05:06 PM, Glen Mazza wrote:
The problem with providing an Ant build is that non-Maven users, never
having worked with it, tend to awfulize Maven, and then stick with Ant,
continuing their misconception of Maven. Maven is really an ice cream
cone, not a brussels sprout, but
[X] Yes, create a JIRA project for Proton.
[ ] No, bah, humbug, Proton can suck it.
Cliff
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
Man, I am so tempted.
But, no. I mustn't vote frivolously just because I like the wording.
I must be grown up about this.
Must ... not ... fool around .
[X] Yes, create a JIRA project for Proton.
[ ] No, bah, humbug, Proton can suck it.
phew.
[X] Yes, create a JIRA project for Proton.
[ ] No, bah, humbug, Proton can suck it.
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
From: Darryl L. Pierce dpie...@redhat.com
The first entry ignores temporary files from Emacs and similar editors.
---
.gitignore | 1 +
1 file changed, 1 insertion(+)
create mode 100644 .gitignore
diff --git a/.gitignore b/.gitignore
new file mode 100644
index 000..b25c15b
--- /dev/null
From: Darryl L. Pierce dpie...@redhat.com
The library file that's generated is named libcproton_ruby.so which
needs to be renamed in order to be used.
---
examples/ruby/EXAMPLES| 1 +
proton-c/bindings/CMakeLists.txt | 6 ++
proton-c/bindings/ruby/CMakeLists.txt | 29
From: rhs rhs@13f79535-47bb-0310-9956-ffa450edef68
git-svn-id: https://svn.apache.org/repos/asf/qpid/proton/trunk@1356935
13f79535-47bb-0310-9956-ffa450edef68
---
proton-c/include/proton/engine.h | 1 +
proton-c/include/proton/error.h | 1 +
proton-c/include/proton/messenger.h |
From: Darryl L. Pierce dpie...@redhat.com
The example apps are:
* recv.rb - Listens on the default port and receives messages
* send.rb - Sends messages that are processed by recv.rb
---
examples/ruby/EXAMPLES | 5
examples/ruby/recv.rb | 70
From: Darryl L. Pierce dpie...@redhat.com
The underscores were causing the Ruby language bindings to output
warning errors concerning their names.
---
proton-c/include/proton/buffer.h| 4 ++--
proton-c/include/proton/codec.h | 4 ++--
proton-c/include/proton/driver.h| 4 ++--
From: Darryl L. Pierce dpie...@redhat.com
* server.rb - Acts as the intermediary, storing messages in mailboxes.
* post.rb - Submits messages for storing in mailboxes.
* fetch.rb - Retrieves messages from mailboxes.
---
examples/ruby/EXAMPLES | 4 +
examples/ruby/fetch.rb | 204
[
https://issues.apache.org/jira/browse/QPID-4141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keith Wall updated QPID-4141:
-
Component/s: Java Broker
Fix Version/s: 0.17
Patch applied.
Add LVQ/SortedQueue
[
https://issues.apache.org/jira/browse/QPID-4141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keith Wall updated QPID-4141:
-
Attachment: (was: 0001-QPID-4141-WIP.patch)
Add LVQ/SortedQueue documentation to java docbook
[
https://issues.apache.org/jira/browse/QPID-4141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keith Wall reassigned QPID-4141:
Assignee: Philip Harvey (was: Keith Wall)
Hi Phil, would you review this change please?
[
https://issues.apache.org/jira/browse/QPID-4164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keith Wall updated QPID-4164:
-
Component/s: Java Management : JMX Console
Java Broker BDB Store
Management
[X] Yes, create a JIRA project for Proton.
[ ] No, bah, humbug, Proton can suck it.
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
On Wed, 2012-07-25 at 13:34 -0400, Rafael Schloming wrote:
[X] Yes, create a JIRA project for Proton.
[ ] No, bah, humbug, Proton can suck it.
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional
Hi Everyone,
There's been a lot of good discussion about proton on the dev list,
however, despite my encouragement, many interested parties do not follow
the qpid dev list and instead email me directly as a matter of
convenience. It's my belief that a proton mailing list would help
encourage
[x ] Yes, create pro...@qpid.apache.org
Rajith
On Wed, Jul 25, 2012 at 3:05 PM, Rafael Schloming rafa...@redhat.com wrote:
Hi Everyone,
There's been a lot of good discussion about proton on the dev list,
however, despite my encouragement, many interested parties do not follow
the qpid dev
[X] Yes, create a JIRA project for Proton.
[ ] No, bah, humbug, Proton can suck it.
- Original Message -
Hi Everyone,
I believe this has been mentioned in a few threads now, but in order
to
release Proton, it needs to have it's own JIRA project. (I tried
managing this with a
[X] Yes, create pro...@qpid.apache.org
[ ] No, people who don't follow dev@qpid.apache.org shouldn't get a say.
- Original Message -
Hi Everyone,
There's been a lot of good discussion about proton on the dev list,
however, despite my encouragement, many interested parties do not
[
https://issues.apache.org/jira/browse/QPID-4134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Darryl L. Pierce updated QPID-4134:
---
Attachment: 0003-Adds-a-Cmake-target-to-generate-a-source-tarball-for.patch
[
https://issues.apache.org/jira/browse/QPID-4134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Darryl L. Pierce updated QPID-4134:
---
Attachment: (was:
0001-Adds-a-Cmake-target-to-generate-a-source-tarball-for.patch)
[
https://issues.apache.org/jira/browse/QPID-4134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13422525#comment-13422525
]
Darryl L. Pierce commented on QPID-4134:
The updated patches fix the issues brought
[X] Yes, create pro...@qpid.apache.org
[ ] No, people who don't follow dev@qpid.apache.org shouldn't get a say.
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[X] Yes, create pro...@qpid.apache.org
[ ] No, people who don't follow dev@qpid.apache.org shouldn't get a say.
next Rafi vote:
[ ] I like Motherhood and apple pie.
[ ] I am a death-cult weirdo who should be locked up or maybe just shot.
( please check one box only. )
[X] Yes, create pro...@qpid.apache.org
[ ] No, people who don't follow dev@qpid.apache.org shouldn't get a say.
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
This looks like a patch for a commit I made on trunk a while back. Did
something go awry with creating the patch set?
--Rafael
On Wed, 2012-07-25 at 14:05 -0400, Darryl L. Pierce wrote:
From: rhs rhs@13f79535-47bb-0310-9956-ffa450edef68
git-svn-id:
(non-binding) [X] No, people who don't follow dev@qpid.apache.org shouldn't
get a say.
It's too early on for proton to have its own mailing lists--instead, people
should be asking questions about it on the Qpid Users' List, or following
development on the dev list. This way regular Qpid-ers
[ X] Yes, create pro...@qpid.apache.org
[ ] No, people who don't follow dev@qpid.apache.org shouldn't get a say.
Cliff
On Wed, Jul 25, 2012 at 12:05 PM, Rafael Schloming rafa...@redhat.com wrote:
Hi Everyone,
There's been a lot of good discussion about proton on the dev list,
however,
[X] Yes, create pro...@qpid.apache.org
[ ] No, people who don't follow dev@qpid.apache.org shouldn't get a say.
--
Darryl L. Pierce, Sr. Software Engineer @ Red Hat, Inc.
Delivering value year after year.
Red Hat ranks #1 in value among software vendors.
http://www.redhat.com/promo/vendor/
[
https://issues.apache.org/jira/browse/QPID-4134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Darryl L. Pierce updated QPID-4134:
---
Attachment: (was:
0001-Statically-linked-the-common-swig-files-into-the-Per.patch)
[
https://issues.apache.org/jira/browse/QPID-4134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Darryl L. Pierce updated QPID-4134:
---
Attachment: (was:
0003-Adds-a-Cmake-target-to-generate-a-source-tarball-for.patch)
[
https://issues.apache.org/jira/browse/QPID-4134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Darryl L. Pierce updated QPID-4134:
---
Attachment: (was:
0002-Installs-the-qpid.i-file-into-the-data-directory.patch)
[
https://issues.apache.org/jira/browse/QPID-4134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Darryl L. Pierce updated QPID-4134:
---
Attachment: 0003-Adds-a-Cmake-target-to-generate-a-source-tarball-for.patch
On 24 July 2012 18:41, Gordon Sim g...@redhat.com wrote:
On 07/23/2012 09:38 PM, Robbie Gemmell wrote:
I wouldn't particularly be in favour of Ant+Ivy for proton.
Any particular reason?
Because I think more people (excluding some of us, obviously) would prefer
that we use maven instead.
On 07/25/2012 04:49 PM, Robbie Gemmell wrote:
Even philosophically it seemed wrong to me - I want to compile my changes
and it goes off looking for any updates to jar files the project or the
tool itself might use. That sort of system update seems to me like it
should be an entirely separate
As others have indicated, many of the points being raised are basically
solvable 'problems'. I really doubt we would be the first project in the
world to use maven that might be included in a distro (or say twenty, for
projects with more widespread reach).
I understand that it might not be the
On 24 July 2012 23:09, Rajith Attapattu rajit...@gmail.com wrote:
On Tue, Jul 24, 2012 at 5:32 PM, Joseph Ottinger j...@enigmastation.com
wrote:
Fair enough. IMO, Maven is *the* build system for Java - people behind
a security layer haven't proven to be impossible to serve with Maven,
and
I also took Alex's suggestion to mean leaving the Ant build in place and
then adding a Maven build too.
Whilst I have stated my dislike for this idea in the past in relation to
the main Qpid tree, if this is what it took to have a maven build for
proton I think it would be the way to go, i.e.
[
https://issues.apache.org/jira/browse/QPID-4164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keith Wall updated QPID-4164:
-
Status: Ready To Review (was: In Progress)
Management moveMessage/copyMessage functions fail to
[
https://issues.apache.org/jira/browse/QPID-4164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keith Wall updated QPID-4164:
-
Affects Version/s: 0.18
0.16
Fix Version/s: (was: 0.18)
[
https://issues.apache.org/jira/browse/QPID-4164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keith Wall reassigned QPID-4164:
Assignee: Robbie Gemmell (was: Keith Wall)
Management moveMessage/copyMessage functions fail
On 22 July 2012 00:53, Justin jr...@redhat.com wrote:
Hi, folks. RC1 is ready at revision 1363863 of our product branch.
Get it here:
http://people.apache.org/~**jross/qpid-0.18-rc1/http://people.apache.org/~jross/qpid-0.18-rc1/
There were many changes between beta and RC1:
63 matches
Mail list logo
