July 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22610) generate email notifications

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22610?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-22610: ----------------------------------- Priority: Optional (was: Major) > generate email notifications > ---------------------------- > > Key: JBIDE-22610 > URL: https://issues.jboss.org/browse/JBIDE-22610 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: target-platform > Affects Versions: 4.4.0.Final > Reporter: Nick Boldt > Priority: Optional > Fix For: 4.4.x > > > TODO: generate email notifications including links to... > * jenkins job, > * diff files, and > * associated JIRA(s), plus > * instructions for how to build the TP locally. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22667) Automation of manual test case in batch integration tests, Reference check

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22667?page=com.atlassian.jira.plugi... ] Ondrej Dockal updated JBIDE-22667: ---------------------------------- Fix Version/s: 4.4.1.Final > Automation of manual test case in batch integration tests, Reference check > -------------------------------------------------------------------------- > > Key: JBIDE-22667 > URL: https://issues.jboss.org/browse/JBIDE-22667 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: qa > Affects Versions: 4.4.x > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Fix For: 4.4.1.Final > > > Based on not automated polarion test case: JBDS-5994 - Search for artifact references > which is covering this features: Check that it is possible to find references for artifacts in job.xm file. See JBIDE-19507 for more details. > Should include this test cases: > Check references for artifacts (also use custom name) > Check references for properties (also use custom name) > Check references for exceptions -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22660) Review test cases after JBIDE-22599 commit in batch tests

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22660?page=com.atlassian.jira.plugi... ] Ondrej Dockal updated JBIDE-22660: ---------------------------------- Fix Version/s: 4.4.x > Review test cases after JBIDE-22599 commit in batch tests > --------------------------------------------------------- > > Key: JBIDE-22660 > URL: https://issues.jboss.org/browse/JBIDE-22660 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: qa > Affects Versions: 4.4.1.Final > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Priority: Minor > Fix For: 4.4.x > > > In jbosstools was added functionality of validating reference attribute of decision tag in javaee-batch component. Some tests must take into account this enhancement, ie.: DesignDecisionElementTest fails. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22662) Automation of manual test case in batch integration test, renaming of artifacts

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22662?page=com.atlassian.jira.plugi... ] Ondrej Dockal updated JBIDE-22662: ---------------------------------- Fix Version/s: 4.4.x > Automation of manual test case in batch integration test, renaming of artifacts > ------------------------------------------------------------------------------- > > Key: JBIDE-22662 > URL: https://issues.jboss.org/browse/JBIDE-22662 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: qa > Affects Versions: 4.4.x > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Fix For: 4.4.x > > > Automation of manual test cases from polarion: JBDS-5058 > based on implemented features from JBIDE-19507. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21692) easy way to copy stacktrace

by Marcel Bruch (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21692?page=com.atlassian.jira.plugi... ] Marcel Bruch closed JBIDE-21692. -------------------------------- Fix Version/s: 4.4.1.Final Resolution: Done Added "Copy to clipboard" button to stack trace section. Will be available on next update. > easy way to copy stacktrace > --------------------------- > > Key: JBIDE-21692 > URL: https://issues.jboss.org/browse/JBIDE-21692 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: aeri > Reporter: Max Rydahl Andersen > Assignee: Marcel Bruch > Priority: Minor > Fix For: 4.4.1.Final > > > Would be great if there was a simple "Copy to clipboard" for the stacktrace and bundle list in aeri webui. > Right now one have to manually select the full stacktrace to get something to put into eclipse stacktrace console. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22701) ConsoleLineTracker is not needed anymore

by Daniel Dekany (JIRA)

Daniel Dekany created JBIDE-22701: ------------------------------------- Summary: ConsoleLineTracker is not needed anymore Key: JBIDE-22701 URL: https://issues.jboss.org/browse/JBIDE-22701 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: freemarker Reporter: Daniel Dekany Because we use the row/col info returned by FM for a while. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-671) Teiid smoke tests are failing on fenix

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-671?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky closed JBTIS-671. ----------------------------------- This issue was fixed by https://github.com/jbosstools/jbosstools-integration-stack-tests/pull/749 which has been already merged > Teiid smoke tests are failing on fenix > -------------------------------------- > > Key: JBTIS-671 > URL: https://issues.jboss.org/browse/JBTIS-671 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: QE, teiid > Affects Versions: 4.0.0 > Reporter: Andrej Podhradsky > Assignee: Matus Makovy > > Stacktrace > {code} > java.lang.AssertionError: null > at org.junit.Assert.fail(Assert.java:86) > at org.junit.Assert.assertTrue(Assert.java:41) > at org.junit.Assert.assertTrue(Assert.java:52) > at org.jboss.tools.teiid.ui.bot.test.ModelWizardTest.xsdDatatypeModel(ModelWizardTest.java:99) > {code} > and > Error Message > The following shells remained open [New Model Wizard] > Stacktrace > {code} > java.lang.AssertionError: The following shells remained open [New Model Wizard] > at org.junit.Assert.fail(Assert.java:88) > at org.jboss.reddeer.junit.extension.after.test.impl.CloseAllShellsExt.run(CloseAllShellsExt.java:68) > at org.jboss.reddeer.junit.extension.after.test.impl.CloseAllShellsExt.runAfterTest(CloseAllShellsExt.java:60) > at org.jboss.reddeer.junit.internal.runner.statement.RunIAfterTestExtensions.evaluate(RunIAfterTestExtensions.java:64) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325) > at org.jboss.reddeer.junit.internal.runner.RequirementsRunner.runChild(RequirementsRunner.java:165) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) > at org.jboss.reddeer.junit.internal.runner.statement.RunBefores.evaluate(RunBefores.java:69) > at org.jboss.reddeer.junit.internal.runner.statement.FulfillRequirementsStatement.evaluate(FulfillRequirementsStatement.java:35) > at org.jboss.reddeer.junit.internal.runner.statement.RunIBeforeClassExtensions.evaluate(RunIBeforeClassExtensions.java:60) > at org.jboss.reddeer.junit.internal.runner.statement.RunAfters.evaluate(RunAfters.java:58) > at org.jboss.reddeer.junit.internal.runner.statement.CleanUpRequirementStatement.evaluate(CleanUpRequirementStatement.java:34) > at org.jboss.reddeer.junit.internal.runner.statement.RunIAfterClassExtensions.evaluate(RunIAfterClassExtensions.java:48) > at org.junit.runners.ParentRunner.run(ParentRunner.java:363) > at org.jboss.reddeer.junit.internal.runner.RequirementsRunner.run(RequirementsRunner.java:146) > at org.junit.runners.Suite.runChild(Suite.java:128) > at org.junit.runners.Suite.runChild(Suite.java:27) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) > at org.junit.runners.ParentRunner.run(ParentRunner.java:363) > at org.junit.runners.Suite.runChild(Suite.java:128) > at org.junit.runners.Suite.runChild(Suite.java:27) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) > at org.junit.runners.ParentRunner.run(ParentRunner.java:363) > at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:264) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:153) > at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:124) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray2(ReflectionUtils.java:208) > at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:156) > at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:82) > at org.eclipse.tycho.surefire.osgibooter.OsgiSurefireBooter.run(OsgiSurefireBooter.java:91) > at org.eclipse.tycho.surefire.osgibooter.AbstractUITestApplication.runTests(AbstractUITestApplication.java:44) > at org.eclipse.e4.ui.internal.workbench.swt.E4Testable$1.run(E4Testable.java:73) > at java.lang.Thread.run(Thread.java:745) > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22700) Upgrade to FreeMarker 2.3.25

by Daniel Dekany (JIRA)

Daniel Dekany created JBIDE-22700: ------------------------------------- Summary: Upgrade to FreeMarker 2.3.25 Key: JBIDE-22700 URL: https://issues.jboss.org/browse/JBIDE-22700 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: freemarker Reporter: Daniel Dekany -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22693) Label for editing name of property in design view is too short. Name seems to be cut.

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22693?page=com.atlassian.jira.plugi... ] Ondrej Dockal commented on JBIDE-22693: --------------------------------------- [~scabanovich], when I open the editor, cells Name and Value are divided equally (or their width can be adjusted), that is alright. I'm sorry for misleading, the problem is in the height of the cell when you are editing it, letters are cut by the bottom border of the edit label. > Label for editing name of property in design view is too short. Name seems to be cut. > ------------------------------------------------------------------------------------- > > Key: JBIDE-22693 > URL: https://issues.jboss.org/browse/JBIDE-22693 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: xml-structured-editor > Environment: devstudio: > Version: 10.0.1.AM1 > Build id: v20160613-2041 > Fedora 24, x86_64 > Reporter: Ondrej Dockal > Assignee: Viacheslav Kabanovich > Fix For: 4.4.x > > Attachments: DesignView1_Batch.png, DesignView2_Batch.png, DesignView3_Batch.png > > > Implies to editing label component in all property tables. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22693) Label for editing name of property in design view is too short. Name seems to be cut.

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22693?page=com.atlassian.jira.plugi... ] Ondrej Dockal updated JBIDE-22693: ---------------------------------- Attachment: DesignView3_Batch.png > Label for editing name of property in design view is too short. Name seems to be cut. > ------------------------------------------------------------------------------------- > > Key: JBIDE-22693 > URL: https://issues.jboss.org/browse/JBIDE-22693 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: xml-structured-editor > Environment: devstudio: > Version: 10.0.1.AM1 > Build id: v20160613-2041 > Fedora 24, x86_64 > Reporter: Ondrej Dockal > Assignee: Viacheslav Kabanovich > Fix For: 4.4.x > > Attachments: DesignView1_Batch.png, DesignView2_Batch.png, DesignView3_Batch.png > > > Implies to editing label component in all property tables. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues July 2016