July 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (ERT-197) JSON editor needs to use original minimal-json library instead of supporting org.eclipse.json plug-in [EBZ#494045]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-197?page=com.atlassian.jira.plugin.sy... ] Gorkem Ercan updated ERT-197: ----------------------------- Story Points: 20 (was: 10) > JSON editor needs to use original minimal-json library instead of supporting org.eclipse.json plug-in [EBZ#494045] > ------------------------------------------------------------------------------------------------------------------ > > Key: ERT-197 > URL: https://issues.jboss.org/browse/ERT-197 > Project: Eclipse Release Train > Issue Type: Task > Components: WTP Source Editing > Reporter: Friendly Jira Robot > Priority: Trivial > Labels: bzira, wst.json > > The reason why org.eclipse.json (a modified copy of minimal-json library https://github.com/ralfstx/minimal-json) was the lack of information on offsets for tokens. > As issue https://github.com/ralfstx/minimal-json/issues/17 is fixed in original minimal-json library, probably we can request the adding of original minimal-json library to the Orbit bundle and depend on it instead of supporting its modified copy in org.eclipse.json plug-in. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ERT-197) JSON editor needs to use original minimal-json library instead of supporting org.eclipse.json plug-in [EBZ#494045]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-197?page=com.atlassian.jira.plugin.sy... ] Gorkem Ercan updated ERT-197: ----------------------------- Sprint: devex #116 June 2016, devex #117 July 2016 (was: devex #116 June 2016) > JSON editor needs to use original minimal-json library instead of supporting org.eclipse.json plug-in [EBZ#494045] > ------------------------------------------------------------------------------------------------------------------ > > Key: ERT-197 > URL: https://issues.jboss.org/browse/ERT-197 > Project: Eclipse Release Train > Issue Type: Task > Components: WTP Source Editing > Reporter: Friendly Jira Robot > Priority: Trivial > Labels: bzira, wst.json > > The reason why org.eclipse.json (a modified copy of minimal-json library https://github.com/ralfstx/minimal-json) was the lack of information on offsets for tokens. > As issue https://github.com/ralfstx/minimal-json/issues/17 is fixed in original minimal-json library, probably we can request the adding of original minimal-json library to the Orbit bundle and depend on it instead of supporting its modified copy in org.eclipse.json plug-in. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ERT-197) JSON editor needs to use original minimal-json library instead of supporting org.eclipse.json plug-in [EBZ#494045]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-197?page=com.atlassian.jira.plugin.sy... ] Gorkem Ercan updated ERT-197: ----------------------------- Summary: JSON editor needs to use original minimal-json library instead of supporting org.eclipse.json plug-in [EBZ#494045] (was: JSON editor need to use original minimal-json library instead of supporting org.eclipse.json plug-in [EBZ#494045]) > JSON editor needs to use original minimal-json library instead of supporting org.eclipse.json plug-in [EBZ#494045] > ------------------------------------------------------------------------------------------------------------------ > > Key: ERT-197 > URL: https://issues.jboss.org/browse/ERT-197 > Project: Eclipse Release Train > Issue Type: Task > Components: WTP Source Editing > Reporter: Friendly Jira Robot > Priority: Trivial > Labels: bzira, wst.json > > The reason why org.eclipse.json (a modified copy of minimal-json library https://github.com/ralfstx/minimal-json) was the lack of information on offsets for tokens. > As issue https://github.com/ralfstx/minimal-json/issues/17 is fixed in original minimal-json library, probably we can request the adding of original minimal-json library to the Orbit bundle and depend on it instead of supporting its modified copy in org.eclipse.json plug-in. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ERT-179) StructuredTextEditor does not allow for custom IDocumentProvider [EBZ#493145]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-179?page=com.atlassian.jira.plugin.sy... ] Gorkem Ercan updated ERT-179: ----------------------------- Sprint: devex #116 June 2016, devex #117 July 2016 (was: devex #116 June 2016) > StructuredTextEditor does not allow for custom IDocumentProvider [EBZ#493145] > ----------------------------------------------------------------------------- > > Key: ERT-179 > URL: https://issues.jboss.org/browse/ERT-179 > Project: Eclipse Release Train > Issue Type: Task > Components: WTP Source Editing > Reporter: Friendly Jira Robot > Assignee: Gorkem Ercan > Priority: Critical > Labels: bzira, wst.sse > > I have a custom IDocumentProvider that is used to get events from the text editor framework (document loaded, modified, closed). > The StructuredTextEditor does not call all methods on my implementation because it uses its own internal document provider. I think this would be great to support that -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ERT-179) StructuredTextEditor does not allow for custom IDocumentProvider [EBZ#493145]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-179?page=com.atlassian.jira.plugin.sy... ] Gorkem Ercan reassigned ERT-179: -------------------------------- Assignee: (was: Gorkem Ercan) > StructuredTextEditor does not allow for custom IDocumentProvider [EBZ#493145] > ----------------------------------------------------------------------------- > > Key: ERT-179 > URL: https://issues.jboss.org/browse/ERT-179 > Project: Eclipse Release Train > Issue Type: Task > Components: WTP Source Editing > Reporter: Friendly Jira Robot > Priority: Critical > Labels: bzira, wst.sse > > I have a custom IDocumentProvider that is used to get events from the text editor framework (document loaded, modified, closed). > The StructuredTextEditor does not call all methods on my implementation because it uses its own internal document provider. I think this would be great to support that -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ERT-177) Selection and dependent functionality works wrong when a file is modified in JS Editor [EBZ#492998]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-177?page=com.atlassian.jira.plugin.sy... ] Gorkem Ercan updated ERT-177: ----------------------------- Sprint: devex #114 May 2016, devex #116 June 2016, devex #117 July 2016 (was: devex #114 May 2016, devex #116 June 2016) > Selection and dependent functionality works wrong when a file is modified in JS Editor [EBZ#492998] > --------------------------------------------------------------------------------------------------- > > Key: ERT-177 > URL: https://issues.jboss.org/browse/ERT-177 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Friendly Jira Robot > Assignee: Victor Rubezhny > Labels: 3.8_RC1, General, bzira > Fix For: Neon (4.6) RC3 > > > Created attachment 261462 > Selection related errors > See the screenshot attached for illustration. > Steps for reproduce: > - Create a javascript file with a function and a call to that function. > - Try to invoke content assist: FAIL: no new function appears in CA proposals > - Save, close and open the file again. > - Try to invoke content assist: Now the new function appears in CA proposals > - Put some text (like just new lines or some statements between the function declaration and its call and select the function name in the declaration > - FAIL: See wrong text regions highlighted. > - Try to rename the function (with inline rename): FAIL: See the wrong places for the inline editing are highlighted. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ERT-142) JavaScript Problems get doubled in Dynamic Web Projects [EBZ#491751]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-142?page=com.atlassian.jira.plugin.sy... ] Gorkem Ercan reassigned ERT-142: -------------------------------- Assignee: Gorkem Ercan (was: Victor Rubezhny) > JavaScript Problems get doubled in Dynamic Web Projects [EBZ#491751] > -------------------------------------------------------------------- > > Key: ERT-142 > URL: https://issues.jboss.org/browse/ERT-142 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Friendly Jira Robot > Assignee: Gorkem Ercan > Labels: General, bzira > > Created attachment 260976 > Doubled problems in Problem view > JavaScript Problems are doubling in Dynamic Web Projects (See the attached screenshot). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ERT-142) JavaScript Problems get doubled in Dynamic Web Projects [EBZ#491751]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-142?page=com.atlassian.jira.plugin.sy... ] Gorkem Ercan reassigned ERT-142: -------------------------------- Assignee: Victor Rubezhny (was: Gorkem Ercan) > JavaScript Problems get doubled in Dynamic Web Projects [EBZ#491751] > -------------------------------------------------------------------- > > Key: ERT-142 > URL: https://issues.jboss.org/browse/ERT-142 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Friendly Jira Robot > Assignee: Victor Rubezhny > Labels: General, bzira > > Created attachment 260976 > Doubled problems in Problem view > JavaScript Problems are doubling in Dynamic Web Projects (See the attached screenshot). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ERT-132) Need to create launch configuration for npm "scripts" [EBZ#491474]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-132?page=com.atlassian.jira.plugin.sy... ] Gorkem Ercan updated ERT-132: ----------------------------- Sprint: devex #116 June 2016, devex #117 July 2016 (was: devex #116 June 2016) > Need to create launch configuration for npm "scripts" [EBZ#491474] > ------------------------------------------------------------------ > > Key: ERT-132 > URL: https://issues.jboss.org/browse/ERT-132 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Nick Boldt > Assignee: Shane Bryzak > Labels: General, bzira > > For now npm is used only as a package manager - only npm Install & npm Update shortcuts available. Need to extend npm functionality by supporting "scripts" property. This will allow to use npm as a Build Tool (like grunt / gulp) i.e. > all scripts defined in package.json should be contributed to CNF with launch shortcuts availbale for launch -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19081) Use simpler Surefire include/exclude pattern in parent pom

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19081?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-19081: ------------------------------------- PR to fix foundation and its missing tests: https://github.com/jbosstools/jbosstools-base/pull/517 Before applying: {noformat} Tests run: 8, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.452 sec - in org.jboss.tools.foundation.checkup.test.FoundationCheckupTestSuite Tests run: 12, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 18.683 sec - in org.jboss.tools.foundation.core.test.FoundationAllTests Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 3.188 sec - in org.jboss.tools.foundation.help.ui.internal.search.SearchiskoEngineTest Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.542 sec - in org.jboss.tools.foundation.ui.test.FoundationUITestSuite Total classes: 4 Total tests run: 27 {noformat} After applying {noformat} Tests run: 7, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.45 sec - in org.jboss.tools.foundation.checkup.test.JVMProblemDetectorTest Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.007 sec - in org.jboss.tools.foundation.checkup.test.TestEnvironmentDetectorTest Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.044 sec - in org.jboss.tools.foundation.core.properties.internal.PropertiesProviderFactoryTest Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.017 sec - in org.jboss.tools.foundation.core.properties.internal.SimpleHierarchicalVersionTest Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.003 sec - in org.jboss.tools.foundation.core.properties.internal.VersionExtractorTest Tests run: 8, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.989 sec - in org.jboss.tools.foundation.core.properties.internal.VersionProviderTest Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.028 sec - in org.jboss.tools.foundation.core.test.credentials.CredentialsModelTest Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.009 sec - in org.jboss.tools.foundation.core.test.digest.DigestUtilsTest Tests run: 9, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 16.977 sec - in org.jboss.tools.foundation.core.test.ecf.URLTransportUtilTest Tests run: 15, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.012 sec - in org.jboss.tools.foundation.core.test.expressions.ExpressionResolverTest Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.018 sec - in org.jboss.tools.foundation.core.test.jobs.WaitJobTest Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 4.371 sec - in org.jboss.tools.foundation.help.ui.internal.search.SearchiskoEngineTest Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.363 sec - in org.jboss.tools.foundation.ui.test.BrowserUtilTest Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.079 sec - in org.jboss.tools.foundation.ui.test.WidgetUtilityTest Total classes: 14 Total tests run: 67 {noformat} > Use simpler Surefire include/exclude pattern in parent pom > ---------------------------------------------------------- > > Key: JBIDE-19081 > URL: https://issues.jboss.org/browse/JBIDE-19081 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Minor > Fix For: 4.4.x > > > 1. In JBDS9, use these new default patterns for Surefire to define which test classes to run/exclude: > {code} > include = *Test*, *Test, *TestCase > exclude = *Abstract* > {code} > 2. If that causes test failures because running incorrectly named > abstract stuff, they can refactor, add their own root pom overrides, use > a TestSuite, or use @Ignore in test classes. > 3. If the count of tests run suddenly DROPS because the pattern isn't > running the correct # of tests, they can add their own root pom > overrides, or use a TestSuite. > Ref: http://lists.jboss.org/pipermail/jbosstools-dev/2015-January/009688.html -- 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