Ok, try the new archive that I just put out there.

Mittler, Nathan wrote:
Tim,
Running the Rat tool shows that the following files are still missing
headers:

./src/decaf/src/main/decaf/lang/Comparable.h
./src/decaf/decaf.pc.in
./src/decaf/doxygen.cfg

Looks like the files at the top level were fixed, but those under decaf
were missed.

Regards,
Nate

-----Original Message-----
From: Timothy Bish [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 30, 2007 6:07 AM
To: [email protected]
Subject: Re: [VOTE] Release ActiveMQ-CPP v2.1.1

Should be there now

Nathan Mittler wrote:
Hmm ... did you overwrite the original file? This file
doesn't seem
to have the changes:


http://people.apache.org/~tabish/activemq-cpp-2.1.1-src.tar.gz<http://
people.apache.org/%7Etabish/activemq-cpp-2.1.1-src.tar.gz>

On 10/29/07, Timothy Bish <[EMAIL PROTECTED]> wrote:
I've placed a new archive out there with these changes.

Hiram Chirino wrote:
Hi,

I just ran the rat tool against the code, and it showed
that a few
files are missing license headers. I think the following
ones are
the only ones that we actually need to added the headers to:
./src/decaf/src/main/decaf/lang/Comparable.h
./activemq-cpp.pc.in
./activemqcpp-config.in
./doxygen.cfg
./src/decaf/decaf.pc.in
./src/decaf/doxygen.cfg

You can get rat from: http://code.google.com/p/arat/

Regards,
Hiram

On 10/29/07, Timothy Bish <[EMAIL PROTECTED]> wrote:

Hi everyone,

Sending a new Notice as the other one got corrupted a bit.

Its time to get ActiveMQ-CPP 2.1.1 out the door. We've
fixed many
bugs, improved performance and added a couple new
features in this
release as well as improved overall stability.

The source bundle for the release candidate can be found here:
http://people.apache.org/~tabish/activemq-cpp-2.1.1-src.tar.gz

And here's the wiki page for the release:
http://activemq.apache.org/cms/activemq-cpp-211-release.html

Please cast your votes:

[ ] +1 *Release* the source as Apache ActiveMQ-CPP 2.1.1 [ ] -1 Veto the *release* (provide specific comments)

Regards,
Tim





Reply via email to