November 2014 - jbosstools-issues

[JBoss JIRA] (JBDS-3204) JBDS 8 workspace launcher is not shown in window list

by Marek Novotny (JIRA)

[ https://issues.jboss.org/browse/JBDS-3204?page=com.atlassian.jira.plugin.... ] Marek Novotny updated JBDS-3204: -------------------------------- Environment: Fedora 20 - Gnome-shell Ubuntu 14.10 - Unity > JBDS 8 workspace launcher is not shown in window list > ----------------------------------------------------- > > Key: JBDS-3204 > URL: https://issues.jboss.org/browse/JBDS-3204 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Affects Versions: 8.0.0.GA > Environment: Fedora 20 - Gnome-shell > Ubuntu 14.10 - Unity > Reporter: Marek Novotny > Assignee: Denis Golovin > > While launching JBDS 8.0.0 - if workspace launcher is in background of another focused window, I can't see it in windows list to switch to it. I need to manually minimize some windows to see it and use it. > This is experienced in Fedora 20 - Gnome Shell environment. I can say that the official Luna install of eclipse behave the same so it is a regression to JBDS 7 or Eclipse Kepler. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3204) JBDS 8 workspace launcher is not shown in window list

by Marek Novotny (JIRA)

[ https://issues.jboss.org/browse/JBDS-3204?page=com.atlassian.jira.plugin.... ] Marek Novotny commented on JBDS-3204: ------------------------------------- [~maxandersen] :), when you suggest this I would replicate Idea 13 and NetBeans is shown in windows list just fine. So java apps are shown fine. Is that SWT thing? seriously I don't think it is a gnome-shell thing, I can see the same behaviour on Unity in Ubuntu - did a check that just for you ;) > JBDS 8 workspace launcher is not shown in window list > ----------------------------------------------------- > > Key: JBDS-3204 > URL: https://issues.jboss.org/browse/JBDS-3204 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Affects Versions: 8.0.0.GA > Reporter: Marek Novotny > Assignee: Denis Golovin > > While launching JBDS 8.0.0 - if workspace launcher is in background of another focused window, I can't see it in windows list to switch to it. I need to manually minimize some windows to see it and use it. > This is experienced in Fedora 20 - Gnome Shell environment. I can say that the official Luna install of eclipse behave the same so it is a regression to JBDS 7 or Eclipse Kepler. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18736) create python tooling to create new milestone targets in JBIDE/JBDS

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18736?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-18736: ------------------------------------ Does it matter which way the data flows as long as all the calendar/schedule/meta are in sync w/o having to manually do the updates? Generating new .tjp content from changes in JIRA is possible (though the output is ugly), but using the .tjp as the sourcefile from which to push to JIRA is also possible. Benefits to flowing from JIRA -> PP: pretty web UI for updating JIRA; many people can edit this way (and we can script it too) Benefits to flowing from PP -> JIRA: controlled from a single sourcefile, which is editable by only PgM So is it better to have more control, or more flexibilty? > create python tooling to create new milestone targets in JBIDE/JBDS > ------------------------------------------------------------------- > > Key: JBIDE-18736 > URL: https://issues.jboss.org/browse/JBIDE-18736 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build > Affects Versions: 4.2.0.Final > Reporter: Nick Boldt > > When the calendar is updated every two weeks to add a new sprint (or simply to add new milestones), we want to be able to update product pages .tjp schedule file [1]; commit to CVS; & run docbot build. > [1] http://cvs.devel.redhat.com/cgi-bin/cvsweb.cgi/program/jbds/jbds-8-0-0/jb... > As part of that build, we can now > * generate updated Zimbra calendar > * generate new PP [2] > [2] https://pp.engineering.redhat.com/pp/product/jbds/release/jbds-8-0.0/over... > In addition, we would like to be able to update JBIDE/JBDS milestones in JIRA. > This can be done programmatically via JIRA REST api, using a POST to /rest/api/2/version ( https://issues.jboss.org/rest/api/2/version ) > Doc: https://docs.atlassian.com/jira/REST/latest/#d2e2421 -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18736) create python tooling to create new milestone targets in JBIDE/JBDS

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18736?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-18736: ------------------------------- Description: When the calendar is updated every two weeks to add a new sprint (or simply to add new milestones), we want to be able to update product pages .tjp schedule file [1]; commit to CVS; & run docbot build. [1] http://cvs.devel.redhat.com/cgi-bin/cvsweb.cgi/program/jbds/jbds-8-0-0/jb... As part of that build, we can now * generate updated Zimbra calendar * generate new PP [2] [2] https://pp.engineering.redhat.com/pp/product/jbds/release/jbds-8-0.0/over... In addition, we would like to be able to update JBIDE/JBDS milestones in JIRA. This can be done programmatically via JIRA REST api, using a POST to /rest/api/2/version ( https://issues.jboss.org/rest/api/2/version ) Doc: https://docs.atlassian.com/jira/REST/latest/#d2e2421 was: When the calendar is updated every two weeks to add a new sprint, we want to be able to update product pages .tjp schedule file; commit to CVS; & run docbot build. As part of that build, we can now * generate updated Zimbra calendar * generate new PP In addition, we would like to be able to update JBIDE/JBDS milestones in JIRA. This can be done programmatically via JIRA REST api, using a POST to /rest/api/2/version ( https://issues.jboss.org/rest/api/2/version ) Doc: https://docs.atlassian.com/jira/REST/latest/#d2e2421 > create python tooling to create new milestone targets in JBIDE/JBDS > ------------------------------------------------------------------- > > Key: JBIDE-18736 > URL: https://issues.jboss.org/browse/JBIDE-18736 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build > Affects Versions: 4.2.0.Final > Reporter: Nick Boldt > > When the calendar is updated every two weeks to add a new sprint (or simply to add new milestones), we want to be able to update product pages .tjp schedule file [1]; commit to CVS; & run docbot build. > [1] http://cvs.devel.redhat.com/cgi-bin/cvsweb.cgi/program/jbds/jbds-8-0-0/jb... > As part of that build, we can now > * generate updated Zimbra calendar > * generate new PP [2] > [2] https://pp.engineering.redhat.com/pp/product/jbds/release/jbds-8-0.0/over... > In addition, we would like to be able to update JBIDE/JBDS milestones in JIRA. > This can be done programmatically via JIRA REST api, using a POST to /rest/api/2/version ( https://issues.jboss.org/rest/api/2/version ) > Doc: https://docs.atlassian.com/jira/REST/latest/#d2e2421 -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18736) create python tooling to create new milestone targets in JBIDE/JBDS

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18736?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-18736: ------------------------------- Summary: create python tooling to create new milestone targets in JBIDE/JBDS (was: create python tooling to create new sprint/milestone targets in JBIDE/JBDS) > create python tooling to create new milestone targets in JBIDE/JBDS > ------------------------------------------------------------------- > > Key: JBIDE-18736 > URL: https://issues.jboss.org/browse/JBIDE-18736 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build > Affects Versions: 4.2.0.Final > Reporter: Nick Boldt > > When the calendar is updated every two weeks to add a new sprint, we want to be able to update product pages .tjp schedule file; commit to CVS; & run docbot build. > As part of that build, we can now > * generate updated Zimbra calendar > * generate new PP > In addition, we would like to be able to update JBIDE/JBDS milestones in JIRA. > This can be done programmatically via JIRA REST api, using a POST to /rest/api/2/version ( https://issues.jboss.org/rest/api/2/version ) > Doc: https://docs.atlassian.com/jira/REST/latest/#d2e2421 -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17696) Enabling Maven Dependency Management job waits forever

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17696?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-17696: ------------------------------- Sprint: Sprint Beta2 CF, Sprint to CR1 Release (was: Sprint to CR1 Release) > Enabling Maven Dependency Management job waits forever > ------------------------------------------------------ > > Key: JBIDE-17696 > URL: https://issues.jboss.org/browse/JBIDE-17696 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven > Affects Versions: 4.2.0.Beta2 > Environment: OpenJDK 1.7, 64b > Ubuntu 12.04, 64b > Reporter: Rastislav Wagner > Assignee: Denis Golovin > Fix For: 4.2.1.Final, 4.3.0.Alpha1 > > Attachments: .options, jstack1.out, jstack2.out, jstack_mvn.out, mvn.png, wait1.png, wait2.png > > > I dont have exact steps to reproduce because this usually occurs after longer work. I'm testing various configurators (CDI/Seam/JAXRS..) using this scenario: > 1. Create Dynamic Web Project > 2. Convert to maven project (using Configure -> Convert to maven..) > 3. Add some dependency > 4. check if proper facet was enabled > 5. delete project and repeat > After trying this 10-15 times (sometimes more, sometimes less), during step 2 "Enabling Maven Dependency Management" job is waiting and never ends - see screenshot - there's always "Setting classpath containers". > JVM thread dump attached. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18055) NullPionterException in VPE Preview Editor initialization

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18055?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-18055: ------------------------------- Sprint: Sprint Beta2 CF, Sprint to CR1 Release (was: Sprint to CR1 Release) > NullPionterException in VPE Preview Editor initialization > --------------------------------------------------------- > > Key: JBIDE-18055 > URL: https://issues.jboss.org/browse/JBIDE-18055 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: visual-page-editor-core > Affects Versions: 4.2.0.Beta3 > Reporter: Denis Golovin > Assignee: Konstantin Marmalyukov > Priority: Minor > Fix For: 4.3.0.Alpha1 > > > Exception below can happen sometimes in case re-sizing visual preview part while preview server serving the editor is not started yet. > {code}java.lang.NullPointerException > at org.jboss.tools.vpe.preview.core.server.VpvServer.getPort(VpvServer.java:66) > at org.jboss.tools.vpe.preview.editor.VpvEditor.formRequestToServer(VpvEditor.java:503) > at org.jboss.tools.vpe.preview.editor.VpvEditor.reload(VpvEditor.java:494) > at org.jboss.tools.vpe.preview.editor.VpvEditorPart.updateVisualEditorVisibility(VpvEditorPart.java:769) > at org.jboss.tools.vpe.preview.editor.VpvEditorPart$5.controlResized(VpvEditorPart.java:386) > at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:235) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4486) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1388) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1412) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1393) > at org.eclipse.swt.widgets.Control.setBounds(Control.java:1042) > at org.eclipse.swt.widgets.Composite.setBounds(Composite.java:1435) > at org.eclipse.swt.widgets.Control.setBounds(Control.java:851) > at org.eclipse.swt.custom.SashForm.onDragSash(SashForm.java:288) > at org.eclipse.swt.custom.SashForm$1.handleEvent(SashForm.java:90) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4486) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1388) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1412) > at org.eclipse.swt.widgets.Widget.sendSelectionEvent(Widget.java:1526) > at org.eclipse.swt.widgets.Sash.gtk_motion_notify_event(Sash.java:396) > at org.eclipse.swt.widgets.Widget.windowProc(Widget.java:2104) > at org.eclipse.swt.widgets.Control.windowProc(Control.java:5510) > at org.eclipse.swt.widgets.Display.windowProc(Display.java:4700) > at org.eclipse.swt.internal.gtk.OS._gtk_main_do_event(Native Method) > at org.eclipse.swt.internal.gtk.OS.gtk_main_do_event(OS.java:9074) > at org.eclipse.swt.widgets.Display.eventProc(Display.java:1253) > at org.eclipse.swt.internal.gtk.OS._g_main_context_iteration(Native Method) > at org.eclipse.swt.internal.gtk.OS.g_main_context_iteration(OS.java:2473) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3439) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1151) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1032) > at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:148) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:636) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:579) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150) > at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:135) > at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:382) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:236) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603) > at org.eclipse.equinox.launcher.Main.run(Main.java:1465) > at org.eclipse.equinox.launcher.Main.main(Main.java:1438) > {code} -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2635) Installation sometimes fail with bundle was not found on Windows

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2635?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-2635: ----------------------------- Sprint: Sprint Beta2 CF, Sprint to CR1 Release (was: Sprint to CR1 Release) > Installation sometimes fail with bundle was not found on Windows > ---------------------------------------------------------------- > > Key: JBDS-2635 > URL: https://issues.jboss.org/browse/JBDS-2635 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 7.0.0.Beta1 > Environment: JBDS 7.0.0.Beta1, W8_64, Java 1.7.0_07 > Reporter: Jiri Peterka > Assignee: Denis Golovin > Fix For: 9.0.0.Alpha1 > > Attachments: 1369261136479.log, 1372203584223.log, 1372203590931.bak_0.log, 1372203590931.bak_1.log, 1372203590931.bak_2.log, 1372203590931.log, 1372355790692.log > > > For the first time JBDS 7.0.0.Beta1 failed on windows8: > {code} > An error occurred while installing the items > session context was:(profile=jbds, phase=org.eclipse.equinox.internal.p2.engine.phases.Install, operand=null --> [R]org.eclipse.jst.common.frameworks 1.1.601.v201208160700, action=org.eclipse.equinox.internal.p2.touchpoint.eclipse.actions.InstallBundleAction). > The artifact file for osgi.bundle,org.eclipse.jst.common.frameworks,1.1.601.v201208160700 was not found. > Application failed, log file location: C:\vw\jbds-7.0.0-beta1\studio\p2\director\configuration\1369261136579.log > {code} -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3004) UnInstaller should have the same application icon as JBoss Developer Studio and appropriate name

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3004?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3004: ----------------------------- Sprint: Sprint Beta2 CF, Sprint to CR1 Release (was: Sprint to CR1 Release) > UnInstaller should have the same application icon as JBoss Developer Studio and appropriate name > ------------------------------------------------------------------------------------------------ > > Key: JBDS-3004 > URL: https://issues.jboss.org/browse/JBDS-3004 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: installer > Reporter: Vlado Pakan > Assignee: Denis Golovin > Priority: Minor > Fix For: 8.0.x > > > See linked Jira about installer icon. I think we should apply the same to Uninstaller icon. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3067) Use JBDevStudio.icns with higher resolution on mac

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3067?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3067: ----------------------------- Sprint: Sprint Beta2 CF, Sprint to CR1 Release (was: Sprint to CR1 Release) > Use JBDevStudio.icns with higher resolution on mac > -------------------------------------------------- > > Key: JBDS-3067 > URL: https://issues.jboss.org/browse/JBDS-3067 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Components: installer > Environment: Mac OS X 10.9.3 (Mavericks) > Reporter: Denis Golovin > Assignee: Daniel Azarov > Priority: Minor > Fix For: 9.0.0.Alpha1 > > Attachments: jbds-in-finder.png > > > Current icon resolution is too low and looks like this > !jbds-in-finder.png! -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 5 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 November 2014