[jbosstools-issues] [JBoss JIRA] (JBIDE-16548) debug info in console when checking dependencies of archetype

[Radim Hopp (JIRA)]

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

Radim Hopp updated JBIDE-16548:
-------------------------------

    Fix Version/s: 4.2.0.Beta1
                       (was: 4.1.1.Beta1)

    
> debug info in console when checking dependencies of archetype
> -------------------------------------------------------------
>
>                 Key: JBIDE-16548
>                 URL: https://issues.jboss.org/browse/JBIDE-16548
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: central, project-examples
>    Affects Versions: 4.2.0.Alpha2
>         Environment: devstudio 8.0.0.Alpha2a
>            Reporter: Radim Hopp
>            Priority: Minor
>             Fix For: 4.2.0.Beta1
>
>
> When is  NewProjectExamplesStacksRequirementsPage  of New Project Example Wizard checking for dependencies (EAP runtime was selected), in shell console [info] debug information is displayed:
> {noformat}
> rhopp at localhost ~> eclipse/jbdevstudio-8.0.0.Alpha2a/jbdevstudio -data workspace-tests
> SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
> SLF4J: Defaulting to no-operation (NOP) logger implementation
> SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
> [INFO] artifact org.jboss.spec:jboss-javaee-web-6.0: checking for updates from central
> [INFO] artifact org.jboss.spec:jboss-javaee-web-6.0: checking for updates from jboss-public-repository-group-brno
> [INFO] artifact org.jboss.spec:jboss-javaee-web-6.0: checking for updates from redhat-techpreview-all-repository-brno
> [INFO] artifact org.jboss.spec:jboss-javaee-web-6.0: checking for updates from maven-central-brno
> {noformat}
> \[info\] is dipsplayed for each maven repository defined in my maven settings.xml

--
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