qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andrea Gazzarini <a.gazzar...@gmail.com>
Subject Re: Qpid 0.5 RC2
Date Tue, 12 May 2009 06:11:02 GMT
Issue QPID-1848 has been resolved.
Regards,
Andrea

2009/5/12 Andrea Gazzarini <a.gazzarini@gmail.com>

> Hi Martin, I checked the QMan archives.
> There's only one problem with the qman-jmx.sh startup script for QMan JMX
> Adapter : it's notworking :(No problem concerning the other scripts and
> the application.
> I created a JIRA issue (QPID-1848) for resolving that and I'm just going to
> submit the fix.
>
> Regards,
> Andrea
>
> 2009/5/11 Martin Ritchie <ritchiem@apache.org>
>
>> Qpid 0.5 RC2 is now ready for final testing:
>> http://people.apache.org/~ritchiem/Qpid-0.5/RC2
>> (Files are uploading, give it 1hr for all artefacts to be available.)
>>
>> Updates are mainly packaging based, though I have updated a number of
>> files for license headers as reported by RAT. The latest RAT output is
>> attached here, the files that are being highlighted with ???? unknown
>> licenses are now generated files or txt files.
>>
>>  - Updated license headers on a number of files. If we are adding a
>> new file and it has a comment structure can we please ensure that we
>> have the license file at the start.
>> - Created new release artefacts for Java (QMan/WSDL, client-examples,
>> qpid-cli)
>>
>> As there are a couple of artefacts that are new I will delay starting
>> the vote thread until Wednesday (2009-05-13).
>>
>> I have verified that the:
>>  - packages contain the required notice/license file
>>  - source bundle can build the release artefacts
>>  - cpp broker package builds and starts on fedora 10
>>  - complete java packaged broker starts up as do the associated tools.
>>  - java broker starts up
>>  - java client examples run using qpid-all.jar as the classpath
>>  - java Eclipse MC linux x68, OS-X start up
>>  - java QMan tool starts up
>>  - java qpid-cli tool starts up
>>
>> I have not investigated dotnet, ruby or python, other than there
>> packaging was completed.
>>
>> The biggest issue I noticed was the lack of bundled documentation at
>> least from the Java side. All the artefacts ship with a README which
>> only details starting the broker, not ideal but something we can work
>> on for our next release.
>>
>> Regards
>>
>> Martin
>> --
>> Martin Ritchie
>>
>>
>>
>> ---------------------------------------------------------------------
>> Apache Qpid - AMQP Messaging Implementation
>> Project:      http://qpid.apache.org
>> Use/Interact: mailto:dev-subscribe@qpid.apache.org
>>
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message