[
https://issues.apache.org/jira/browse/DERBY-3285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dag H. Wanvik updated DERBY-3285:
---------------------------------
Issue Type: Improvement (was: Bug)
Summary: Make derby.system.bootAll work regardless of whether
derby.system.home is explicitly set or not (was: derby.system.bootAll does not
work unless derby.system.home is explicitly set)
> Make derby.system.bootAll work regardless of whether derby.system.home is
> explicitly set or not
> -----------------------------------------------------------------------------------------------
>
> Key: DERBY-3285
> URL: https://issues.apache.org/jira/browse/DERBY-3285
> Project: Derby
> Issue Type: Improvement
> Components: Services
> Affects Versions: 10.3.1.4, 10.3.2.1, 10.4.1.3
> Reporter: Dag H. Wanvik
> Priority: Minor
>
> Cf discussion under DERBY-2182, which revealed that bootAll only works as
> intended (?!) when derby.system.home. If
> it has its default value, user.dir, no autoboot takes place.
> We also saw an exception: The network server sets derby.system.home
> explicitly, unless
> -noSecurityManager is set, so in this case the auto-booting is not affected
> by this bug.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
