Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@jackrabbit.apache.org
Received-SPF: pass (athena.apache.org: domain of jukka.zitting@gmail.com
 designates 74.125.46.28 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition;
        b=Oa6aarC+ECumeKDrr/lOzj3WjL32pMEt6zxfhS79lWt2v0bC6pF/FVZRCsJZtKHELjI6s1hHc+yLBy045tLbSuOSvMFICX7qqlrNmNhi+KvmbMGqY81M5+wqBMysppwlsm87FSbVRpLXVvdidpQkCuV5NFJe5y21WKA1DhYic3U=
Message-ID: <510143ac0804021306o2852fd0dkc89154255ab0eecb@mail.gmail.com>
Date: Wed, 2 Apr 2008 23:06:40 +0300
From: "Jukka Zitting" <jukka.zitting@gmail.com>
To: dev@jackrabbit.apache.org
Subject: Known issues in release notes (Was: svn commit: r644024 -
 /jackrabbit/branches/1.4/jackrabbit-jcr-rmi/RELEASE-NOTES.txt)
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Hi,

On Wed, Apr 2, 2008 at 10:52 PM,  <fmeschbe@apache.org> wrote:
>  +  Known Issues:
>  +  [JCR-300]  Streamline the JCR-RMI network interfaces
>  +  [JCR-301]  Improve the JCR-RMI Value classes
>  +  [JCR-781]  RMI: Allow custom socket factories
>  +  [JCR-1317] Add a MBean method to programatically create a new Workspace.
>  +  [JCR-1457] Restart of RMI-component fails (because it's not ...

I've typically only included bug reports in the list of known issues,
as those are the only ones that users really need to be aware of if
they expect the component to work as documented.

The Jira query I've used for generating the known issue lists is:

    Project: Jackrabbit
    Issue Type: Bug
    Components: <release component(s)>
    Resolution: Unresolved

For jcr-rmi the only known issue based on that criteria would have
been JCR-1457, but it seems more of an jackrabbit-webapp issue and
I've updated it accordingly.

BR,

Jukka Zitting