[ 
http://issues.ops4j.org/browse/PAXLOGGING-65?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13215#action_13215
 ] 

Niclas Hedhman commented on PAXLOGGING-65:
------------------------------------------

IIUIC, this is an equivalent of PAXLOGGING-58.

See my argument over there, why I maintain that this is both a bad idea and 
fixing the wrong problem.

> JCL LogFactory.FACTORY_DEFAULT points to non-existent LogFactory 
> implementation
> -------------------------------------------------------------------------------
>
>                 Key: PAXLOGGING-65
>                 URL: http://issues.ops4j.org/browse/PAXLOGGING-65
>             Project: Pax Logging
>          Issue Type: Bug
>          Components: API
>    Affects Versions: 1.4
>            Reporter: Jarek Gawor
>            Assignee: Niclas Hedhman
>         Attachments: PAXLOGGING-65.patch
>
>
> The LogFactory.FACTORY_DEFAULT constant exported via JCL API points to 
> non-existent LogFactory implementation. I ran into a library that tries to 
> instantiate the LogFactory implementation using that constant. And that 
> obviously fails as there is no such class present in the bundle.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://issues.ops4j.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

_______________________________________________
general mailing list
general@lists.ops4j.org
http://lists.ops4j.org/mailman/listinfo/general

Reply via email to