You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by "Michael Concini (JIRA)" <de...@myfaces.apache.org> on 2010/02/20 01:40:27 UTC
[jira] Resolved: (MYFACES-2567) Log indicates Tomahawk starting
even if Tomahawk is not on the classpath
[ https://issues.apache.org/jira/browse/MYFACES-2567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Concini resolved MYFACES-2567.
--------------------------------------
Resolution: Fixed
Fix Version/s: 2.0.0-beta-3
> Log indicates Tomahawk starting even if Tomahawk is not on the classpath
> ------------------------------------------------------------------------
>
> Key: MYFACES-2567
> URL: https://issues.apache.org/jira/browse/MYFACES-2567
> Project: MyFaces Core
> Issue Type: Bug
> Components: JSR-314
> Affects Versions: 2.0.0-beta-2
> Reporter: Michael Concini
> Assignee: Michael Concini
> Priority: Trivial
> Fix For: 2.0.0-beta-3
>
>
> This is an extremely trivial issue, but can be confusing for a user, especially someone new to MyFaces, who doesn't have Tomahawk installed.
> We shouldn't be outputting the message the Tomahawk is starting on either MyFaces or the Sun RI respectively if Tomahawk itself is not actually available.
> This technically affects prior releases as well, but I'm not sure we want to back port changes in logging after this many releases of the 1.x streams so I don't plan on changing them at this point.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.