You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Robbie Gemmell (JIRA)" <ji...@apache.org> on 2018/06/26 14:45:00 UTC
[jira] [Closed] (QPIDIT-39) Make qpid-jms-client version a
parameter of Maven build
[ https://issues.apache.org/jira/browse/QPIDIT-39?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robbie Gemmell closed QPIDIT-39.
--------------------------------
Resolution: Fixed
> 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 Interoperability Test Suite
> Issue Type: Improvement
> Components: Qpid Jms Shim
> Affects Versions: 0.1.0
> Reporter: Jiri Daněk
> Assignee: Kim van der Riet
> Priority: Critical
> Fix For: 0.1.0
>
>
> 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}
> On a related task, it might be helpful to use Maven to produce an uberjar, a jar that bundles all runtime dependencies in itself. It would simplify running the shim from the test program, because then there would be no classpath to deal with.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org