[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:
----------------------------------------
As I said you don't need to disable KB validation for every project in your worspace. Just disable it Preferences -> JBoss Tools -> Web -> Knowledge Base -> Validator and clean/rebuild your workspace. If you already have some warnings then this won't help (when you disable validation, the old warning are not removed). I have created a new issue for that bug - JBIDE-20913
As workaround you can set "Capabilities are not enabled in Java uitl module" to "Ignore" in Preferences -> JBoss Tools -> Web -> Knowledge Base -> Validator. Then clean/rebuild the workspace. It will remove the validtion warnings.
KB is not for JSF2 only. It's more general and used by JSF, Batch and some other tooling too.
JBoss Tools maven integration enables KB for Java EE maven projects automatically. You can disable this integration in Preferences -> JBoss Tools -> Maven integration.
Seam, CDI, JSF integration it's what you need to disable if you don't want JBoss Tools automatically configure the corresponding maven projects.
> 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-20913) Knowledge Base validation preference is ingnored
by Alexey Kazakov (JIRA)
Alexey Kazakov created JBIDE-20913:
--------------------------------------
Summary: Knowledge Base validation preference is ingnored
Key: JBIDE-20913
URL: https://issues.jboss.org/browse/JBIDE-20913
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: common/jst/core
Affects Versions: 4.3.0.CR2
Reporter: Alexey Kazakov
Assignee: Viacheslav Kabanovich
Fix For: 4.3.1.Final, 4.4.0.Alpha1
1. Create two java project, Project1 and Project2
2. Project1 depends on Project2
3. Enable KB support for Project1 (Proejct Properties->JBoss Tools Knowledge Base)
4. ASSERT: There is a warning on Project1 that there is no KB nature installed on required Projet2.
5. Go to Preferences->JBoss Tools->Web->Knowledge Base->Validator
6. Uncheck Enable Validation
7. Clean/rebuild Project1
8. FAILURE: The warning is still there
If you set "Capabilities are not enabled in Java uitl module" to "Ignore" then the warning disappears.
It looks like when we disable the KB validator at all then the old warning is not removed.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 6 months
[JBoss JIRA] (JBIDE-20912) LiveReload is not disabled
by Ilya Buziuk (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20912?page=com.atlassian.jira.plugi... ]
Ilya Buziuk commented on JBIDE-20912:
-------------------------------------
[~maxandersen], yeah what Vlado means is that BrowserSim settings (enable / disable LiveReload) not working in this case. LiveReload will be enabled anyways
> LiveReload is not disabled
> --------------------------
>
> Key: JBIDE-20912
> URL: https://issues.jboss.org/browse/JBIDE-20912
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: browsersim, cordovasim
> Affects Versions: 4.3.0.CR2
> Environment: JBDS 9.0.0.GA-v20151002-2235-B124, Fedora 22 KDE 64 bit, Oracle Java 1.8
> Reporter: Vlado Pakan
> Assignee: Ilya Buziuk
> Fix For: 4.3.1.Final
>
>
> 1. Import HTML 5 project from JBoss Central
> 2. Run it on server
> 3. Open Server view, expand running server, select HTML 5 project, click on context menu 'Show In' > 'Web Browser via LiveReolad Server'
> ASSERT: index.html page is opened in system web browser
> 4. Copy link with index.html from system web broweer to Browsersim
> ASSERT: LiveReload is enabled in BrowserSim context menu
> 5. Open index.html page in VPE, change content and save it
> ASSERT: Changes are rendered in BrowserSim and system web browser
> 6. Disable LiveReload in BrowserSim context menu
> 7. change content of index.html and save it
> ASSERT: Changes are rendered in system web browser
> ERROR: Changes are rendered in BrowserSim (CordovaSim)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 6 months
[JBoss JIRA] (JBIDE-20912) LiveReload is not disabled
by Vlado Pakan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20912?page=com.atlassian.jira.plugi... ]
Vlado Pakan edited comment on JBIDE-20912 at 10/5/15 12:20 PM:
---------------------------------------------------------------
When LiveReload is disabled within BrowserSim (via BrowserSim context menu) web page displayed in BrowserSim is still redisplayed after web page is updated on file system.
was (Author: vpakan):
When LiveReload is disabled within BrowserSim (via BrowserSim context menu) web page displayed in BrowserSim is still redislpayed after web page is updated on file system.
> LiveReload is not disabled
> --------------------------
>
> Key: JBIDE-20912
> URL: https://issues.jboss.org/browse/JBIDE-20912
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: browsersim, cordovasim
> Affects Versions: 4.3.0.CR2
> Environment: JBDS 9.0.0.GA-v20151002-2235-B124, Fedora 22 KDE 64 bit, Oracle Java 1.8
> Reporter: Vlado Pakan
> Assignee: Ilya Buziuk
> Fix For: 4.3.1.Final
>
>
> 1. Import HTML 5 project from JBoss Central
> 2. Run it on server
> 3. Open Server view, expand running server, select HTML 5 project, click on context menu 'Show In' > 'Web Browser via LiveReolad Server'
> ASSERT: index.html page is opened in system web browser
> 4. Copy link with index.html from system web broweer to Browsersim
> ASSERT: LiveReload is enabled in BrowserSim context menu
> 5. Open index.html page in VPE, change content and save it
> ASSERT: Changes are rendered in BrowserSim and system web browser
> 6. Disable LiveReload in BrowserSim context menu
> 7. change content of index.html and save it
> ASSERT: Changes are rendered in system web browser
> ERROR: Changes are rendered in BrowserSim (CordovaSim)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 6 months
[JBoss JIRA] (JBIDE-20912) LiveReload is not disabled
by Vlado Pakan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20912?page=com.atlassian.jira.plugi... ]
Vlado Pakan commented on JBIDE-20912:
-------------------------------------
When LiveReload is disabled within BrowserSim (via BrowserSim context menu) web page displayed in BrowserSim is still redislpayed after web page is updated on file system.
> LiveReload is not disabled
> --------------------------
>
> Key: JBIDE-20912
> URL: https://issues.jboss.org/browse/JBIDE-20912
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: browsersim, cordovasim
> Affects Versions: 4.3.0.CR2
> Environment: JBDS 9.0.0.GA-v20151002-2235-B124, Fedora 22 KDE 64 bit, Oracle Java 1.8
> Reporter: Vlado Pakan
> Assignee: Ilya Buziuk
> Fix For: 4.3.1.Final
>
>
> 1. Import HTML 5 project from JBoss Central
> 2. Run it on server
> 3. Open Server view, expand running server, select HTML 5 project, click on context menu 'Show In' > 'Web Browser via LiveReolad Server'
> ASSERT: index.html page is opened in system web browser
> 4. Copy link with index.html from system web broweer to Browsersim
> ASSERT: LiveReload is enabled in BrowserSim context menu
> 5. Open index.html page in VPE, change content and save it
> ASSERT: Changes are rendered in BrowserSim and system web browser
> 6. Disable LiveReload in BrowserSim context menu
> 7. change content of index.html and save it
> ASSERT: Changes are rendered in system web browser
> ERROR: Changes are rendered in BrowserSim (CordovaSim)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 6 months
[JBoss JIRA] (JBIDE-20912) LiveReload is not disabled
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20912?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-20912:
---------------------------------------------
im not following what is the error is here ? sounds like it works as expected ? (that when you load a page with livereload.js injected then livereload is enabled)
> LiveReload is not disabled
> --------------------------
>
> Key: JBIDE-20912
> URL: https://issues.jboss.org/browse/JBIDE-20912
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: browsersim, cordovasim
> Affects Versions: 4.3.0.CR2
> Environment: JBDS 9.0.0.GA-v20151002-2235-B124, Fedora 22 KDE 64 bit, Oracle Java 1.8
> Reporter: Vlado Pakan
> Assignee: Ilya Buziuk
> Fix For: 4.3.1.Final
>
>
> 1. Import HTML 5 project from JBoss Central
> 2. Run it on server
> 3. Open Server view, expand running server, select HTML 5 project, click on context menu 'Show In' > 'Web Browser via LiveReolad Server'
> ASSERT: index.html page is opened in system web browser
> 4. Copy link with index.html from system web broweer to Browsersim
> ASSERT: LiveReload is enabled in BrowserSim context menu
> 5. Open index.html page in VPE, change content and save it
> ASSERT: Changes are rendered in BrowserSim and system web browser
> 6. Disable LiveReload in BrowserSim context menu
> 7. change content of index.html and save it
> ASSERT: Changes are rendered in system web browser
> ERROR: Changes are rendered in BrowserSim (CordovaSim)
--
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 edited comment on JBIDE-12365 at 10/5/15 12:13 PM:
--------------------------------------------------------------------
Somehow JBoss Tools instructed itself to enable the KB settings for some projects, causing the warning to appear that those projects depend on other projects without KB.
How can I disable the KB setting for any project that I import? I hate for all developers in my company to have to go through this ordeal and have to uncheck 80 boxes individually.
-deleted text-These are disabled already-deleted text-, 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-...
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.
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-...
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.
> 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 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-...
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)
10 years, 6 months
[JBoss JIRA] (TOOLSDOC-687) Review JBDS 9 GA Release Notes
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-687?page=com.atlassian.jira.plug... ]
Martin Malina commented on TOOLSDOC-687:
----------------------------------------
2. About this Release
It includes Eclipse Mars.
- should say: Eclipse Mars.1
- FYI, Mars.1 is what would previously be called SR1
3. New Features
This release of JBoss Developer Studio includes new features to enhance and extend its functionality as detailed here: (TBD)
- remove the string "(TBD)"
4.1. Resolved Issues
The query seems wrong. If you look at 8.1 release notes:
https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Developer_Stu...
The idea is to show bugs that were logged against something older than any of the 9.0 milestones. Also, there is no 9.0.0.Final or 4.3.0.GA.
So should be like this:
{code}
(project in (JBDS) AND affectedVersion < 9.0.0.Alpha1 AND fixVersion in (9.0.0.Alpha1, 9.0.0.Alpha2, 9.0.0.Beta1, 9.0.0.Beta2, 9.0.0.CR1, 9.0.0.CR2, 9.0.0.GA) OR project in (JBIDE) AND affectedVersion < 4.3.0.Alpha1 AND fixVersion in (4.3.0.Alpha1, 4.3.0.Alpha2, 4.3.0.Beta1, 4.3.0.Beta2, 4.3.0.Final)) AND type in (Bug) AND resolution in (Done)
{code}
Otherwise it looks ok.
> Review JBDS 9 GA Release Notes
> ------------------------------
>
> Key: TOOLSDOC-687
> URL: https://issues.jboss.org/browse/TOOLSDOC-687
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Sub-task
> Components: Release Notes
> Reporter: Misha Ali
> Assignee: Martin Malina
>
> Please review here: http://docbuilder.usersys.redhat.com/23115/
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 6 months