[jbosstools-issues] [JBoss JIRA] (JBIDE-12365) Enable JBoss Tools Knowledge Base support for dependencies

[Fred Bricon (JIRA)]

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

Fred Bricon updated JBIDE-12365:
--------------------------------

    Fix Version/s: 4.0.0.M2
                       (was: 4.0.0.M1)


This is not that trivial.

We currently have no dependency to org.jboss.tools.jst.web on the Maven plugins. Moreover Maven/JSF is gonna move to eclipse.org as part of m2e-wtp (along with the JPA and JAX-RS connectors), So I really don't want to add that dependency now.

Anyway, can you give me a concrete example why the KB nature should be added to non JSF/CDI/Seam dependencies? The KB builder always seemed really slow to me so that's really something I wouldn't want to add to a project, if not necessary.


                
> Enable JBoss Tools Knowledge Base support for dependencies
> ----------------------------------------------------------
>
>                 Key: JBIDE-12365
>                 URL: https://issues.jboss.org/browse/JBIDE-12365
>             Project: Tools (JBoss Tools)
>          Issue Type: Feature Request
>          Components: maven
>    Affects Versions: 3.3.0.Final
>            Reporter: Alexey Kazakov
>            Assignee: Fred Bricon
>             Fix For: 4.0.0.M2
>
>
> Suppose we have two maven projects.
> One is CDI/Seam/JSF (any kind of project that requires KB builder/nature).
> The other is a plain java project.
> The first one includes the second one as a dependency.
> When our maven intergration plugins enables CDI/Seam/JSF they also should enable KB support for all the dependencies (direct or indirect ones).
> You can enable KB via org.jboss.tools.jst.web.kb.WebKbPlugin.enableKB(IProject project, IProgressMonitor monitor)
> So CDI/Seam/JSF (KB included) should be enabled for the first project.
> And KB should be enabled for the second one.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira