You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jetspeed-dev@portals.apache.org by "Randy Watler (JIRA)" <je...@portals.apache.org> on 2009/09/25 21:03:17 UTC

[jira] Updated: (JS2-1021) logging in J2 installer using webapp APA logging

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

Randy Watler updated JS2-1021:
------------------------------

    Fix Version/s:     (was: 2.2.1)
                   2.2.2

> logging in J2 installer using webapp APA logging
> ------------------------------------------------
>
>                 Key: JS2-1021
>                 URL: https://issues.apache.org/jira/browse/JS2-1021
>             Project: Jetspeed 2
>          Issue Type: Bug
>          Components: Installer
>    Affects Versions: 2.2.0
>         Environment: installer ant build
>            Reporter: Randy Watler
>            Assignee: Randy Watler
>            Priority: Minor
>             Fix For: 2.2.2
>
>
> SVN commit 777555 - jetspeed-installer/etc/database/build.xml
> Added definition of org.apache.portals.logdir to get through release, but this should not be required. Here is the related email thread:
> -----------------------------------------------------------------------------------------------------------------------------------------------------
> Randy Watler wrote:
> > Ate,
> >
> > Why does the serializer need org.apache.portals.logdir?
> >
> > That seems wrong to me. My intention was that only webapps needed that. Obviously, it is needed somehow now... how is the serializer getting webapp applications log4j.properties files?
> Because the serializer (and page serializer for db psml) are executed in the context/installation path of the jetspeed portal installation itself.
> We can also provide a overriding log4j configuration but this seemed more quick and convenient, which was what I needed.
> >
> > Randy 

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


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