[
https://issues.apache.org/jira/browse/QPID-5527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13887896#comment-13887896
]
Emmanuel Bourg commented on QPID-5527:
--
Thank you Robbie. I could have closed the pull
Emmanuel Bourg created QPID-5527:
Summary: Upgrade to Jetty 8
Key: QPID-5527
URL: https://issues.apache.org/jira/browse/QPID-5527
Project: Qpid
Issue Type: Task
Components: Java
Emmanuel Bourg created QPID-4016:
Summary: Official Windows installer
Key: QPID-4016
URL: https://issues.apache.org/jira/browse/QPID-4016
Project: Qpid
Issue Type: Task
Components
Thank you very much for the information Keith. Do you think I can
provide a patch to restore the ability to open a connection without
specifying explicitely the delegate? Is there a chance that it will be
accepted?
Emmanuel Bourg
Le 20/04/2012 10:39, Keith W a écrit :
Hi Emmanuel
You
SASL).
At this point I'm a bit lost. Couldn't the delegate be initialized
automatically with a basic implementation and SASL not checked if it's
not used? Is the delegate essential for establishing the connection?
Emmanuel Bourg
[1] http://ebourg.github.com/qpid-hessian
smime.p7s
[
https://issues.apache.org/jira/browse/QPID-3914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Bourg updated QPID-3914:
-
Summary: SSL Client Authentication support for the Windows C++ client
(was: SSL Cleint
: Bug
Components: Java Broker
Affects Versions: 0.14, 0.16
Reporter: Emmanuel Bourg
{{qpid-server.bat}} in the Qpid 0.14 release and on the trunk fails to work on
Windows XP with Java 6u31. The following trace appears on the console:
{code}
Warning: Qpid classpath
[
https://issues.apache.org/jira/browse/QPID-3961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Bourg updated QPID-3961:
-
Affects Version/s: (was: 0.16)
I didn't notice the .bat left environment variables behind, I
[
https://issues.apache.org/jira/browse/QPID-3961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Bourg resolved QPID-3961.
--
Resolution: Invalid
qpid-server.bat doesn't work (MalformedURLException: unknown protocol
[
https://issues.apache.org/jira/browse/QPID-3961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13257026#comment-13257026
]
Emmanuel Bourg commented on QPID-3961:
--
Yes that's fine with the trunk, sorry
Le 27/04/2011 21:34, Jonathan Robie a écrit :
Would there be copyright issues?
With the proper copyright notice on the Javadoc pages there is nothing
to worry about.
Emmanuel Bourg
smime.p7s
Description: S/MIME Cryptographic Signature
/tree/light-client
Emmanuel Bourg
-
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org
in the central repo and I can
confirm it works great.
Do you think it's possible to publish the javadoc for the latest release
on the Qpid site?
Emmanuel Bourg
-
Apache Qpid - AMQP Messaging Implementation
Project: http
the
Qpid code, be it on the client or on the server side.
Emmanuel Bourg
-
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org
[
https://issues.apache.org/jira/browse/QPID-2498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13022792#comment-13022792
]
Emmanuel Bourg commented on QPID-2498:
--
I refreshed the patch on Github:
https
These instructions are for a Maven or an Ant+Ivy setup. For Qpid we used
an Ant+Maven Task setup, so I don't really know how to publish to Nexus
with our build.
Emmanuel Bourg
smime.p7s
Description: S/MIME Cryptographic Signature
[
https://issues.apache.org/jira/browse/QPID-2693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13012593#comment-13012593
]
Emmanuel Bourg commented on QPID-2693:
--
I've made some tests with session.processed
system :) -
I believe it's best to discuss that important topic in it's own thread or
atleast in a separate email from this one:).
I will wait for some response on the structure before I get into
discussing the build system.
*cough* Maven anyone ? ;)
Emmanuel Bourg
[
https://issues.apache.org/jira/browse/QPID-3149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13009722#comment-13009722
]
Emmanuel Bourg commented on QPID-3149:
--
It would be nice if the Hudson setup could
Le 09/03/2011 12:40, Robbie Gemmell a écrit :
Yes I noticed, I meant an example with it turned on hehe :)
Ok :) There are some examples in these issues from the Commons CLI project:
https://issues.apache.org/jira/browse/CLI-137
https://issues.apache.org/jira/browse/CLI-156
Emmanuel Bourg
and adds complexity to our queries.
+1
That would be almost equivalent to dropping the odd/even numbering.
The next step would be to name the development version as next release
number-dev or -snapshot and Qpid would be just like every other project
out there ;)
Emmanuel Bourg
smime.p7s
at the settings and try to
enable it ?
Emmanuel Bourg
smime.p7s
Description: S/MIME Cryptographic Signature
it changed?
Thank you Robbie,
The comments in QPID-2693 have several code blocks that are formatted as
plain text.
Emmanuel Bourg
smime.p7s
Description: S/MIME Cryptographic Signature
[
https://issues.apache.org/jira/browse/QPID-2693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13004483#comment-13004483
]
Emmanuel Bourg commented on QPID-2693:
--
This is slightly more difficult to test since
Le 15/02/2011 17:21, Rajith Attapattu a écrit :
Hi All,
It seems there is good support for adding a pre-commit hook for checking
JIRA reference.
While we are at it, I'd like to draw your attention to another problem that
makes a release managers job unnecessarily tedious.
We all have been
[
https://issues.apache.org/jira/browse/QPID-2693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12986555#action_12986555
]
Emmanuel Bourg commented on QPID-2693:
--
Thank you for the update Robbie. I ran another
official
Maven artifacts. I think it should even be a release goal.
Emmanuel Bourg
smime.p7s
Description: S/MIME Cryptographic Signature
: Emmanuel Bourg
Priority: Trivial
Fix For: 0.9
slf4j has been updated to the version 1.6.1 recently, but the corresponding pom
files were not updated in qpid/java/lib/poms. The 1.4.0 poms should be removed
and replaced by these:
http://repo1.maven.org/maven2/org/slf4j/slf4j
Just a suggestion, on the page release_notes_0.8.html I would merge the
0.8 and 0.7 sections since 0.7 is of no interest for end users. I would
also put the new features first, and push the tasks to the bottom.
Emmanuel Bourg
Le 06/12/2010 01:17, Robbie Gemmell a écrit :
Hi everyone,
Here
[
https://issues.apache.org/jira/browse/QPID-2693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Bourg updated QPID-2693:
-
Attachment: qpid-dump.txt
qpid-log.txt
I ran a new test to collect more
[
https://issues.apache.org/jira/browse/QPID-2693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12964689#action_12964689
]
Emmanuel Bourg commented on QPID-2693:
--
An extract of the the client code used to send
[
https://issues.apache.org/jira/browse/QPID-2693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12964691#action_12964691
]
Emmanuel Bourg commented on QPID-2693:
--
On the consumer side the connection
Hi,
I've found a minor issue with the Java broker. On Debian the qpid.start
script doesn't work:
ebo...@sirius:~/qpid-broker-0.8/bin$ ./qpid.start
./qpid.start: line 21: exec: qpid-server: not found
I had to replace exec with sh to get it to work.
Emmanuel Bourg
Le 14/11/2010 23
to 0.8, otherwise people will keep asking what happened to the
0.7 release.
Personally I still think this release should have been Qpid 0.7 and not
0.8, the alternatives to an odd/even numbering were never seriously
discussed on the list.
Emmanuel Bourg
smime.p7s
Description: S/MIME
[
https://issues.apache.org/jira/browse/QPID-2693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12929519#action_12929519
]
Emmanuel Bourg commented on QPID-2693:
--
Thank you for the tests Robbie. I tried again
[
https://issues.apache.org/jira/browse/QPID-2498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Bourg updated QPID-2498:
-
Attachment: mina-upgrade.patch
Upgrade Mina to 1.1.7
Thank you for taking care of this Andrew. Do you know if it will make it
into the 0.8 release?
I attached a diff to JIRA.
Emmanuel Bourg
Le 19/10/2010 09:18, Andrew Kennedy a écrit :
Thanks for that. I hadn't seen some of the changes you made there, so I
have added them to the branch code
:)
Emmanuel Bourg
smime.p7s
Description: S/MIME Cryptographic Signature
[
https://issues.apache.org/jira/browse/QPID-2693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Bourg updated QPID-2693:
-
Targeting the issue to 0.7 to get more visibility for the next release.
Broker instability
[
https://issues.apache.org/jira/browse/QPID-2693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Bourg updated QPID-2693:
-
Fix Version/s: 0.7
Broker instability with the topic exchange
[
https://issues.apache.org/jira/browse/QPID-2498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12922357#action_12922357
]
Emmanuel Bourg commented on QPID-2498:
--
I updated the patch, it's now available
connection from a
user.
Thank you Sorin. My use case is slightly different though, rather than
vetoing a new connection I'd like to close the previous one from the
same account. The goal is to prevent the users from abusing the service
by sharing a single account among several users.
Emmanuel
Hi,
Is there a way to enforce a per account exclusive access to the broker?
For example if a user has an opened connection to the broker, when he
opens another connection the first one is automatically closed.
Emmanuel Bourg
smime.p7s
Description: S/MIME Cryptographic Signature
[
https://issues.apache.org/jira/browse/QPID-1916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Bourg updated QPID-1916:
-
Attachment: genpom.patch
Maven releases for the client and management jars
());
}
Emmanuel Bourg
smime.p7s
Description: S/MIME Cryptographic Signature
Replace the remaining references to the incubator
-
Key: QPID-2709
URL: https://issues.apache.org/jira/browse/QPID-2709
Project: Qpid
Issue Type: Task
Reporter: Emmanuel Bourg
[
https://issues.apache.org/jira/browse/QPID-2709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Bourg updated QPID-2709:
-
Attachment: incubator.patch
This patch updates the most visible references to the incubator
: 0.7
Environment: java version 1.6.0_12
Java(TM) SE Runtime Environment (build 1.6.0_12-b04)
Java HotSpot(TM) 64-Bit Server VM (build 11.2-b01, mixed mode)
Linux 2.6.24-11-pve #1 SMP PREEMPT Fri May 14 09:28:08 CEST 2010 x86_64
GNU/Linux
Reporter: Emmanuel Bourg
Le 23/06/2010 21:55, Marnie McCormack a écrit :
I don't think we've seen this issue before - probably best to raise it as a
JIRA with a blocker priority for 0.7 I think ?
Thank you Marnie. I filed QPID-2693, I hope I provided enough details.
Emmanuel Bourg
smime.p7s
Description: S/MIME
[
https://issues.apache.org/jira/browse/QPID-2526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Bourg reopened QPID-2526:
--
Reopening sorry, the gen_logging target moved to module.xml and breaks again
when the path
[
https://issues.apache.org/jira/browse/QPID-2526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12881630#action_12881630
]
Emmanuel Bourg commented on QPID-2526:
--
Here is how to fix this:
{code}
Index:
broker
Hi,
I ran the Java broker from the trunk today and I noticed a new message
on the console when a client connects and open a queue:
*** Reconfiguring queue with config:null
Anyone know what this means?
Emmanuel Bourg
smime.p7s
Description: S/MIME Cryptographic Signature
appears once, then the
IllegalArgumentException appears many times.
Emmanuel Bourg
2010-06-23 15:14:59,912 [WARN ] UNHANDLED:
[ssn:3ea4e882-cd75-44a0-af49-a39bf0d1fd2d] ch=0
SessionRequestTimeout(timeout=0)
2010-06-23 15:15:00,504 [WARN ] UNHANDLED:
[ssn:ba461728-265e-4119-a85b-b10f7f0da788
Le 23/06/2010 15:56, Martin Ritchie a écrit :
Means I left in some debug for processing topic configuration.
Shall be sorted directly.
Nothing to worry about then :) Thank you.
Emmanuel Bourg
smime.p7s
Description: S/MIME Cryptographic Signature
[
https://issues.apache.org/jira/browse/QPID-2526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Bourg reopened QPID-2526:
--
Reopening because the same issue has been reintroduced in the build file of the
slow consumer
[
https://issues.apache.org/jira/browse/QPID-2526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Bourg updated QPID-2526:
-
Attachment: build-slowconsumer.patch
Ant build fails if the path contains a space character
[
https://issues.apache.org/jira/browse/QPID-2526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12876867#action_12876867
]
Emmanuel Bourg commented on QPID-2526:
--
That was fast, thank you!
Ant build fails
Reporter: Emmanuel Bourg
Priority: Trivial
Fix For: 0.7
A Java broker packaged on Windows will not run on Linux due to the CR LF line
endings in the shell scripts controlling the server.
A solution would be to force the eol-style in Subversion for these files
,
MessageAcquireMode.PRE_ACQUIRED, new Header(deliveryProps), msg);
Emmanuel Bourg
smime.p7s
Description: S/MIME Cryptographic Signature
count remained at zero. I should have checked first before
asking, sorry for the trouble.
Thanks everyone for the help!
Emmanuel Bourg
smime.p7s
Description: S/MIME Cryptographic Signature
the message count increasing
for this queue. I tried to set a TTL on the messages produced but that
didn't change anything, the queue keeps growing.
Did I miss something?
Emmanuel Bourg
smime.p7s
Description: S/MIME Cryptographic Signature
there could be one jar per version, and the user would keep
only those he needs.
Emmanuel Bourg
smime.p7s
Description: S/MIME Cryptographic Signature
[
https://issues.apache.org/jira/browse/QPID-2498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Bourg updated QPID-2498:
-
Attachment: mina-update.patch
Updated patch for the latest trunk
Upgrade Mina to 1.1.7
[
https://issues.apache.org/jira/browse/QPID-2498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Bourg updated QPID-2498:
-
Attachment: (was: mina-poms.patch)
Upgrade Mina to 1.1.7
[
https://issues.apache.org/jira/browse/QPID-2498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Bourg updated QPID-2498:
-
Attachment: (was: mina2.patch)
Upgrade Mina to 1.1.7
[
https://issues.apache.org/jira/browse/QPID-2498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Bourg updated QPID-2498:
-
Attachment: (was: mina.patch)
Upgrade Mina to 1.1.7
Le 27/05/2010 02:35, Martin Ritchie a écrit :
Don't for get to count your favourite slf4j binding to make the total
size of a usable client.
SLF4J 1.6 has been released earlier this month. The bindings are now
optional and you can run with just the base jar (24K only).
Emmanuel Bourg
concurrent classes rather than
using the 1.4 compatible approach.
I updated the patch in QPID-2498 if you want to review it this weekend.
Emmanuel Bourg
smime.p7s
Description: S/MIME Cryptographic Signature
[
https://issues.apache.org/jira/browse/QPID-2629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12872015#action_12872015
]
Emmanuel Bourg commented on QPID-2629:
--
That's fine to copy the classes from Commons
Reporter: Emmanuel Bourg
Priority: Trivial
Fix For: 0.7
There is a typo in ServerConnectionDelegate, when a client connects to an
unknown virtual host it receives the message:
ConnectionException: Unknown vistrulhost 'foo'
--
This message is automatically generated
[
https://issues.apache.org/jira/browse/QPID-2626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12871082#action_12871082
]
Emmanuel Bourg commented on QPID-2626:
--
The patch also fixes an unchecked assignment
[
https://issues.apache.org/jira/browse/QPID-2626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Bourg updated QPID-2626:
-
Attachment: vhost-typo.patch
Typo in ServerConnectionDelegate
[
https://issues.apache.org/jira/browse/QPID-2498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12871085#action_12871085
]
Emmanuel Bourg commented on QPID-2498:
--
Martin, let me know if you need an updated
patch ready for everything
else if you are interested.
Emmanuel Bourg
smime.p7s
Description: S/MIME Cryptographic Signature
.
Emmanuel Bourg
smime.p7s
Description: S/MIME Cryptographic Signature
, Java Common
Affects Versions: 0.6
Reporter: Emmanuel Bourg
Priority: Minor
Fix For: 0.7
The Java client doesn't use Mina for the transport but still depends on it due
to several usages of the extensible ByteBuffer. The dependency on Mina could be
removed
[
https://issues.apache.org/jira/browse/QPID-2627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Bourg updated QPID-2627:
-
Attachment: minabuffer.patch
Partial patch removing the usage of the Mina ByteBuffer. This patch
Le 25/05/2010 16:17, Rajith Attapattu a écrit :
Sure, pls file a JIRA and attach it.
Lets see what others also think.
The patch is attached to QPID-2627
https://issues.apache.org/jira/browse/QPID-2627
Emmanuel Bourg
smime.p7s
Description: S/MIME Cryptographic Signature
as long as it's close to the AMQP semantic and well
supported.
Emmanuel Bourg
smime.p7s
Description: S/MIME Cryptographic Signature
on exposing AMQP functionality in the java
client it may subject to change.
Thank you Martin,
I looked at AMQSession but it seems my understanding of the code isn't
good enough to implement the unbind feature myself. If someone could
look into it that would be really nice.
Emmanuel Bourg
to the server is initialized.
Emmanuel Bourg
Le 17/05/2010 15:52, Rajith Attapattu a écrit :
Hi Emmanuel,
It can be done easily using the new addressing format.
For example you could use the following in the jndi.properties file.
destination.myTopic = ADDR:amq.topic/topic1; { create: always
it seems significantly more convoluted. I've been able
to get only one topic per queue so far.
Thank you,
Emmanuel Bourg
smime.p7s
Description: S/MIME Cryptographic Signature
what Aidan and Robert proposed.
Emmanuel Bourg
smime.p7s
Description: S/MIME Cryptographic Signature
Affects Versions: 0.6
Reporter: Emmanuel Bourg
Priority: Minor
Fix For: 0.7
JMSException has an archaic mechanism to chain the root cause by calling the
setLinkedException() method. It predates the introduction of the
Throwable.initCause() method in Java
[
https://issues.apache.org/jira/browse/QPID-2594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Bourg updated QPID-2594:
-
Attachment: initcause.patch
Exception chaining for JMSExceptions
Le 11/05/2010 15:44, Rajith Attapattu a écrit :
I am slammed atm, so a patch would be very much appreciated !
Here it is:
https://issues.apache.org/jira/browse/QPID-2594
https://issues.apache.org/jira/secure/attachment/12444205/initcause.patch
Emmanuel Bourg
smime.p7s
Description: S
[
https://issues.apache.org/jira/browse/QPID-2594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Bourg resolved QPID-2594.
--
Resolution: Fixed
Patch applied by Rajith
Exception chaining for JMSExceptions
to an authentication issue unless you remember to look at
the linked exception. That would be useful to chain the exceptions with
initCause().
Emmanuel Bourg
smime.p7s
Description: S/MIME Cryptographic Signature
Le 23/03/2010 13:57, Rajith Attapattu a écrit :
Thanks for the input.
I will create a JIRA and take care of this.
This change would be much welcome. I didn't find the JIRA report, if you
want I can provide a patch addressing this issue.
Emmanuel Bourg
smime.p7s
Description: S/MIME
an exception. Apparently no error is reported
by the client, it just times out.
Emmanuel Bourg
smime.p7s
Description: S/MIME Cryptographic Signature
.
There is an alternative that wasn't proposed in the discussion, that's
the addition of a suffix to the version number. Something like 0.7-dev
or 0.7-SNAPSHOT to specify it's a development version, that's a common
practice.
Emmanuel Bourg
smime.p7s
Description: S/MIME Cryptographic Signature
Le 06/05/2010 14:22, Andrew Stitcher a écrit :
The decision has been taken
I may have missed something, but it seems that was just quickly
discussed before Christmas while some people were on holiday, and no
vote took place to settle the consensus.
Emmanuel Bourg
smime.p7s
Description
for automated publishing.
The svn repository used doesn't have to be the same as the one used for
the code. The infra team can create a separate repository if large
binary files aren't desired in the code repository (like the PDFs
generated from the docbook files).
Emmanuel Bourg
[
https://issues.apache.org/jira/browse/QPID-2531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12860536#action_12860536
]
Emmanuel Bourg commented on QPID-2531:
--
What part of the build expects this directory
[
https://issues.apache.org/jira/browse/QPID-2531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12860381#action_12860381
]
Emmanuel Bourg commented on QPID-2531:
--
The directory java/broker-plugins/src is empty
/
And the Maven repository is there (it contains only the qpid-common and
qpid-client snapshots at this time):
http://people.apache.org/~ebourg/qpid/maven/
Emmanuel Bourg
-
Apache Qpid - AMQP Messaging Implementation
[
https://issues.apache.org/jira/browse/QPID-1916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Bourg updated QPID-1916:
-
Attachment: maven.patch
I attached an alternative patch to generate the Maven artifacts:
- like
://issues.apache.org/jira/browse/QPID-2433
Emmanuel Bourg
-
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org
: Ant Build System, Java Common
Affects Versions: 0.6
Reporter: Emmanuel Bourg
Priority: Minor
Fix For: 0.7
The gentools target of the common module fails when the path contains a space
character.
For example if the project sources are copied into /home
[
https://issues.apache.org/jira/browse/QPID-2526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Bourg updated QPID-2526:
-
Attachment: build-common.patch
I attached a patch that quotes the parameters
1 - 100 of 130 matches
Mail list logo
