[
https://issues.apache.org/jira/browse/QPIDIT-39?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15512891#comment-15512891
]
Jiri Danek commented on QPIDIT-39:
----------------------------------
If you agree with what I am proposing, I could implement it myself and send a
patch. But this may be already in the works as part of the Jenkins issue.
> Make qpid-jms-client version a parameter of Maven build
> -------------------------------------------------------
>
> Key: QPIDIT-39
> URL: https://issues.apache.org/jira/browse/QPIDIT-39
> Project: Apache QPID IT
> Issue Type: Improvement
> Components: Qpid Jms Shim
> Reporter: Jiri Danek
> Priority: Critical
>
> I wish to be able to change the version of qpid-jms-client library used in
> the jms shim. This would allow running the test with older versions of the
> library and also with various proprietary builds of the library.
> One possible way to implement this would be to make the library version a
> maven attribute and to switch between geronimo-jms_1.1_spec and the 2.0
> version using maven profile, e.g.:
> {noformat}
> mvn -Pjms11 -Dqpid-jms-client.version=0.11.0.mycompany-1 package
> mvn -Pjms20 -Dqpid-jms-client.version=0.20.0 package
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
