[JBoss JIRA] (JBIDE-18524) Avoid using multiple IDocuments when opening an FTL file
by Peter Palaga (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18524?page=com.atlassian.jira.plugi... ]
Peter Palaga commented on JBIDE-18524:
--------------------------------------
Fix sent https://github.com/jbosstools/jbosstools-freemarker/pull/24
> Avoid using multiple IDocuments when opening an FTL file
> --------------------------------------------------------
>
> Key: JBIDE-18524
> URL: https://issues.jboss.org/browse/JBIDE-18524
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: freemarker
> Affects Versions: 4.2.0.CR2
> Reporter: Peter Palaga
> Assignee: Peter Palaga
> Priority: Minor
>
> This is a matter of effectiveness and getting in line with what is usual in other plugins:
> (1) In the FreeMarker {{Editor}} constructor, we currently create a per-{{Editor}} instance of {{DocumentProvider}}. {{Editor}}s should rather use a single {{DocumentProvider}} hosted in {{Plugin}}. This is how it is done in many other editors, see e.g. {{AntEditor.initializeEditor()}}, {{PropertiesFileEditor.initializeEditor()}}, {{ClassFileEditor()}}, etc.
> (2) {{Editor.init(IEditorSite, IEditorInput)}} is called twice from {{FreemarkerMultiPageEditor}} when opening an FTL file. This causes e.g. partitioning twice. Steps to verify: put a breakpoint on {{AbstractTextEditor.init(IEditorSite, IEditorInput)}} and open an FTL file. NOT OK: the breakpoint gets hit twice, ECPECTED: the breakpoint should be visited once only.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months
[JBoss JIRA] (JBIDE-18036) Decouple FTL target language syntax coloring
by Peter Palaga (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18036?page=com.atlassian.jira.plugi... ]
Peter Palaga commented on JBIDE-18036:
--------------------------------------
A new fix sent: https://github.com/jbosstools/jbosstools-freemarker/pull/24
> Decouple FTL target language syntax coloring
> --------------------------------------------
>
> Key: JBIDE-18036
> URL: https://issues.jboss.org/browse/JBIDE-18036
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: freemarker
> Reporter: Peter Palaga
> Assignee: Peter Palaga
> Fix For: 4.2.1.Final
>
> Attachments: coloring-issues.png
>
>
> This issue covers the requirement formulated in point (1) of my earlier comment in [JBIDE-11287|https://issues.jboss.org/browse/JBIDE-11287?focusedCommentId=...].
> The present Freemarker plugin has a hard-coded XML/HTML syntax coloring. Although XML/HTML may well be the most common target language of an FTL template, it is clearly not the only possible target language. One can target virtually any language or even plaintext, where {{<}} and {{<!--}} may have completely different meanings or no meanigs at all. Hardcoding XML highlighting for every file opened by the FTL editor is thus simply incorrect.
> Let's define the present task as follows:
> (1) Decouple the syntax coloring of the target language of a FTL template by introducing an interface (call it {{TargetLanguageSupport}}) that will provide the general functionality needed for coloring of target languages.
> (2) At least two implementations of {{TargetLanguageSupport}} should be added:
> (2.1) XML/HTML and
> (2.2) plain text.
> (3) Some kind of target-language detection should be added, e.g. based on file extensions, making XML/HTML syntax coloring active for files ending with {{\*.xml.ftl}}, {{\*.xhtml.ftl}}, {{\*.html.ftl}} and {{\*.htm.ftl}}.
> (3.1) There should be a workspace-wide preference that will say for which file extensions will e.g. XML/HTML syntax coloring be active.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months
[JBoss JIRA] (JBIDE-17956) Add progress bar to Add Arquillian profiles dialog
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17956?page=com.atlassian.jira.plugi... ]
Snjezana Peco updated JBIDE-17956:
----------------------------------
Fix Version/s: 4.2.0.CR2
(was: 4.3.0.Alpha1)
> Add progress bar to Add Arquillian profiles dialog
> --------------------------------------------------
>
> Key: JBIDE-17956
> URL: https://issues.jboss.org/browse/JBIDE-17956
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: testing-tools
> Affects Versions: 4.2.0.Beta3
> Reporter: Lucia Jelinkova
> Assignee: Snjezana Peco
> Priority: Minor
> Labels: respin-a
> Fix For: 4.2.0.CR2
>
> Attachments: progressbar-1.ogv, progressbar-2.ogv
>
>
> In Add Arquillian profiles dialog, when I select all profiles and press OK, it takes quite a long time to finish the task. There should be a progress bar in this case.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months
[JBoss JIRA] (JBIDE-18265) NullPointerException in ArquillianBuilder when creating test class with the name Test
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18265?page=com.atlassian.jira.plugi... ]
Snjezana Peco resolved JBIDE-18265.
-----------------------------------
Resolution: Done
> NullPointerException in ArquillianBuilder when creating test class with the name Test
> -------------------------------------------------------------------------------------
>
> Key: JBIDE-18265
> URL: https://issues.jboss.org/browse/JBIDE-18265
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: testing-tools
> Affects Versions: 4.2.0.CR1
> Reporter: Lucia Jelinkova
> Assignee: Snjezana Peco
> Priority: Critical
> Labels: respin-a
> Fix For: 4.2.0.CR2
>
>
> When I try to create an Arquillan test class with the name Test, it is created, however, the Arquillian builder fails with NP.
> {code}
> java.lang.NullPointerException
> at org.eclipse.jdt.core.dom.MethodBinding.filterTypeAnnotations(MethodBinding.java:205)
> at org.eclipse.jdt.core.dom.MethodBinding.getAnnotations(MethodBinding.java:104)
> at org.jboss.tools.arquillian.core.internal.util.ArquillianSearchEngine.isDeploymentMethod(ArquillianSearchEngine.java:862)
> at org.jboss.tools.arquillian.core.internal.util.ArquillianSearchEngine.getDeploymentMethods(ArquillianSearchEngine.java:849)
> at org.jboss.tools.arquillian.core.internal.util.ArquillianSearchEngine.hasDeploymentMethod(ArquillianSearchEngine.java:599)
> at org.jboss.tools.arquillian.core.internal.builder.ArquillianBuilder.build(ArquillianBuilder.java:255)
> at org.jboss.tools.arquillian.core.internal.builder.ArquillianBuilder.buildDelta(ArquillianBuilder.java:210)
> at org.jboss.tools.arquillian.core.internal.builder.ArquillianBuilder.build(ArquillianBuilder.java:109)
> at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:734)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:206)
> at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:246)
> at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:299)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:302)
> at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:358)
> at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:381)
> at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:143)
> at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:241)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
> {code}
> This is because the test method is generated with the @Test annotation without fully qualified name.
> {code}
> @Test
> public void test() {
> fail("Not yet implemented");
> }
> {code}
> In JUnit, when I tried to create test class with the name Test, the @Test annotation was generated with fullly qualified name
> {code}
> @Test
> @org.junit.Test
> public void test() {
> fail("Not yet implemented");
> }
> {code}
> However, when I checked that I want do generate tearDown method, JUnit created the annotation withou fully qualified name too.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months
[JBoss JIRA] (JBIDE-18265) NullPointerException in ArquillianBuilder when creating test class with the name Test
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18265?page=com.atlassian.jira.plugi... ]
Snjezana Peco updated JBIDE-18265:
----------------------------------
Fix Version/s: 4.2.0.CR2
(was: 4.3.0.Alpha1)
> NullPointerException in ArquillianBuilder when creating test class with the name Test
> -------------------------------------------------------------------------------------
>
> Key: JBIDE-18265
> URL: https://issues.jboss.org/browse/JBIDE-18265
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: testing-tools
> Affects Versions: 4.2.0.CR1
> Reporter: Lucia Jelinkova
> Assignee: Snjezana Peco
> Priority: Critical
> Labels: respin-a
> Fix For: 4.2.0.CR2
>
>
> When I try to create an Arquillan test class with the name Test, it is created, however, the Arquillian builder fails with NP.
> {code}
> java.lang.NullPointerException
> at org.eclipse.jdt.core.dom.MethodBinding.filterTypeAnnotations(MethodBinding.java:205)
> at org.eclipse.jdt.core.dom.MethodBinding.getAnnotations(MethodBinding.java:104)
> at org.jboss.tools.arquillian.core.internal.util.ArquillianSearchEngine.isDeploymentMethod(ArquillianSearchEngine.java:862)
> at org.jboss.tools.arquillian.core.internal.util.ArquillianSearchEngine.getDeploymentMethods(ArquillianSearchEngine.java:849)
> at org.jboss.tools.arquillian.core.internal.util.ArquillianSearchEngine.hasDeploymentMethod(ArquillianSearchEngine.java:599)
> at org.jboss.tools.arquillian.core.internal.builder.ArquillianBuilder.build(ArquillianBuilder.java:255)
> at org.jboss.tools.arquillian.core.internal.builder.ArquillianBuilder.buildDelta(ArquillianBuilder.java:210)
> at org.jboss.tools.arquillian.core.internal.builder.ArquillianBuilder.build(ArquillianBuilder.java:109)
> at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:734)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:206)
> at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:246)
> at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:299)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:302)
> at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:358)
> at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:381)
> at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:143)
> at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:241)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
> {code}
> This is because the test method is generated with the @Test annotation without fully qualified name.
> {code}
> @Test
> public void test() {
> fail("Not yet implemented");
> }
> {code}
> In JUnit, when I tried to create test class with the name Test, the @Test annotation was generated with fullly qualified name
> {code}
> @Test
> @org.junit.Test
> public void test() {
> fail("Not yet implemented");
> }
> {code}
> However, when I checked that I want do generate tearDown method, JUnit created the annotation withou fully qualified name too.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months
[JBoss JIRA] (JBIDE-18265) NullPointerException in ArquillianBuilder when creating test class with the name Test
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18265?page=com.atlassian.jira.plugi... ]
Snjezana Peco updated JBIDE-18265:
----------------------------------
Labels: respin-a (was: )
> NullPointerException in ArquillianBuilder when creating test class with the name Test
> -------------------------------------------------------------------------------------
>
> Key: JBIDE-18265
> URL: https://issues.jboss.org/browse/JBIDE-18265
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: testing-tools
> Affects Versions: 4.2.0.CR1
> Reporter: Lucia Jelinkova
> Assignee: Snjezana Peco
> Priority: Critical
> Labels: respin-a
> Fix For: 4.2.0.CR2
>
>
> When I try to create an Arquillan test class with the name Test, it is created, however, the Arquillian builder fails with NP.
> {code}
> java.lang.NullPointerException
> at org.eclipse.jdt.core.dom.MethodBinding.filterTypeAnnotations(MethodBinding.java:205)
> at org.eclipse.jdt.core.dom.MethodBinding.getAnnotations(MethodBinding.java:104)
> at org.jboss.tools.arquillian.core.internal.util.ArquillianSearchEngine.isDeploymentMethod(ArquillianSearchEngine.java:862)
> at org.jboss.tools.arquillian.core.internal.util.ArquillianSearchEngine.getDeploymentMethods(ArquillianSearchEngine.java:849)
> at org.jboss.tools.arquillian.core.internal.util.ArquillianSearchEngine.hasDeploymentMethod(ArquillianSearchEngine.java:599)
> at org.jboss.tools.arquillian.core.internal.builder.ArquillianBuilder.build(ArquillianBuilder.java:255)
> at org.jboss.tools.arquillian.core.internal.builder.ArquillianBuilder.buildDelta(ArquillianBuilder.java:210)
> at org.jboss.tools.arquillian.core.internal.builder.ArquillianBuilder.build(ArquillianBuilder.java:109)
> at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:734)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:206)
> at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:246)
> at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:299)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:302)
> at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:358)
> at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:381)
> at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:143)
> at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:241)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
> {code}
> This is because the test method is generated with the @Test annotation without fully qualified name.
> {code}
> @Test
> public void test() {
> fail("Not yet implemented");
> }
> {code}
> In JUnit, when I tried to create test class with the name Test, the @Test annotation was generated with fullly qualified name
> {code}
> @Test
> @org.junit.Test
> public void test() {
> fail("Not yet implemented");
> }
> {code}
> However, when I checked that I want do generate tearDown method, JUnit created the annotation withou fully qualified name too.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months
[JBoss JIRA] (JBDS-2730) Faster download of updatesite content via akamai
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-2730?page=com.atlassian.jira.plugin.... ]
Nick Boldt edited comment on JBDS-2730 at 10/7/14 12:58 PM:
------------------------------------------------------------
Test script for performing performance tests of JBDS 8 Beta3 -> CR1b updates:
[^JBDS2730-test-script-JBDS-install-then-update-from-Akamai.txt]
Note: to use the Akamai staging server instead of the current site, use dig or nslookup to get the correct local IP:
{code}dig devstudio.redhat.com.edgekey-staging.net{code}
Then add the result to your /etc/hosts file, eg.,:
{code}23.35.182.29 devstudio.redhat.com devstudio.jboss.com{code}
was (Author: nickboldt):
Test script for performing performance tests of JBDS 8 Beta3 -> CR1b updates:
[^JBDS2730-test-script-JBDS-install-then-update-from-Akamai.txt]
> Faster download of updatesite content via akamai
> ------------------------------------------------
>
> Key: JBDS-2730
> URL: https://issues.jboss.org/browse/JBDS-2730
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: requirements, updatesite
> Reporter: Burr Sutter
> Assignee: Nick Boldt
> Priority: Critical
> Labels: JBDS80_Approved_Scope
> Fix For: 8.0.0.GA
>
> Attachments: JBDS2730-test-script-JBDS-install-then-update-from-Akamai.txt
>
>
> The updatesite used by marketplace should be behind akamai for smoother/faster download.
> Investigate using akamai/download.jboss.org backed storage.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months
[JBoss JIRA] (JBIDE-18111) Arquillian warnings are not cleared properly
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18111?page=com.atlassian.jira.plugi... ]
Snjezana Peco updated JBIDE-18111:
----------------------------------
Fix Version/s: 4.2.0.CR2
(was: 4.3.0.Alpha1)
> Arquillian warnings are not cleared properly
> --------------------------------------------
>
> Key: JBIDE-18111
> URL: https://issues.jboss.org/browse/JBIDE-18111
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: testing-tools
> Affects Versions: 4.2.0.Beta3
> Reporter: Lucia Jelinkova
> Assignee: Snjezana Peco
> Labels: respin-a
> Fix For: 4.2.0.CR2
>
>
> When I create an arquillian test without test method and deployment method, I get 2 warnings - that is correct. However, when I mark class as abstract, these warnings should disappear, but they do not. I need to clean the project (causing to rebuild the project) to make those warnings disappear.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months