You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by Alan Conway <ac...@redhat.com> on 2010/03/16 20:31:30 UTC
Version madness: places that refer to the project version.
I was trying to figure out where the project version is stored and it appears to
be stored in many places (and out of date in most of them)
Files that refer to 0.7
./extras/qmf/setup.py:23: version="0.7",
./tests/setup.py:23: version="0.7",
./cpp/src/qpid/Version.h:39: const std::string version = "0.7";
./cpp/configure.ac:14:AC_INIT([qpidc], [0.7], [dev@qpid.apache.org])
./python/setup.py:301: version="0.7",
./java/management/common/src/main/java/management-common.bnd:1:ver: 0.7.0
./java/client/src/main/java/client.bnd:1:ver: 0.7.0
./java/common.xml:26: <property name="project.version" value="0.7"/>
Files that refer to 0.6
./doc/book/src/SASL-Compatibility.xml:20:| Python Client
|0.6\[[#2]\]|0.6\[[#2]\]|0.6\[[#2]\] |0.6\[[#2]\]|0.6\[[#2]\] | M4 |
./doc/book/src/SASL-Compatibility.xml:21:| Ruby Client
|0.6\[[#2]\]|0.6\[[#2]\]|0.6\[[#2]\] |0.6\[[#2]\]|0.6\[[#2]\] | M4 |
./cpp/bld-winsdk.ps1:27:$ver='0.6'
./cpp/examples/README.txt:19: C:\Program Files\qpidc-0.6\examples\direct>
declare_queues
./java/broker/src/test/java/org/apache/qpid/server/logging/messages/BrokerMessagesTest.java:32:
String version = "Qpid 0.6";
./java/broker/src/main/java/org/apache/qpid/server/plugins/PluginManager.java:82:
"org.apache.qpid.junit.extensions.util; version=0.6.1,"
./java/common/src/main/java/common.bnd:1:ver: 0.6.0
./java/systests/src/main/java/org/apache/qpid/server/logging/BrokerLoggingTest.java:348:
* <date> MESSAGE BRK-1001 : Startup : qpid Version: 0.6 Build: 767150
I propose we create a single file: qpid/QPID_VERSION.txt and have all the build
systems copy that into their builds when built in an SVN checkout. Any
objections or better ideas? I can fix up C++, any volunteers to do python/ruby/java?
Cheers,
Alan.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
Re: Version madness: places that refer to the project version.
Posted by Jonathan Robie <jo...@redhat.com>.
On 03/16/2010 03:31 PM, Alan Conway wrote:
>
> I propose we create a single file: qpid/QPID_VERSION.txt and have all
> the build systems copy that into their builds when built in an SVN
> checkout. Any objections or better ideas?
+1
I'll use it in the documentation to create the header page ...
Jonathan
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
Re: Version madness: places that refer to the project version.
Posted by Aidan Skinner <ai...@gmail.com>.
+lots I'll fix the java and 0-8 and 0-10 C# clients next week. I don't have
Visual Studio (or even a Windows install) so can't help with the WCF client
On 16 Mar 2010 19:32, "Alan Conway" <ac...@redhat.com> wrote:
I was trying to figure out where the project version is stored and it
appears to be stored in many places (and out of date in most of them)
Files that refer to 0.7
./extras/qmf/setup.py:23: version="0.7",
./tests/setup.py:23: version="0.7",
./cpp/src/qpid/Version.h:39: const std::string version = "0.7";
./cpp/configure.ac:14:AC_INIT([qpidc], [0.7], [dev@qpid.apache.org])
./python/setup.py:301: version="0.7",
./java/management/common/src/main/java/management-common.bnd:1:ver: 0.7.0
./java/client/src/main/java/client.bnd:1:ver: 0.7.0
./java/common.xml:26: <property name="project.version" value="0.7"/>
Files that refer to 0.6
./doc/book/src/SASL-Compatibility.xml:20:| Python Client
|0.6\[[#2]\]|0.6\[[#2]\]|0.6\[[#2]\] |0.6\[[#2]\]|0.6\[[#2]\] | M4
|
./doc/book/src/SASL-Compatibility.xml:21:| Ruby Client
|0.6\[[#2]\]|0.6\[[#2]\]|0.6\[[#2]\] |0.6\[[#2]\]|0.6\[[#2]\] | M4
|
./cpp/bld-winsdk.ps1:27:$ver='0.6'
./cpp/examples/README.txt:19: C:\Program Files\qpidc-0.6\examples\direct>
declare_queues
./java/broker/src/test/java/org/apache/qpid/server/logging/messages/BrokerMessagesTest.java:32:
String version = "Qpid 0.6";
./java/broker/src/main/java/org/apache/qpid/server/plugins/PluginManager.java:82:
"org.apache.qpid.junit.extensions.util; version=0.6.1,"
./java/common/src/main/java/common.bnd:1:ver: 0.6.0
./java/systests/src/main/java/org/apache/qpid/server/logging/BrokerLoggingTest.java:348:
* <date> MESSAGE BRK-1001 : Startup : qpid Version: 0.6 Build: 767150
I propose we create a single file: qpid/QPID_VERSION.txt and have all the
build systems copy that into their builds when built in an SVN checkout. Any
objections or better ideas? I can fix up C++, any volunteers to do
python/ruby/java?
Cheers,
Alan.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
Re: Version madness: places that refer to the project version.
Posted by Rajith Attapattu <ra...@gmail.com>.
Certainly this would make a release managers life easy.
+1
Rajith
On Tue, Mar 16, 2010 at 3:31 PM, Alan Conway <ac...@redhat.com> wrote:
> I was trying to figure out where the project version is stored and it
> appears to be stored in many places (and out of date in most of them)
>
> Files that refer to 0.7
> ./extras/qmf/setup.py:23: version="0.7",
> ./tests/setup.py:23: version="0.7",
> ./cpp/src/qpid/Version.h:39: const std::string version = "0.7";
> ./cpp/configure.ac:14:AC_INIT([qpidc], [0.7], [dev@qpid.apache.org])
> ./python/setup.py:301: version="0.7",
> ./java/management/common/src/main/java/management-common.bnd:1:ver: 0.7.0
> ./java/client/src/main/java/client.bnd:1:ver: 0.7.0
> ./java/common.xml:26: <property name="project.version" value="0.7"/>
>
> Files that refer to 0.6
> ./doc/book/src/SASL-Compatibility.xml:20:| Python Client
> |0.6\[[#2]\]|0.6\[[#2]\]|0.6\[[#2]\] |0.6\[[#2]\]|0.6\[[#2]\] | M4
> |
> ./doc/book/src/SASL-Compatibility.xml:21:| Ruby Client
> |0.6\[[#2]\]|0.6\[[#2]\]|0.6\[[#2]\] |0.6\[[#2]\]|0.6\[[#2]\] | M4
> |
> ./cpp/bld-winsdk.ps1:27:$ver='0.6'
> ./cpp/examples/README.txt:19: C:\Program Files\qpidc-0.6\examples\direct>
> declare_queues
> ./java/broker/src/test/java/org/apache/qpid/server/logging/messages/BrokerMessagesTest.java:32:
> String version = "Qpid 0.6";
> ./java/broker/src/main/java/org/apache/qpid/server/plugins/PluginManager.java:82:
> "org.apache.qpid.junit.extensions.util; version=0.6.1,"
> ./java/common/src/main/java/common.bnd:1:ver: 0.6.0
> ./java/systests/src/main/java/org/apache/qpid/server/logging/BrokerLoggingTest.java:348:
> * <date> MESSAGE BRK-1001 : Startup : qpid Version: 0.6 Build: 767150
>
> I propose we create a single file: qpid/QPID_VERSION.txt and have all the
> build systems copy that into their builds when built in an SVN checkout. Any
> objections or better ideas? I can fix up C++, any volunteers to do
> python/ruby/java?
>
> Cheers,
> Alan.
>
> ---------------------------------------------------------------------
> Apache Qpid - AMQP Messaging Implementation
> Project: http://qpid.apache.org
> Use/Interact: mailto:dev-subscribe@qpid.apache.org
>
>
--
Regards,
Rajith Attapattu
Red Hat
http://rajith.2rlabs.com/
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org