Build works fine on Windows 7 with Java 1.5 and 1.7, artifacts and site
look good.
One thing I noticed, not sure whether this is actually a problem: The
artifacts for adapters and api have the same manifest information as the
main jar. Are they intended to be used in an OSGi environment? Could
this cause problems?
Oliver
Am 16.03.2013 14:06, schrieb Thomas Neidhart:
Hi,
I'd like to call a vote for releasing Commons Logging 1.1.2 based on RC2.
This release candidate has the following changes compared to RC1:
* Fix deployment process to include also missing bin/src assemblies
* Disable reference release test for WeakHashtable as it was unreliable
on various JVMs
* Fix several unit tests related to security permissions when run with
IBM JVM 6
The files:
The artifacts are deployed to Nexus:
https://repository.apache.org/content/repositories/orgapachecommons-007/commons-logging/commons-logging/1.1.2/
The tag:
https://svn.apache.org/repos/asf/commons/proper/logging/tags/LOGGING_1_1_2_RC2/
The site:
http://people.apache.org/builds/commons/logging/1.1.2/RC2/
Additional Notes:
o the download page and api links to older releases only work on
the published site and will be corrected after release.
Please take a look at the commons-logging-1.1.2 artifacts and vote!
------------------------------------------------
[ ] +1 release it.
[ ] +0 go ahead; I don't care.
[ ] -0 there are a few minor glitches: ...
[ ] -1 no, do not release it because ...
------------------------------------------------
Vote will remain open for at least 72 hours.
Thanks in advance,
Thomas
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
