You are viewing a plain text version of this content. The canonical link for it is here.
Posted to general@incubator.apache.org by Peter Firmstone <ji...@zeus.net.au> on 2010/03/10 10:39:41 UTC
[VOTE] Release Apache River 2.1.2
Please vote on releasing Apache River 2.1.2
The voting period is open, due to the size of the River release, it will
remain open until it passes with a majority of at least three +1 River
Incubator PMC votes or until a valid objection causes its rejection.
All are encouraged to show their support by validating and casting a
vote for this release, please ensure you reply to both lists, so those
on general can see your interest in and support for our project:
general@incubator.apache.org
river-dev@incubator.apache.org
A candidate for the Apache River 2.1.2 Release is available at
http://people.apache.org/~peter_firmstone/
The release candidate sources are zip / tar.gz archives of the sources in:
http://svn.apache.org/repos/asf/incubator/river/jtsk/trunk/
The source release artifact SHA1 checksums are:
apache-river-2.1.2-incubating-src.tar.gz:
6B18 E089 C22C 9790 B0A4 89CC A410 2250 7A0A 4890
apache-river-2.1.2-incubating-src.zip:
28F8 ABB3 0BDF 149F 6FA0 8D8B C982 47A6 19EF AE43
The binary release artifact SHA1 checksums:
apache-river-2.1.2-incubating-bin.tar.gz:
3813 613B 4432 B5A9 E6F3 EFCA D649 D55A C73A 1BA8
apache-river-2.1.2-incubating-bin.zip:
F692 BCDC A050 9BCF 3ADD A5E4 C500 4263 0FAE 6BEE
Apache River
v2.1.2 Release Notes
------------------------------------------------------------------------
Apache River is an effort undergoing incubation at The Apache Software
Foundation (ASF), sponsored by the Apache Incubator. Incubation is
required of all newly accepted projects until a further review indicates
that the infrastructure, communications, and decision making process
have stabilized in a manner consistent with other successful ASF
projects. While incubation status is not necessarily a reflection of the
completeness or stability of the code, it does indicate that the project
has yet to be fully endorsed by the ASF.
Apache River is aimed at the development and advancement of the River
technology core infrastructure. River technology is a service oriented
architecture that defines a programming model which both exploits and
extends Java technology to enable the construction of secure,
distributed systems which are adaptive to change.
------------------------------------------------------------------------
Notes of Interest for this Release
This second release from the Apache River project is based on the
contributions of Sun's Jini Technology Starter Kit (Starter Kit) v2.1
and Service UI from Artima. The release focuses on merging the two
contributions together, structuring separate src and bin releases, and
amending the source and documentation naming/versioning/etc to the
Apache River project.
Some points of note:
* NOTICE file and source license headers updated
* Source and documentation updated for release name ("Apache River
release") and version ("v2.1.2")
* Graphical installer (which was a 3rd party application in the
Starter Kit) is no longer available
* The combined source and binary release in the Starter Kit has been
separated into two releases: src and bin
* The "logstore" implementation of com.sun.jini.outrigger.Store has
been removed
The persistent version of Outrigger relies on a pluggable
persistence layer, |com.sun.jini.outrigger.Store|. Previous
releases of the Starter Kit included two implementations of the
Store interface, /logstore/ and /snaplogstore/. This release
removes logstore.
Logstore has been around in various forms since the 1.0 version of
Outrigger. Snapstore was introduced in v2.1 of the Starter Kit.
The v2.0.n releases of the Starter Kit used logstore as the
default Store implementation, this release has no default Store.
In order to switch an existing set of configuration files,
security policy files, etc., from using logstore to snaplogstore,
you will need to change the |com.sun.jini.outrigger.store|
configuration entry (or add a store configuration entry if you
don't already have one) to yield a
|com.sun.jini.outrigger.snaplogstore.LogStore| object. You will
also need to ensure that |outrigger-snaplogstore.jar| has been
granted sufficient permissions (see Outrigger's package
documentation for a sample security policy file.).
Note that depending on the nature of your application snaplogstore
can have a significantly different performance profile than logstore.
The storage formats used by snaplogstore and logstore are mutually
incompatible.
------------------------------------------------------------------------
Submitting Issues
If you would like to submit a bug against the Apache River release,
please use the River JIRA <http://issues.apache.org/jira/browse/RIVER>.
To discuss problems, questions, or suggestions on the release, please
subscribe to the |river-dev| list from the project Mailing Lists
<http://incubator.apache.org/river/mailing.html> page.
------------------------------------------------------------------------
Upcoming Changes planned for the next version of Apache River
# All packages ouside of the net.jini namespace will be renamed to
org.apache.river.
# Support for Java 5 language features
# Support for Modular Frameworks conforming to the OSGi r4.2 core
Specification
------------------------------------------------------------------------
Changes made since Apache River v2.1.1
Bug
* [RIVER-5 <https://issues.apache.org/jira/browse/RIVER-5>] -
HTTMPMD URLs can be considered equal while they are not
* [RIVER-8 <https://issues.apache.org/jira/browse/RIVER-8>] -
com.sun.jini.tool.ClassDep empty inside collection doesn't work
* [RIVER-17 <https://issues.apache.org/jira/browse/RIVER-17>] -
Misleading logging message when discovery constraint checking is
delayed
* [RIVER-18 <https://issues.apache.org/jira/browse/RIVER-18>] -
Order of discovery providers not maintained
* [RIVER-22 <https://issues.apache.org/jira/browse/RIVER-22>] - NPE
in
net.jini.jeri.tcp.TcpEndpoint$ConnectionImpl.checkConnectPermission
* [RIVER-24 <https://issues.apache.org/jira/browse/RIVER-24>] -
PreferredListGen can create illegal PREFERRED.LIST
* [RIVER-78 <https://issues.apache.org/jira/browse/RIVER-78>] -
ClassDep generates duplicate output lines
* [RIVER-82 <https://issues.apache.org/jira/browse/RIVER-82>] -
ClassDep generates duplicate output lines
* [RIVER-91 <https://issues.apache.org/jira/browse/RIVER-91>] -
Uninstaller does not remove all items
* [RIVER-205 <https://issues.apache.org/jira/browse/RIVER-205>] -
LookupDiscovery can give untrusted code access to privileged threads
* [RIVER-209 <https://issues.apache.org/jira/browse/RIVER-209>] -
NullPointerException in SslConnection.checkConnectPermission()
* [RIVER-212 <https://issues.apache.org/jira/browse/RIVER-212>] -
use of "enum" as a variable name
* [RIVER-213 <https://issues.apache.org/jira/browse/RIVER-213>] -
(DOC) - JoinManger has typo in javadoc (missing </code>
termination tag)
* [RIVER-215 <https://issues.apache.org/jira/browse/RIVER-215>] -
LookupDiscovery throws NullPointerException on terminate
* [RIVER-216 <https://issues.apache.org/jira/browse/RIVER-216>] -
ConfigurationFile should throw ExceptionInInitializerError if
unable to read prohibited methods
* [RIVER-217 <https://issues.apache.org/jira/browse/RIVER-217>] -
Browser incorrectly assumes event source is ServiceRegistrar proxy
* [RIVER-223 <https://issues.apache.org/jira/browse/RIVER-223>] -
test: jtreg/net/jini/jeri/tcp/connectTimeout/TestConnectTimeout
fails on Linux
* [RIVER-224 <https://issues.apache.org/jira/browse/RIVER-224>] -
Problem using browser to destroy service that supports
DestroyAdmin but not JoinAdmin
* [RIVER-225 <https://issues.apache.org/jira/browse/RIVER-225>] -
NullPointerException in Reggie during destroy
* [RIVER-227 <https://issues.apache.org/jira/browse/RIVER-227>] -
tools manpages command lines do not include line continuation
characters
* [RIVER-230 <https://issues.apache.org/jira/browse/RIVER-230>] -
(mux) SelectionManager catch Error block assumes getMessage()
returns non-null
* [RIVER-232 <https://issues.apache.org/jira/browse/RIVER-232>] -
JarWrapper and PreferredListGen uses jsk_install_dir and install_dir
* [RIVER-234 <https://issues.apache.org/jira/browse/RIVER-234>] -
(DOC) Fiddler manpage directions for HTTP server should reference
classserver.jar, not tools.jar
* [RIVER-240 <https://issues.apache.org/jira/browse/RIVER-240>] -
BasicInvocationDispatcher.dispatch could log more info for some
exceptions
* [RIVER-241 <https://issues.apache.org/jira/browse/RIVER-241>] -
Mercury spelling errore
* [RIVER-242 <https://issues.apache.org/jira/browse/RIVER-242>] - if
a given ConnectionManager instance cannot create a reaper thread
once, it never will again
* [RIVER-245 <https://issues.apache.org/jira/browse/RIVER-245>] -
Unicast discovery should close socket in case of connection
exception.
* [RIVER-252 <https://issues.apache.org/jira/browse/RIVER-252>] -
ComputeHttpmdCodebase NPE if resource bundle not found
* [RIVER-253 <https://issues.apache.org/jira/browse/RIVER-253>] -
ComputeDigest NPE if resource bundle not found
* [RIVER-254 <https://issues.apache.org/jira/browse/RIVER-254>] -
request initiation can block on I/O for inapplicable connection
* [RIVER-255 <https://issues.apache.org/jira/browse/RIVER-255>] -
Outrigger DestroyThread does not catch exceptions from
exporter.unexport
* [RIVER-284 <https://issues.apache.org/jira/browse/RIVER-284>] -
[PATCH] fix bad ParticipantHandle.compareTo
* [RIVER-286 <https://issues.apache.org/jira/browse/RIVER-286>] -
[PATCH] iterators on synchronized collections still need
synchronization
* [RIVER-289 <https://issues.apache.org/jira/browse/RIVER-289>] -
Fix for RIVER-247 introduced wrong license headers and references
* [RIVER-298 <https://issues.apache.org/jira/browse/RIVER-298>] - No
JavaDocs generated for package "com.sun.jini.reliableLog"
* [RIVER-302 <https://issues.apache.org/jira/browse/RIVER-302>] -
ClassDep -newdirbehaviour option does not work
* [RIVER-305 <https://issues.apache.org/jira/browse/RIVER-305>] -
qa/GetPermissions test still uses "enum" keyword
* [RIVER-320 <https://issues.apache.org/jira/browse/RIVER-320>] -
Prebuilt hello example certificates have expired - need to provide
new ones
* [RIVER-324 <https://issues.apache.org/jira/browse/RIVER-324>] -
Under certain circumstances, the ServiceDiscoveryManager internal
LookupCache implementation can incorrectly process attribute
change events before the lookup snapshot is processed.
Improvement
* [RIVER-7 <https://issues.apache.org/jira/browse/RIVER-7>] -
com.sun.jini.tool.ClassDep should be smarter with outer classes
* [RIVER-9 <https://issues.apache.org/jira/browse/RIVER-9>] -
PreferredClassLoader should try to avoid making a direct check
against the first URL
* [RIVER-25 <https://issues.apache.org/jira/browse/RIVER-25>] -
Improve logging for JoinManager at INFO and WARNING level
* [RIVER-115 <https://issues.apache.org/jira/browse/RIVER-115>] -
Multiple jar files with conflicting lists need facilities to map
the chosen preferred value
* [RIVER-116 <https://issues.apache.org/jira/browse/RIVER-116>] -
Multiple jar files with conflicting lists need facilities to map
the chosen preferred value
* [RIVER-160 <https://issues.apache.org/jira/browse/RIVER-160>] -
add TrustEquivalence to browser's list of uninterestingInterfaces
* [RIVER-201 <https://issues.apache.org/jira/browse/RIVER-201>] -
Show interfaces rather than classes in browser's Matching Services
pane.
* [RIVER-206 <https://issues.apache.org/jira/browse/RIVER-206>] -
Change default load factors from 3 to 1
* [RIVER-210 <https://issues.apache.org/jira/browse/RIVER-210>] -
Browser should cancel event lease on exit
* [RIVER-220 <https://issues.apache.org/jira/browse/RIVER-220>] -
LookupLocatorDiscovery catch Throwable blocks should also catch
Throwable
* [RIVER-226 <https://issues.apache.org/jira/browse/RIVER-226>] -
LLD: consider delaying the queuing of a discovery request
immediately after a discard
* [RIVER-229 <https://issues.apache.org/jira/browse/RIVER-229>] -
reduce number of Reaper threads created by ConnectionManager
* [RIVER-231 <https://issues.apache.org/jira/browse/RIVER-231>] -
ComputeHttpmdCodebase man page could be clarified with respect to
algorithm used
* [RIVER-233 <https://issues.apache.org/jira/browse/RIVER-233>] -
ComputeDigest instructions reference sha and sha1
* [RIVER-243 <https://issues.apache.org/jira/browse/RIVER-243>] -
JarWrapper javadoc could be clearer wrt to classpath manifests
* [RIVER-244 <https://issues.apache.org/jira/browse/RIVER-244>] -
Text area below menu bar in ServiceBrowser should not be editable
* [RIVER-246 <https://issues.apache.org/jira/browse/RIVER-246>] -
Consider adding shutdown hook so Reggie sends final multicast
packet if its VM is terminated
* [RIVER-247 <https://issues.apache.org/jira/browse/RIVER-247>] -
Destroy processing should use configurable duration and interval
for unexporting
* [RIVER-256 <https://issues.apache.org/jira/browse/RIVER-256>] -
Outrigger catch Throwable blocks should also catch Throwable
* [RIVER-262 <https://issues.apache.org/jira/browse/RIVER-262>] -
ServiceUI Specification
* [RIVER-270 <https://issues.apache.org/jira/browse/RIVER-270>] -
tar tasks in release* ant targets fail due to 100-char limitation
and are disabled
* [RIVER-285 <https://issues.apache.org/jira/browse/RIVER-285>] -
LookupDiscoveryManager has unused variable declarations
New Feature
* [RIVER-151 <https://issues.apache.org/jira/browse/RIVER-151>] -
ClassDep should have a method to determine if problems occurred
* [RIVER-161 <https://issues.apache.org/jira/browse/RIVER-161>] -
Coalesce jars from multiple source dirs while retain current
Manifest Classpath semantics
* [RIVER-163 <https://issues.apache.org/jira/browse/RIVER-163>] -
ClassDep doesn't pick up annotation or type parameter dependencies
* [RIVER-292 <https://issues.apache.org/jira/browse/RIVER-292>] -
The service browser should provide support for the ServiceUI support
* [RIVER-295 <https://issues.apache.org/jira/browse/RIVER-295>] -
Support configurable option to prevent from popup windows that
require a confirmation by the user
Task
* [RIVER-294 <https://issues.apache.org/jira/browse/RIVER-294>] -
Remove http://svn.apache.org/repos/asf/incubator/river/trunk/ from
the SVN repository
Test
* [RIVER-291 <https://issues.apache.org/jira/browse/RIVER-291>] -
Cannot build QA tests using the supplied make files
See the Release Artifacts for remaining release notes.
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [VOTE] Release Apache River 2.1.2
Posted by Tom Hobbs <tv...@googlemail.com>.
+1
Looks good to me.
Tom
On Wed, Mar 10, 2010 at 12:05 PM, Jim Waldo <Ji...@sun.com> wrote:
> +1 for the release
>
> Jim Waldo
>
> On Mar 10, 2010, at 4:39 AM, Peter Firmstone wrote:
>
> > Please vote on releasing Apache River 2.1.2
> >
>
>
Re: [VOTE] Release Apache River 2.1.2
Posted by Tom Hobbs <tv...@googlemail.com>.
+1
Looks good to me.
Tom
On Wed, Mar 10, 2010 at 12:05 PM, Jim Waldo <Ji...@sun.com> wrote:
> +1 for the release
>
> Jim Waldo
>
> On Mar 10, 2010, at 4:39 AM, Peter Firmstone wrote:
>
> > Please vote on releasing Apache River 2.1.2
> >
>
>
Re: [VOTE] Release Apache River 2.1.2
Posted by Jim Waldo <Ji...@Sun.COM>.
+1 for the release
Jim Waldo
On Mar 10, 2010, at 4:39 AM, Peter Firmstone wrote:
> Please vote on releasing Apache River 2.1.2
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [VOTE] Release Apache River 2.1.2
Posted by Sim IJskes - QCG <si...@qcg.nl>.
vote +1 (non-binding)
[based on: code works in production environment]
--
QCG, Software voor het MKB, 071-5890970, http://www.qcg.nl
Quality Consultancy Group b.v., Leiderdorp, Kvk Leiden: 28088397
RE: [VOTE] Release Apache River 2.1.2 (UNCLASSIFIED)
Posted by "Nelson, David C CTR US USA AMC" <da...@us.army.mil>.
Classification: UNCLASSIFIED
Caveats: FOUO
vote +1 (non-binding)
Quite excited with the direction this project is going! Great effort!
...
Please vote on releasing Apache River 2.1.2
...
Classification: UNCLASSIFIED
Caveats: FOUO
Re: [RESULT] Re: [VOTE] Release Apache River 2.1.2
Posted by Jukka Zitting <ju...@gmail.com>.
Hi,
On Thu, Apr 1, 2010 at 2:42 AM, Peter Firmstone <ji...@zeus.net.au> wrote:
> On this occassion, we have received the minimum three Incubator PMC votes,
> the vote has passed.
>
> No, it's no April fools joke, it's time to sit back, relax and have a quiet
> celebratory drink, to Apache River.
Excellent news, thanks!
BR,
Jukka Zitting
Re: [RESULT] Re: [VOTE] Release Apache River 2.1.2
Posted by Peter Firmstone <ji...@zeus.net.au>.
Thanks Jim,
Sorry, just can't let the future of computing die?
Logic:
Java / Bytecode - Open, Platform Independent, Network Transportable.
Network Computing is the future, but message passing is Protocol
Dependant, far less flexible and consumes more bandwidth...
Jini / River - Open and promises Protocol Independent, Dynamic
Distributed Computing. Pervasive Computing, perhaps one day.
I'd like to see River scale out into the internet.
Issues to be solved:
1. Package Version Metadata - add to Marshalled Object's, so we can
reconstruct an object from initially identical and later,
compatible bytecode and Package.
2. Obfuscate code base origin, obtain compatible bytecode via service
from compatible package, so objects can be unmarshalled long after
their creator node has vanished.
3. Organise ClassLoader structure, share bytecode by Package version
to minimise Class Loading and maximise Object compatibility and
interoperability.
4. Firewall Traversal - Various methods have been described, this is
solvable.
5. Internet Scale Discovery & Lookup, using MarshalledObject's and or
Streaming lookup results by Package version, to allow sharing of
bytecode and garbage collection to clean up unwanted ClassLoader's
/ bytecode after a group of Service Objects from a common package
have been inspected.
6. Untrusted Networks - perhaps the most difficult issue. If
downloaded bytecode can be trusted by both the client and service,
by utilising key signing and rings of trust while
MarshalledObject's are transmitted via encrypted means, there is a
chance that trust can be established and re-established if
necessary, since the code, service or client can be authenticated
/ trusted separately.
7. Easier application development and testing.
The lower hanging fruit would probably be 1, 2, 4 and 5. 3 and 6 are
perhaps the most difficult.
Had any thoughts lately?
Cheers,
Peter.
Jim Waldo wrote:
> Peter--
>
> Getting this out was your doing, and I thank you for the work you put in and the leadership you showed...
>
> Jim Waldo
>
> On Mar 31, 2010, at 8:42 PM, Peter Firmstone wrote:
>
>
>> Those voting in favour of Apache River Incubator Release 2.1.2 are (in chronological order):
>>
>> Sim IJskes
>> Jim Waldo
>> Jim Hurley
>> Tom Hobbs
>> Brian Murphy
>> David C Nelson
>> Gert Vanthienen
>> Jukka Zitting
>> Niclas Hedhman
>> Zsolt Kúti
>> Dan Rollo
>> Ant Elder
>> Jonathan Costers
>>
>> No votes against.
>>
>> On this occassion, we have received the minimum three Incubator PMC votes, the vote has passed.
>>
>> No, it's no April fools joke, it's time to sit back, relax and have a quiet celebratory drink, to Apache River.
>>
>> Thank you; to all our new contributors, committers, leaders and longtime stewards (you know who you are), whose efforts have made this latest release possible.
>>
>> Cheers,
>>
>> Peter Firmstone.
>>
>> Peter Firmstone wrote:
>>
>>> Please vote on releasing Apache River 2.1.2
>>>
>>> The voting period is open, due to the size of the River release, it will remain open until it passes with a majority of at least three +1 River Incubator PMC votes or until a valid objection causes its rejection.
>>>
>>> All are encouraged to show their support by validating and casting a vote for this release, please ensure you reply to both lists, so those on general can see your interest in and support for our project:
>>>
>>> general@incubator.apache.org
>>> river-dev@incubator.apache.org
>>>
>>> A candidate for the Apache River 2.1.2 Release is available at
>>>
>>> http://people.apache.org/~peter_firmstone/
>>>
>>> The release candidate sources are zip / tar.gz archives of the sources in:
>>>
>>> http://svn.apache.org/repos/asf/incubator/river/jtsk/trunk/
>>>
>>> The source release artifact SHA1 checksums are:
>>>
>>> apache-river-2.1.2-incubating-src.tar.gz:
>>> 6B18 E089 C22C 9790 B0A4 89CC A410 2250 7A0A 4890
>>> apache-river-2.1.2-incubating-src.zip:
>>> 28F8 ABB3 0BDF 149F 6FA0 8D8B C982 47A6 19EF AE43
>>>
>>> The binary release artifact SHA1 checksums:
>>>
>>> apache-river-2.1.2-incubating-bin.tar.gz:
>>> 3813 613B 4432 B5A9 E6F3 EFCA D649 D55A C73A 1BA8
>>> apache-river-2.1.2-incubating-bin.zip:
>>> F692 BCDC A050 9BCF 3ADD A5E4 C500 4263 0FAE 6BEE
>>>
>>>
>>> Apache River
>>> v2.1.2 Release Notes
>>>
>>> ------------------------------------------------------------------------
>>> Apache River is an effort undergoing incubation at The Apache Software
>>> Foundation (ASF), sponsored by the Apache Incubator. Incubation is
>>> required of all newly accepted projects until a further review indicates
>>> that the infrastructure, communications, and decision making process
>>> have stabilized in a manner consistent with other successful ASF
>>> projects. While incubation status is not necessarily a reflection of the
>>> completeness or stability of the code, it does indicate that the project
>>> has yet to be fully endorsed by the ASF.
>>>
>>> Apache River is aimed at the development and advancement of the River
>>> technology core infrastructure. River technology is a service oriented
>>> architecture that defines a programming model which both exploits and
>>> extends Java technology to enable the construction of secure,
>>> distributed systems which are adaptive to change.
>>>
>>> ------------------------------------------------------------------------
>>>
>>>
>>> Notes of Interest for this Release
>>>
>>> This second release from the Apache River project is based on the
>>> contributions of Sun's Jini Technology Starter Kit (Starter Kit) v2.1
>>> and Service UI from Artima. The release focuses on merging the two
>>> contributions together, structuring separate src and bin releases, and
>>> amending the source and documentation naming/versioning/etc to the
>>> Apache River project.
>>>
>>> Some points of note:
>>>
>>> * NOTICE file and source license headers updated
>>> * Source and documentation updated for release name ("Apache River
>>> release") and version ("v2.1.2")
>>> * Graphical installer (which was a 3rd party application in the
>>> Starter Kit) is no longer available
>>> * The combined source and binary release in the Starter Kit has been
>>> separated into two releases: src and bin
>>> * The "logstore" implementation of com.sun.jini.outrigger.Store has
>>> been removed
>>>
>>> The persistent version of Outrigger relies on a pluggable
>>> persistence layer, |com.sun.jini.outrigger.Store|. Previous
>>> releases of the Starter Kit included two implementations of the
>>> Store interface, /logstore/ and /snaplogstore/. This release
>>> removes logstore.
>>>
>>> Logstore has been around in various forms since the 1.0 version of
>>> Outrigger. Snapstore was introduced in v2.1 of the Starter Kit.
>>>
>>> The v2.0.n releases of the Starter Kit used logstore as the
>>> default Store implementation, this release has no default Store.
>>> In order to switch an existing set of configuration files,
>>> security policy files, etc., from using logstore to snaplogstore,
>>> you will need to change the |com.sun.jini.outrigger.store|
>>> configuration entry (or add a store configuration entry if you
>>> don't already have one) to yield a
>>> |com.sun.jini.outrigger.snaplogstore.LogStore| object. You will
>>> also need to ensure that |outrigger-snaplogstore.jar| has been
>>> granted sufficient permissions (see Outrigger's package
>>> documentation for a sample security policy file.).
>>>
>>> Note that depending on the nature of your application snaplogstore
>>> can have a significantly different performance profile than logstore.
>>>
>>> The storage formats used by snaplogstore and logstore are mutually
>>> incompatible.
>>>
>>> ------------------------------------------------------------------------
>>>
>>>
>>> Submitting Issues
>>>
>>> If you would like to submit a bug against the Apache River release,
>>> please use the River JIRA <http://issues.apache.org/jira/browse/RIVER>.
>>> To discuss problems, questions, or suggestions on the release, please
>>> subscribe to the |river-dev| list from the project Mailing Lists
>>> <http://incubator.apache.org/river/mailing.html> page.
>>>
>>> ------------------------------------------------------------------------
>>>
>>>
>>> Upcoming Changes planned for the next version of Apache River
>>>
>>> # All packages ouside of the net.jini namespace will be renamed to
>>> org.apache.river.
>>> # Support for Java 5 language features
>>> # Support for Modular Frameworks conforming to the OSGi r4.2 core
>>> Specification
>>> ------------------------------------------------------------------------
>>>
>>>
>>> Changes made since Apache River v2.1.1
>>>
>>>
>>> Bug
>>>
>>> * [RIVER-5 <https://issues.apache.org/jira/browse/RIVER-5>] -
>>> HTTMPMD URLs can be considered equal while they are not
>>> * [RIVER-8 <https://issues.apache.org/jira/browse/RIVER-8>] -
>>> com.sun.jini.tool.ClassDep empty inside collection doesn't work
>>> * [RIVER-17 <https://issues.apache.org/jira/browse/RIVER-17>] -
>>> Misleading logging message when discovery constraint checking is
>>> delayed
>>> * [RIVER-18 <https://issues.apache.org/jira/browse/RIVER-18>] -
>>> Order of discovery providers not maintained
>>> * [RIVER-22 <https://issues.apache.org/jira/browse/RIVER-22>] - NPE
>>> in
>>> net.jini.jeri.tcp.TcpEndpoint$ConnectionImpl.checkConnectPermission
>>> * [RIVER-24 <https://issues.apache.org/jira/browse/RIVER-24>] -
>>> PreferredListGen can create illegal PREFERRED.LIST
>>> * [RIVER-78 <https://issues.apache.org/jira/browse/RIVER-78>] -
>>> ClassDep generates duplicate output lines
>>> * [RIVER-82 <https://issues.apache.org/jira/browse/RIVER-82>] -
>>> ClassDep generates duplicate output lines
>>> * [RIVER-91 <https://issues.apache.org/jira/browse/RIVER-91>] -
>>> Uninstaller does not remove all items
>>> * [RIVER-205 <https://issues.apache.org/jira/browse/RIVER-205>] -
>>> LookupDiscovery can give untrusted code access to privileged threads
>>> * [RIVER-209 <https://issues.apache.org/jira/browse/RIVER-209>] -
>>> NullPointerException in SslConnection.checkConnectPermission()
>>> * [RIVER-212 <https://issues.apache.org/jira/browse/RIVER-212>] -
>>> use of "enum" as a variable name
>>> * [RIVER-213 <https://issues.apache.org/jira/browse/RIVER-213>] -
>>> (DOC) - JoinManger has typo in javadoc (missing </code>
>>> termination tag)
>>> * [RIVER-215 <https://issues.apache.org/jira/browse/RIVER-215>] -
>>> LookupDiscovery throws NullPointerException on terminate
>>> * [RIVER-216 <https://issues.apache.org/jira/browse/RIVER-216>] -
>>> ConfigurationFile should throw ExceptionInInitializerError if
>>> unable to read prohibited methods
>>> * [RIVER-217 <https://issues.apache.org/jira/browse/RIVER-217>] -
>>> Browser incorrectly assumes event source is ServiceRegistrar proxy
>>> * [RIVER-223 <https://issues.apache.org/jira/browse/RIVER-223>] -
>>> test: jtreg/net/jini/jeri/tcp/connectTimeout/TestConnectTimeout
>>> fails on Linux
>>> * [RIVER-224 <https://issues.apache.org/jira/browse/RIVER-224>] -
>>> Problem using browser to destroy service that supports
>>> DestroyAdmin but not JoinAdmin
>>> * [RIVER-225 <https://issues.apache.org/jira/browse/RIVER-225>] -
>>> NullPointerException in Reggie during destroy
>>> * [RIVER-227 <https://issues.apache.org/jira/browse/RIVER-227>] -
>>> tools manpages command lines do not include line continuation
>>> characters
>>> * [RIVER-230 <https://issues.apache.org/jira/browse/RIVER-230>] -
>>> (mux) SelectionManager catch Error block assumes getMessage()
>>> returns non-null
>>> * [RIVER-232 <https://issues.apache.org/jira/browse/RIVER-232>] -
>>> JarWrapper and PreferredListGen uses jsk_install_dir and install_dir
>>> * [RIVER-234 <https://issues.apache.org/jira/browse/RIVER-234>] -
>>> (DOC) Fiddler manpage directions for HTTP server should reference
>>> classserver.jar, not tools.jar
>>> * [RIVER-240 <https://issues.apache.org/jira/browse/RIVER-240>] -
>>> BasicInvocationDispatcher.dispatch could log more info for some
>>> exceptions
>>> * [RIVER-241 <https://issues.apache.org/jira/browse/RIVER-241>] -
>>> Mercury spelling errore
>>> * [RIVER-242 <https://issues.apache.org/jira/browse/RIVER-242>] - if
>>> a given ConnectionManager instance cannot create a reaper thread
>>> once, it never will again
>>> * [RIVER-245 <https://issues.apache.org/jira/browse/RIVER-245>] -
>>> Unicast discovery should close socket in case of connection
>>> exception.
>>> * [RIVER-252 <https://issues.apache.org/jira/browse/RIVER-252>] -
>>> ComputeHttpmdCodebase NPE if resource bundle not found
>>> * [RIVER-253 <https://issues.apache.org/jira/browse/RIVER-253>] -
>>> ComputeDigest NPE if resource bundle not found
>>> * [RIVER-254 <https://issues.apache.org/jira/browse/RIVER-254>] -
>>> request initiation can block on I/O for inapplicable connection
>>> * [RIVER-255 <https://issues.apache.org/jira/browse/RIVER-255>] -
>>> Outrigger DestroyThread does not catch exceptions from
>>> exporter.unexport
>>> * [RIVER-284 <https://issues.apache.org/jira/browse/RIVER-284>] -
>>> [PATCH] fix bad ParticipantHandle.compareTo
>>> * [RIVER-286 <https://issues.apache.org/jira/browse/RIVER-286>] -
>>> [PATCH] iterators on synchronized collections still need
>>> synchronization
>>> * [RIVER-289 <https://issues.apache.org/jira/browse/RIVER-289>] -
>>> Fix for RIVER-247 introduced wrong license headers and references
>>> * [RIVER-298 <https://issues.apache.org/jira/browse/RIVER-298>] - No
>>> JavaDocs generated for package "com.sun.jini.reliableLog"
>>> * [RIVER-302 <https://issues.apache.org/jira/browse/RIVER-302>] -
>>> ClassDep -newdirbehaviour option does not work
>>> * [RIVER-305 <https://issues.apache.org/jira/browse/RIVER-305>] -
>>> qa/GetPermissions test still uses "enum" keyword
>>> * [RIVER-320 <https://issues.apache.org/jira/browse/RIVER-320>] -
>>> Prebuilt hello example certificates have expired - need to provide
>>> new ones
>>> * [RIVER-324 <https://issues.apache.org/jira/browse/RIVER-324>] -
>>> Under certain circumstances, the ServiceDiscoveryManager internal
>>> LookupCache implementation can incorrectly process attribute
>>> change events before the lookup snapshot is processed.
>>>
>>>
>>> Improvement
>>>
>>> * [RIVER-7 <https://issues.apache.org/jira/browse/RIVER-7>] -
>>> com.sun.jini.tool.ClassDep should be smarter with outer classes
>>> * [RIVER-9 <https://issues.apache.org/jira/browse/RIVER-9>] -
>>> PreferredClassLoader should try to avoid making a direct check
>>> against the first URL
>>> * [RIVER-25 <https://issues.apache.org/jira/browse/RIVER-25>] -
>>> Improve logging for JoinManager at INFO and WARNING level
>>> * [RIVER-115 <https://issues.apache.org/jira/browse/RIVER-115>] -
>>> Multiple jar files with conflicting lists need facilities to map
>>> the chosen preferred value
>>> * [RIVER-116 <https://issues.apache.org/jira/browse/RIVER-116>] -
>>> Multiple jar files with conflicting lists need facilities to map
>>> the chosen preferred value
>>> * [RIVER-160 <https://issues.apache.org/jira/browse/RIVER-160>] -
>>> add TrustEquivalence to browser's list of uninterestingInterfaces
>>> * [RIVER-201 <https://issues.apache.org/jira/browse/RIVER-201>] -
>>> Show interfaces rather than classes in browser's Matching Services
>>> pane.
>>> * [RIVER-206 <https://issues.apache.org/jira/browse/RIVER-206>] -
>>> Change default load factors from 3 to 1
>>> * [RIVER-210 <https://issues.apache.org/jira/browse/RIVER-210>] -
>>> Browser should cancel event lease on exit
>>> * [RIVER-220 <https://issues.apache.org/jira/browse/RIVER-220>] -
>>> LookupLocatorDiscovery catch Throwable blocks should also catch
>>> Throwable
>>> * [RIVER-226 <https://issues.apache.org/jira/browse/RIVER-226>] -
>>> LLD: consider delaying the queuing of a discovery request
>>> immediately after a discard
>>> * [RIVER-229 <https://issues.apache.org/jira/browse/RIVER-229>] -
>>> reduce number of Reaper threads created by ConnectionManager
>>> * [RIVER-231 <https://issues.apache.org/jira/browse/RIVER-231>] -
>>> ComputeHttpmdCodebase man page could be clarified with respect to
>>> algorithm used
>>> * [RIVER-233 <https://issues.apache.org/jira/browse/RIVER-233>] -
>>> ComputeDigest instructions reference sha and sha1
>>> * [RIVER-243 <https://issues.apache.org/jira/browse/RIVER-243>] -
>>> JarWrapper javadoc could be clearer wrt to classpath manifests
>>> * [RIVER-244 <https://issues.apache.org/jira/browse/RIVER-244>] -
>>> Text area below menu bar in ServiceBrowser should not be editable
>>> * [RIVER-246 <https://issues.apache.org/jira/browse/RIVER-246>] -
>>> Consider adding shutdown hook so Reggie sends final multicast
>>> packet if its VM is terminated
>>> * [RIVER-247 <https://issues.apache.org/jira/browse/RIVER-247>] -
>>> Destroy processing should use configurable duration and interval
>>> for unexporting
>>> * [RIVER-256 <https://issues.apache.org/jira/browse/RIVER-256>] -
>>> Outrigger catch Throwable blocks should also catch Throwable
>>> * [RIVER-262 <https://issues.apache.org/jira/browse/RIVER-262>] -
>>> ServiceUI Specification
>>> * [RIVER-270 <https://issues.apache.org/jira/browse/RIVER-270>] -
>>> tar tasks in release* ant targets fail due to 100-char limitation
>>> and are disabled
>>> * [RIVER-285 <https://issues.apache.org/jira/browse/RIVER-285>] -
>>> LookupDiscoveryManager has unused variable declarations
>>>
>>>
>>> New Feature
>>>
>>> * [RIVER-151 <https://issues.apache.org/jira/browse/RIVER-151>] -
>>> ClassDep should have a method to determine if problems occurred
>>> * [RIVER-161 <https://issues.apache.org/jira/browse/RIVER-161>] -
>>> Coalesce jars from multiple source dirs while retain current
>>> Manifest Classpath semantics
>>> * [RIVER-163 <https://issues.apache.org/jira/browse/RIVER-163>] -
>>> ClassDep doesn't pick up annotation or type parameter dependencies
>>> * [RIVER-292 <https://issues.apache.org/jira/browse/RIVER-292>] -
>>> The service browser should provide support for the ServiceUI support
>>> * [RIVER-295 <https://issues.apache.org/jira/browse/RIVER-295>] -
>>> Support configurable option to prevent from popup windows that
>>> require a confirmation by the user
>>>
>>>
>>> Task
>>>
>>> * [RIVER-294 <https://issues.apache.org/jira/browse/RIVER-294>] -
>>> Remove http://svn.apache.org/repos/asf/incubator/river/trunk/ from
>>> the SVN repository
>>>
>>>
>>> Test
>>>
>>> * [RIVER-291 <https://issues.apache.org/jira/browse/RIVER-291>] -
>>> Cannot build QA tests using the supplied make files
>>>
>>> See the Release Artifacts for remaining release notes.
>>>
>>>
>>>
>>>
>>>
>>>
>
>
>
Re: [RESULT] Re: [VOTE] Release Apache River 2.1.2
Posted by Mike McGrady <mm...@topiatechnology.com>.
+1 good job
Sent from my iPhone
Michael McGrady
Principal investigator AF081_028 SBIR
Senior Engineer
Topia Technology, Inc
Work 1.253.572.9712
Cel 1.253.720.3365
On Apr 1, 2010, at 4:38 AM, Jim Waldo <ji...@oracle.com> wrote:
> Peter--
>
> Getting this out was your doing, and I thank you for the work you
> put in and the leadership you showed...
>
> Jim Waldo
>
> On Mar 31, 2010, at 8:42 PM, Peter Firmstone wrote:
>
>> Those voting in favour of Apache River Incubator Release 2.1.2 are
>> (in chronological order):
>>
>> Sim IJskes
>> Jim Waldo
>> Jim Hurley
>> Tom Hobbs
>> Brian Murphy
>> David C Nelson
>> Gert Vanthienen
>> Jukka Zitting
>> Niclas Hedhman
>> Zsolt Kúti
>> Dan Rollo
>> Ant Elder
>> Jonathan Costers
>>
>> No votes against.
>>
>> On this occassion, we have received the minimum three Incubator PMC
>> votes, the vote has passed.
>>
>> No, it's no April fools joke, it's time to sit back, relax and have
>> a quiet celebratory drink, to Apache River.
>>
>> Thank you; to all our new contributors, committers, leaders and
>> longtime stewards (you know who you are), whose efforts have made
>> this latest release possible.
>>
>> Cheers,
>>
>> Peter Firmstone.
>>
>> Peter Firmstone wrote:
>>> Please vote on releasing Apache River 2.1.2
>>>
>>> The voting period is open, due to the size of the River release,
>>> it will remain open until it passes with a majority of at least
>>> three +1 River Incubator PMC votes or until a valid objection
>>> causes its rejection.
>>>
>>> All are encouraged to show their support by validating and casting
>>> a vote for this release, please ensure you reply to both lists, so
>>> those on general can see your interest in and support for our
>>> project:
>>>
>>> general@incubator.apache.org
>>> river-dev@incubator.apache.org
>>>
>>> A candidate for the Apache River 2.1.2 Release is available at
>>>
>>> http://people.apache.org/~peter_firmstone/
>>>
>>> The release candidate sources are zip / tar.gz archives of the
>>> sources in:
>>>
>>> http://svn.apache.org/repos/asf/incubator/river/jtsk/trunk/
>>>
>>> The source release artifact SHA1 checksums are:
>>>
>>> apache-river-2.1.2-incubating-src.tar.gz:
>>> 6B18 E089 C22C 9790 B0A4 89CC A410 2250 7A0A 4890
>>> apache-river-2.1.2-incubating-src.zip:
>>> 28F8 ABB3 0BDF 149F 6FA0 8D8B C982 47A6 19EF AE43
>>>
>>> The binary release artifact SHA1 checksums:
>>>
>>> apache-river-2.1.2-incubating-bin.tar.gz:
>>> 3813 613B 4432 B5A9 E6F3 EFCA D649 D55A C73A 1BA8
>>> apache-river-2.1.2-incubating-bin.zip:
>>> F692 BCDC A050 9BCF 3ADD A5E4 C500 4263 0FAE 6BEE
>>>
>>>
>>> Apache River
>>> v2.1.2 Release Notes
>>>
>>> ---
>>> ---
>>> ------------------------------------------------------------------
>>> Apache River is an effort undergoing incubation at The Apache
>>> Software
>>> Foundation (ASF), sponsored by the Apache Incubator. Incubation is
>>> required of all newly accepted projects until a further review
>>> indicates
>>> that the infrastructure, communications, and decision making process
>>> have stabilized in a manner consistent with other successful ASF
>>> projects. While incubation status is not necessarily a reflection
>>> of the
>>> completeness or stability of the code, it does indicate that the
>>> project
>>> has yet to be fully endorsed by the ASF.
>>>
>>> Apache River is aimed at the development and advancement of the
>>> River
>>> technology core infrastructure. River technology is a service
>>> oriented
>>> architecture that defines a programming model which both exploits
>>> and
>>> extends Java technology to enable the construction of secure,
>>> distributed systems which are adaptive to change.
>>>
>>> ---
>>> ---
>>> ------------------------------------------------------------------
>>>
>>>
>>> Notes of Interest for this Release
>>>
>>> This second release from the Apache River project is based on the
>>> contributions of Sun's Jini Technology Starter Kit (Starter Kit)
>>> v2.1
>>> and Service UI from Artima. The release focuses on merging the two
>>> contributions together, structuring separate src and bin releases,
>>> and
>>> amending the source and documentation naming/versioning/etc to the
>>> Apache River project.
>>>
>>> Some points of note:
>>>
>>> * NOTICE file and source license headers updated
>>> * Source and documentation updated for release name ("Apache River
>>> release") and version ("v2.1.2")
>>> * Graphical installer (which was a 3rd party application in the
>>> Starter Kit) is no longer available
>>> * The combined source and binary release in the Starter Kit has
>>> been
>>> separated into two releases: src and bin
>>> * The "logstore" implementation of com.sun.jini.outrigger.Store has
>>> been removed
>>>
>>> The persistent version of Outrigger relies on a pluggable
>>> persistence layer, |com.sun.jini.outrigger.Store|. Previous
>>> releases of the Starter Kit included two implementations of the
>>> Store interface, /logstore/ and /snaplogstore/. This release
>>> removes logstore.
>>>
>>> Logstore has been around in various forms since the 1.0 version
>>> of
>>> Outrigger. Snapstore was introduced in v2.1 of the Starter Kit.
>>>
>>> The v2.0.n releases of the Starter Kit used logstore as the
>>> default Store implementation, this release has no default Store.
>>> In order to switch an existing set of configuration files,
>>> security policy files, etc., from using logstore to snaplogstore,
>>> you will need to change the |com.sun.jini.outrigger.store|
>>> configuration entry (or add a store configuration entry if you
>>> don't already have one) to yield a
>>> |com.sun.jini.outrigger.snaplogstore.LogStore| object. You will
>>> also need to ensure that |outrigger-snaplogstore.jar| has been
>>> granted sufficient permissions (see Outrigger's package
>>> documentation for a sample security policy file.).
>>>
>>> Note that depending on the nature of your application
>>> snaplogstore
>>> can have a significantly different performance profile than
>>> logstore.
>>>
>>> The storage formats used by snaplogstore and logstore are
>>> mutually
>>> incompatible.
>>>
>>> ---
>>> ---
>>> ------------------------------------------------------------------
>>>
>>>
>>> Submitting Issues
>>>
>>> If you would like to submit a bug against the Apache River release,
>>> please use the River JIRA <http://issues.apache.org/jira/browse/RIVER
>>> >.
>>> To discuss problems, questions, or suggestions on the release,
>>> please
>>> subscribe to the |river-dev| list from the project Mailing Lists
>>> <http://incubator.apache.org/river/mailing.html> page.
>>>
>>> ---
>>> ---
>>> ------------------------------------------------------------------
>>>
>>>
>>> Upcoming Changes planned for the next version of Apache River
>>>
>>> # All packages ouside of the net.jini namespace will be renamed to
>>> org.apache.river.
>>> # Support for Java 5 language features
>>> # Support for Modular Frameworks conforming to the OSGi r4.2 core
>>> Specification
>>> ---
>>> ---
>>> ------------------------------------------------------------------
>>>
>>>
>>> Changes made since Apache River v2.1.1
>>>
>>>
>>> Bug
>>>
>>> * [RIVER-5 <https://issues.apache.org/jira/browse/RIVER-5>] -
>>> HTTMPMD URLs can be considered equal while they are not
>>> * [RIVER-8 <https://issues.apache.org/jira/browse/RIVER-8>] -
>>> com.sun.jini.tool.ClassDep empty inside collection doesn't work
>>> * [RIVER-17 <https://issues.apache.org/jira/browse/RIVER-17>] -
>>> Misleading logging message when discovery constraint checking is
>>> delayed
>>> * [RIVER-18 <https://issues.apache.org/jira/browse/RIVER-18>] -
>>> Order of discovery providers not maintained
>>> * [RIVER-22 <https://issues.apache.org/jira/browse/RIVER-22>] - NPE
>>> in
>>> net.jini.jeri.tcp.TcpEndpoint
>>> $ConnectionImpl.checkConnectPermission
>>> * [RIVER-24 <https://issues.apache.org/jira/browse/RIVER-24>] -
>>> PreferredListGen can create illegal PREFERRED.LIST
>>> * [RIVER-78 <https://issues.apache.org/jira/browse/RIVER-78>] -
>>> ClassDep generates duplicate output lines
>>> * [RIVER-82 <https://issues.apache.org/jira/browse/RIVER-82>] -
>>> ClassDep generates duplicate output lines
>>> * [RIVER-91 <https://issues.apache.org/jira/browse/RIVER-91>] -
>>> Uninstaller does not remove all items
>>> * [RIVER-205 <https://issues.apache.org/jira/browse/RIVER-205>] -
>>> LookupDiscovery can give untrusted code access to privileged
>>> threads
>>> * [RIVER-209 <https://issues.apache.org/jira/browse/RIVER-209>] -
>>> NullPointerException in SslConnection.checkConnectPermission()
>>> * [RIVER-212 <https://issues.apache.org/jira/browse/RIVER-212>] -
>>> use of "enum" as a variable name
>>> * [RIVER-213 <https://issues.apache.org/jira/browse/RIVER-213>] -
>>> (DOC) - JoinManger has typo in javadoc (missing </code>
>>> termination tag)
>>> * [RIVER-215 <https://issues.apache.org/jira/browse/RIVER-215>] -
>>> LookupDiscovery throws NullPointerException on terminate
>>> * [RIVER-216 <https://issues.apache.org/jira/browse/RIVER-216>] -
>>> ConfigurationFile should throw ExceptionInInitializerError if
>>> unable to read prohibited methods
>>> * [RIVER-217 <https://issues.apache.org/jira/browse/RIVER-217>] -
>>> Browser incorrectly assumes event source is ServiceRegistrar
>>> proxy
>>> * [RIVER-223 <https://issues.apache.org/jira/browse/RIVER-223>] -
>>> test: jtreg/net/jini/jeri/tcp/connectTimeout/TestConnectTimeout
>>> fails on Linux
>>> * [RIVER-224 <https://issues.apache.org/jira/browse/RIVER-224>] -
>>> Problem using browser to destroy service that supports
>>> DestroyAdmin but not JoinAdmin
>>> * [RIVER-225 <https://issues.apache.org/jira/browse/RIVER-225>] -
>>> NullPointerException in Reggie during destroy
>>> * [RIVER-227 <https://issues.apache.org/jira/browse/RIVER-227>] -
>>> tools manpages command lines do not include line continuation
>>> characters
>>> * [RIVER-230 <https://issues.apache.org/jira/browse/RIVER-230>] -
>>> (mux) SelectionManager catch Error block assumes getMessage()
>>> returns non-null
>>> * [RIVER-232 <https://issues.apache.org/jira/browse/RIVER-232>] -
>>> JarWrapper and PreferredListGen uses jsk_install_dir and
>>> install_dir
>>> * [RIVER-234 <https://issues.apache.org/jira/browse/RIVER-234>] -
>>> (DOC) Fiddler manpage directions for HTTP server should reference
>>> classserver.jar, not tools.jar
>>> * [RIVER-240 <https://issues.apache.org/jira/browse/RIVER-240>] -
>>> BasicInvocationDispatcher.dispatch could log more info for some
>>> exceptions
>>> * [RIVER-241 <https://issues.apache.org/jira/browse/RIVER-241>] -
>>> Mercury spelling errore
>>> * [RIVER-242 <https://issues.apache.org/jira/browse/RIVER-242>] -
>>> if
>>> a given ConnectionManager instance cannot create a reaper thread
>>> once, it never will again
>>> * [RIVER-245 <https://issues.apache.org/jira/browse/RIVER-245>] -
>>> Unicast discovery should close socket in case of connection
>>> exception.
>>> * [RIVER-252 <https://issues.apache.org/jira/browse/RIVER-252>] -
>>> ComputeHttpmdCodebase NPE if resource bundle not found
>>> * [RIVER-253 <https://issues.apache.org/jira/browse/RIVER-253>] -
>>> ComputeDigest NPE if resource bundle not found
>>> * [RIVER-254 <https://issues.apache.org/jira/browse/RIVER-254>] -
>>> request initiation can block on I/O for inapplicable connection
>>> * [RIVER-255 <https://issues.apache.org/jira/browse/RIVER-255>] -
>>> Outrigger DestroyThread does not catch exceptions from
>>> exporter.unexport
>>> * [RIVER-284 <https://issues.apache.org/jira/browse/RIVER-284>] -
>>> [PATCH] fix bad ParticipantHandle.compareTo
>>> * [RIVER-286 <https://issues.apache.org/jira/browse/RIVER-286>] -
>>> [PATCH] iterators on synchronized collections still need
>>> synchronization
>>> * [RIVER-289 <https://issues.apache.org/jira/browse/RIVER-289>] -
>>> Fix for RIVER-247 introduced wrong license headers and references
>>> * [RIVER-298 <https://issues.apache.org/jira/browse/RIVER-298>] -
>>> No
>>> JavaDocs generated for package "com.sun.jini.reliableLog"
>>> * [RIVER-302 <https://issues.apache.org/jira/browse/RIVER-302>] -
>>> ClassDep -newdirbehaviour option does not work
>>> * [RIVER-305 <https://issues.apache.org/jira/browse/RIVER-305>] -
>>> qa/GetPermissions test still uses "enum" keyword
>>> * [RIVER-320 <https://issues.apache.org/jira/browse/RIVER-320>] -
>>> Prebuilt hello example certificates have expired - need to
>>> provide
>>> new ones
>>> * [RIVER-324 <https://issues.apache.org/jira/browse/RIVER-324>] -
>>> Under certain circumstances, the ServiceDiscoveryManager internal
>>> LookupCache implementation can incorrectly process attribute
>>> change events before the lookup snapshot is processed.
>>>
>>>
>>> Improvement
>>>
>>> * [RIVER-7 <https://issues.apache.org/jira/browse/RIVER-7>] -
>>> com.sun.jini.tool.ClassDep should be smarter with outer classes
>>> * [RIVER-9 <https://issues.apache.org/jira/browse/RIVER-9>] -
>>> PreferredClassLoader should try to avoid making a direct check
>>> against the first URL
>>> * [RIVER-25 <https://issues.apache.org/jira/browse/RIVER-25>] -
>>> Improve logging for JoinManager at INFO and WARNING level
>>> * [RIVER-115 <https://issues.apache.org/jira/browse/RIVER-115>] -
>>> Multiple jar files with conflicting lists need facilities to map
>>> the chosen preferred value
>>> * [RIVER-116 <https://issues.apache.org/jira/browse/RIVER-116>] -
>>> Multiple jar files with conflicting lists need facilities to map
>>> the chosen preferred value
>>> * [RIVER-160 <https://issues.apache.org/jira/browse/RIVER-160>] -
>>> add TrustEquivalence to browser's list of uninterestingInterfaces
>>> * [RIVER-201 <https://issues.apache.org/jira/browse/RIVER-201>] -
>>> Show interfaces rather than classes in browser's Matching
>>> Services
>>> pane.
>>> * [RIVER-206 <https://issues.apache.org/jira/browse/RIVER-206>] -
>>> Change default load factors from 3 to 1
>>> * [RIVER-210 <https://issues.apache.org/jira/browse/RIVER-210>] -
>>> Browser should cancel event lease on exit
>>> * [RIVER-220 <https://issues.apache.org/jira/browse/RIVER-220>] -
>>> LookupLocatorDiscovery catch Throwable blocks should also catch
>>> Throwable
>>> * [RIVER-226 <https://issues.apache.org/jira/browse/RIVER-226>] -
>>> LLD: consider delaying the queuing of a discovery request
>>> immediately after a discard
>>> * [RIVER-229 <https://issues.apache.org/jira/browse/RIVER-229>] -
>>> reduce number of Reaper threads created by ConnectionManager
>>> * [RIVER-231 <https://issues.apache.org/jira/browse/RIVER-231>] -
>>> ComputeHttpmdCodebase man page could be clarified with respect to
>>> algorithm used
>>> * [RIVER-233 <https://issues.apache.org/jira/browse/RIVER-233>] -
>>> ComputeDigest instructions reference sha and sha1
>>> * [RIVER-243 <https://issues.apache.org/jira/browse/RIVER-243>] -
>>> JarWrapper javadoc could be clearer wrt to classpath manifests
>>> * [RIVER-244 <https://issues.apache.org/jira/browse/RIVER-244>] -
>>> Text area below menu bar in ServiceBrowser should not be editable
>>> * [RIVER-246 <https://issues.apache.org/jira/browse/RIVER-246>] -
>>> Consider adding shutdown hook so Reggie sends final multicast
>>> packet if its VM is terminated
>>> * [RIVER-247 <https://issues.apache.org/jira/browse/RIVER-247>] -
>>> Destroy processing should use configurable duration and interval
>>> for unexporting
>>> * [RIVER-256 <https://issues.apache.org/jira/browse/RIVER-256>] -
>>> Outrigger catch Throwable blocks should also catch Throwable
>>> * [RIVER-262 <https://issues.apache.org/jira/browse/RIVER-262>] -
>>> ServiceUI Specification
>>> * [RIVER-270 <https://issues.apache.org/jira/browse/RIVER-270>] -
>>> tar tasks in release* ant targets fail due to 100-char limitation
>>> and are disabled
>>> * [RIVER-285 <https://issues.apache.org/jira/browse/RIVER-285>] -
>>> LookupDiscoveryManager has unused variable declarations
>>>
>>>
>>> New Feature
>>>
>>> * [RIVER-151 <https://issues.apache.org/jira/browse/RIVER-151>] -
>>> ClassDep should have a method to determine if problems occurred
>>> * [RIVER-161 <https://issues.apache.org/jira/browse/RIVER-161>] -
>>> Coalesce jars from multiple source dirs while retain current
>>> Manifest Classpath semantics
>>> * [RIVER-163 <https://issues.apache.org/jira/browse/RIVER-163>] -
>>> ClassDep doesn't pick up annotation or type parameter
>>> dependencies
>>> * [RIVER-292 <https://issues.apache.org/jira/browse/RIVER-292>] -
>>> The service browser should provide support for the ServiceUI
>>> support
>>> * [RIVER-295 <https://issues.apache.org/jira/browse/RIVER-295>] -
>>> Support configurable option to prevent from popup windows that
>>> require a confirmation by the user
>>>
>>>
>>> Task
>>>
>>> * [RIVER-294 <https://issues.apache.org/jira/browse/RIVER-294>] -
>>> Remove http://svn.apache.org/repos/asf/incubator/river/trunk/
>>> from
>>> the SVN repository
>>>
>>>
>>> Test
>>>
>>> * [RIVER-291 <https://issues.apache.org/jira/browse/RIVER-291>] -
>>> Cannot build QA tests using the supplied make files
>>>
>>> See the Release Artifacts for remaining release notes.
>>>
>>>
>>>
>>>
>>>
>>
>
Re: [RESULT] Re: [VOTE] Release Apache River 2.1.2
Posted by Jim Waldo <ji...@oracle.com>.
Peter--
Getting this out was your doing, and I thank you for the work you put in and the leadership you showed...
Jim Waldo
On Mar 31, 2010, at 8:42 PM, Peter Firmstone wrote:
> Those voting in favour of Apache River Incubator Release 2.1.2 are (in chronological order):
>
> Sim IJskes
> Jim Waldo
> Jim Hurley
> Tom Hobbs
> Brian Murphy
> David C Nelson
> Gert Vanthienen
> Jukka Zitting
> Niclas Hedhman
> Zsolt Kúti
> Dan Rollo
> Ant Elder
> Jonathan Costers
>
> No votes against.
>
> On this occassion, we have received the minimum three Incubator PMC votes, the vote has passed.
>
> No, it's no April fools joke, it's time to sit back, relax and have a quiet celebratory drink, to Apache River.
>
> Thank you; to all our new contributors, committers, leaders and longtime stewards (you know who you are), whose efforts have made this latest release possible.
>
> Cheers,
>
> Peter Firmstone.
>
> Peter Firmstone wrote:
>> Please vote on releasing Apache River 2.1.2
>>
>> The voting period is open, due to the size of the River release, it will remain open until it passes with a majority of at least three +1 River Incubator PMC votes or until a valid objection causes its rejection.
>>
>> All are encouraged to show their support by validating and casting a vote for this release, please ensure you reply to both lists, so those on general can see your interest in and support for our project:
>>
>> general@incubator.apache.org
>> river-dev@incubator.apache.org
>>
>> A candidate for the Apache River 2.1.2 Release is available at
>>
>> http://people.apache.org/~peter_firmstone/
>>
>> The release candidate sources are zip / tar.gz archives of the sources in:
>>
>> http://svn.apache.org/repos/asf/incubator/river/jtsk/trunk/
>>
>> The source release artifact SHA1 checksums are:
>>
>> apache-river-2.1.2-incubating-src.tar.gz:
>> 6B18 E089 C22C 9790 B0A4 89CC A410 2250 7A0A 4890
>> apache-river-2.1.2-incubating-src.zip:
>> 28F8 ABB3 0BDF 149F 6FA0 8D8B C982 47A6 19EF AE43
>>
>> The binary release artifact SHA1 checksums:
>>
>> apache-river-2.1.2-incubating-bin.tar.gz:
>> 3813 613B 4432 B5A9 E6F3 EFCA D649 D55A C73A 1BA8
>> apache-river-2.1.2-incubating-bin.zip:
>> F692 BCDC A050 9BCF 3ADD A5E4 C500 4263 0FAE 6BEE
>>
>>
>> Apache River
>> v2.1.2 Release Notes
>>
>> ------------------------------------------------------------------------
>> Apache River is an effort undergoing incubation at The Apache Software
>> Foundation (ASF), sponsored by the Apache Incubator. Incubation is
>> required of all newly accepted projects until a further review indicates
>> that the infrastructure, communications, and decision making process
>> have stabilized in a manner consistent with other successful ASF
>> projects. While incubation status is not necessarily a reflection of the
>> completeness or stability of the code, it does indicate that the project
>> has yet to be fully endorsed by the ASF.
>>
>> Apache River is aimed at the development and advancement of the River
>> technology core infrastructure. River technology is a service oriented
>> architecture that defines a programming model which both exploits and
>> extends Java technology to enable the construction of secure,
>> distributed systems which are adaptive to change.
>>
>> ------------------------------------------------------------------------
>>
>>
>> Notes of Interest for this Release
>>
>> This second release from the Apache River project is based on the
>> contributions of Sun's Jini Technology Starter Kit (Starter Kit) v2.1
>> and Service UI from Artima. The release focuses on merging the two
>> contributions together, structuring separate src and bin releases, and
>> amending the source and documentation naming/versioning/etc to the
>> Apache River project.
>>
>> Some points of note:
>>
>> * NOTICE file and source license headers updated
>> * Source and documentation updated for release name ("Apache River
>> release") and version ("v2.1.2")
>> * Graphical installer (which was a 3rd party application in the
>> Starter Kit) is no longer available
>> * The combined source and binary release in the Starter Kit has been
>> separated into two releases: src and bin
>> * The "logstore" implementation of com.sun.jini.outrigger.Store has
>> been removed
>>
>> The persistent version of Outrigger relies on a pluggable
>> persistence layer, |com.sun.jini.outrigger.Store|. Previous
>> releases of the Starter Kit included two implementations of the
>> Store interface, /logstore/ and /snaplogstore/. This release
>> removes logstore.
>>
>> Logstore has been around in various forms since the 1.0 version of
>> Outrigger. Snapstore was introduced in v2.1 of the Starter Kit.
>>
>> The v2.0.n releases of the Starter Kit used logstore as the
>> default Store implementation, this release has no default Store.
>> In order to switch an existing set of configuration files,
>> security policy files, etc., from using logstore to snaplogstore,
>> you will need to change the |com.sun.jini.outrigger.store|
>> configuration entry (or add a store configuration entry if you
>> don't already have one) to yield a
>> |com.sun.jini.outrigger.snaplogstore.LogStore| object. You will
>> also need to ensure that |outrigger-snaplogstore.jar| has been
>> granted sufficient permissions (see Outrigger's package
>> documentation for a sample security policy file.).
>>
>> Note that depending on the nature of your application snaplogstore
>> can have a significantly different performance profile than logstore.
>>
>> The storage formats used by snaplogstore and logstore are mutually
>> incompatible.
>>
>> ------------------------------------------------------------------------
>>
>>
>> Submitting Issues
>>
>> If you would like to submit a bug against the Apache River release,
>> please use the River JIRA <http://issues.apache.org/jira/browse/RIVER>.
>> To discuss problems, questions, or suggestions on the release, please
>> subscribe to the |river-dev| list from the project Mailing Lists
>> <http://incubator.apache.org/river/mailing.html> page.
>>
>> ------------------------------------------------------------------------
>>
>>
>> Upcoming Changes planned for the next version of Apache River
>>
>> # All packages ouside of the net.jini namespace will be renamed to
>> org.apache.river.
>> # Support for Java 5 language features
>> # Support for Modular Frameworks conforming to the OSGi r4.2 core
>> Specification
>> ------------------------------------------------------------------------
>>
>>
>> Changes made since Apache River v2.1.1
>>
>>
>> Bug
>>
>> * [RIVER-5 <https://issues.apache.org/jira/browse/RIVER-5>] -
>> HTTMPMD URLs can be considered equal while they are not
>> * [RIVER-8 <https://issues.apache.org/jira/browse/RIVER-8>] -
>> com.sun.jini.tool.ClassDep empty inside collection doesn't work
>> * [RIVER-17 <https://issues.apache.org/jira/browse/RIVER-17>] -
>> Misleading logging message when discovery constraint checking is
>> delayed
>> * [RIVER-18 <https://issues.apache.org/jira/browse/RIVER-18>] -
>> Order of discovery providers not maintained
>> * [RIVER-22 <https://issues.apache.org/jira/browse/RIVER-22>] - NPE
>> in
>> net.jini.jeri.tcp.TcpEndpoint$ConnectionImpl.checkConnectPermission
>> * [RIVER-24 <https://issues.apache.org/jira/browse/RIVER-24>] -
>> PreferredListGen can create illegal PREFERRED.LIST
>> * [RIVER-78 <https://issues.apache.org/jira/browse/RIVER-78>] -
>> ClassDep generates duplicate output lines
>> * [RIVER-82 <https://issues.apache.org/jira/browse/RIVER-82>] -
>> ClassDep generates duplicate output lines
>> * [RIVER-91 <https://issues.apache.org/jira/browse/RIVER-91>] -
>> Uninstaller does not remove all items
>> * [RIVER-205 <https://issues.apache.org/jira/browse/RIVER-205>] -
>> LookupDiscovery can give untrusted code access to privileged threads
>> * [RIVER-209 <https://issues.apache.org/jira/browse/RIVER-209>] -
>> NullPointerException in SslConnection.checkConnectPermission()
>> * [RIVER-212 <https://issues.apache.org/jira/browse/RIVER-212>] -
>> use of "enum" as a variable name
>> * [RIVER-213 <https://issues.apache.org/jira/browse/RIVER-213>] -
>> (DOC) - JoinManger has typo in javadoc (missing </code>
>> termination tag)
>> * [RIVER-215 <https://issues.apache.org/jira/browse/RIVER-215>] -
>> LookupDiscovery throws NullPointerException on terminate
>> * [RIVER-216 <https://issues.apache.org/jira/browse/RIVER-216>] -
>> ConfigurationFile should throw ExceptionInInitializerError if
>> unable to read prohibited methods
>> * [RIVER-217 <https://issues.apache.org/jira/browse/RIVER-217>] -
>> Browser incorrectly assumes event source is ServiceRegistrar proxy
>> * [RIVER-223 <https://issues.apache.org/jira/browse/RIVER-223>] -
>> test: jtreg/net/jini/jeri/tcp/connectTimeout/TestConnectTimeout
>> fails on Linux
>> * [RIVER-224 <https://issues.apache.org/jira/browse/RIVER-224>] -
>> Problem using browser to destroy service that supports
>> DestroyAdmin but not JoinAdmin
>> * [RIVER-225 <https://issues.apache.org/jira/browse/RIVER-225>] -
>> NullPointerException in Reggie during destroy
>> * [RIVER-227 <https://issues.apache.org/jira/browse/RIVER-227>] -
>> tools manpages command lines do not include line continuation
>> characters
>> * [RIVER-230 <https://issues.apache.org/jira/browse/RIVER-230>] -
>> (mux) SelectionManager catch Error block assumes getMessage()
>> returns non-null
>> * [RIVER-232 <https://issues.apache.org/jira/browse/RIVER-232>] -
>> JarWrapper and PreferredListGen uses jsk_install_dir and install_dir
>> * [RIVER-234 <https://issues.apache.org/jira/browse/RIVER-234>] -
>> (DOC) Fiddler manpage directions for HTTP server should reference
>> classserver.jar, not tools.jar
>> * [RIVER-240 <https://issues.apache.org/jira/browse/RIVER-240>] -
>> BasicInvocationDispatcher.dispatch could log more info for some
>> exceptions
>> * [RIVER-241 <https://issues.apache.org/jira/browse/RIVER-241>] -
>> Mercury spelling errore
>> * [RIVER-242 <https://issues.apache.org/jira/browse/RIVER-242>] - if
>> a given ConnectionManager instance cannot create a reaper thread
>> once, it never will again
>> * [RIVER-245 <https://issues.apache.org/jira/browse/RIVER-245>] -
>> Unicast discovery should close socket in case of connection
>> exception.
>> * [RIVER-252 <https://issues.apache.org/jira/browse/RIVER-252>] -
>> ComputeHttpmdCodebase NPE if resource bundle not found
>> * [RIVER-253 <https://issues.apache.org/jira/browse/RIVER-253>] -
>> ComputeDigest NPE if resource bundle not found
>> * [RIVER-254 <https://issues.apache.org/jira/browse/RIVER-254>] -
>> request initiation can block on I/O for inapplicable connection
>> * [RIVER-255 <https://issues.apache.org/jira/browse/RIVER-255>] -
>> Outrigger DestroyThread does not catch exceptions from
>> exporter.unexport
>> * [RIVER-284 <https://issues.apache.org/jira/browse/RIVER-284>] -
>> [PATCH] fix bad ParticipantHandle.compareTo
>> * [RIVER-286 <https://issues.apache.org/jira/browse/RIVER-286>] -
>> [PATCH] iterators on synchronized collections still need
>> synchronization
>> * [RIVER-289 <https://issues.apache.org/jira/browse/RIVER-289>] -
>> Fix for RIVER-247 introduced wrong license headers and references
>> * [RIVER-298 <https://issues.apache.org/jira/browse/RIVER-298>] - No
>> JavaDocs generated for package "com.sun.jini.reliableLog"
>> * [RIVER-302 <https://issues.apache.org/jira/browse/RIVER-302>] -
>> ClassDep -newdirbehaviour option does not work
>> * [RIVER-305 <https://issues.apache.org/jira/browse/RIVER-305>] -
>> qa/GetPermissions test still uses "enum" keyword
>> * [RIVER-320 <https://issues.apache.org/jira/browse/RIVER-320>] -
>> Prebuilt hello example certificates have expired - need to provide
>> new ones
>> * [RIVER-324 <https://issues.apache.org/jira/browse/RIVER-324>] -
>> Under certain circumstances, the ServiceDiscoveryManager internal
>> LookupCache implementation can incorrectly process attribute
>> change events before the lookup snapshot is processed.
>>
>>
>> Improvement
>>
>> * [RIVER-7 <https://issues.apache.org/jira/browse/RIVER-7>] -
>> com.sun.jini.tool.ClassDep should be smarter with outer classes
>> * [RIVER-9 <https://issues.apache.org/jira/browse/RIVER-9>] -
>> PreferredClassLoader should try to avoid making a direct check
>> against the first URL
>> * [RIVER-25 <https://issues.apache.org/jira/browse/RIVER-25>] -
>> Improve logging for JoinManager at INFO and WARNING level
>> * [RIVER-115 <https://issues.apache.org/jira/browse/RIVER-115>] -
>> Multiple jar files with conflicting lists need facilities to map
>> the chosen preferred value
>> * [RIVER-116 <https://issues.apache.org/jira/browse/RIVER-116>] -
>> Multiple jar files with conflicting lists need facilities to map
>> the chosen preferred value
>> * [RIVER-160 <https://issues.apache.org/jira/browse/RIVER-160>] -
>> add TrustEquivalence to browser's list of uninterestingInterfaces
>> * [RIVER-201 <https://issues.apache.org/jira/browse/RIVER-201>] -
>> Show interfaces rather than classes in browser's Matching Services
>> pane.
>> * [RIVER-206 <https://issues.apache.org/jira/browse/RIVER-206>] -
>> Change default load factors from 3 to 1
>> * [RIVER-210 <https://issues.apache.org/jira/browse/RIVER-210>] -
>> Browser should cancel event lease on exit
>> * [RIVER-220 <https://issues.apache.org/jira/browse/RIVER-220>] -
>> LookupLocatorDiscovery catch Throwable blocks should also catch
>> Throwable
>> * [RIVER-226 <https://issues.apache.org/jira/browse/RIVER-226>] -
>> LLD: consider delaying the queuing of a discovery request
>> immediately after a discard
>> * [RIVER-229 <https://issues.apache.org/jira/browse/RIVER-229>] -
>> reduce number of Reaper threads created by ConnectionManager
>> * [RIVER-231 <https://issues.apache.org/jira/browse/RIVER-231>] -
>> ComputeHttpmdCodebase man page could be clarified with respect to
>> algorithm used
>> * [RIVER-233 <https://issues.apache.org/jira/browse/RIVER-233>] -
>> ComputeDigest instructions reference sha and sha1
>> * [RIVER-243 <https://issues.apache.org/jira/browse/RIVER-243>] -
>> JarWrapper javadoc could be clearer wrt to classpath manifests
>> * [RIVER-244 <https://issues.apache.org/jira/browse/RIVER-244>] -
>> Text area below menu bar in ServiceBrowser should not be editable
>> * [RIVER-246 <https://issues.apache.org/jira/browse/RIVER-246>] -
>> Consider adding shutdown hook so Reggie sends final multicast
>> packet if its VM is terminated
>> * [RIVER-247 <https://issues.apache.org/jira/browse/RIVER-247>] -
>> Destroy processing should use configurable duration and interval
>> for unexporting
>> * [RIVER-256 <https://issues.apache.org/jira/browse/RIVER-256>] -
>> Outrigger catch Throwable blocks should also catch Throwable
>> * [RIVER-262 <https://issues.apache.org/jira/browse/RIVER-262>] -
>> ServiceUI Specification
>> * [RIVER-270 <https://issues.apache.org/jira/browse/RIVER-270>] -
>> tar tasks in release* ant targets fail due to 100-char limitation
>> and are disabled
>> * [RIVER-285 <https://issues.apache.org/jira/browse/RIVER-285>] -
>> LookupDiscoveryManager has unused variable declarations
>>
>>
>> New Feature
>>
>> * [RIVER-151 <https://issues.apache.org/jira/browse/RIVER-151>] -
>> ClassDep should have a method to determine if problems occurred
>> * [RIVER-161 <https://issues.apache.org/jira/browse/RIVER-161>] -
>> Coalesce jars from multiple source dirs while retain current
>> Manifest Classpath semantics
>> * [RIVER-163 <https://issues.apache.org/jira/browse/RIVER-163>] -
>> ClassDep doesn't pick up annotation or type parameter dependencies
>> * [RIVER-292 <https://issues.apache.org/jira/browse/RIVER-292>] -
>> The service browser should provide support for the ServiceUI support
>> * [RIVER-295 <https://issues.apache.org/jira/browse/RIVER-295>] -
>> Support configurable option to prevent from popup windows that
>> require a confirmation by the user
>>
>>
>> Task
>>
>> * [RIVER-294 <https://issues.apache.org/jira/browse/RIVER-294>] -
>> Remove http://svn.apache.org/repos/asf/incubator/river/trunk/ from
>> the SVN repository
>>
>>
>> Test
>>
>> * [RIVER-291 <https://issues.apache.org/jira/browse/RIVER-291>] -
>> Cannot build QA tests using the supplied make files
>>
>> See the Release Artifacts for remaining release notes.
>>
>>
>>
>>
>>
>
[RESULT] Re: [VOTE] Release Apache River 2.1.2
Posted by Peter Firmstone <ji...@zeus.net.au>.
Those voting in favour of Apache River Incubator Release 2.1.2 are (in
chronological order):
Sim IJskes
Jim Waldo
Jim Hurley
Tom Hobbs
Brian Murphy
David C Nelson
Gert Vanthienen
Jukka Zitting
Niclas Hedhman
Zsolt Kúti
Dan Rollo
Ant Elder
Jonathan Costers
No votes against.
On this occassion, we have received the minimum three Incubator PMC
votes, the vote has passed.
No, it's no April fools joke, it's time to sit back, relax and have a
quiet celebratory drink, to Apache River.
Thank you; to all our new contributors, committers, leaders and longtime
stewards (you know who you are), whose efforts have made this latest
release possible.
Cheers,
Peter Firmstone.
Peter Firmstone wrote:
> Please vote on releasing Apache River 2.1.2
>
> The voting period is open, due to the size of the River release, it
> will remain open until it passes with a majority of at least three +1
> River Incubator PMC votes or until a valid objection causes its
> rejection.
>
> All are encouraged to show their support by validating and casting a
> vote for this release, please ensure you reply to both lists, so those
> on general can see your interest in and support for our project:
>
> general@incubator.apache.org
> river-dev@incubator.apache.org
>
> A candidate for the Apache River 2.1.2 Release is available at
>
> http://people.apache.org/~peter_firmstone/
>
> The release candidate sources are zip / tar.gz archives of the sources
> in:
>
> http://svn.apache.org/repos/asf/incubator/river/jtsk/trunk/
>
> The source release artifact SHA1 checksums are:
>
> apache-river-2.1.2-incubating-src.tar.gz:
> 6B18 E089 C22C 9790 B0A4 89CC A410 2250 7A0A 4890
> apache-river-2.1.2-incubating-src.zip:
> 28F8 ABB3 0BDF 149F 6FA0 8D8B C982 47A6 19EF AE43
>
> The binary release artifact SHA1 checksums:
>
> apache-river-2.1.2-incubating-bin.tar.gz:
> 3813 613B 4432 B5A9 E6F3 EFCA D649 D55A C73A 1BA8
> apache-river-2.1.2-incubating-bin.zip:
> F692 BCDC A050 9BCF 3ADD A5E4 C500 4263 0FAE 6BEE
>
>
> Apache River
> v2.1.2 Release Notes
>
> ------------------------------------------------------------------------
> Apache River is an effort undergoing incubation at The Apache Software
> Foundation (ASF), sponsored by the Apache Incubator. Incubation is
> required of all newly accepted projects until a further review indicates
> that the infrastructure, communications, and decision making process
> have stabilized in a manner consistent with other successful ASF
> projects. While incubation status is not necessarily a reflection of the
> completeness or stability of the code, it does indicate that the project
> has yet to be fully endorsed by the ASF.
>
> Apache River is aimed at the development and advancement of the River
> technology core infrastructure. River technology is a service oriented
> architecture that defines a programming model which both exploits and
> extends Java technology to enable the construction of secure,
> distributed systems which are adaptive to change.
>
> ------------------------------------------------------------------------
>
>
> Notes of Interest for this Release
>
> This second release from the Apache River project is based on the
> contributions of Sun's Jini Technology Starter Kit (Starter Kit) v2.1
> and Service UI from Artima. The release focuses on merging the two
> contributions together, structuring separate src and bin releases, and
> amending the source and documentation naming/versioning/etc to the
> Apache River project.
>
> Some points of note:
>
> * NOTICE file and source license headers updated
> * Source and documentation updated for release name ("Apache River
> release") and version ("v2.1.2")
> * Graphical installer (which was a 3rd party application in the
> Starter Kit) is no longer available
> * The combined source and binary release in the Starter Kit has been
> separated into two releases: src and bin
> * The "logstore" implementation of com.sun.jini.outrigger.Store has
> been removed
>
> The persistent version of Outrigger relies on a pluggable
> persistence layer, |com.sun.jini.outrigger.Store|. Previous
> releases of the Starter Kit included two implementations of the
> Store interface, /logstore/ and /snaplogstore/. This release
> removes logstore.
>
> Logstore has been around in various forms since the 1.0 version of
> Outrigger. Snapstore was introduced in v2.1 of the Starter Kit.
>
> The v2.0.n releases of the Starter Kit used logstore as the
> default Store implementation, this release has no default Store.
> In order to switch an existing set of configuration files,
> security policy files, etc., from using logstore to snaplogstore,
> you will need to change the |com.sun.jini.outrigger.store|
> configuration entry (or add a store configuration entry if you
> don't already have one) to yield a
> |com.sun.jini.outrigger.snaplogstore.LogStore| object. You will
> also need to ensure that |outrigger-snaplogstore.jar| has been
> granted sufficient permissions (see Outrigger's package
> documentation for a sample security policy file.).
>
> Note that depending on the nature of your application snaplogstore
> can have a significantly different performance profile than
> logstore.
>
> The storage formats used by snaplogstore and logstore are mutually
> incompatible.
>
> ------------------------------------------------------------------------
>
>
> Submitting Issues
>
> If you would like to submit a bug against the Apache River release,
> please use the River JIRA <http://issues.apache.org/jira/browse/RIVER>.
> To discuss problems, questions, or suggestions on the release, please
> subscribe to the |river-dev| list from the project Mailing Lists
> <http://incubator.apache.org/river/mailing.html> page.
>
> ------------------------------------------------------------------------
>
>
> Upcoming Changes planned for the next version of Apache River
>
> # All packages ouside of the net.jini namespace will be renamed to
> org.apache.river.
> # Support for Java 5 language features
> # Support for Modular Frameworks conforming to the OSGi r4.2 core
> Specification
> ------------------------------------------------------------------------
>
>
> Changes made since Apache River v2.1.1
>
>
> Bug
>
> * [RIVER-5 <https://issues.apache.org/jira/browse/RIVER-5>] -
> HTTMPMD URLs can be considered equal while they are not
> * [RIVER-8 <https://issues.apache.org/jira/browse/RIVER-8>] -
> com.sun.jini.tool.ClassDep empty inside collection doesn't work
> * [RIVER-17 <https://issues.apache.org/jira/browse/RIVER-17>] -
> Misleading logging message when discovery constraint checking is
> delayed
> * [RIVER-18 <https://issues.apache.org/jira/browse/RIVER-18>] -
> Order of discovery providers not maintained
> * [RIVER-22 <https://issues.apache.org/jira/browse/RIVER-22>] - NPE
> in
> net.jini.jeri.tcp.TcpEndpoint$ConnectionImpl.checkConnectPermission
> * [RIVER-24 <https://issues.apache.org/jira/browse/RIVER-24>] -
> PreferredListGen can create illegal PREFERRED.LIST
> * [RIVER-78 <https://issues.apache.org/jira/browse/RIVER-78>] -
> ClassDep generates duplicate output lines
> * [RIVER-82 <https://issues.apache.org/jira/browse/RIVER-82>] -
> ClassDep generates duplicate output lines
> * [RIVER-91 <https://issues.apache.org/jira/browse/RIVER-91>] -
> Uninstaller does not remove all items
> * [RIVER-205 <https://issues.apache.org/jira/browse/RIVER-205>] -
> LookupDiscovery can give untrusted code access to privileged threads
> * [RIVER-209 <https://issues.apache.org/jira/browse/RIVER-209>] -
> NullPointerException in SslConnection.checkConnectPermission()
> * [RIVER-212 <https://issues.apache.org/jira/browse/RIVER-212>] -
> use of "enum" as a variable name
> * [RIVER-213 <https://issues.apache.org/jira/browse/RIVER-213>] -
> (DOC) - JoinManger has typo in javadoc (missing </code>
> termination tag)
> * [RIVER-215 <https://issues.apache.org/jira/browse/RIVER-215>] -
> LookupDiscovery throws NullPointerException on terminate
> * [RIVER-216 <https://issues.apache.org/jira/browse/RIVER-216>] -
> ConfigurationFile should throw ExceptionInInitializerError if
> unable to read prohibited methods
> * [RIVER-217 <https://issues.apache.org/jira/browse/RIVER-217>] -
> Browser incorrectly assumes event source is ServiceRegistrar proxy
> * [RIVER-223 <https://issues.apache.org/jira/browse/RIVER-223>] -
> test: jtreg/net/jini/jeri/tcp/connectTimeout/TestConnectTimeout
> fails on Linux
> * [RIVER-224 <https://issues.apache.org/jira/browse/RIVER-224>] -
> Problem using browser to destroy service that supports
> DestroyAdmin but not JoinAdmin
> * [RIVER-225 <https://issues.apache.org/jira/browse/RIVER-225>] -
> NullPointerException in Reggie during destroy
> * [RIVER-227 <https://issues.apache.org/jira/browse/RIVER-227>] -
> tools manpages command lines do not include line continuation
> characters
> * [RIVER-230 <https://issues.apache.org/jira/browse/RIVER-230>] -
> (mux) SelectionManager catch Error block assumes getMessage()
> returns non-null
> * [RIVER-232 <https://issues.apache.org/jira/browse/RIVER-232>] -
> JarWrapper and PreferredListGen uses jsk_install_dir and install_dir
> * [RIVER-234 <https://issues.apache.org/jira/browse/RIVER-234>] -
> (DOC) Fiddler manpage directions for HTTP server should reference
> classserver.jar, not tools.jar
> * [RIVER-240 <https://issues.apache.org/jira/browse/RIVER-240>] -
> BasicInvocationDispatcher.dispatch could log more info for some
> exceptions
> * [RIVER-241 <https://issues.apache.org/jira/browse/RIVER-241>] -
> Mercury spelling errore
> * [RIVER-242 <https://issues.apache.org/jira/browse/RIVER-242>] - if
> a given ConnectionManager instance cannot create a reaper thread
> once, it never will again
> * [RIVER-245 <https://issues.apache.org/jira/browse/RIVER-245>] -
> Unicast discovery should close socket in case of connection
> exception.
> * [RIVER-252 <https://issues.apache.org/jira/browse/RIVER-252>] -
> ComputeHttpmdCodebase NPE if resource bundle not found
> * [RIVER-253 <https://issues.apache.org/jira/browse/RIVER-253>] -
> ComputeDigest NPE if resource bundle not found
> * [RIVER-254 <https://issues.apache.org/jira/browse/RIVER-254>] -
> request initiation can block on I/O for inapplicable connection
> * [RIVER-255 <https://issues.apache.org/jira/browse/RIVER-255>] -
> Outrigger DestroyThread does not catch exceptions from
> exporter.unexport
> * [RIVER-284 <https://issues.apache.org/jira/browse/RIVER-284>] -
> [PATCH] fix bad ParticipantHandle.compareTo
> * [RIVER-286 <https://issues.apache.org/jira/browse/RIVER-286>] -
> [PATCH] iterators on synchronized collections still need
> synchronization
> * [RIVER-289 <https://issues.apache.org/jira/browse/RIVER-289>] -
> Fix for RIVER-247 introduced wrong license headers and references
> * [RIVER-298 <https://issues.apache.org/jira/browse/RIVER-298>] - No
> JavaDocs generated for package "com.sun.jini.reliableLog"
> * [RIVER-302 <https://issues.apache.org/jira/browse/RIVER-302>] -
> ClassDep -newdirbehaviour option does not work
> * [RIVER-305 <https://issues.apache.org/jira/browse/RIVER-305>] -
> qa/GetPermissions test still uses "enum" keyword
> * [RIVER-320 <https://issues.apache.org/jira/browse/RIVER-320>] -
> Prebuilt hello example certificates have expired - need to provide
> new ones
> * [RIVER-324 <https://issues.apache.org/jira/browse/RIVER-324>] -
> Under certain circumstances, the ServiceDiscoveryManager internal
> LookupCache implementation can incorrectly process attribute
> change events before the lookup snapshot is processed.
>
>
> Improvement
>
> * [RIVER-7 <https://issues.apache.org/jira/browse/RIVER-7>] -
> com.sun.jini.tool.ClassDep should be smarter with outer classes
> * [RIVER-9 <https://issues.apache.org/jira/browse/RIVER-9>] -
> PreferredClassLoader should try to avoid making a direct check
> against the first URL
> * [RIVER-25 <https://issues.apache.org/jira/browse/RIVER-25>] -
> Improve logging for JoinManager at INFO and WARNING level
> * [RIVER-115 <https://issues.apache.org/jira/browse/RIVER-115>] -
> Multiple jar files with conflicting lists need facilities to map
> the chosen preferred value
> * [RIVER-116 <https://issues.apache.org/jira/browse/RIVER-116>] -
> Multiple jar files with conflicting lists need facilities to map
> the chosen preferred value
> * [RIVER-160 <https://issues.apache.org/jira/browse/RIVER-160>] -
> add TrustEquivalence to browser's list of uninterestingInterfaces
> * [RIVER-201 <https://issues.apache.org/jira/browse/RIVER-201>] -
> Show interfaces rather than classes in browser's Matching Services
> pane.
> * [RIVER-206 <https://issues.apache.org/jira/browse/RIVER-206>] -
> Change default load factors from 3 to 1
> * [RIVER-210 <https://issues.apache.org/jira/browse/RIVER-210>] -
> Browser should cancel event lease on exit
> * [RIVER-220 <https://issues.apache.org/jira/browse/RIVER-220>] -
> LookupLocatorDiscovery catch Throwable blocks should also catch
> Throwable
> * [RIVER-226 <https://issues.apache.org/jira/browse/RIVER-226>] -
> LLD: consider delaying the queuing of a discovery request
> immediately after a discard
> * [RIVER-229 <https://issues.apache.org/jira/browse/RIVER-229>] -
> reduce number of Reaper threads created by ConnectionManager
> * [RIVER-231 <https://issues.apache.org/jira/browse/RIVER-231>] -
> ComputeHttpmdCodebase man page could be clarified with respect to
> algorithm used
> * [RIVER-233 <https://issues.apache.org/jira/browse/RIVER-233>] -
> ComputeDigest instructions reference sha and sha1
> * [RIVER-243 <https://issues.apache.org/jira/browse/RIVER-243>] -
> JarWrapper javadoc could be clearer wrt to classpath manifests
> * [RIVER-244 <https://issues.apache.org/jira/browse/RIVER-244>] -
> Text area below menu bar in ServiceBrowser should not be editable
> * [RIVER-246 <https://issues.apache.org/jira/browse/RIVER-246>] -
> Consider adding shutdown hook so Reggie sends final multicast
> packet if its VM is terminated
> * [RIVER-247 <https://issues.apache.org/jira/browse/RIVER-247>] -
> Destroy processing should use configurable duration and interval
> for unexporting
> * [RIVER-256 <https://issues.apache.org/jira/browse/RIVER-256>] -
> Outrigger catch Throwable blocks should also catch Throwable
> * [RIVER-262 <https://issues.apache.org/jira/browse/RIVER-262>] -
> ServiceUI Specification
> * [RIVER-270 <https://issues.apache.org/jira/browse/RIVER-270>] -
> tar tasks in release* ant targets fail due to 100-char limitation
> and are disabled
> * [RIVER-285 <https://issues.apache.org/jira/browse/RIVER-285>] -
> LookupDiscoveryManager has unused variable declarations
>
>
> New Feature
>
> * [RIVER-151 <https://issues.apache.org/jira/browse/RIVER-151>] -
> ClassDep should have a method to determine if problems occurred
> * [RIVER-161 <https://issues.apache.org/jira/browse/RIVER-161>] -
> Coalesce jars from multiple source dirs while retain current
> Manifest Classpath semantics
> * [RIVER-163 <https://issues.apache.org/jira/browse/RIVER-163>] -
> ClassDep doesn't pick up annotation or type parameter dependencies
> * [RIVER-292 <https://issues.apache.org/jira/browse/RIVER-292>] -
> The service browser should provide support for the ServiceUI support
> * [RIVER-295 <https://issues.apache.org/jira/browse/RIVER-295>] -
> Support configurable option to prevent from popup windows that
> require a confirmation by the user
>
>
> Task
>
> * [RIVER-294 <https://issues.apache.org/jira/browse/RIVER-294>] -
> Remove http://svn.apache.org/repos/asf/incubator/river/trunk/ from
> the SVN repository
>
>
> Test
>
> * [RIVER-291 <https://issues.apache.org/jira/browse/RIVER-291>] -
> Cannot build QA tests using the supplied make files
>
> See the Release Artifacts for remaining release notes.
>
>
>
>
>
Re: [VOTE] Release Apache River 2.1.2
Posted by Sim IJskes - QCG <si...@qcg.nl>.
vote +1 (non-binding)
[based on: code works in production environment]
--
QCG, Software voor het MKB, 071-5890970, http://www.qcg.nl
Quality Consultancy Group b.v., Leiderdorp, Kvk Leiden: 28088397
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [VOTE] Release Apache River 2.1.2
Posted by Jonathan Costers <jo...@googlemail.com>.
+1 !!
Great job Peter
Thanks
Jonathan
Re: [VOTE] Release Apache River 2.1.2
Posted by Peter Firmstone <ji...@zeus.net.au>.
ant elder wrote:
> Looks ok to me, +1.
>
> As an aside there are still Java package names that are using com.sun
> instead of org.apache, are they going to be changed before graduation
> (I forget what the feeling is about this these days in the Incubator
> PMC)?
>
Thanks Ant, yes, that's planned next release.
Cheers,
Peter.
> ...ant
>
> On Sat, Mar 20, 2010 at 9:37 AM, Jukka Zitting <ju...@gmail.com> wrote:
>
>> Hi,
>>
>> On Thu, Mar 18, 2010 at 4:54 PM, Jukka Zitting <ju...@gmail.com> wrote:
>>
>>> On Wed, Mar 10, 2010 at 10:39 AM, Peter Firmstone <ji...@zeus.net.au> wrote:
>>>
>>>> Please vote on releasing Apache River 2.1.2
>>>>
>>> +1 (sorry for the delay)
>>>
>>> PS. IPMC members; we still need two more IPMC votes to make this
>>> release official.
>>>
>> Hmm, looks like I forgot to cc general@ on this.
>>
>> We're still lacking one IPMC vote to make this release official.
>> Getting this release prepared was a huge effort and IMHO the biggest
>> positive sign of community activity in River since the podling was
>> started. Let's not stall the release for a missing IPMC vote!
>>
>> BR,
>>
>> Jukka Zitting
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> For additional commands, e-mail: general-help@incubator.apache.org
>>
>>
>>
>
>
Re: [VOTE] Release Apache River 2.1.2
Posted by ant elder <an...@gmail.com>.
Looks ok to me, +1.
As an aside there are still Java package names that are using com.sun
instead of org.apache, are they going to be changed before graduation
(I forget what the feeling is about this these days in the Incubator
PMC)?
...ant
On Sat, Mar 20, 2010 at 9:37 AM, Jukka Zitting <ju...@gmail.com> wrote:
> Hi,
>
> On Thu, Mar 18, 2010 at 4:54 PM, Jukka Zitting <ju...@gmail.com> wrote:
>> On Wed, Mar 10, 2010 at 10:39 AM, Peter Firmstone <ji...@zeus.net.au> wrote:
>>> Please vote on releasing Apache River 2.1.2
>>
>> +1 (sorry for the delay)
>>
>> PS. IPMC members; we still need two more IPMC votes to make this
>> release official.
>
> Hmm, looks like I forgot to cc general@ on this.
>
> We're still lacking one IPMC vote to make this release official.
> Getting this release prepared was a huge effort and IMHO the biggest
> positive sign of community activity in River since the podling was
> started. Let's not stall the release for a missing IPMC vote!
>
> BR,
>
> Jukka Zitting
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [VOTE] Release Apache River 2.1.2
Posted by ant elder <an...@gmail.com>.
Looks ok to me, +1.
As an aside there are still Java package names that are using com.sun
instead of org.apache, are they going to be changed before graduation
(I forget what the feeling is about this these days in the Incubator
PMC)?
...ant
On Sat, Mar 20, 2010 at 9:37 AM, Jukka Zitting <ju...@gmail.com> wrote:
> Hi,
>
> On Thu, Mar 18, 2010 at 4:54 PM, Jukka Zitting <ju...@gmail.com> wrote:
>> On Wed, Mar 10, 2010 at 10:39 AM, Peter Firmstone <ji...@zeus.net.au> wrote:
>>> Please vote on releasing Apache River 2.1.2
>>
>> +1 (sorry for the delay)
>>
>> PS. IPMC members; we still need two more IPMC votes to make this
>> release official.
>
> Hmm, looks like I forgot to cc general@ on this.
>
> We're still lacking one IPMC vote to make this release official.
> Getting this release prepared was a huge effort and IMHO the biggest
> positive sign of community activity in River since the podling was
> started. Let's not stall the release for a missing IPMC vote!
>
> BR,
>
> Jukka Zitting
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>
Re: [VOTE] Release Apache River 2.1.2
Posted by Jukka Zitting <ju...@gmail.com>.
Hi,
On Thu, Mar 18, 2010 at 4:54 PM, Jukka Zitting <ju...@gmail.com> wrote:
> On Wed, Mar 10, 2010 at 10:39 AM, Peter Firmstone <ji...@zeus.net.au> wrote:
>> Please vote on releasing Apache River 2.1.2
>
> +1 (sorry for the delay)
>
> PS. IPMC members; we still need two more IPMC votes to make this
> release official.
Hmm, looks like I forgot to cc general@ on this.
We're still lacking one IPMC vote to make this release official.
Getting this release prepared was a huge effort and IMHO the biggest
positive sign of community activity in River since the podling was
started. Let's not stall the release for a missing IPMC vote!
BR,
Jukka Zitting
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [VOTE] Release Apache River 2.1.2
Posted by Zsolt Kúti <la...@gmail.com>.
On Sat, 20 Mar 2010 17:05:55 +1000
Peter Firmstone <ji...@zeus.net.au> wrote:
> Thanks Nic,
>
> The following also deserve some thanks for their recent contributions
...
The only little thing I can do to give supportive words and express my
appreciation for all people doing so much for River to remain alive and
improve.
> One more IPMC vote & we have a release! Everyone else keep your
> votes coming, they count too by helping motivate IPMC members and
> other interested parties.
+1 (non-binding)
Zsolt
Re: [VOTE] Release Apache River 2.1.2
Posted by Peter Firmstone <ji...@zeus.net.au>.
Thanks Nic,
The following also deserve some thanks for their recent contributions
(not in any particular order, just my memory stack):
Jonathan Costers - Completing Integration of the qa tests
Tom Hobbs - Getting the qa test integration started.
Tim Blackman - Code contribution and assistance with ClassDep tool
replacement
Peter Jones - For his ongoing invaluable assistance with testing and
debugging the test suite integration.
Dennis Reedy - Contribution of Groovy configuration code (my apologies
for not integrating it yet).
And of course thanks to recent patches from:
Sim IJskes
Brian Murphy
Bob Scheifler
Apologies if I've missed anybody.
Recent interest & discussions have been very positive & I'm hoping that
we'll receive more contributions from those newly joining too.
One more IPMC vote & we have a release! Everyone else keep your votes
coming, they count too by helping motivate IPMC members and other
interested parties.
Cheers,
Peter.
Niclas Hedhman wrote:
> I think Peter is heroic. River must be one of the most complex
> codebases to release around here...
>
>
> +1
>
> On Thu, Mar 18, 2010 at 11:54 PM, Jukka Zitting <ju...@gmail.com> wrote:
>
>> Hi,
>>
>> On Wed, Mar 10, 2010 at 10:39 AM, Peter Firmstone <ji...@zeus.net.au> wrote:
>>
>>> Please vote on releasing Apache River 2.1.2
>>>
>> +1 (sorry for the delay)
>>
>> PS. IPMC members; we still need two more IPMC votes to make this
>> release official.
>>
>> BR,
>>
>> Jukka Zitting
>>
>>
>
>
>
>
Re: [VOTE] Release Apache River 2.1.2
Posted by Dan Rollo <da...@gmail.com>.
Ditto!
(non-binding +1)
Dan
On Mar 19, 2010, at 11:25 PM, Niclas Hedhman <ni...@hedhman.org> wrote:
> I think Peter is heroic. River must be one of the most complex
> codebases to release around here...
>
>
> +1
>
> On Thu, Mar 18, 2010 at 11:54 PM, Jukka Zitting <jukka.zitting@gmail.com
> > wrote:
>> Hi,
>>
>> On Wed, Mar 10, 2010 at 10:39 AM, Peter Firmstone
>> <ji...@zeus.net.au> wrote:
>>> Please vote on releasing Apache River 2.1.2
>>
>> +1 (sorry for the delay)
>>
>> PS. IPMC members; we still need two more IPMC votes to make this
>> release official.
>>
>> BR,
>>
>> Jukka Zitting
>>
>
>
>
> --
> Niclas Hedhman, Software Developer
> http://www.qi4j.org - New Energy for Java
>
> I live here; http://tinyurl.com/2qq9er
> I work here; http://tinyurl.com/2ymelc
> I relax here; http://tinyurl.com/2cgsug
Re: [VOTE] Release Apache River 2.1.2
Posted by Niclas Hedhman <ni...@hedhman.org>.
I think Peter is heroic. River must be one of the most complex
codebases to release around here...
+1
On Thu, Mar 18, 2010 at 11:54 PM, Jukka Zitting <ju...@gmail.com> wrote:
> Hi,
>
> On Wed, Mar 10, 2010 at 10:39 AM, Peter Firmstone <ji...@zeus.net.au> wrote:
>> Please vote on releasing Apache River 2.1.2
>
> +1 (sorry for the delay)
>
> PS. IPMC members; we still need two more IPMC votes to make this
> release official.
>
> BR,
>
> Jukka Zitting
>
--
Niclas Hedhman, Software Developer
http://www.qi4j.org - New Energy for Java
I live here; http://tinyurl.com/2qq9er
I work here; http://tinyurl.com/2ymelc
I relax here; http://tinyurl.com/2cgsug
Re: [VOTE] Release Apache River 2.1.2
Posted by Jukka Zitting <ju...@gmail.com>.
Hi,
On Wed, Mar 10, 2010 at 10:39 AM, Peter Firmstone <ji...@zeus.net.au> wrote:
> Please vote on releasing Apache River 2.1.2
+1 (sorry for the delay)
PS. IPMC members; we still need two more IPMC votes to make this
release official.
BR,
Jukka Zitting
Re: [VOTE] Release Apache River 2.1.2
Posted by Peter Firmstone <ji...@zeus.net.au>.
Wish Granted (pun intended):
https://svn.apache.org/repos/asf/incubator/river/jtsk/branches/2.1.2
Cheers,
Peter.
Gert Vanthienen wrote:
> L.S.,
>
> +1 (non-binding)
>
> I think it would be good if you could create a tag in the svn
> repository for this release, so we could actually go and check out the
> sources for this release directly from svn as well.
>
> Regards,
>
> Gert Vanthienen
> ------------------------
> Open Source SOA: http://fusesource.com
> Blog: http://gertvanthienen.blogspot.com/
>
>
>
> On 11 March 2010 14:11, Brian Murphy <bt...@gmail.com> wrote:
>
>> On Wed, Mar 10, 2010 at 4:39 AM, Peter Firmstone <ji...@zeus.net.au> wrote:
>>
>> Please vote on releasing Apache River 2.1.2
>>
>>> please ensure you reply to both lists,
>>>
>>> general@incubator.apache.org
>>> river-dev@incubator.apache.org
>>>
>> +1
>>
>>
>
>
Re: [VOTE] Release Apache River 2.1.2
Posted by Gert Vanthienen <ge...@gmail.com>.
L.S.,
+1 (non-binding)
I think it would be good if you could create a tag in the svn
repository for this release, so we could actually go and check out the
sources for this release directly from svn as well.
Regards,
Gert Vanthienen
------------------------
Open Source SOA: http://fusesource.com
Blog: http://gertvanthienen.blogspot.com/
On 11 March 2010 14:11, Brian Murphy <bt...@gmail.com> wrote:
> On Wed, Mar 10, 2010 at 4:39 AM, Peter Firmstone <ji...@zeus.net.au> wrote:
>
> Please vote on releasing Apache River 2.1.2
>>
>> please ensure you reply to both lists,
>>
>> general@incubator.apache.org
>> river-dev@incubator.apache.org
>
>
> +1
>
Re: [VOTE] Release Apache River 2.1.2
Posted by Gert Vanthienen <ge...@gmail.com>.
L.S.,
+1 (non-binding)
I think it would be good if you could create a tag in the svn
repository for this release, so we could actually go and check out the
sources for this release directly from svn as well.
Regards,
Gert Vanthienen
------------------------
Open Source SOA: http://fusesource.com
Blog: http://gertvanthienen.blogspot.com/
On 11 March 2010 14:11, Brian Murphy <bt...@gmail.com> wrote:
> On Wed, Mar 10, 2010 at 4:39 AM, Peter Firmstone <ji...@zeus.net.au> wrote:
>
> Please vote on releasing Apache River 2.1.2
>>
>> please ensure you reply to both lists,
>>
>> general@incubator.apache.org
>> river-dev@incubator.apache.org
>
>
> +1
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [VOTE] Release Apache River 2.1.2
Posted by Brian Murphy <bt...@gmail.com>.
On Wed, Mar 10, 2010 at 4:39 AM, Peter Firmstone <ji...@zeus.net.au> wrote:
Please vote on releasing Apache River 2.1.2
>
> please ensure you reply to both lists,
>
> general@incubator.apache.org
> river-dev@incubator.apache.org
+1
RE: [VOTE] Release Apache River 2.1.2 (UNCLASSIFIED)
Posted by "Nelson, David C CTR US USA AMC" <da...@us.army.mil>.
Classification: UNCLASSIFIED
Caveats: FOUO
vote +1 (non-binding)
Quite excited with the direction this project is going! Great effort!
...
Please vote on releasing Apache River 2.1.2
...
Classification: UNCLASSIFIED
Caveats: FOUO
Re: [VOTE] Release Apache River 2.1.2
Posted by Brian Murphy <bt...@gmail.com>.
On Wed, Mar 10, 2010 at 4:39 AM, Peter Firmstone <ji...@zeus.net.au> wrote:
Please vote on releasing Apache River 2.1.2
>
> please ensure you reply to both lists,
>
> general@incubator.apache.org
> river-dev@incubator.apache.org
+1
Re: [VOTE] Release Apache River 2.1.2
Posted by Jim Hurley <ji...@mac.com>.
+1
(Thanks for driving this, Peter.)
-Jim
On Mar 10, 2010, at 4:39 AM, Peter Firmstone wrote:
> Please vote on releasing Apache River 2.1.2
>
> The voting period is open, due to the size of the River release, it
> will remain open until it passes with a majority of at least three
> +1 River Incubator PMC votes or until a valid objection causes its
> rejection.
>
> All are encouraged to show their support by validating and casting a
> vote for this release, please ensure you reply to both lists, so
> those on general can see your interest in and support for our project:
>
> general@incubator.apache.org
> river-dev@incubator.apache.org
>
> A candidate for the Apache River 2.1.2 Release is available at
>
> http://people.apache.org/~peter_firmstone/
>
> The release candidate sources are zip / tar.gz archives of the
> sources in:
>
> http://svn.apache.org/repos/asf/incubator/river/jtsk/trunk/
>
> The source release artifact SHA1 checksums are:
>
> apache-river-2.1.2-incubating-src.tar.gz:
> 6B18 E089 C22C 9790 B0A4 89CC A410 2250 7A0A 4890
> apache-river-2.1.2-incubating-src.zip:
> 28F8 ABB3 0BDF 149F 6FA0 8D8B C982 47A6 19EF AE43
>
> The binary release artifact SHA1 checksums:
>
> apache-river-2.1.2-incubating-bin.tar.gz:
> 3813 613B 4432 B5A9 E6F3 EFCA D649 D55A C73A 1BA8
> apache-river-2.1.2-incubating-bin.zip:
> F692 BCDC A050 9BCF 3ADD A5E4 C500 4263 0FAE 6BEE
>
>
> Apache River
> v2.1.2 Release Notes
>
> ------------------------------------------------------------------------
> Apache River is an effort undergoing incubation at The Apache Software
> Foundation (ASF), sponsored by the Apache Incubator. Incubation is
> required of all newly accepted projects until a further review
> indicates
> that the infrastructure, communications, and decision making process
> have stabilized in a manner consistent with other successful ASF
> projects. While incubation status is not necessarily a reflection of
> the
> completeness or stability of the code, it does indicate that the
> project
> has yet to be fully endorsed by the ASF.
>
> Apache River is aimed at the development and advancement of the River
> technology core infrastructure. River technology is a service oriented
> architecture that defines a programming model which both exploits and
> extends Java technology to enable the construction of secure,
> distributed systems which are adaptive to change.
>
> ------------------------------------------------------------------------
>
>
> Notes of Interest for this Release
>
> This second release from the Apache River project is based on the
> contributions of Sun's Jini Technology Starter Kit (Starter Kit) v2.1
> and Service UI from Artima. The release focuses on merging the two
> contributions together, structuring separate src and bin releases, and
> amending the source and documentation naming/versioning/etc to the
> Apache River project.
>
> Some points of note:
>
> * NOTICE file and source license headers updated
> * Source and documentation updated for release name ("Apache River
> release") and version ("v2.1.2")
> * Graphical installer (which was a 3rd party application in the
> Starter Kit) is no longer available
> * The combined source and binary release in the Starter Kit has been
> separated into two releases: src and bin
> * The "logstore" implementation of com.sun.jini.outrigger.Store has
> been removed
>
> The persistent version of Outrigger relies on a pluggable
> persistence layer, |com.sun.jini.outrigger.Store|. Previous
> releases of the Starter Kit included two implementations of the
> Store interface, /logstore/ and /snaplogstore/. This release
> removes logstore.
>
> Logstore has been around in various forms since the 1.0 version of
> Outrigger. Snapstore was introduced in v2.1 of the Starter Kit.
>
> The v2.0.n releases of the Starter Kit used logstore as the
> default Store implementation, this release has no default Store.
> In order to switch an existing set of configuration files,
> security policy files, etc., from using logstore to snaplogstore,
> you will need to change the |com.sun.jini.outrigger.store|
> configuration entry (or add a store configuration entry if you
> don't already have one) to yield a
> |com.sun.jini.outrigger.snaplogstore.LogStore| object. You will
> also need to ensure that |outrigger-snaplogstore.jar| has been
> granted sufficient permissions (see Outrigger's package
> documentation for a sample security policy file.).
>
> Note that depending on the nature of your application snaplogstore
> can have a significantly different performance profile than
> logstore.
>
> The storage formats used by snaplogstore and logstore are mutually
> incompatible.
>
> ------------------------------------------------------------------------
>
>
> Submitting Issues
>
> If you would like to submit a bug against the Apache River release,
> please use the River JIRA <http://issues.apache.org/jira/browse/
> RIVER>.
> To discuss problems, questions, or suggestions on the release, please
> subscribe to the |river-dev| list from the project Mailing Lists
> <http://incubator.apache.org/river/mailing.html> page.
>
> ------------------------------------------------------------------------
>
>
> Upcoming Changes planned for the next version of Apache River
>
> # All packages ouside of the net.jini namespace will be renamed to
> org.apache.river.
> # Support for Java 5 language features
> # Support for Modular Frameworks conforming to the OSGi r4.2 core
> Specification
> ------------------------------------------------------------------------
>
>
> Changes made since Apache River v2.1.1
>
>
> Bug
>
> * [RIVER-5 <https://issues.apache.org/jira/browse/RIVER-5>] -
> HTTMPMD URLs can be considered equal while they are not
> * [RIVER-8 <https://issues.apache.org/jira/browse/RIVER-8>] -
> com.sun.jini.tool.ClassDep empty inside collection doesn't work
> * [RIVER-17 <https://issues.apache.org/jira/browse/RIVER-17>] -
> Misleading logging message when discovery constraint checking is
> delayed
> * [RIVER-18 <https://issues.apache.org/jira/browse/RIVER-18>] -
> Order of discovery providers not maintained
> * [RIVER-22 <https://issues.apache.org/jira/browse/RIVER-22>] - NPE
> in
> net.jini.jeri.tcp.TcpEndpoint
> $ConnectionImpl.checkConnectPermission
> * [RIVER-24 <https://issues.apache.org/jira/browse/RIVER-24>] -
> PreferredListGen can create illegal PREFERRED.LIST
> * [RIVER-78 <https://issues.apache.org/jira/browse/RIVER-78>] -
> ClassDep generates duplicate output lines
> * [RIVER-82 <https://issues.apache.org/jira/browse/RIVER-82>] -
> ClassDep generates duplicate output lines
> * [RIVER-91 <https://issues.apache.org/jira/browse/RIVER-91>] -
> Uninstaller does not remove all items
> * [RIVER-205 <https://issues.apache.org/jira/browse/RIVER-205>] -
> LookupDiscovery can give untrusted code access to privileged
> threads
> * [RIVER-209 <https://issues.apache.org/jira/browse/RIVER-209>] -
> NullPointerException in SslConnection.checkConnectPermission()
> * [RIVER-212 <https://issues.apache.org/jira/browse/RIVER-212>] -
> use of "enum" as a variable name
> * [RIVER-213 <https://issues.apache.org/jira/browse/RIVER-213>] -
> (DOC) - JoinManger has typo in javadoc (missing </code>
> termination tag)
> * [RIVER-215 <https://issues.apache.org/jira/browse/RIVER-215>] -
> LookupDiscovery throws NullPointerException on terminate
> * [RIVER-216 <https://issues.apache.org/jira/browse/RIVER-216>] -
> ConfigurationFile should throw ExceptionInInitializerError if
> unable to read prohibited methods
> * [RIVER-217 <https://issues.apache.org/jira/browse/RIVER-217>] -
> Browser incorrectly assumes event source is ServiceRegistrar proxy
> * [RIVER-223 <https://issues.apache.org/jira/browse/RIVER-223>] -
> test: jtreg/net/jini/jeri/tcp/connectTimeout/TestConnectTimeout
> fails on Linux
> * [RIVER-224 <https://issues.apache.org/jira/browse/RIVER-224>] -
> Problem using browser to destroy service that supports
> DestroyAdmin but not JoinAdmin
> * [RIVER-225 <https://issues.apache.org/jira/browse/RIVER-225>] -
> NullPointerException in Reggie during destroy
> * [RIVER-227 <https://issues.apache.org/jira/browse/RIVER-227>] -
> tools manpages command lines do not include line continuation
> characters
> * [RIVER-230 <https://issues.apache.org/jira/browse/RIVER-230>] -
> (mux) SelectionManager catch Error block assumes getMessage()
> returns non-null
> * [RIVER-232 <https://issues.apache.org/jira/browse/RIVER-232>] -
> JarWrapper and PreferredListGen uses jsk_install_dir and
> install_dir
> * [RIVER-234 <https://issues.apache.org/jira/browse/RIVER-234>] -
> (DOC) Fiddler manpage directions for HTTP server should reference
> classserver.jar, not tools.jar
> * [RIVER-240 <https://issues.apache.org/jira/browse/RIVER-240>] -
> BasicInvocationDispatcher.dispatch could log more info for some
> exceptions
> * [RIVER-241 <https://issues.apache.org/jira/browse/RIVER-241>] -
> Mercury spelling errore
> * [RIVER-242 <https://issues.apache.org/jira/browse/RIVER-242>] - if
> a given ConnectionManager instance cannot create a reaper thread
> once, it never will again
> * [RIVER-245 <https://issues.apache.org/jira/browse/RIVER-245>] -
> Unicast discovery should close socket in case of connection
> exception.
> * [RIVER-252 <https://issues.apache.org/jira/browse/RIVER-252>] -
> ComputeHttpmdCodebase NPE if resource bundle not found
> * [RIVER-253 <https://issues.apache.org/jira/browse/RIVER-253>] -
> ComputeDigest NPE if resource bundle not found
> * [RIVER-254 <https://issues.apache.org/jira/browse/RIVER-254>] -
> request initiation can block on I/O for inapplicable connection
> * [RIVER-255 <https://issues.apache.org/jira/browse/RIVER-255>] -
> Outrigger DestroyThread does not catch exceptions from
> exporter.unexport
> * [RIVER-284 <https://issues.apache.org/jira/browse/RIVER-284>] -
> [PATCH] fix bad ParticipantHandle.compareTo
> * [RIVER-286 <https://issues.apache.org/jira/browse/RIVER-286>] -
> [PATCH] iterators on synchronized collections still need
> synchronization
> * [RIVER-289 <https://issues.apache.org/jira/browse/RIVER-289>] -
> Fix for RIVER-247 introduced wrong license headers and references
> * [RIVER-298 <https://issues.apache.org/jira/browse/RIVER-298>] - No
> JavaDocs generated for package "com.sun.jini.reliableLog"
> * [RIVER-302 <https://issues.apache.org/jira/browse/RIVER-302>] -
> ClassDep -newdirbehaviour option does not work
> * [RIVER-305 <https://issues.apache.org/jira/browse/RIVER-305>] -
> qa/GetPermissions test still uses "enum" keyword
> * [RIVER-320 <https://issues.apache.org/jira/browse/RIVER-320>] -
> Prebuilt hello example certificates have expired - need to provide
> new ones
> * [RIVER-324 <https://issues.apache.org/jira/browse/RIVER-324>] -
> Under certain circumstances, the ServiceDiscoveryManager internal
> LookupCache implementation can incorrectly process attribute
> change events before the lookup snapshot is processed.
>
>
> Improvement
>
> * [RIVER-7 <https://issues.apache.org/jira/browse/RIVER-7>] -
> com.sun.jini.tool.ClassDep should be smarter with outer classes
> * [RIVER-9 <https://issues.apache.org/jira/browse/RIVER-9>] -
> PreferredClassLoader should try to avoid making a direct check
> against the first URL
> * [RIVER-25 <https://issues.apache.org/jira/browse/RIVER-25>] -
> Improve logging for JoinManager at INFO and WARNING level
> * [RIVER-115 <https://issues.apache.org/jira/browse/RIVER-115>] -
> Multiple jar files with conflicting lists need facilities to map
> the chosen preferred value
> * [RIVER-116 <https://issues.apache.org/jira/browse/RIVER-116>] -
> Multiple jar files with conflicting lists need facilities to map
> the chosen preferred value
> * [RIVER-160 <https://issues.apache.org/jira/browse/RIVER-160>] -
> add TrustEquivalence to browser's list of uninterestingInterfaces
> * [RIVER-201 <https://issues.apache.org/jira/browse/RIVER-201>] -
> Show interfaces rather than classes in browser's Matching Services
> pane.
> * [RIVER-206 <https://issues.apache.org/jira/browse/RIVER-206>] -
> Change default load factors from 3 to 1
> * [RIVER-210 <https://issues.apache.org/jira/browse/RIVER-210>] -
> Browser should cancel event lease on exit
> * [RIVER-220 <https://issues.apache.org/jira/browse/RIVER-220>] -
> LookupLocatorDiscovery catch Throwable blocks should also catch
> Throwable
> * [RIVER-226 <https://issues.apache.org/jira/browse/RIVER-226>] -
> LLD: consider delaying the queuing of a discovery request
> immediately after a discard
> * [RIVER-229 <https://issues.apache.org/jira/browse/RIVER-229>] -
> reduce number of Reaper threads created by ConnectionManager
> * [RIVER-231 <https://issues.apache.org/jira/browse/RIVER-231>] -
> ComputeHttpmdCodebase man page could be clarified with respect to
> algorithm used
> * [RIVER-233 <https://issues.apache.org/jira/browse/RIVER-233>] -
> ComputeDigest instructions reference sha and sha1
> * [RIVER-243 <https://issues.apache.org/jira/browse/RIVER-243>] -
> JarWrapper javadoc could be clearer wrt to classpath manifests
> * [RIVER-244 <https://issues.apache.org/jira/browse/RIVER-244>] -
> Text area below menu bar in ServiceBrowser should not be editable
> * [RIVER-246 <https://issues.apache.org/jira/browse/RIVER-246>] -
> Consider adding shutdown hook so Reggie sends final multicast
> packet if its VM is terminated
> * [RIVER-247 <https://issues.apache.org/jira/browse/RIVER-247>] -
> Destroy processing should use configurable duration and interval
> for unexporting
> * [RIVER-256 <https://issues.apache.org/jira/browse/RIVER-256>] -
> Outrigger catch Throwable blocks should also catch Throwable
> * [RIVER-262 <https://issues.apache.org/jira/browse/RIVER-262>] -
> ServiceUI Specification
> * [RIVER-270 <https://issues.apache.org/jira/browse/RIVER-270>] -
> tar tasks in release* ant targets fail due to 100-char limitation
> and are disabled
> * [RIVER-285 <https://issues.apache.org/jira/browse/RIVER-285>] -
> LookupDiscoveryManager has unused variable declarations
>
>
> New Feature
>
> * [RIVER-151 <https://issues.apache.org/jira/browse/RIVER-151>] -
> ClassDep should have a method to determine if problems occurred
> * [RIVER-161 <https://issues.apache.org/jira/browse/RIVER-161>] -
> Coalesce jars from multiple source dirs while retain current
> Manifest Classpath semantics
> * [RIVER-163 <https://issues.apache.org/jira/browse/RIVER-163>] -
> ClassDep doesn't pick up annotation or type parameter dependencies
> * [RIVER-292 <https://issues.apache.org/jira/browse/RIVER-292>] -
> The service browser should provide support for the ServiceUI
> support
> * [RIVER-295 <https://issues.apache.org/jira/browse/RIVER-295>] -
> Support configurable option to prevent from popup windows that
> require a confirmation by the user
>
>
> Task
>
> * [RIVER-294 <https://issues.apache.org/jira/browse/RIVER-294>] -
> Remove http://svn.apache.org/repos/asf/incubator/river/trunk/ from
> the SVN repository
>
>
> Test
>
> * [RIVER-291 <https://issues.apache.org/jira/browse/RIVER-291>] -
> Cannot build QA tests using the supplied make files
>
> See the Release Artifacts for remaining release notes.
>
>
>
>
Re: [VOTE] Release Apache River 2.1.2
Posted by Jim Waldo <Ji...@Sun.COM>.
+1 for the release
Jim Waldo
On Mar 10, 2010, at 4:39 AM, Peter Firmstone wrote:
> Please vote on releasing Apache River 2.1.2
>
[RESULT] Re: [VOTE] Release Apache River 2.1.2
Posted by Peter Firmstone <ji...@zeus.net.au>.
Those voting in favour of Apache River Incubator Release 2.1.2 are (in
chronological order):
Sim IJskes
Jim Waldo
Jim Hurley
Tom Hobbs
Brian Murphy
David C Nelson
Gert Vanthienen
Jukka Zitting
Niclas Hedhman
Zsolt Kúti
Dan Rollo
Ant Elder
Jonathan Costers
No votes against.
On this occassion, we have received the minimum three Incubator PMC
votes, the vote has passed.
No, it's no April fools joke, it's time to sit back, relax and have a
quiet celebratory drink, to Apache River.
Thank you; to all our new contributors, committers, leaders and longtime
stewards (you know who you are), whose efforts have made this latest
release possible.
Cheers,
Peter Firmstone.
Peter Firmstone wrote:
> Please vote on releasing Apache River 2.1.2
>
> The voting period is open, due to the size of the River release, it
> will remain open until it passes with a majority of at least three +1
> River Incubator PMC votes or until a valid objection causes its
> rejection.
>
> All are encouraged to show their support by validating and casting a
> vote for this release, please ensure you reply to both lists, so those
> on general can see your interest in and support for our project:
>
> general@incubator.apache.org
> river-dev@incubator.apache.org
>
> A candidate for the Apache River 2.1.2 Release is available at
>
> http://people.apache.org/~peter_firmstone/
>
> The release candidate sources are zip / tar.gz archives of the sources
> in:
>
> http://svn.apache.org/repos/asf/incubator/river/jtsk/trunk/
>
> The source release artifact SHA1 checksums are:
>
> apache-river-2.1.2-incubating-src.tar.gz:
> 6B18 E089 C22C 9790 B0A4 89CC A410 2250 7A0A 4890
> apache-river-2.1.2-incubating-src.zip:
> 28F8 ABB3 0BDF 149F 6FA0 8D8B C982 47A6 19EF AE43
>
> The binary release artifact SHA1 checksums:
>
> apache-river-2.1.2-incubating-bin.tar.gz:
> 3813 613B 4432 B5A9 E6F3 EFCA D649 D55A C73A 1BA8
> apache-river-2.1.2-incubating-bin.zip:
> F692 BCDC A050 9BCF 3ADD A5E4 C500 4263 0FAE 6BEE
>
>
> Apache River
> v2.1.2 Release Notes
>
> ------------------------------------------------------------------------
> Apache River is an effort undergoing incubation at The Apache Software
> Foundation (ASF), sponsored by the Apache Incubator. Incubation is
> required of all newly accepted projects until a further review indicates
> that the infrastructure, communications, and decision making process
> have stabilized in a manner consistent with other successful ASF
> projects. While incubation status is not necessarily a reflection of the
> completeness or stability of the code, it does indicate that the project
> has yet to be fully endorsed by the ASF.
>
> Apache River is aimed at the development and advancement of the River
> technology core infrastructure. River technology is a service oriented
> architecture that defines a programming model which both exploits and
> extends Java technology to enable the construction of secure,
> distributed systems which are adaptive to change.
>
> ------------------------------------------------------------------------
>
>
> Notes of Interest for this Release
>
> This second release from the Apache River project is based on the
> contributions of Sun's Jini Technology Starter Kit (Starter Kit) v2.1
> and Service UI from Artima. The release focuses on merging the two
> contributions together, structuring separate src and bin releases, and
> amending the source and documentation naming/versioning/etc to the
> Apache River project.
>
> Some points of note:
>
> * NOTICE file and source license headers updated
> * Source and documentation updated for release name ("Apache River
> release") and version ("v2.1.2")
> * Graphical installer (which was a 3rd party application in the
> Starter Kit) is no longer available
> * The combined source and binary release in the Starter Kit has been
> separated into two releases: src and bin
> * The "logstore" implementation of com.sun.jini.outrigger.Store has
> been removed
>
> The persistent version of Outrigger relies on a pluggable
> persistence layer, |com.sun.jini.outrigger.Store|. Previous
> releases of the Starter Kit included two implementations of the
> Store interface, /logstore/ and /snaplogstore/. This release
> removes logstore.
>
> Logstore has been around in various forms since the 1.0 version of
> Outrigger. Snapstore was introduced in v2.1 of the Starter Kit.
>
> The v2.0.n releases of the Starter Kit used logstore as the
> default Store implementation, this release has no default Store.
> In order to switch an existing set of configuration files,
> security policy files, etc., from using logstore to snaplogstore,
> you will need to change the |com.sun.jini.outrigger.store|
> configuration entry (or add a store configuration entry if you
> don't already have one) to yield a
> |com.sun.jini.outrigger.snaplogstore.LogStore| object. You will
> also need to ensure that |outrigger-snaplogstore.jar| has been
> granted sufficient permissions (see Outrigger's package
> documentation for a sample security policy file.).
>
> Note that depending on the nature of your application snaplogstore
> can have a significantly different performance profile than
> logstore.
>
> The storage formats used by snaplogstore and logstore are mutually
> incompatible.
>
> ------------------------------------------------------------------------
>
>
> Submitting Issues
>
> If you would like to submit a bug against the Apache River release,
> please use the River JIRA <http://issues.apache.org/jira/browse/RIVER>.
> To discuss problems, questions, or suggestions on the release, please
> subscribe to the |river-dev| list from the project Mailing Lists
> <http://incubator.apache.org/river/mailing.html> page.
>
> ------------------------------------------------------------------------
>
>
> Upcoming Changes planned for the next version of Apache River
>
> # All packages ouside of the net.jini namespace will be renamed to
> org.apache.river.
> # Support for Java 5 language features
> # Support for Modular Frameworks conforming to the OSGi r4.2 core
> Specification
> ------------------------------------------------------------------------
>
>
> Changes made since Apache River v2.1.1
>
>
> Bug
>
> * [RIVER-5 <https://issues.apache.org/jira/browse/RIVER-5>] -
> HTTMPMD URLs can be considered equal while they are not
> * [RIVER-8 <https://issues.apache.org/jira/browse/RIVER-8>] -
> com.sun.jini.tool.ClassDep empty inside collection doesn't work
> * [RIVER-17 <https://issues.apache.org/jira/browse/RIVER-17>] -
> Misleading logging message when discovery constraint checking is
> delayed
> * [RIVER-18 <https://issues.apache.org/jira/browse/RIVER-18>] -
> Order of discovery providers not maintained
> * [RIVER-22 <https://issues.apache.org/jira/browse/RIVER-22>] - NPE
> in
> net.jini.jeri.tcp.TcpEndpoint$ConnectionImpl.checkConnectPermission
> * [RIVER-24 <https://issues.apache.org/jira/browse/RIVER-24>] -
> PreferredListGen can create illegal PREFERRED.LIST
> * [RIVER-78 <https://issues.apache.org/jira/browse/RIVER-78>] -
> ClassDep generates duplicate output lines
> * [RIVER-82 <https://issues.apache.org/jira/browse/RIVER-82>] -
> ClassDep generates duplicate output lines
> * [RIVER-91 <https://issues.apache.org/jira/browse/RIVER-91>] -
> Uninstaller does not remove all items
> * [RIVER-205 <https://issues.apache.org/jira/browse/RIVER-205>] -
> LookupDiscovery can give untrusted code access to privileged threads
> * [RIVER-209 <https://issues.apache.org/jira/browse/RIVER-209>] -
> NullPointerException in SslConnection.checkConnectPermission()
> * [RIVER-212 <https://issues.apache.org/jira/browse/RIVER-212>] -
> use of "enum" as a variable name
> * [RIVER-213 <https://issues.apache.org/jira/browse/RIVER-213>] -
> (DOC) - JoinManger has typo in javadoc (missing </code>
> termination tag)
> * [RIVER-215 <https://issues.apache.org/jira/browse/RIVER-215>] -
> LookupDiscovery throws NullPointerException on terminate
> * [RIVER-216 <https://issues.apache.org/jira/browse/RIVER-216>] -
> ConfigurationFile should throw ExceptionInInitializerError if
> unable to read prohibited methods
> * [RIVER-217 <https://issues.apache.org/jira/browse/RIVER-217>] -
> Browser incorrectly assumes event source is ServiceRegistrar proxy
> * [RIVER-223 <https://issues.apache.org/jira/browse/RIVER-223>] -
> test: jtreg/net/jini/jeri/tcp/connectTimeout/TestConnectTimeout
> fails on Linux
> * [RIVER-224 <https://issues.apache.org/jira/browse/RIVER-224>] -
> Problem using browser to destroy service that supports
> DestroyAdmin but not JoinAdmin
> * [RIVER-225 <https://issues.apache.org/jira/browse/RIVER-225>] -
> NullPointerException in Reggie during destroy
> * [RIVER-227 <https://issues.apache.org/jira/browse/RIVER-227>] -
> tools manpages command lines do not include line continuation
> characters
> * [RIVER-230 <https://issues.apache.org/jira/browse/RIVER-230>] -
> (mux) SelectionManager catch Error block assumes getMessage()
> returns non-null
> * [RIVER-232 <https://issues.apache.org/jira/browse/RIVER-232>] -
> JarWrapper and PreferredListGen uses jsk_install_dir and install_dir
> * [RIVER-234 <https://issues.apache.org/jira/browse/RIVER-234>] -
> (DOC) Fiddler manpage directions for HTTP server should reference
> classserver.jar, not tools.jar
> * [RIVER-240 <https://issues.apache.org/jira/browse/RIVER-240>] -
> BasicInvocationDispatcher.dispatch could log more info for some
> exceptions
> * [RIVER-241 <https://issues.apache.org/jira/browse/RIVER-241>] -
> Mercury spelling errore
> * [RIVER-242 <https://issues.apache.org/jira/browse/RIVER-242>] - if
> a given ConnectionManager instance cannot create a reaper thread
> once, it never will again
> * [RIVER-245 <https://issues.apache.org/jira/browse/RIVER-245>] -
> Unicast discovery should close socket in case of connection
> exception.
> * [RIVER-252 <https://issues.apache.org/jira/browse/RIVER-252>] -
> ComputeHttpmdCodebase NPE if resource bundle not found
> * [RIVER-253 <https://issues.apache.org/jira/browse/RIVER-253>] -
> ComputeDigest NPE if resource bundle not found
> * [RIVER-254 <https://issues.apache.org/jira/browse/RIVER-254>] -
> request initiation can block on I/O for inapplicable connection
> * [RIVER-255 <https://issues.apache.org/jira/browse/RIVER-255>] -
> Outrigger DestroyThread does not catch exceptions from
> exporter.unexport
> * [RIVER-284 <https://issues.apache.org/jira/browse/RIVER-284>] -
> [PATCH] fix bad ParticipantHandle.compareTo
> * [RIVER-286 <https://issues.apache.org/jira/browse/RIVER-286>] -
> [PATCH] iterators on synchronized collections still need
> synchronization
> * [RIVER-289 <https://issues.apache.org/jira/browse/RIVER-289>] -
> Fix for RIVER-247 introduced wrong license headers and references
> * [RIVER-298 <https://issues.apache.org/jira/browse/RIVER-298>] - No
> JavaDocs generated for package "com.sun.jini.reliableLog"
> * [RIVER-302 <https://issues.apache.org/jira/browse/RIVER-302>] -
> ClassDep -newdirbehaviour option does not work
> * [RIVER-305 <https://issues.apache.org/jira/browse/RIVER-305>] -
> qa/GetPermissions test still uses "enum" keyword
> * [RIVER-320 <https://issues.apache.org/jira/browse/RIVER-320>] -
> Prebuilt hello example certificates have expired - need to provide
> new ones
> * [RIVER-324 <https://issues.apache.org/jira/browse/RIVER-324>] -
> Under certain circumstances, the ServiceDiscoveryManager internal
> LookupCache implementation can incorrectly process attribute
> change events before the lookup snapshot is processed.
>
>
> Improvement
>
> * [RIVER-7 <https://issues.apache.org/jira/browse/RIVER-7>] -
> com.sun.jini.tool.ClassDep should be smarter with outer classes
> * [RIVER-9 <https://issues.apache.org/jira/browse/RIVER-9>] -
> PreferredClassLoader should try to avoid making a direct check
> against the first URL
> * [RIVER-25 <https://issues.apache.org/jira/browse/RIVER-25>] -
> Improve logging for JoinManager at INFO and WARNING level
> * [RIVER-115 <https://issues.apache.org/jira/browse/RIVER-115>] -
> Multiple jar files with conflicting lists need facilities to map
> the chosen preferred value
> * [RIVER-116 <https://issues.apache.org/jira/browse/RIVER-116>] -
> Multiple jar files with conflicting lists need facilities to map
> the chosen preferred value
> * [RIVER-160 <https://issues.apache.org/jira/browse/RIVER-160>] -
> add TrustEquivalence to browser's list of uninterestingInterfaces
> * [RIVER-201 <https://issues.apache.org/jira/browse/RIVER-201>] -
> Show interfaces rather than classes in browser's Matching Services
> pane.
> * [RIVER-206 <https://issues.apache.org/jira/browse/RIVER-206>] -
> Change default load factors from 3 to 1
> * [RIVER-210 <https://issues.apache.org/jira/browse/RIVER-210>] -
> Browser should cancel event lease on exit
> * [RIVER-220 <https://issues.apache.org/jira/browse/RIVER-220>] -
> LookupLocatorDiscovery catch Throwable blocks should also catch
> Throwable
> * [RIVER-226 <https://issues.apache.org/jira/browse/RIVER-226>] -
> LLD: consider delaying the queuing of a discovery request
> immediately after a discard
> * [RIVER-229 <https://issues.apache.org/jira/browse/RIVER-229>] -
> reduce number of Reaper threads created by ConnectionManager
> * [RIVER-231 <https://issues.apache.org/jira/browse/RIVER-231>] -
> ComputeHttpmdCodebase man page could be clarified with respect to
> algorithm used
> * [RIVER-233 <https://issues.apache.org/jira/browse/RIVER-233>] -
> ComputeDigest instructions reference sha and sha1
> * [RIVER-243 <https://issues.apache.org/jira/browse/RIVER-243>] -
> JarWrapper javadoc could be clearer wrt to classpath manifests
> * [RIVER-244 <https://issues.apache.org/jira/browse/RIVER-244>] -
> Text area below menu bar in ServiceBrowser should not be editable
> * [RIVER-246 <https://issues.apache.org/jira/browse/RIVER-246>] -
> Consider adding shutdown hook so Reggie sends final multicast
> packet if its VM is terminated
> * [RIVER-247 <https://issues.apache.org/jira/browse/RIVER-247>] -
> Destroy processing should use configurable duration and interval
> for unexporting
> * [RIVER-256 <https://issues.apache.org/jira/browse/RIVER-256>] -
> Outrigger catch Throwable blocks should also catch Throwable
> * [RIVER-262 <https://issues.apache.org/jira/browse/RIVER-262>] -
> ServiceUI Specification
> * [RIVER-270 <https://issues.apache.org/jira/browse/RIVER-270>] -
> tar tasks in release* ant targets fail due to 100-char limitation
> and are disabled
> * [RIVER-285 <https://issues.apache.org/jira/browse/RIVER-285>] -
> LookupDiscoveryManager has unused variable declarations
>
>
> New Feature
>
> * [RIVER-151 <https://issues.apache.org/jira/browse/RIVER-151>] -
> ClassDep should have a method to determine if problems occurred
> * [RIVER-161 <https://issues.apache.org/jira/browse/RIVER-161>] -
> Coalesce jars from multiple source dirs while retain current
> Manifest Classpath semantics
> * [RIVER-163 <https://issues.apache.org/jira/browse/RIVER-163>] -
> ClassDep doesn't pick up annotation or type parameter dependencies
> * [RIVER-292 <https://issues.apache.org/jira/browse/RIVER-292>] -
> The service browser should provide support for the ServiceUI support
> * [RIVER-295 <https://issues.apache.org/jira/browse/RIVER-295>] -
> Support configurable option to prevent from popup windows that
> require a confirmation by the user
>
>
> Task
>
> * [RIVER-294 <https://issues.apache.org/jira/browse/RIVER-294>] -
> Remove http://svn.apache.org/repos/asf/incubator/river/trunk/ from
> the SVN repository
>
>
> Test
>
> * [RIVER-291 <https://issues.apache.org/jira/browse/RIVER-291>] -
> Cannot build QA tests using the supplied make files
>
> See the Release Artifacts for remaining release notes.
>
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org