db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Siddharth Srivastava (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-4862) Store version info in derbyTesting.jar and report its version with sysinfo, maybe with a warning that it should not be deployed
Date Thu, 10 Feb 2011 19:11:58 GMT

    [ https://issues.apache.org/jira/browse/DERBY-4862?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12993175#comment-12993175
] 

Siddharth Srivastava commented on DERBY-4862:
---------------------------------------------

I would like to start working on this bug. Some pointers would be helpful. Thanks

> Store version info in derbyTesting.jar and report its version with sysinfo, maybe with
a warning that it should  not be deployed
> --------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-4862
>                 URL: https://issues.apache.org/jira/browse/DERBY-4862
>             Project: Derby
>          Issue Type: Improvement
>          Components: Test, Tools
>    Affects Versions: 10.5.3.0, 10.6.2.1, 10.7.1.1
>            Reporter: Kathey Marsden
>            Assignee: Siddharth Srivastava
>            Priority: Minor
>
> derbyTesting.jar is put in a separate directory for releases, which is good in that it
tends to deter folks from accidentally deploying it, but sometimes for people that do run
tests, this means that it might accidentally get separated or mismatched with the product
jars. It would be nice if sysinfo reported derbyTesting.jar and its version if present and
could also print a warning that derbyTesting.jar should never be deployed in production.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message