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 "Knut Anders Hatlen (JIRA)" <de...@db.apache.org> on 2005/11/01 16:30:55 UTC

[jira] Created: (DERBY-667) Derbyall should test the framework scripts

Derbyall should test the framework scripts
------------------------------------------

         Key: DERBY-667
         URL: http://issues.apache.org/jira/browse/DERBY-667
     Project: Derby
        Type: Test
  Components: Test, Demos/Scripts  
    Versions: 10.1.3.0, 10.2.0.0    
    Reporter: Knut Anders Hatlen
    Priority: Minor
     Fix For: 10.1.3.0, 10.2.0.0


As the release process for Derby 10.1.2.0 has shown, the scripts in
the frameworks directory are not heavily tested. There should have
been a test of the scripts in derbyall, so problems with running them
are discovered.


-- 
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-667) Derbyall should test the framework scripts

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

Kathey Marsden updated DERBY-667:
---------------------------------

    Version:     (was: 10.1.3.0)

Taking this off of 10.1.3 as nobody responded that they were signed up to fix it.


> Derbyall should test the framework scripts
> ------------------------------------------
>
>          Key: DERBY-667
>          URL: http://issues.apache.org/jira/browse/DERBY-667
>      Project: Derby
>         Type: Test

>   Components: Test, Demos/Scripts
>     Versions: 10.2.0.0
>     Reporter: Knut Anders Hatlen
>     Priority: Minor
>      Fix For: 10.1.3.0, 10.2.0.0

>
> As the release process for Derby 10.1.2.0 has shown, the scripts in
> the frameworks directory are not heavily tested. There should have
> been a test of the scripts in derbyall, so problems with running them
> are discovered.

-- 
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-667) Derbyall should test the framework scripts

Posted by "Kathey Marsden (JIRA)" <de...@db.apache.org>.
    [ http://issues.apache.org/jira/browse/DERBY-667?page=comments#action_12379155 ] 

Kathey Marsden commented on DERBY-667:
--------------------------------------

This is marked 10.1.3.0 but is unassigned. Is someone planning to fix this issue for the release?


> Derbyall should test the framework scripts
> ------------------------------------------
>
>          Key: DERBY-667
>          URL: http://issues.apache.org/jira/browse/DERBY-667
>      Project: Derby
>         Type: Test

>   Components: Test, Demos/Scripts
>     Versions: 10.1.3.0, 10.2.0.0
>     Reporter: Knut Anders Hatlen
>     Priority: Minor
>      Fix For: 10.1.3.0, 10.2.0.0

>
> As the release process for Derby 10.1.2.0 has shown, the scripts in
> the frameworks directory are not heavily tested. There should have
> been a test of the scripts in derbyall, so problems with running them
> are discovered.

-- 
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-667) Derbyall should test the framework scripts

Posted by "Daniel John Debrunner (JIRA)" <de...@db.apache.org>.
    [ http://issues.apache.org/jira/browse/DERBY-667?page=comments#action_12413172 ] 

Daniel John Debrunner commented on DERBY-667:
---------------------------------------------

The framework scripts are still part of derby and should be tested so this is a valid Jira entry.

> Derbyall should test the framework scripts
> ------------------------------------------
>
>          Key: DERBY-667
>          URL: http://issues.apache.org/jira/browse/DERBY-667
>      Project: Derby
>         Type: Test

>   Components: Test, Demos/Scripts
>     Versions: 10.2.0.0, 10.1.3.0
>     Reporter: Knut Anders Hatlen
>     Priority: Minor
>      Fix For: 10.2.0.0

>
> As the release process for Derby 10.1.2.0 has shown, the scripts in
> the frameworks directory are not heavily tested. There should have
> been a test of the scripts in derbyall, so problems with running them
> are discovered.

-- 
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-667) Derbyall should test the framework scripts

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

Dag H. Wanvik updated DERBY-667:
--------------------------------

    Issue Type: Improvement  (was: Test)

> Derbyall should test the framework scripts
> ------------------------------------------
>
>                 Key: DERBY-667
>                 URL: https://issues.apache.org/jira/browse/DERBY-667
>             Project: Derby
>          Issue Type: Improvement
>          Components: Demos/Scripts, Test
>    Affects Versions: 10.1.3.1, 10.2.1.6
>            Reporter: Knut Anders Hatlen
>            Priority: Minor
>
> As the release process for Derby 10.1.2.0 has shown, the scripts in
> the frameworks directory are not heavily tested. There should have
> been a test of the scripts in derbyall, so problems with running them
> are discovered.

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


[jira] Commented: (DERBY-667) Derbyall should test the framework scripts

Posted by "John H. Embretsen (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/DERBY-667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12533693 ] 

John H. Embretsen commented on DERBY-667:
-----------------------------------------

FYI, the framework scripts have now been removed from trunk (see DERBY-3026 ), but tests of the bin scripts would be just as useful.

> Derbyall should test the framework scripts
> ------------------------------------------
>
>                 Key: DERBY-667
>                 URL: https://issues.apache.org/jira/browse/DERBY-667
>             Project: Derby
>          Issue Type: Test
>          Components: Demos/Scripts, Test
>    Affects Versions: 10.1.3.1, 10.2.1.6
>            Reporter: Knut Anders Hatlen
>            Priority: Minor
>
> As the release process for Derby 10.1.2.0 has shown, the scripts in
> the frameworks directory are not heavily tested. There should have
> been a test of the scripts in derbyall, so problems with running them
> are discovered.

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


[jira] Updated: (DERBY-667) Derbyall should test the framework scripts

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

Rick Hillegas updated DERBY-667:
--------------------------------

    Urgency: Low

> Derbyall should test the framework scripts
> ------------------------------------------
>
>                 Key: DERBY-667
>                 URL: http://issues.apache.org/jira/browse/DERBY-667
>             Project: Derby
>          Issue Type: Test
>          Components: Test, Demos/Scripts
>    Affects Versions: 10.2.0.0, 10.1.3.0
>            Reporter: Knut Anders Hatlen
>            Priority: Minor
>             Fix For: 10.2.0.0
>
>
> As the release process for Derby 10.1.2.0 has shown, the scripts in
> the frameworks directory are not heavily tested. There should have
> been a test of the scripts in derbyall, so problems with running them
> are discovered.

-- 
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-667) Derbyall should test the framework scripts

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

Andrew McIntyre updated DERBY-667:
----------------------------------

    Fix Version:     (was: 10.1.3.0)
        Version: 10.1.3.0

> Derbyall should test the framework scripts
> ------------------------------------------
>
>          Key: DERBY-667
>          URL: http://issues.apache.org/jira/browse/DERBY-667
>      Project: Derby
>         Type: Test

>   Components: Test, Demos/Scripts
>     Versions: 10.2.0.0, 10.1.3.0
>     Reporter: Knut Anders Hatlen
>     Priority: Minor
>      Fix For: 10.2.0.0

>
> As the release process for Derby 10.1.2.0 has shown, the scripts in
> the frameworks directory are not heavily tested. There should have
> been a test of the scripts in derbyall, so problems with running them
> are discovered.

-- 
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-667) Derbyall should test the framework scripts

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

Andrew McIntyre updated DERBY-667:
----------------------------------

    Fix Version/s: 10.3.0.0
                       (was: 10.2.0.0)

Pushing to 10.3, since /bin scripts are pending, and there's no clear plan for how to test any of the scripts yet.

> Derbyall should test the framework scripts
> ------------------------------------------
>
>                 Key: DERBY-667
>                 URL: http://issues.apache.org/jira/browse/DERBY-667
>             Project: Derby
>          Issue Type: Test
>          Components: Test, Demos/Scripts
>    Affects Versions: 10.2.0.0, 10.1.3.0
>            Reporter: Knut Anders Hatlen
>            Priority: Minor
>             Fix For: 10.3.0.0
>
>
> As the release process for Derby 10.1.2.0 has shown, the scripts in
> the frameworks directory are not heavily tested. There should have
> been a test of the scripts in derbyall, so problems with running them
> are discovered.

-- 
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-667) Derbyall should test the framework scripts

Posted by "Knut Anders Hatlen (JIRA)" <de...@db.apache.org>.
    [ http://issues.apache.org/jira/browse/DERBY-667?page=comments#action_12413087 ] 

Knut Anders Hatlen commented on DERBY-667:
------------------------------------------

This issue is probably not so important in 10.2 since we have the runnable jar files. Should we just close it?

> Derbyall should test the framework scripts
> ------------------------------------------
>
>          Key: DERBY-667
>          URL: http://issues.apache.org/jira/browse/DERBY-667
>      Project: Derby
>         Type: Test

>   Components: Test, Demos/Scripts
>     Versions: 10.2.0.0, 10.1.3.0
>     Reporter: Knut Anders Hatlen
>     Priority: Minor
>      Fix For: 10.2.0.0

>
> As the release process for Derby 10.1.2.0 has shown, the scripts in
> the frameworks directory are not heavily tested. There should have
> been a test of the scripts in derbyall, so problems with running them
> are discovered.

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