Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <13498465.1157586623509.JavaMail.jira@brutus>
Date: Wed, 6 Sep 2006 16:50:23 -0700 (PDT)
From: "Susan Cline (JIRA)" <derby-dev@db.apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Commented: (DERBY-1152) Failures in sysinfo and
 sysinfo_withproperties induced by classpath wiring
In-Reply-To: <1522073946.1143479418991.JavaMail.jira@ajax>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

    [ http://issues.apache.org/jira/browse/DERBY-1152?page=comments#action_12432998 ] 
            
Susan Cline commented on DERBY-1152:
------------------------------------

Hi Bryan,

Thanks for your response.  I'll make an addition to the documentation to change it accordingly then.

Susan

> Failures in sysinfo and sysinfo_withproperties induced by classpath wiring
> --------------------------------------------------------------------------
>
>                 Key: DERBY-1152
>                 URL: http://issues.apache.org/jira/browse/DERBY-1152
>             Project: Derby
>          Issue Type: Bug
>          Components: Test
>    Affects Versions: 10.2.1.0
>            Reporter: Rick Hillegas
>         Assigned To: Bryan Pendleton
>             Fix For: 10.2.1.0
>
>         Attachments: derby-1152-looser-policy.diff
>
>
> If you wire your classpath together out of the compiled classtree and the checked-in jars, you get the following error in the sysinfo and sysinfo_withproperties tests. You don't see this error if you run against the built Derby jar files:
> 15d14
> < Unable to analyze class path: access denied (java.util.PropertyPermission java.class.path read)
> 43d41
> < Unable to analyze class path: access denied (java.util.PropertyPermission java.class.path read)
> 72d69
> < Unable to analyze class path: access denied (java.util.PropertyPermission java.class.path read)
> Test Failed.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira