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 "Siddharth Srivastava (JIRA)" <ji...@apache.org> on 2011/03/27 13:12:05 UTC
[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
[ https://issues.apache.org/jira/browse/DERBY-4862?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13011776#comment-13011776 ]
Siddharth Srivastava commented on DERBY-4862:
---------------------------------------------
I looked upon the above files.
Though I am now able to understand how things are working behind but I am not able to get the logic behind inclusion of specific files in dnc.properties, tools.properties etc ?
What criteria is behind inclusion of those files ?
> 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