September 2015 - jbosstools-issues

[JBoss JIRA] (JBIDE-20833) Version of playground plugins is CR2 instead of Final

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20833?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-20833: ---------------------------------------- No, it's not a blocker IMO. > Version of playground plugins is CR2 instead of Final > ----------------------------------------------------- > > Key: JBIDE-20833 > URL: https://issues.jboss.org/browse/JBIDE-20833 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: easymport, playground > Affects Versions: 4.3.0.CR2 > Reporter: Lucia Jelinkova > Assignee: Nick Boldt > Priority: Critical > > All plugins in JBT CR2 build have Final version, except for Easymport: > org.jboss.tools.playground.easymport.jee_1.0.0.CR2-v20150924-2213-B23.jar > org.jboss.tools.playground.easymport.maven_1.0.0.CR2-v20150924-2213-B23.jar -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20833) Version of playground plugins is CR2 instead of Final

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20833?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-20833: -------------------------------------- Assignee: Nick Boldt > Version of playground plugins is CR2 instead of Final > ----------------------------------------------------- > > Key: JBIDE-20833 > URL: https://issues.jboss.org/browse/JBIDE-20833 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: easymport, playground > Affects Versions: 4.3.0.CR2 > Reporter: Lucia Jelinkova > Assignee: Nick Boldt > Priority: Critical > > All plugins in JBT CR2 build have Final version, except for Easymport: > org.jboss.tools.playground.easymport.jee_1.0.0.CR2-v20150924-2213-B23.jar > org.jboss.tools.playground.easymport.maven_1.0.0.CR2-v20150924-2213-B23.jar -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19952) v3 Application wizard: Template label decorators don't go away

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19952?page=com.atlassian.jira.plugi... ] Snjezana Peco commented on JBIDE-19952: --------------------------------------- [~adietish] You are right. I have created https://bugs.eclipse.org/bugs/show_bug.cgi?id=478618. > v3 Application wizard: Template label decorators don't go away > -------------------------------------------------------------- > > Key: JBIDE-19952 > URL: https://issues.jboss.org/browse/JBIDE-19952 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Jeff Cantrill > Assignee: Snjezana Peco > Priority: Minor > Labels: application_wizard, openshift_v3 > Fix For: 4.3.0.CR1 > > Attachments: additional-error-marker.png, inital_opeon_on_linux.png, Resource Label dialog.png, validators.png > > > While adding a new label when creating a template, the validation decorator persists and sometime the validation message even for valid labels. See attachment. > Also, noticed focusing away from dialog and back makes them go away. Repainting issue? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20687) Deployed war is NOT the specified war name

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20687?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-20687: ------------------------------------- Yes a fix will be released for Mars.2. I just haven't decided yet if it'll be 1.3.0 or 1.2.2. > Deployed war is NOT the specified war name > ------------------------------------------ > > Key: JBIDE-20687 > URL: https://issues.jboss.org/browse/JBIDE-20687 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven, server, upstream > Affects Versions: 4.3.0.CR1 > Reporter: ehsavoie Hugonnet > Assignee: Fred Bricon > Priority: Critical > Fix For: 4.3.1.Final > > > The deployed war name is the *artifactId* and not the specified *warName* from the war plugin nor the *finalName*. > Sample pom.xml which exibits the issue > {code:xml}<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd"> > <modelVersion>4.0.0</modelVersion> > <groupId>org.glassfish-samples</groupId> > <artifactId>auction</artifactId> > <version>4.0-SNAPSHOT</version> > <packaging>war</packaging> > <name>WebSocket Auction Sample Application</name> > > <dependencies> > <dependency> > <groupId>javax</groupId> > <artifactId>javaee-api</artifactId> > <version>7.0</version> > <scope>provided</scope> > </dependency> > </dependencies> > > <build> > <finalName>websocket-auction</finalName> > <plugins> > <plugin> > <artifactId>maven-compiler-plugin</artifactId> > <version>3.1</version> > <configuration> > <source>1.8</source> > <target>1.8</target> > </configuration> > </plugin> > <plugin> > <groupId>org.apache.maven.plugins</groupId> > <artifactId>maven-war-plugin</artifactId> > <version>2.3</version> > <configuration> > <failOnMissingWebXml>false</failOnMissingWebXml> > <warName>websocket-auction</warName> > </configuration> > </plugin> > </plugins> > </build> > </project> > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20834) Fix issues with styled label providers

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20834?page=com.atlassian.jira.plugi... ] Snjezana Peco reassigned JBIDE-20834: ------------------------------------- Assignee: Andre Dietisheim (was: Snjezana Peco) Could you, please, review the PR. > Fix issues with styled label providers > -------------------------------------- > > Key: JBIDE-20834 > URL: https://issues.jboss.org/browse/JBIDE-20834 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift, upstream > Affects Versions: 4.3.0.CR1 > Reporter: Snjezana Peco > Assignee: Andre Dietisheim > > Since https://bugs.eclipse.org/bugs/show_bug.cgi?id=466499 has been fixed, we can remove the workaround related to styled label providers. > The fix is included in Mars 4.5.1 (Mars.1) and Neon 4.6.0M2. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3532) Installer and updatesite-core zip contain different timestamps for JBDS product IU

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBDS-3532?page=com.atlassian.jira.plugin.... ] Mickael Istria commented on JBDS-3532: -------------------------------------- The issue is in the Jenkins job configuration of devstudio-product_9.0.mars: Once the build completed and installer zip is created, we call "mvn deploy" a 2nd time on the site in order to publish it to devstudio.redhat.com. As a consequence the site is rebuild, and the unit for product is re-created, with a newer timestamp. We need to figure out a way to only run the deploy phase, skipping the package part. > Installer and updatesite-core zip contain different timestamps for JBDS product IU > ---------------------------------------------------------------------------------- > > Key: JBDS-3532 > URL: https://issues.jboss.org/browse/JBDS-3532 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: updatesite > Affects Versions: 9.0.0.CR2 > Environment: jboss-devstudio-9.0.0.GA-v20150925-1252-B116-installer-standalone.jar > jboss-devstudio-9.0.0.GA-v20150925-1252-B116-updatesite-core.zip > downloaded from > http://www.qa.jboss.com/binaries/RHDS/9.0/staging/builds/devstudio-9.0.0.... > Reporter: Jan Richter > Priority: Blocker > > The updatesite zip has a later timestamp than what you get from the installer but it is still the same build. So you can basically update to the same build because of that. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20834) Fix issues with styled label providers

by Snjezana Peco (JIRA)

Snjezana Peco created JBIDE-20834: ------------------------------------- Summary: Fix issues with styled label providers Key: JBIDE-20834 URL: https://issues.jboss.org/browse/JBIDE-20834 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift, upstream Affects Versions: 4.3.0.CR1 Reporter: Snjezana Peco Assignee: Snjezana Peco Since https://bugs.eclipse.org/bugs/show_bug.cgi?id=466499 has been fixed, we can remove the workaround related to styled label providers. The fix is included in Mars 4.5.1 (Mars.1) and Neon 4.6.0M2. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19536) Infinite job loop when creating project

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19536?page=com.atlassian.jira.plugi... ] Snjezana Peco commented on JBIDE-19536: --------------------------------------- [~rawagner] I can reproduce the issue in Mars 4.5.1 when using your workspace. The patch fixes it. > Infinite job loop when creating project > --------------------------------------- > > Key: JBIDE-19536 > URL: https://issues.jboss.org/browse/JBIDE-19536 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdi, upstream > Affects Versions: 4.3.0.Alpha1 > Reporter: Rastislav Wagner > Assignee: Snjezana Peco > Priority: Critical > Fix For: 4.3.1.Final, 4.4.0.Alpha1 > > Attachments: building.png, cdi_jstack, jstack.out, threaddump-1440009974151.tdump, threaddump-1440009999047.tdump, threaddump-1440010035476.tdump, workspace_jbds9_endless_building_loop.rar > > > Sometimes i end up in infinite job loop after creating a CDI project. There's no description of what jobs are running, not exception in log. In progress view I can see only "Building workspace (sleeping)" -see on video https://vimeo.com/123634974 > I was able to reproduce on CDI projects (1.0,1.2) but not on any other (Dynamic Web..) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20690) DnD over VPE source part fails under Mac OS X and partially frozen UI

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20690?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-20690. --------------------------------- Verified in JBDS 9.0.0.CR2 B116 > DnD over VPE source part fails under Mac OS X and partially frozen UI > --------------------------------------------------------------------- > > Key: JBIDE-20690 > URL: https://issues.jboss.org/browse/JBIDE-20690 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsp/jsf/xml/html-source-editing > Affects Versions: 4.3.0.CR1 > Environment: Mac OS X 10.10.3 x86_64 > Reporter: Denis Golovin > Assignee: Denis Golovin > Priority: Blocker > Fix For: 4.3.0.CR2 > > > Exception happens when project is dragged over VPE source part. > {code}java.lang.IllegalArgumentException: Index out of bounds > at org.eclipse.swt.SWT.error(SWT.java:4472) > at org.eclipse.swt.SWT.error(SWT.java:4406) > at org.eclipse.swt.SWT.error(SWT.java:4377) > at org.eclipse.swt.custom.StyledText.getLocationAtOffset(StyledText.java:4372) > at org.jboss.tools.jst.web.ui.internal.editor.jspeditor.xpl.StyledTextDropTargetEffect.dragOver(StyledTextDropTargetEffect.java:157) > at org.eclipse.swt.dnd.DNDListener.handleEvent(DNDListener.java:84) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4230) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1491) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1514) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1499) > at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1299) > at org.eclipse.swt.dnd.DropTarget.draggingUpdated(DropTarget.java:319) > at org.eclipse.swt.dnd.DropTarget.dropTargetProc(DropTarget.java:452) > at org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method) > at org.eclipse.swt.widgets.Widget.callSuper(Widget.java:227) > at org.eclipse.swt.widgets.Widget.mouseDownSuper(Widget.java:1121) > at org.eclipse.swt.widgets.Tree.mouseDownSuper(Tree.java:2047) > at org.eclipse.swt.widgets.Widget.mouseDown(Widget.java:1113) > at org.eclipse.swt.widgets.Control.mouseDown(Control.java:2569) > at org.eclipse.swt.widgets.Tree.mouseDown(Tree.java:2015) > at org.eclipse.swt.widgets.Display.windowProc(Display.java:5692) > at org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method) > at org.eclipse.swt.widgets.Widget.callSuper(Widget.java:227) > at org.eclipse.swt.widgets.Widget.windowSendEvent(Widget.java:2130) > at org.eclipse.swt.widgets.Shell.windowSendEvent(Shell.java:2337) > at org.eclipse.swt.widgets.Display.windowProc(Display.java:5756) > at org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method) > at org.eclipse.swt.widgets.Display.applicationSendEvent(Display.java:5193) > at org.eclipse.swt.widgets.Display.applicationProc(Display.java:5342) > at org.eclipse.swt.internal.cocoa.OS.objc_msgSend(Native Method) > at org.eclipse.swt.internal.cocoa.NSApplication.sendEvent(NSApplication.java:128) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3695) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1127) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1018) > at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:654) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:598) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150) > at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:139) > 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:380) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:669) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:608) > at org.eclipse.equinox.launcher.Main.run(Main.java:1515){code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3532) Installer and updatesite-core zip contain different timestamps for JBDS product IU

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-3532?page=com.atlassian.jira.plugin.... ] Jan Richter commented on JBDS-3532: ----------------------------------- It's not something I would normally check. I found this after I added the zip to the update sites and 'Update available' came up. And I just tested this in 8.1.0.GA - it's not affected by this issue. > Installer and updatesite-core zip contain different timestamps for JBDS product IU > ---------------------------------------------------------------------------------- > > Key: JBDS-3532 > URL: https://issues.jboss.org/browse/JBDS-3532 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: updatesite > Affects Versions: 9.0.0.CR2 > Environment: jboss-devstudio-9.0.0.GA-v20150925-1252-B116-installer-standalone.jar > jboss-devstudio-9.0.0.GA-v20150925-1252-B116-updatesite-core.zip > downloaded from > http://www.qa.jboss.com/binaries/RHDS/9.0/staging/builds/devstudio-9.0.0.... > Reporter: Jan Richter > Priority: Blocker > > The updatesite zip has a later timestamp than what you get from the installer but it is still the same build. So you can basically update to the same build because of that. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 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 September 2015