May 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22196) Code Recommenders Snippet view is not working

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22196?page=com.atlassian.jira.plugi... ] Jan Richter commented on JBIDE-22196: ------------------------------------- I can't get the particular view to show up in the menu neither in 4.3.1 nor in 4.4.0. The only 'snippets' view I can get is in the 'general' category and it works for both versions. Is there some extra plugin needed atop the default installation? > Code Recommenders Snippet view is not working > --------------------------------------------- > > Key: JBIDE-22196 > URL: https://issues.jboss.org/browse/JBIDE-22196 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform > Affects Versions: 4.3.1.CR1 > Reporter: Aurélien Pupier > Assignee: Nick Boldt > Fix For: 4.4.0.Alpha2 > > Attachments: screenshot-1.png > > > When trying to open a view (Alt+Shift+Q,Q), a Snippet view is available under "Code Recommenders" but there is a big red square > when I try to open it, there is an error. > In log we have: > {noformat} > java.io.IOException: Unable to resolve plug-in "platform:/plugin/org.eclipse.recommenders.snipmatch.rcp/icons/view16/snippets.png". > at org.eclipse.core.internal.runtime.PlatformURLPluginConnection.parse(PlatformURLPluginConnection.java:65) > at org.eclipse.core.internal.runtime.FindSupport.find(FindSupport.java:290) > at org.eclipse.core.runtime.FileLocator.find(FileLocator.java:152) > at org.eclipse.jface.resource.URLImageDescriptor.getFilePath(URLImageDescriptor.java:215) > at org.eclipse.jface.resource.URLImageDescriptor.createImage(URLImageDescriptor.java:283) > at org.eclipse.jface.resource.ImageDescriptor.createImage(ImageDescriptor.java:224) > at org.eclipse.jface.resource.ImageDescriptor.createImage(ImageDescriptor.java:202) > at org.eclipse.ui.internal.dialogs.ViewLabelProvider.getImage(ViewLabelProvider.java:93) > at org.eclipse.jface.viewers.ColumnLabelProvider.update(ColumnLabelProvider.java:35) > at org.eclipse.jface.viewers.ViewerColumn.refresh(ViewerColumn.java:154) > at org.eclipse.jface.viewers.AbstractTreeViewer.doUpdateItem(AbstractTreeViewer.java:949) > at org.eclipse.jface.viewers.AbstractTreeViewer$UpdateItemSafeRunnable.run(AbstractTreeViewer.java:114) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:50) > at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:173) > at org.eclipse.jface.viewers.AbstractTreeViewer.doUpdateItem(AbstractTreeViewer.java:1029) > at org.eclipse.jface.viewers.StructuredViewer$UpdateItemSafeRunnable.run(StructuredViewer.java:473) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:50) > at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:173) > at org.eclipse.jface.viewers.StructuredViewer.updateItem(StructuredViewer.java:2176) > at org.eclipse.jface.viewers.AbstractTreeViewer.createTreeItem(AbstractTreeViewer.java:843) > at org.eclipse.jface.viewers.AbstractTreeViewer$1.run(AbstractTreeViewer.java:818) > {noformat} > In plugins folder there is no org.eclipse.recommenders.snipmatch.rcp plugin -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13287) examples URLs should use major/minor/service/milestone convention

by Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13287?page=com.atlassian.jira.plugi... ] Josef Kopriva closed JBIDE-13287. --------------------------------- Examples URLs now pointing to the new structure and are accessible. Closing. Verified in: Version: 10.0.0.Alpha1 Build id: Alpha1-v20160520-1027-B5398 Build date: 20160520-1027 > examples URLs should use major/minor/service/milestone convention > ------------------------------------------------------------------ > > Key: JBIDE-13287 > URL: https://issues.jboss.org/browse/JBIDE-13287 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: project-examples > Affects Versions: 4.1.0.Alpha1 > Reporter: Nick Boldt > Assignee: Fred Bricon > Fix For: 4.4.0.Alpha2 > > > Instead of > {code:title=http://download.jboss.org/jbosstools/examples/} > project-examples-community-4.0.GA.xml > project-examples-jbds60.xml > project-examples-maven-4.0.GA.xml > project-examples-shared-4.0.GA.xml > ... > {code} > We should consider using something like 6/1/0/Alpha1/project-examples*.xml -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22302) Outdated project examples in Help menu

by Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22302?page=com.atlassian.jira.plugi... ] Josef Kopriva closed JBIDE-22302. --------------------------------- Tags are now OK and ide-config.properties have now correct links to examples. Closing. Tested in: Version: 10.0.0.Alpha1 Build id: Alpha1-v20160520-1027-B5398 Build date: 20160520-1027 > Outdated project examples in Help menu > -------------------------------------- > > Key: JBIDE-22302 > URL: https://issues.jboss.org/browse/JBIDE-22302 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: project-examples > Affects Versions: 4.3.1.Final > Reporter: Josef Kopriva > Assignee: Fred Bricon > Fix For: 4.4.0.Alpha2 > > Attachments: JBDS_8.0_Examples.png > > > Project examples are probably outdated in menu: *Help* >> *Project Examples...* > Repository[1] from configuration file[2] contains outdated files. > In *JBDS 9.1.0.GA* are also old sites - *8.0* - screenshot attached. > [1] http://download.jboss.org/jbosstools/examples/ > [2] http://download.jboss.org/jbosstools/configuration/ide-config.properties -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-725) Fix Model Wizard Test

by Matus Makovy (JIRA)

Matus Makovy created JBTIS-725: ---------------------------------- Summary: Fix Model Wizard Test Key: JBTIS-725 URL: https://issues.jboss.org/browse/JBTIS-725 Project: JBoss Tools Integration Stack Issue Type: Bug Components: QE, teiid Affects Versions: 4.3.0.Final Reporter: Matus Makovy Assignee: Matus Makovy Fix For: 4.3.1.Final Fix model names in new Model Wizard -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22465) npm, bower not recognized as an internal or external command on windows

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22465?page=com.atlassian.jira.plugi... ] Pavol Srna commented on JBIDE-22465: ------------------------------------ If I use the nodejs installer on win 10, it works. If I install npm using https://github.com/coreybutler/nvm-windows it does not work. The strange thing is that cmd has npm on path (see screenshot) > npm, bower not recognized as an internal or external command on windows > ----------------------------------------------------------------------- > > Key: JBIDE-22465 > URL: https://issues.jboss.org/browse/JBIDE-22465 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: nodejs > Affects Versions: 4.4.0.Alpha3 > Reporter: Pavol Srna > Assignee: Ilya Buziuk > Priority: Blocker > Fix For: 4.4.0.Alpha3 > > Attachments: bower.png, cmd.png, npm.png > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3917) Verify target-platform PR by running compile/package (no tests) build for all modules

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBDS-3917?page=com.atlassian.jira.plugin.... ] Mickael Istria commented on JBDS-3917: -------------------------------------- Do you think you could put such a job on the wonka server and have it triggered on incoming PRs? > Verify target-platform PR by running compile/package (no tests) build for all modules > ------------------------------------------------------------------------------------- > > Key: JBDS-3917 > URL: https://issues.jboss.org/browse/JBDS-3917 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Enhancement > Components: build, target-platform > Affects Versions: 10.0.0.Alpha2 > Reporter: Denis Golovin > > Would be good to have this as part of TP PR Verification build. > Example of repository with git submodules https://github.com/dgolovin/devstudio-releng. > Example for possible full build https://github.com/dgolovin/jbosstools-dev. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22443) Add to TP build a check that produced TP can be installed in target Eclipse version

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22443?page=com.atlassian.jira.plugi... ] Denis Golovin commented on JBIDE-22443: --------------------------------------- [~mickael_istria] I created JBDS-3917 and put links to my full build and git repo with submodules as an example. > Add to TP build a check that produced TP can be installed in target Eclipse version > ----------------------------------------------------------------------------------- > > Key: JBIDE-22443 > URL: https://issues.jboss.org/browse/JBIDE-22443 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build, target-platform > Reporter: Mickael Istria > > Recently, a change in TP (jetty 9.3.6) was introduced and everything built fine with it; until the very end of the build process: during install-tests. > This issue would *probably* have occured if trying to install all content of the TP into the target Eclipse IDE (using install-grinder or p2director or whatever installation). So it would be good to have inside the TP build (as a "verify" plugin in pom.xml) something that would try to find whether target Eclipse version and our TP are already compatible. > Technical notes: > * Trying to install all IUs from the release train site + our TP seems easier to implement > * We do not need to actually install the artifacts, just making the p2 request and getting whether the request managed to find a working plan without remediation seems enough. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3917) Verify target-platform PR by running compile/package (no tests) build for all modules

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-3917?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-3917: ----------------------------- > Verify target-platform PR by running compile/package (no tests) build for all modules > ------------------------------------------------------------------------------------- > > Key: JBDS-3917 > URL: https://issues.jboss.org/browse/JBDS-3917 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Enhancement > Components: build, target-platform > Affects Versions: 10.0.0.Alpha2 > Reporter: Denis Golovin > > Would be good to have this as part of TP PR Verification build. > Example of repository with git submodules https://github.com/dgolovin/devstudio-releng. > Example for possible full build https://github.com/dgolovin/jbosstools-dev. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3917) Verify target-platform PR by running compile/package (no tests) build for all modules

by Denis Golovin (JIRA)

Denis Golovin created JBDS-3917: ----------------------------------- Summary: Verify target-platform PR by running compile/package (no tests) build for all modules Key: JBDS-3917 URL: https://issues.jboss.org/browse/JBDS-3917 Project: Red Hat Developer Studio (DevStudio) Issue Type: Enhancement Components: build, target-platform Affects Versions: 10.0.0.Alpha2 Reporter: Denis Golovin Would be good to have this as part of TP PR Verification build. Example of repository with git submodules https://github.com/dgolovin/devstudio-releng. Example for possible full build https://github.com/dgolovin/jbosstools-dev. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21066) update tm.terminal in JBT/JBDS target platforms (was Extra step in opening terminal in git perspective?)

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21066?page=com.atlassian.jira.plugi... ] Jan Richter closed JBIDE-21066. ------------------------------- Verified with 4.4.0.Alpha3 nightly. > update tm.terminal in JBT/JBDS target platforms (was Extra step in opening terminal in git perspective?) > -------------------------------------------------------------------------------------------------------- > > Key: JBIDE-21066 > URL: https://issues.jboss.org/browse/JBIDE-21066 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform, upstream > Affects Versions: 4.3.0.Final > Reporter: Len DiMaggio > Assignee: Nick Boldt > Fix For: 4.4.0.Alpha2 > > Attachments: terminal.png, Terminal.webm, tm.term.view.png > > > If a user opens a terminal view from the git perspective - for example, by performing "show in" for a local repo, an empty terminal view is displayed. The user must then click on the terminal icon to actually open the terminal. This seems like an extra step - why wouldn't we open a terminal when we open the terminal view? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 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 May 2016