[jbosstools-issues] [JBoss JIRA] (JBIDE-16170) Latest HTML5 archetype doesn't show unavailable maven repo in wizard

Fred Bricon (JIRA) jira-events at lists.jboss.org
Tue Dec 3 20:04:06 EST 2013


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

Fred Bricon commented on JBIDE-16170:
-------------------------------------

Please review https://github.com/jbosstools/jbosstools-central/pull/190

if https://github.com/jboss-jdf/jdf-stack/pull/30 has not be applied, then start JBT/JBDS with -Dorg.jboss.tools.stacks.url_stacks=https://raw.github.com/fbricon/jdf-stack/patch-2/stacks.yaml in *.ini to test
                
> Latest HTML5 archetype doesn't show unavailable maven repo in wizard
> --------------------------------------------------------------------
>
>                 Key: JBIDE-16170
>                 URL: https://issues.jboss.org/browse/JBIDE-16170
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: central, project-examples
>    Affects Versions: 4.1.1.CR1
>            Reporter: Fred Bricon
>            Assignee: Fred Bricon
>            Priority: Blocker
>             Fix For: 4.1.1.Final
>
>
> The latest HTML 5 archetype now depends on WFK dependencies by default (there used to be a community/enterprise distinction before, not anymore)
> Problem is, the missing enterprise dependencies warning (JBIDE-14909) only shows up if an enterprise runtime is selected. In this case, it should also be displayed for all runtimes.
> So all JBoss Central users not selecting an enterprise runtime will create a broken project if the maven redhat repo is missing from their settings.xml. Which is bad :/

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


More information about the jbosstools-issues mailing list