You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@synapse.apache.org by "Andreas Veithen (JIRA)" <ji...@apache.org> on 2008/08/02 20:17:44 UTC
[jira] Created: (SYNAPSE-417) Qpid dependency conflict between AMQP
transport and JMS unit tests
Qpid dependency conflict between AMQP transport and JMS unit tests
------------------------------------------------------------------
Key: SYNAPSE-417
URL: https://issues.apache.org/jira/browse/SYNAPSE-417
Project: Synapse
Issue Type: Bug
Components: Transports
Affects Versions: NIGHTLY
Environment: N/A
Reporter: Andreas Veithen
I'm currently developing a set of unit tests for the JMS transport. Initially I used Mockrunner as a JMS provider in these tests, but since it doesn't implement all JMS features correctly, I decided to switch to Qpid. The unit tests run well with Qpid's in-VM broker, but this approach introduces a new issue: the JMS unit tests use version 1.0-incubating-M2.1, while the AMQP transport implementation in the same Maven module relies on 1.0-incubating-M3-615355. The M3 snapshot can't be used for the JMS unit tests because the qpid-broker artifact is not available for this version. On the other hand, the AMQP transport doesn't compile with M2.1. I tried to convince Maven to use different versions for compile and test, but this doesn't seem to be possible.
The only solution seems to be to split the synapse-transports such that the AMQP transport and the JMS unit tests become part of two different Maven modules. While waiting for feedback on this question, I will temporarily change the Qpid version and exclude the AMQP transport from compilation.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
[jira] Assigned: (SYNAPSE-417) Qpid dependency conflict between
AMQP transport and JMS unit tests
Posted by "Andreas Veithen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SYNAPSE-417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andreas Veithen reassigned SYNAPSE-417:
---------------------------------------
Assignee: Asankha C. Perera (was: Andreas Veithen)
> Qpid dependency conflict between AMQP transport and JMS unit tests
> ------------------------------------------------------------------
>
> Key: SYNAPSE-417
> URL: https://issues.apache.org/jira/browse/SYNAPSE-417
> Project: Synapse
> Issue Type: Bug
> Components: Transports
> Affects Versions: NIGHTLY
> Environment: N/A
> Reporter: Andreas Veithen
> Assignee: Asankha C. Perera
>
> I'm currently developing a set of unit tests for the JMS transport. Initially I used Mockrunner as a JMS provider in these tests, but since it doesn't implement all JMS features correctly, I decided to switch to Qpid. The unit tests run well with Qpid's in-VM broker, but this approach introduces a new issue: the JMS unit tests use version 1.0-incubating-M2.1, while the AMQP transport implementation in the same Maven module relies on 1.0-incubating-M3-615355. The M3 snapshot can't be used for the JMS unit tests because the qpid-broker artifact is not available for this version. On the other hand, the AMQP transport doesn't compile with M2.1. I tried to convince Maven to use different versions for compile and test, but this doesn't seem to be possible.
> The only solution seems to be to split the synapse-transports such that the AMQP transport and the JMS unit tests become part of two different Maven modules. While waiting for feedback on this question, I will temporarily change the Qpid version and exclude the AMQP transport from compilation.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
[jira] Resolved: (SYNAPSE-417) Qpid dependency conflict between
AMQP transport and JMS unit tests
Posted by "Andreas Veithen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SYNAPSE-417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andreas Veithen resolved SYNAPSE-417.
-------------------------------------
Resolution: Fixed
Fix Version/s: NIGHTLY
Thanks Indika.
I reenabled the AMQP transport. It seems to build fine.
> Qpid dependency conflict between AMQP transport and JMS unit tests
> ------------------------------------------------------------------
>
> Key: SYNAPSE-417
> URL: https://issues.apache.org/jira/browse/SYNAPSE-417
> Project: Synapse
> Issue Type: Bug
> Components: Transports
> Affects Versions: NIGHTLY
> Environment: N/A
> Reporter: Andreas Veithen
> Assignee: Andreas Veithen
> Fix For: NIGHTLY
>
>
> I'm currently developing a set of unit tests for the JMS transport. Initially I used Mockrunner as a JMS provider in these tests, but since it doesn't implement all JMS features correctly, I decided to switch to Qpid. The unit tests run well with Qpid's in-VM broker, but this approach introduces a new issue: the JMS unit tests use version 1.0-incubating-M2.1, while the AMQP transport implementation in the same Maven module relies on 1.0-incubating-M3-615355. The M3 snapshot can't be used for the JMS unit tests because the qpid-broker artifact is not available for this version. On the other hand, the AMQP transport doesn't compile with M2.1. I tried to convince Maven to use different versions for compile and test, but this doesn't seem to be possible.
> The only solution seems to be to split the synapse-transports such that the AMQP transport and the JMS unit tests become part of two different Maven modules. While waiting for feedback on this question, I will temporarily change the Qpid version and exclude the AMQP transport from compilation.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
[jira] Commented: (SYNAPSE-417) Qpid dependency conflict between
AMQP transport and JMS unit tests
Posted by "indika priyantha kumara (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SYNAPSE-417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12635372#action_12635372 ]
indika priyantha kumara commented on SYNAPSE-417:
-------------------------------------------------
I have fixed the issue with qpid-client artifact name .
Thanks
Indika
> Qpid dependency conflict between AMQP transport and JMS unit tests
> ------------------------------------------------------------------
>
> Key: SYNAPSE-417
> URL: https://issues.apache.org/jira/browse/SYNAPSE-417
> Project: Synapse
> Issue Type: Bug
> Components: Transports
> Affects Versions: NIGHTLY
> Environment: N/A
> Reporter: Andreas Veithen
> Assignee: Asankha C. Perera
>
> I'm currently developing a set of unit tests for the JMS transport. Initially I used Mockrunner as a JMS provider in these tests, but since it doesn't implement all JMS features correctly, I decided to switch to Qpid. The unit tests run well with Qpid's in-VM broker, but this approach introduces a new issue: the JMS unit tests use version 1.0-incubating-M2.1, while the AMQP transport implementation in the same Maven module relies on 1.0-incubating-M3-615355. The M3 snapshot can't be used for the JMS unit tests because the qpid-broker artifact is not available for this version. On the other hand, the AMQP transport doesn't compile with M2.1. I tried to convince Maven to use different versions for compile and test, but this doesn't seem to be possible.
> The only solution seems to be to split the synapse-transports such that the AMQP transport and the JMS unit tests become part of two different Maven modules. While waiting for feedback on this question, I will temporarily change the Qpid version and exclude the AMQP transport from compilation.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
[jira] Commented: (SYNAPSE-417) Qpid dependency conflict between
AMQP transport and JMS unit tests
Posted by "Andreas Veithen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SYNAPSE-417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12635153#action_12635153 ]
Andreas Veithen commented on SYNAPSE-417:
-----------------------------------------
Since the JMS transport including the unit tests has been moved to ws-commons, we could now revert my temporary change and solve this issue. However, this would break the build for most people because the qpid-client artifact in the dist.wso2.org repository has an invalid version number (61535 instead of 615355).
Asankha, can you talk to the WSO2 people to correct the name of the qpid-client JAR in dist.wso2.org?
> Qpid dependency conflict between AMQP transport and JMS unit tests
> ------------------------------------------------------------------
>
> Key: SYNAPSE-417
> URL: https://issues.apache.org/jira/browse/SYNAPSE-417
> Project: Synapse
> Issue Type: Bug
> Components: Transports
> Affects Versions: NIGHTLY
> Environment: N/A
> Reporter: Andreas Veithen
> Assignee: Andreas Veithen
>
> I'm currently developing a set of unit tests for the JMS transport. Initially I used Mockrunner as a JMS provider in these tests, but since it doesn't implement all JMS features correctly, I decided to switch to Qpid. The unit tests run well with Qpid's in-VM broker, but this approach introduces a new issue: the JMS unit tests use version 1.0-incubating-M2.1, while the AMQP transport implementation in the same Maven module relies on 1.0-incubating-M3-615355. The M3 snapshot can't be used for the JMS unit tests because the qpid-broker artifact is not available for this version. On the other hand, the AMQP transport doesn't compile with M2.1. I tried to convince Maven to use different versions for compile and test, but this doesn't seem to be possible.
> The only solution seems to be to split the synapse-transports such that the AMQP transport and the JMS unit tests become part of two different Maven modules. While waiting for feedback on this question, I will temporarily change the Qpid version and exclude the AMQP transport from compilation.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
[jira] Assigned: (SYNAPSE-417) Qpid dependency conflict between
AMQP transport and JMS unit tests
Posted by "Andreas Veithen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SYNAPSE-417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andreas Veithen reassigned SYNAPSE-417:
---------------------------------------
Assignee: Andreas Veithen
> Qpid dependency conflict between AMQP transport and JMS unit tests
> ------------------------------------------------------------------
>
> Key: SYNAPSE-417
> URL: https://issues.apache.org/jira/browse/SYNAPSE-417
> Project: Synapse
> Issue Type: Bug
> Components: Transports
> Affects Versions: NIGHTLY
> Environment: N/A
> Reporter: Andreas Veithen
> Assignee: Andreas Veithen
>
> I'm currently developing a set of unit tests for the JMS transport. Initially I used Mockrunner as a JMS provider in these tests, but since it doesn't implement all JMS features correctly, I decided to switch to Qpid. The unit tests run well with Qpid's in-VM broker, but this approach introduces a new issue: the JMS unit tests use version 1.0-incubating-M2.1, while the AMQP transport implementation in the same Maven module relies on 1.0-incubating-M3-615355. The M3 snapshot can't be used for the JMS unit tests because the qpid-broker artifact is not available for this version. On the other hand, the AMQP transport doesn't compile with M2.1. I tried to convince Maven to use different versions for compile and test, but this doesn't seem to be possible.
> The only solution seems to be to split the synapse-transports such that the AMQP transport and the JMS unit tests become part of two different Maven modules. While waiting for feedback on this question, I will temporarily change the Qpid version and exclude the AMQP transport from compilation.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
[jira] Assigned: (SYNAPSE-417) Qpid dependency conflict between
AMQP transport and JMS unit tests
Posted by "Andreas Veithen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SYNAPSE-417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andreas Veithen reassigned SYNAPSE-417:
---------------------------------------
Assignee: Andreas Veithen (was: Asankha C. Perera)
> Qpid dependency conflict between AMQP transport and JMS unit tests
> ------------------------------------------------------------------
>
> Key: SYNAPSE-417
> URL: https://issues.apache.org/jira/browse/SYNAPSE-417
> Project: Synapse
> Issue Type: Bug
> Components: Transports
> Affects Versions: NIGHTLY
> Environment: N/A
> Reporter: Andreas Veithen
> Assignee: Andreas Veithen
>
> I'm currently developing a set of unit tests for the JMS transport. Initially I used Mockrunner as a JMS provider in these tests, but since it doesn't implement all JMS features correctly, I decided to switch to Qpid. The unit tests run well with Qpid's in-VM broker, but this approach introduces a new issue: the JMS unit tests use version 1.0-incubating-M2.1, while the AMQP transport implementation in the same Maven module relies on 1.0-incubating-M3-615355. The M3 snapshot can't be used for the JMS unit tests because the qpid-broker artifact is not available for this version. On the other hand, the AMQP transport doesn't compile with M2.1. I tried to convince Maven to use different versions for compile and test, but this doesn't seem to be possible.
> The only solution seems to be to split the synapse-transports such that the AMQP transport and the JMS unit tests become part of two different Maven modules. While waiting for feedback on this question, I will temporarily change the Qpid version and exclude the AMQP transport from compilation.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org