You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ofbiz.apache.org by "Michael Imhof (JIRA)" <ji...@apache.org> on 2007/05/15 14:52:16 UTC

[jira] Created: (OFBIZ-987) Log configuration in multiple files

Log configuration in multiple files
-----------------------------------

                 Key: OFBIZ-987
                 URL: https://issues.apache.org/jira/browse/OFBIZ-987
             Project: OFBiz (The Open for Business Project)
          Issue Type: Improvement
         Environment: SUSE Linux 10.1 & MySql 5
            Reporter: Michael Imhof
         Attachments: log4jPatch.txt

To change a log file location I had to change the following files:
debug.properties
start.properties (or install.properties, test.properties,...)
ofbiz-containers.xml

And I had to be sure, that the debug.properties location is the same
as the start.properites location!!

Patch feature
==========
The patch is decreasing the configuration to one file. The start.properties (or install.properties, test.properties,.... Depends on wich
functionality you're starting).
In this file you can define: 
  ofbiz.log.dir=logs
  ofbiz.log.file=ofbiz.log

Even catalina (access.log) is using the same location if not defined otherwise in the ofbiz-containers.xml.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (OFBIZ-987) Log configuration in multiple files

Posted by "Jacopo Cappellato (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/OFBIZ-987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jacopo Cappellato updated OFBIZ-987:
------------------------------------

    Component/s: framework
       Priority: Minor  (was: Major)

> Log configuration in multiple files
> -----------------------------------
>
>                 Key: OFBIZ-987
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-987
>             Project: OFBiz (The Open for Business Project)
>          Issue Type: Improvement
>          Components: framework
>         Environment: SUSE Linux 10.1 & MySql 5
>            Reporter: Michael Imhof
>            Priority: Minor
>         Attachments: log4jPatch.txt
>
>
> To change a log file location I had to change the following files:
> debug.properties
> start.properties (or install.properties, test.properties,...)
> ofbiz-containers.xml
> And I had to be sure, that the debug.properties location is the same
> as the start.properites location!!
> Patch feature
> ==========
> The patch is decreasing the configuration to one file. The start.properties (or install.properties, test.properties,.... Depends on wich
> functionality you're starting).
> In this file you can define: 
>   ofbiz.log.dir=logs
>   ofbiz.log.file=ofbiz.log
> Even catalina (access.log) is using the same location if not defined otherwise in the ofbiz-containers.xml.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (OFBIZ-987) Log configuration in multiple files

Posted by "Michael Imhof (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/OFBIZ-987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Imhof updated OFBIZ-987:
--------------------------------

    Attachment: log4jPatch.txt

> Log configuration in multiple files
> -----------------------------------
>
>                 Key: OFBIZ-987
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-987
>             Project: OFBiz (The Open for Business Project)
>          Issue Type: Improvement
>         Environment: SUSE Linux 10.1 & MySql 5
>            Reporter: Michael Imhof
>         Attachments: log4jPatch.txt
>
>
> To change a log file location I had to change the following files:
> debug.properties
> start.properties (or install.properties, test.properties,...)
> ofbiz-containers.xml
> And I had to be sure, that the debug.properties location is the same
> as the start.properites location!!
> Patch feature
> ==========
> The patch is decreasing the configuration to one file. The start.properties (or install.properties, test.properties,.... Depends on wich
> functionality you're starting).
> In this file you can define: 
>   ofbiz.log.dir=logs
>   ofbiz.log.file=ofbiz.log
> Even catalina (access.log) is using the same location if not defined otherwise in the ofbiz-containers.xml.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (OFBIZ-987) Log configuration in multiple files

Posted by "Jacques Le Roux (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/OFBIZ-987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12512630 ] 

Jacques Le Roux commented on OFBIZ-987:
---------------------------------------

Michael,

Why in debug.properties do you remove other lines than log4j.appender.file.File=framework/logs/ofbiz.log in this patch ?

Quickly some remarks, please, don' t  :
. use tabs in your patches
. put comments like : // 15.05.07 Start change by Immi or  //  End Change by nowhow DABR

And last but no least, please read carefully : http://docs.ofbiz.org/display/OFBADMIN/OFBiz+Contributors+Best+Practices


> Log configuration in multiple files
> -----------------------------------
>
>                 Key: OFBIZ-987
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-987
>             Project: OFBiz
>          Issue Type: Improvement
>          Components: framework
>         Environment: SUSE Linux 10.1 & MySql 5
>            Reporter: Michael Imhof
>            Priority: Minor
>         Attachments: log4jPatch.txt
>
>
> To change a log file location I had to change the following files:
> debug.properties
> start.properties (or install.properties, test.properties,...)
> ofbiz-containers.xml
> And I had to be sure, that the debug.properties location is the same
> as the start.properites location!!
> Patch feature
> ==========
> The patch is decreasing the configuration to one file. The start.properties (or install.properties, test.properties,.... Depends on wich
> functionality you're starting).
> In this file you can define: 
>   ofbiz.log.dir=logs
>   ofbiz.log.file=ofbiz.log
> Even catalina (access.log) is using the same location if not defined otherwise in the ofbiz-containers.xml.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Assigned: (OFBIZ-987) Log configuration in multiple files

Posted by "Jacques Le Roux (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/OFBIZ-987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jacques Le Roux reassigned OFBIZ-987:
-------------------------------------

    Assignee: Jacques Le Roux

> Log configuration in multiple files
> -----------------------------------
>
>                 Key: OFBIZ-987
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-987
>             Project: OFBiz
>          Issue Type: Improvement
>          Components: framework
>         Environment: SUSE Linux 10.1 & MySql 5
>            Reporter: Michael Imhof
>            Assignee: Jacques Le Roux
>            Priority: Minor
>         Attachments: log4jPatch.txt
>
>
> To change a log file location I had to change the following files:
> debug.properties
> start.properties (or install.properties, test.properties,...)
> ofbiz-containers.xml
> And I had to be sure, that the debug.properties location is the same
> as the start.properites location!!
> Patch feature
> ==========
> The patch is decreasing the configuration to one file. The start.properties (or install.properties, test.properties,.... Depends on wich
> functionality you're starting).
> In this file you can define: 
>   ofbiz.log.dir=logs
>   ofbiz.log.file=ofbiz.log
> Even catalina (access.log) is using the same location if not defined otherwise in the ofbiz-containers.xml.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Closed: (OFBIZ-987) Log configuration in multiple files

Posted by "Michael Imhof (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/OFBIZ-987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Imhof closed OFBIZ-987.
-------------------------------

    Resolution: Cannot Reproduce

Well, patching is getting more and more complicated for us because we create company internally patches and they are based
on OfBiz version from February 2007.
That's why you have tabs, comments and changed debug.properties (I'm sorry about the debug.properties, that shouldn't be in this patch).

If somebody is really interested in this patch, I can take the time (reimplement and testing) and create a new issue with a patch on the current OfBiz version (trunk).

Michael

> Log configuration in multiple files
> -----------------------------------
>
>                 Key: OFBIZ-987
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-987
>             Project: OFBiz
>          Issue Type: Improvement
>          Components: framework
>         Environment: SUSE Linux 10.1 & MySql 5
>            Reporter: Michael Imhof
>            Assignee: Jacques Le Roux
>            Priority: Minor
>         Attachments: log4jPatch.txt
>
>
> To change a log file location I had to change the following files:
> debug.properties
> start.properties (or install.properties, test.properties,...)
> ofbiz-containers.xml
> And I had to be sure, that the debug.properties location is the same
> as the start.properites location!!
> Patch feature
> ==========
> The patch is decreasing the configuration to one file. The start.properties (or install.properties, test.properties,.... Depends on wich
> functionality you're starting).
> In this file you can define: 
>   ofbiz.log.dir=logs
>   ofbiz.log.file=ofbiz.log
> Even catalina (access.log) is using the same location if not defined otherwise in the ofbiz-containers.xml.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.