directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shawn McKinney (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FC-163) [ fortress-core ] fortress.properties is not required
Date Mon, 28 Mar 2016 04:13:25 GMT

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

Shawn McKinney commented on FC-163:
-----------------------------------

Tested web component by adding these params to catalina.sh:

JAVA_OPTS="$JAVA_OPTS -Dfortress.admin.user=uid=admin,ou=system -Dfortress.admin.pw=secret
-Dfortress.config.root=ou=Config,dc=example,dc=com -Dfortress.port=10389"

> [ fortress-core ] fortress.properties is not required 
> ------------------------------------------------------
>
>                 Key: FC-163
>                 URL: https://issues.apache.org/jira/browse/FC-163
>             Project: FORTRESS
>          Issue Type: Improvement
>    Affects Versions: 1.0.0-RC42
>            Reporter: Shawn McKinney
>             Fix For: 1.0.0
>
>
> Change the fortress core bootstrap to make fortress.properties optional.  This will allow
the system to bootstrap itself with defaults and java.system.properties only.  
> The rationale is the fortress web and rest war that are deployed from a download version
will not have a fortress.properties file.  This change enables the war to be deployed and
system operational iff the necessary system properties are set:
> -Dfortress.admin.user=cn=Manager,dc=example,dc=com -Dfortress.admin.pw=secret -Dfortress.config.root=ou=Config,dc=example,dc=com



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message