[JBoss JIRA] (JBTIS-504) publish Alpha2 IS discovery jars into JBT/JBDS CR1(a) discovery site when available
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBTIS-504?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBTIS-504:
----------------------------------
{quote}
If I just eliminate all of the certificationId="org.jboss.tools.discovery.certification.notavailable" connectors then the user will have no idea that "Fuse Tooling" is available under early access.{quote}
Correct. No notavailable connector == no adver'teasing.
You can certainly say {quote}"Select the 'Enable Early Access' check box for an early access installation. Also available in Red Hat JBoss Developer Studio 8.x"{quote}
But a less verbose way might be:
"Enable Early Access to install this. Also available in Red Hat JBoss Developer Studio 8."
> publish Alpha2 IS discovery jars into JBT/JBDS CR1(a) discovery site when available
> -----------------------------------------------------------------------------------
>
> Key: JBTIS-504
> URL: https://issues.jboss.org/browse/JBTIS-504
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: distribution
> Affects Versions: 4.3.0.Alpha2
> Reporter: Nick Boldt
> Assignee: Paul Leacu
> Fix For: 4.3.0.Alpha2
>
> Attachments: is-in-dev.png, is-in-dev_JBDS.png
>
>
> Per the details in JBIDE-20100, when IS is ready to go, it needs to provide the discovery jars into the JBT/JBDS CR1 site so that the "not available" connectors will be seen in JBT/JBDS.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 6 months
[JBoss JIRA] (JBTIS-504) publish Alpha2 IS discovery jars into JBT/JBDS CR1(a) discovery site when available
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBTIS-504?page=com.atlassian.jira.plugin.... ]
Nick Boldt edited comment on JBTIS-504 at 10/5/15 11:59 AM:
------------------------------------------------------------
{quote}If I just eliminate all of the certificationId="org.jboss.tools.discovery.certification.notavailable" connectors then the user will have no idea that "Fuse Tooling" is available under early access.{quote}
Correct. No notavailable connector == no adver'teasing.
You can certainly say {quote}"Select the 'Enable Early Access' check box for an early access installation. Also available in Red Hat JBoss Developer Studio 8.x"{quote}
But a less verbose way might be:
"Enable Early Access to install this. Also available in Red Hat JBoss Developer Studio 8."
was (Author: nickboldt):
{quote}
If I just eliminate all of the certificationId="org.jboss.tools.discovery.certification.notavailable" connectors then the user will have no idea that "Fuse Tooling" is available under early access.{quote}
Correct. No notavailable connector == no adver'teasing.
You can certainly say {quote}"Select the 'Enable Early Access' check box for an early access installation. Also available in Red Hat JBoss Developer Studio 8.x"{quote}
But a less verbose way might be:
"Enable Early Access to install this. Also available in Red Hat JBoss Developer Studio 8."
> publish Alpha2 IS discovery jars into JBT/JBDS CR1(a) discovery site when available
> -----------------------------------------------------------------------------------
>
> Key: JBTIS-504
> URL: https://issues.jboss.org/browse/JBTIS-504
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: distribution
> Affects Versions: 4.3.0.Alpha2
> Reporter: Nick Boldt
> Assignee: Paul Leacu
> Fix For: 4.3.0.Alpha2
>
> Attachments: is-in-dev.png, is-in-dev_JBDS.png
>
>
> Per the details in JBIDE-20100, when IS is ready to go, it needs to provide the discovery jars into the JBT/JBDS CR1 site so that the "not available" connectors will be seen in JBT/JBDS.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 6 months
[JBoss JIRA] (JBIDE-12365) Enable JBoss Tools Knowledge Base support for dependencies
by Martijn Dashorst (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12365?page=com.atlassian.jira.plugi... ]
Martijn Dashorst commented on JBIDE-12365:
------------------------------------------
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)
10 years, 6 months
[JBoss JIRA] (JBIDE-12365) Enable JBoss Tools Knowledge Base support for dependencies
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12365?page=com.atlassian.jira.plugi... ]
Alexey Kazakov commented on JBIDE-12365:
----------------------------------------
org.jboss.tools.jst.web.kb is the JBoss Tools Knowledge Base plugin
You can disable this validation in Project properties -> JBoss Tools Knowledge Base -> Validator for you project(s) or you can disable it for the whole workspace in Window -> Preferences -> JBoss Tools -> Web -> Knowledge Base -> Validator
Or you can access these preferences using a quick fix for the validation problem.
> 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)
10 years, 6 months
[JBoss JIRA] (JBIDE-12365) Enable JBoss Tools Knowledge Base support for dependencies
by Martijn Dashorst (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12365?page=com.atlassian.jira.plugi... ]
Martijn Dashorst commented on JBIDE-12365:
------------------------------------------
My workspace is now flooded with warnings:
"JBoss Tools Knowledge Base problem: Nature is not installed on required Java project «project»"
As we strive for a zero-warning policy at our company, and this warning is the top in the warning view, how can I disable this check?
And I don't have any plugin resembling the "JBoss Tools Knowledge Base" installed.
> 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)
10 years, 6 months