[jbosstools-issues] [JBoss JIRA] (JBIDE-14917) Warings in console, when stacks.yaml isn't reachable

[Fred Bricon (JIRA)]

     [ https://issues.jboss.org/browse/JBIDE-14917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Fred Bricon reassigned JBIDE-14917:
-----------------------------------

    Assignee: Rob Stryker  (was: Fred Bricon)


We should provide our own [StacksMessages|https://github.com/jboss-jdf/jdf-stacks-client/blob/master/src/main/java/org/jboss/jdf/stacks/client/messages/StacksMessages.java] implementation that would redirect logging to Eclipse's standard logging fmwk, when instantiating [StacksClient|https://github.com/jboss-jdf/jdf-stacks-client/blob/master/src/main/java/org/jboss/jdf/stacks/client/StacksClient.java#L63]
                
> Warings in console, when stacks.yaml isn't reachable
> ----------------------------------------------------
>
>                 Key: JBIDE-14917
>                 URL: https://issues.jboss.org/browse/JBIDE-14917
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: Central, project-examples
>    Affects Versions: 4.1.0.Beta2
>            Reporter: Radim Hopp
>            Assignee: Rob Stryker
>            Priority: Minor
>             Fix For: 4.1.x, 4.2.x
>
>
> {noformat}
> $ eclipse/eclipse-jbt-4.1.0.Beta2/eclipse -data workspace-test
> Jun 18, 2013 2:03:47 PM org.jboss.jdf.stacks.client.messages.JBossLoggingMessages showWarnMessage
> WARN: It was not possible to contact the repository at https://raw.github.com/jboss-jdf/jdf-stack/1.0.0.Final/stacks.yaml . Cause raw.github.com
> Jun 18, 2013 2:03:47 PM org.jboss.jdf.stacks.client.messages.JBossLoggingMessages showWarnMessage
> WARN: Falling back to cache!
> Jun 18, 2013 2:03:47 PM org.jboss.jdf.stacks.client.messages.JBossLoggingMessages showWarnMessage
> WARN: Cache empty. Falling back to embed file
> {noformat}
> Is it possible to log these warnings to Error Log?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira