[jbosstools-issues] [JBoss JIRA] (JBIDE-16966) Warning isn't shown if bom file is in local repository

[Fred Bricon (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-16966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12958040#comment-12958040 ] 

Fred Bricon commented on JBIDE-16966:
-------------------------------------

this is expected, kinda. Once m2e/Maven has resolved a dependency, it won't try again for the next 24hrs. It's been the default behavior for years now.

We can probably try override that behavior though.
                
> Warning isn't shown if bom file is in local repository
> ------------------------------------------------------
>
>                 Key: JBIDE-16966
>                 URL: https://issues.jboss.org/browse/JBIDE-16966
>             Project: Tools (JBoss Tools)
>          Issue Type: Enhancement
>          Components: central
>    Affects Versions: 4.2.0.Beta1
>            Reporter: Rastislav Wagner
>            Assignee: Fred Bricon
>            Priority: Minor
>             Fix For: 4.2.0.Beta2
>
>
> When I try to import some central example (HTML5, JavaEE) no warning is displayed if jboss-javaee-6.0-bom is in my local repository. This is causing issues when I had enterprise repo in my settings.xml in the past but right now its not there (but bom was downloaded into my local repo).
>  
> I think that in past we didn't check local repository right ? Why was this behaviour changed ? Is it because of offline mode ? In that case maybe we should check if maven is in offline mode, if not than we should check remote repositories, not local.
> Steps to reproduce:
> 1. open HTML5 wizard from central
> 2. add enterprise repo via warning
> ASSERT: warning disappears
> 3. close wizard
> 4. remove enterprise repo from settings.xml
> 5. open HTML5 wizard from central
> FAIL: no warning is diplayed even that enterprise repo is missing (only local repo contains javaee-6.0-bom)

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