[jira] [Resolved] (JAMES-2355) Startup: setenv vs setenv.sh

["Tellier Benoit (JIRA)" <se...@james.apache.org>]

     [ https://issues.apache.org/jira/browse/JAMES-2355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tellier Benoit resolved JAMES-2355.
-----------------------------------
    Resolution: Fixed

https://github.com/apache/james-project/pull/108 solved the issue

> Startup:  setenv vs setenv.sh
> -----------------------------
>
>                 Key: JAMES-2355
>                 URL: https://issues.apache.org/jira/browse/JAMES-2355
>             Project: James Server
>          Issue Type: Bug
>    Affects Versions: 3.0.0, master, 3.0.1
>            Reporter: phansson
>            Priority: Major
>
> On Unix/Linux using binary distribution of Apache James 3.0.1:
>  
> The shell script {{james}} will look for {{setenv}} and source it if it exists. However, on the disk, the file is named {{setenv.sh}}. This means that the setenv file has no effect in an out-of-the-box install of James.
> Current workaround is to rename {{setenv.sh}} to {{setenv}} during first time setup.
> If the bundled {{setenv.sh}} file is only meant as a template (is it?), then it should be named appropriately and it should have instructions in it for how to make it take effect.
> On another note: The idea of having a setenv file which can affect startup is a good one. Indeed Tomcat does the same. However, I've never understood why this file is found in the /bin directory and not the /conf directory. This is indeed configuration. When you update to a newer version of James you have to remember to bring this file with you. Well, well, this 'deficiency' is shared with Tomcat, so I guess it has become kind of accepted. Except by me. :)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org