[ 
https://issues.apache.org/jira/browse/QPID-6739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alex Rudyy resolved QPID-6739.
------------------------------
       Resolution: Fixed
    Fix Version/s: qpid-java-6.0

The requested changes have been made

> Allow setting and overriding Qpid client version suffix in 
> qpid-common.properties
> ---------------------------------------------------------------------------------
>
>                 Key: QPID-6739
>                 URL: https://issues.apache.org/jira/browse/QPID-6739
>             Project: Qpid
>          Issue Type: Improvement
>          Components: Java Broker, Java Client, Java Common
>            Reporter: Alex Rudyy
>            Assignee: Alex Rudyy
>             Fix For: qpid-java-6.0
>
>
> At the moment qpid version suffix is set in qpidversion.properties which is 
> generated on qpid-common build. As result, any client based on apache 
> qpid-common cannot set the suffix without repackaging  qpid-common  and 
> modifying  qpidversion.properties. We need to introduce a way to set and 
> override Qpid client version suffix in external client builds in order to 
> differentiate apache and external qpid client and broker builds
> The following approach can be implemented:
> # Move the public API from QpidProperties into CommonProperties and call 
> CommonProperties everywhere where QpidProperties  is called at the moment. 
> Remove QpidProperties class.
> # qpidversion.properties will be loaded as part of of initialization 
> CommonProperties together with loading of qpid-common.properties. Later we 
> will load change the code to get build specific information from jar 
> Manifest. 
> # Version suffix can be set in qpid-common.properties and corresponding 
> release version field can be set to have version suffix loaded from 
> qpid-common.properties



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to