January 2018 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (ERT-602) [templates] Templates for empty .java files [EBZ#505610]

by Friendly Jira Robot (JIRA)

Friendly Jira Robot created ERT-602: --------------------------------------- Summary: [templates] Templates for empty .java files [EBZ#505610] Key: ERT-602 URL: https://issues.jboss.org/browse/ERT-602 Project: Eclipse Release Train Issue Type: Task Components: JDT Reporter: Friendly Jira Robot Priority: Trivial Assuming someone tries content-assist on an empty .java file, it would be nice to show templates such as "Create new class <fileName>", "Create new interface <fileName>", "Create new enum <fileName>"... that would scaffold a minimal content (packange and object declaration at least). Or maybe those completion items could directly open the right New wizard without leaving opportunity to change the name and let the wizard perform the change. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ERT-568) [JDT] New API for organize imports

by Roland Grunberg (JIRA)

[ https://issues.jboss.org/browse/ERT-568?page=com.atlassian.jira.plugin.sy... ] Roland Grunberg commented on ERT-568: ------------------------------------- - Removed some changes that were extraneous and made patch tougher to review - Made some exposed fields internal and provided better API to access them > [JDT] New API for organize imports > ---------------------------------- > > Key: ERT-568 > URL: https://issues.jboss.org/browse/ERT-568 > Project: Eclipse Release Train > Issue Type: Task > Components: Platform > Reporter: Roland Grunberg > Assignee: Roland Grunberg > > See https://bugs.eclipse.org/bugs/show_bug.cgi?id=506239 for full details. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ERT-537) Update to com.spotify.docker.client 8.9.2 [EBZ#522659]

by Roland Grunberg (JIRA)

[ https://issues.jboss.org/browse/ERT-537?page=com.atlassian.jira.plugin.sy... ] Roland Grunberg commented on ERT-537: ------------------------------------- CQs and ATO CQs have all been filed and approved so I just need to carve out some time to rebase, and push. > Update to com.spotify.docker.client 8.9.2 [EBZ#522659] > ------------------------------------------------------ > > Key: ERT-537 > URL: https://issues.jboss.org/browse/ERT-537 > Project: Eclipse Release Train > Issue Type: Task > Components: Linux Tools > Reporter: Friendly Jira Robot > Assignee: Roland Grunberg > Labels: Docker, bzira > > This is currently the latest upstream version of docker-client. There are also some API breaking changes, so aside from just bringing a newer version into Orbit, we'll also need to update the sources. > (/) Update Jackson 2.9.2 Stack in Orbit (from 2.6.2) > (/) Confirm the changes made should allow Docker Tooling to function > (/) Create CQs, ATO CQs for JNR stack update > (?) Update JNR stack, along with docker-client in Orbit > (?) Push all changes necessary to Docker Tooling -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ERT-537) Update to com.spotify.docker.client 8.9.2 [EBZ#522659]

by Roland Grunberg (JIRA)

[ https://issues.jboss.org/browse/ERT-537?page=com.atlassian.jira.plugin.sy... ] Roland Grunberg updated ERT-537: -------------------------------- Summary: Update to com.spotify.docker.client 8.9.2 [EBZ#522659] (was: Update to com.spotify.docker.client 8.9.0 [EBZ#522659]) > Update to com.spotify.docker.client 8.9.2 [EBZ#522659] > ------------------------------------------------------ > > Key: ERT-537 > URL: https://issues.jboss.org/browse/ERT-537 > Project: Eclipse Release Train > Issue Type: Task > Components: Linux Tools > Reporter: Friendly Jira Robot > Assignee: Roland Grunberg > Labels: Docker, bzira > > This is currently the latest upstream version of docker-client. There are also some API breaking changes, so aside from just bringing a newer version into Orbit, we'll also need to update the sources. > (/) Update Jackson 2.9.2 Stack in Orbit (from 2.6.2) > (/) Confirm the changes made should allow Docker Tooling to function > (?) Create CQs, ATO CQs for JNR stack update > (?) Update JNR stack, along with docker-client in Orbit > (?) Push all changes necessary to Docker Tooling -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ERT-537) Update to com.spotify.docker.client 8.9.2 [EBZ#522659]

by Roland Grunberg (JIRA)

[ https://issues.jboss.org/browse/ERT-537?page=com.atlassian.jira.plugin.sy... ] Roland Grunberg updated ERT-537: -------------------------------- Description: This is currently the latest upstream version of docker-client. There are also some API breaking changes, so aside from just bringing a newer version into Orbit, we'll also need to update the sources. (/) Update Jackson 2.9.2 Stack in Orbit (from 2.6.2) (/) Confirm the changes made should allow Docker Tooling to function (/) Create CQs, ATO CQs for JNR stack update (?) Update JNR stack, along with docker-client in Orbit (?) Push all changes necessary to Docker Tooling was: This is currently the latest upstream version of docker-client. There are also some API breaking changes, so aside from just bringing a newer version into Orbit, we'll also need to update the sources. (/) Update Jackson 2.9.2 Stack in Orbit (from 2.6.2) (/) Confirm the changes made should allow Docker Tooling to function (?) Create CQs, ATO CQs for JNR stack update (?) Update JNR stack, along with docker-client in Orbit (?) Push all changes necessary to Docker Tooling > Update to com.spotify.docker.client 8.9.2 [EBZ#522659] > ------------------------------------------------------ > > Key: ERT-537 > URL: https://issues.jboss.org/browse/ERT-537 > Project: Eclipse Release Train > Issue Type: Task > Components: Linux Tools > Reporter: Friendly Jira Robot > Assignee: Roland Grunberg > Labels: Docker, bzira > > This is currently the latest upstream version of docker-client. There are also some API breaking changes, so aside from just bringing a newer version into Orbit, we'll also need to update the sources. > (/) Update Jackson 2.9.2 Stack in Orbit (from 2.6.2) > (/) Confirm the changes made should allow Docker Tooling to function > (/) Create CQs, ATO CQs for JNR stack update > (?) Update JNR stack, along with docker-client in Orbit > (?) Push all changes necessary to Docker Tooling -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4637) Failing quickstart WildFly-11 [template]

by Vojtech Prusa (JIRA)

[ https://issues.jboss.org/browse/JBDS-4637?page=com.atlassian.jira.plugin.... ] Vojtech Prusa closed JBDS-4637. ------------------------------- > Failing quickstart WildFly-11 [template] > ---------------------------------------- > > Key: JBDS-4637 > URL: https://issues.jboss.org/browse/JBDS-4637 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: project-examples > Affects Versions: 11.2.0.AM2 > Environment: https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/examples... > WF11 > quickstartes 11.0.0.Final > Reporter: Vojtech Prusa > Assignee: Vojtech Prusa > Fix For: 11.2.0.AM3 > > Attachments: pom.xml > > > Automation fails because of error after template project is imported. > Test report: > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/examples... > Solutions: > https://stackoverflow.com/questions/31835033/web-xml-is-missing-and-failo... > Updated pom.xml as attachment does no show errors after Project Maven -> Update project .. > Idk if right solution is to change pom or generate web.xml with "Java EE Tools -> Generate Deployment Descriptor Stub" in test. > Please comment recommendations [~n1hility] [~ctomc] [~trepel] [~sgilda] [~jkopriva] > Thank you. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24845) [regression] unable to open the Maven Repositories wizard

by Vojtech Prusa (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24845?page=com.atlassian.jira.plugi... ] Vojtech Prusa closed JBIDE-24845. --------------------------------- Verified, used http://download.eclipse.org/technology/m2e/snapshots/1.9.0/latest/ and was able to open Configure Maven Repositories > [regression] unable to open the Maven Repositories wizard > --------------------------------------------------------- > > Key: JBIDE-24845 > URL: https://issues.jboss.org/browse/JBIDE-24845 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven > Affects Versions: 4.4.4.Final > Reporter: Fred Bricon > Assignee: Dmitrii Bocharov > Fix For: 4.5.2.AM2 > > > 1 - open Preferences > JBoss Tools > JBoss Maven Integration > 2 - click on the Configure Maven Repositories... button > expected: the Maven repositories wizard open > actual: Unhandled event loop exception: > {noformat} > java.lang.NoSuchFieldError: DEFAULT_USER_SETTINGS_FILE > at org.jboss.tools.maven.ui.wizard.ConfigureMavenRepositoriesWizardPage.getUserSettings(ConfigureMavenRepositoriesWizardPage.java:988) > at org.jboss.tools.maven.ui.wizard.ConfigureMavenRepositoriesWizardPage.createControl(ConfigureMavenRepositoriesWizardPage.java:242) > at org.eclipse.jface.wizard.Wizard.createPageControls(Wizard.java:176) > at org.eclipse.jface.wizard.WizardDialog.createPageControls(WizardDialog.java:688) > at org.eclipse.jface.wizard.WizardDialog.createContents(WizardDialog.java:580) > at org.eclipse.jface.window.Window.create(Window.java:426) > at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1096) > at org.jboss.tools.maven.ui.preferences.ConfiguratorPreferencePage$2.widgetSelected(ConfiguratorPreferencePage.java:155) > at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:249) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:86) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4257) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1502) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1525) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1510) > at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1314) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4081) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3698) > at org.eclipse.jface.window.Window.runEventLoop(Window.java:818) > at org.eclipse.jface.window.Window.open(Window.java:794) > at org.eclipse.ui.internal.dialogs.WorkbenchPreferenceDialog.open(WorkbenchPreferenceDialog.java:211) > at org.eclipse.ui.internal.handlers.ShowPreferencePageHandler.execute(ShowPreferencePageHandler.java:59) > {noformat} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25584) batch itests on macosx fail or timeout most of the time

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25584?page=com.atlassian.jira.plugi... ] Pavol Srna commented on JBIDE-25584: ------------------------------------ [~nickboldt] there is no such thing as mac os *virtual* slaves. All are physical mac slaves. Either co-located in central-ci lab, or in BRQ lab. But as Ondrej pointed out, zamek has some problems. > batch itests on macosx fail or timeout most of the time > ------------------------------------------------------- > > Key: JBIDE-25584 > URL: https://issues.jboss.org/browse/JBIDE-25584 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: batch > Reporter: Nick Boldt > Assignee: Ondrej Dockal > Fix For: 4.5.3.AM1 > > > Not sure if we care about this since the tests pass on Win10 and RHEL7, but the Batch tests on OSX pretty consistently either timeout (120 mins) or fail. > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > Last good build was 20 runs ago on Jan 12: > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > So if only one good build happens in 20+ runs over 2 days... there's a problem. > Related question is: why is this test running so often? 20 itest runs in 2 days? Seems overkill, no? -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25676) Missing image for Jboss Tools Aeri

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25676?page=com.atlassian.jira.plugi... ] Jeff MAURY reassigned JBIDE-25676: ---------------------------------- Assignee: Jeff MAURY > Missing image for Jboss Tools Aeri > ---------------------------------- > > Key: JBIDE-25676 > URL: https://issues.jboss.org/browse/JBIDE-25676 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aeri > Affects Versions: 4.5.2.Final > Reporter: Aurélien Pupier > Assignee: Jeff MAURY > Fix For: 4.5.3.AM2 > > Attachments: image-2018-01-30-15-49-40-666.png > > > !image-2018-01-30-15-49-40-666.png|thumbnail! -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25676) Missing image for Jboss Tools Aeri

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25676?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-25676: ------------------------------- Fix Version/s: 4.5.3.AM2 > Missing image for Jboss Tools Aeri > ---------------------------------- > > Key: JBIDE-25676 > URL: https://issues.jboss.org/browse/JBIDE-25676 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aeri > Affects Versions: 4.5.2.Final > Reporter: Aurélien Pupier > Assignee: Jeff MAURY > Fix For: 4.5.3.AM2 > > Attachments: image-2018-01-30-15-49-40-666.png > > > !image-2018-01-30-15-49-40-666.png|thumbnail! -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues January 2018