qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robbie Gemmell (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (QPIDIT-39) Make qpid-jms-client version a parameter of Maven build
Date Fri, 20 Oct 2017 21:29:00 GMT

    [ https://issues.apache.org/jira/browse/QPIDIT-39?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16213274#comment-16213274

Robbie Gemmell commented on QPIDIT-39:

Kim did this already: https://github.com/apache/qpid-interop-test/blob/master/pom.xml#L56

> 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
>            Reporter: Jiri Daněk
>            Assignee: Kim van der Riet
>            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}
> 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

To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org

View raw message