You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Deepa Remesh (JIRA)" <de...@db.apache.org> on 2006/03/22 00:03:11 UTC

[jira] Created: (DERBY-1135) Run upgrade test using a security manager

Run upgrade test using a security manager
-----------------------------------------

         Key: DERBY-1135
         URL: http://issues.apache.org/jira/browse/DERBY-1135
     Project: Derby
        Type: Sub-task
  Components: Test  
    Reporter: Deepa Remesh
 Assigned to: Deepa Remesh 
     Fix For: 10.2.0.0


To be able to run the upgrade test using the test harness, it should be possible to run the test using the harness' security manager. Some issues in doing this are identified in http://www.nabble.com/Upgrade-test-and-security-permissions-p3517019.html. We need to identify the set of permissions required to run the test. This seems to a slightly more involved task because of use of jars from multiple versions. Hence opening it as a sub-task.

As a temporary solution, I think we can add "noSecurityManager=true" to allow the test to run in the harness.






-- 
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


[jira] Updated: (DERBY-1135) Run upgrade test using a security manager

Posted by "Rick Hillegas (JIRA)" <de...@db.apache.org>.
     [ http://issues.apache.org/jira/browse/DERBY-1135?page=all ]

Rick Hillegas updated DERBY-1135:
---------------------------------

    Fix Version/s: 10.2.2.0
                       (was: 10.2.1.0)

Moving to 10.2.2.0.

> Run upgrade test using a security manager
> -----------------------------------------
>
>                 Key: DERBY-1135
>                 URL: http://issues.apache.org/jira/browse/DERBY-1135
>             Project: Derby
>          Issue Type: Sub-task
>          Components: Test
>            Reporter: Deepa Remesh
>         Assigned To: Deepa Remesh
>             Fix For: 10.2.2.0
>
>
> To be able to run the upgrade test using the test harness, it should be possible to run the test using the harness' security manager. Some issues in doing this are identified in http://www.nabble.com/Upgrade-test-and-security-permissions-p3517019.html. We need to identify the set of permissions required to run the test. This seems to a slightly more involved task because of use of jars from multiple versions. Hence opening it as a sub-task.
> As a temporary solution, I think we can add "noSecurityManager=true" to allow the test to run in the harness.

-- 
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

        

[jira] Assigned: (DERBY-1135) Run upgrade test using a security manager

Posted by "Kathey Marsden (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/DERBY-1135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kathey Marsden reassigned DERBY-1135:
-------------------------------------

    Assignee:     (was: Deepa Remesh)

> Run upgrade test using a security manager
> -----------------------------------------
>
>                 Key: DERBY-1135
>                 URL: https://issues.apache.org/jira/browse/DERBY-1135
>             Project: Derby
>          Issue Type: Sub-task
>          Components: Test
>            Reporter: Deepa Remesh
>
> To be able to run the upgrade test using the test harness, it should be possible to run the test using the harness' security manager. Some issues in doing this are identified in http://www.nabble.com/Upgrade-test-and-security-permissions-p3517019.html. We need to identify the set of permissions required to run the test. This seems to a slightly more involved task because of use of jars from multiple versions. Hence opening it as a sub-task.
> As a temporary solution, I think we can add "noSecurityManager=true" to allow the test to run in the harness.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (DERBY-1135) Run upgrade test using a security manager

Posted by "Rick Hillegas (JIRA)" <de...@db.apache.org>.
     [ http://issues.apache.org/jira/browse/DERBY-1135?page=all ]

Rick Hillegas updated DERBY-1135:
---------------------------------

    Urgency: Normal

> Run upgrade test using a security manager
> -----------------------------------------
>
>                 Key: DERBY-1135
>                 URL: http://issues.apache.org/jira/browse/DERBY-1135
>             Project: Derby
>          Issue Type: Sub-task
>          Components: Test
>            Reporter: Deepa Remesh
>         Assigned To: Deepa Remesh
>             Fix For: 10.2.0.0
>
>
> To be able to run the upgrade test using the test harness, it should be possible to run the test using the harness' security manager. Some issues in doing this are identified in http://www.nabble.com/Upgrade-test-and-security-permissions-p3517019.html. We need to identify the set of permissions required to run the test. This seems to a slightly more involved task because of use of jars from multiple versions. Hence opening it as a sub-task.
> As a temporary solution, I think we can add "noSecurityManager=true" to allow the test to run in the harness.

-- 
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

        

[jira] Commented: (DERBY-1135) Run upgrade test using a security manager

Posted by "Myrna van Lunteren (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/DERBY-1135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12654495#action_12654495 ] 

Myrna van Lunteren commented on DERBY-1135:
-------------------------------------------

Is this issue still relevant? Or is it no longer interesting because we've converted to junit?
If so, we could close this with 'will not fix'.

> Run upgrade test using a security manager
> -----------------------------------------
>
>                 Key: DERBY-1135
>                 URL: https://issues.apache.org/jira/browse/DERBY-1135
>             Project: Derby
>          Issue Type: Sub-task
>          Components: Test
>            Reporter: Deepa Remesh
>
> To be able to run the upgrade test using the test harness, it should be possible to run the test using the harness' security manager. Some issues in doing this are identified in http://www.nabble.com/Upgrade-test-and-security-permissions-p3517019.html. We need to identify the set of permissions required to run the test. This seems to a slightly more involved task because of use of jars from multiple versions. Hence opening it as a sub-task.
> As a temporary solution, I think we can add "noSecurityManager=true" to allow the test to run in the harness.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (DERBY-1135) Run upgrade test using a security manager

Posted by "Rick Hillegas (JIRA)" <ji...@apache.org>.
     [ http://issues.apache.org/jira/browse/DERBY-1135?page=all ]

Rick Hillegas updated DERBY-1135:
---------------------------------

    Fix Version/s:     (was: 10.2.2.0)

Unknown release vehicle.

> Run upgrade test using a security manager
> -----------------------------------------
>
>                 Key: DERBY-1135
>                 URL: http://issues.apache.org/jira/browse/DERBY-1135
>             Project: Derby
>          Issue Type: Sub-task
>          Components: Test
>            Reporter: Deepa Remesh
>         Assigned To: Deepa Remesh
>
> To be able to run the upgrade test using the test harness, it should be possible to run the test using the harness' security manager. Some issues in doing this are identified in http://www.nabble.com/Upgrade-test-and-security-permissions-p3517019.html. We need to identify the set of permissions required to run the test. This seems to a slightly more involved task because of use of jars from multiple versions. Hence opening it as a sub-task.
> As a temporary solution, I think we can add "noSecurityManager=true" to allow the test to run in the harness.

-- 
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