April 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3842) Migrating to Eclipse Neon

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-3842?page=com.atlassian.jira.plugin.... ] CDW Engine reassigned JBDS-3842: -------------------------------- > Migrating to Eclipse Neon > ------------------------- > > Key: JBDS-3842 > URL: https://issues.jboss.org/browse/JBDS-3842 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Epic > Components: build > Reporter: Alexey Kazakov > Assignee: Alexey Kazakov > Labels: new_and_noteworthy > Fix For: 10.0.0.Alpha1 > > > This Epic is for tasks related to Devstudio migration to Eclipse Neon. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3842) Migrating to Eclipse Neon

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3842?page=com.atlassian.jira.plugin.... ] Alexey Kazakov updated JBDS-3842: --------------------------------- > Migrating to Eclipse Neon > ------------------------- > > Key: JBDS-3842 > URL: https://issues.jboss.org/browse/JBDS-3842 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Epic > Components: build > Reporter: Alexey Kazakov > Assignee: Alexey Kazakov > Labels: new_and_noteworthy > Fix For: 10.0.0.Alpha1 > > > This Epic is for tasks related to Devstudio migration to Eclipse Neon. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22199) N&N for Betas are not aggregated into 4.3.1.Final

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22199?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-22199: ---------------------------------------- {quote}Xavier said it doesn't work because there is no item in the releases yaml, but it was suggested to try and create an empty item as a workaround. Whether or not this has been done I don't know - I don't see any such commit in the repo.{quote} This was done for tools.stage.jboss.org and has been pushed to tools.jboss.org by now. But we need to improve this aggregation mechanism. Why just not to trigger aggregation when any .Final.adoc is available? Something to look at for next releases. > N&N for Betas are not aggregated into 4.3.1.Final > ------------------------------------------------- > > Key: JBIDE-22199 > URL: https://issues.jboss.org/browse/JBIDE-22199 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: website > Affects Versions: 4.3.1.Final > Reporter: Martin Malina > Assignee: Xavier Coulon > Fix For: 4.4.x > > > As discussed yesterday on hipchat, this doesn't work as expected. > http://tools.jboss.org/documentation/whatsnew/jbosstools/4.3.1.Final.html > should contain new features for cr1/final as well as relevant features from Beta1 and Beta2: > http://tools.jboss.org/documentation/whatsnew/jbosstools/4.3.1.Beta1.html > http://tools.jboss.org/documentation/whatsnew/jbosstools/4.3.1.Beta2.html > Xavier said it doesn't work because there is no item in the releases yaml, but it was suggested to try and create an empty item as a workaround. Whether or not this has been done I don't know - I don't see any such commit in the repo. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22199) N&N for Betas are not aggregated into 4.3.1.Final

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22199?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-22199: ----------------------------------- Fix Version/s: 4.4.x (was: 4.3.1.Final) > N&N for Betas are not aggregated into 4.3.1.Final > ------------------------------------------------- > > Key: JBIDE-22199 > URL: https://issues.jboss.org/browse/JBIDE-22199 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: website > Affects Versions: 4.3.1.Final > Reporter: Martin Malina > Assignee: Xavier Coulon > Fix For: 4.4.x > > > As discussed yesterday on hipchat, this doesn't work as expected. > http://tools.jboss.org/documentation/whatsnew/jbosstools/4.3.1.Final.html > should contain new features for cr1/final as well as relevant features from Beta1 and Beta2: > http://tools.jboss.org/documentation/whatsnew/jbosstools/4.3.1.Beta1.html > http://tools.jboss.org/documentation/whatsnew/jbosstools/4.3.1.Beta2.html > Xavier said it doesn't work because there is no item in the releases yaml, but it was suggested to try and create an empty item as a workaround. Whether or not this has been done I don't know - I don't see any such commit in the repo. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22199) N&N for Betas are not aggregated into *.Final

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22199?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-22199: ----------------------------------- Summary: N&N for Betas are not aggregated into *.Final (was: N&N for Betas are not aggregated into 4.3.1.Final) > N&N for Betas are not aggregated into *.Final > --------------------------------------------- > > Key: JBIDE-22199 > URL: https://issues.jboss.org/browse/JBIDE-22199 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: website > Affects Versions: 4.3.1.Final > Reporter: Martin Malina > Assignee: Xavier Coulon > Fix For: 4.4.x > > > As discussed yesterday on hipchat, this doesn't work as expected. > http://tools.jboss.org/documentation/whatsnew/jbosstools/4.3.1.Final.html > should contain new features for cr1/final as well as relevant features from Beta1 and Beta2: > http://tools.jboss.org/documentation/whatsnew/jbosstools/4.3.1.Beta1.html > http://tools.jboss.org/documentation/whatsnew/jbosstools/4.3.1.Beta2.html > Xavier said it doesn't work because there is no item in the releases yaml, but it was suggested to try and create an empty item as a workaround. Whether or not this has been done I don't know - I don't see any such commit in the repo. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 12 months

1
0
0 / 0

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

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22196?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-22196: ----------------------------------- Component/s: build > 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: build > Affects Versions: 4.3.1.CR1 > Reporter: Aurélien Pupier > 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, 12 months

1
0
0 / 0

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

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22196?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-22196: -------------------------------------- Assignee: Nick Boldt [~nickboldt] can you please take a look. Do we miss something in our TP or it's an upstream issue. > 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: build > Affects Versions: 4.3.1.CR1 > Reporter: Aurélien Pupier > Assignee: Nick Boldt > 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, 12 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3841) Installer Sets Path for Wrong User

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3841?page=com.atlassian.jira.plugin.... ] Alexey Kazakov updated JBDS-3841: --------------------------------- Priority: Blocker (was: Major) > Installer Sets Path for Wrong User > ---------------------------------- > > Key: JBDS-3841 > URL: https://issues.jboss.org/browse/JBDS-3841 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.x > Environment: Windows 10 > Reporter: Thomas Mäder > Priority: Blocker > Fix For: 10.0.0.Alpha1 > > > When I run the offline installer from my non-privileged account, I am prompted by UAC for an administrator login. When I enter my admin login and proceed, tools like vagrant, etc. will not be available from the command line in my non-privileged account. It turns out, the necessary path entries were added to the user-specific path of the admin user, not the user starting the installer. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3841) Installer Sets Path for Wrong User

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3841?page=com.atlassian.jira.plugin.... ] Alexey Kazakov updated JBDS-3841: --------------------------------- Fix Version/s: 10.0.0.Alpha1 > Installer Sets Path for Wrong User > ---------------------------------- > > Key: JBDS-3841 > URL: https://issues.jboss.org/browse/JBDS-3841 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.x > Environment: Windows 10 > Reporter: Thomas Mäder > Priority: Blocker > Fix For: 10.0.0.Alpha1 > > > When I run the offline installer from my non-privileged account, I am prompted by UAC for an administrator login. When I enter my admin login and proceed, tools like vagrant, etc. will not be available from the command line in my non-privileged account. It turns out, the necessary path entries were added to the user-specific path of the admin user, not the user starting the installer. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3841) Installer Sets Path for Wrong User

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3841?page=com.atlassian.jira.plugin.... ] Alexey Kazakov reassigned JBDS-3841: ------------------------------------ Assignee: Denis Golovin > Installer Sets Path for Wrong User > ---------------------------------- > > Key: JBDS-3841 > URL: https://issues.jboss.org/browse/JBDS-3841 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.x > Environment: Windows 10 > Reporter: Thomas Mäder > Assignee: Denis Golovin > Priority: Blocker > Fix For: 10.0.0.Alpha1 > > > When I run the offline installer from my non-privileged account, I am prompted by UAC for an administrator login. When I enter my admin login and proceed, tools like vagrant, etc. will not be available from the command line in my non-privileged account. It turns out, the necessary path entries were added to the user-specific path of the admin user, not the user starting the installer. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

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