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

[Martijn Dashorst (JIRA)]

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

Martijn Dashorst edited comment on JBIDE-12365 at 10/5/15 12:05 PM:
--------------------------------------------------------------------

These are disabled already, yet the warnings are still generated in my workspace. Removing the warnings from the problems view, and rebuilding my workspace resurfaces the warnings. There is no way to remove them and keep these warnings away.

If you want the exact setup, you can use a clean 4.5.1 mars "Java developers" (not Java EE) download, and import these plugins and features:

https://github.com/topicusonderwijs/topicusonderwijs/blob/master/eclipse-mars.p2f

We want to have a minimal setup so we try to install the bare minimum of plugins. Therefore we remove all handy tool integrations such as CDI and JPA validators. As we also don't use JSF, we really don't have a use case for JSF tools. etc. 

As far as I know, I can't remove the JBoss Standard Tools (which generates these warnings) from the setup because the other tools depend on it.


was (Author: dashorst):
These are disabled already, yet the warnings are still generated in my workspace. Removing the warnings from the problems view, and rebuilding my workspace resurfaces the warnings. There is no way to remove them and keep these warnings away.

> 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: Alexey Kazakov
>             Fix For: LATER
>
>
> 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 was sent by Atlassian JIRA
(v6.4.11#64026)