January 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-19039) Window size shouldn't be computed proportionally to 'display' size but rather aligned with the components

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19039?page=com.atlassian.jira.plugi... ] Len DiMaggio reassigned JBIDE-19039: ------------------------------------ Assignee: Snjezana Peco > Window size shouldn't be computed proportionally to 'display' size but rather aligned with the components > --------------------------------------------------------------------------------------------------------- > > Key: JBIDE-19039 > URL: https://issues.jboss.org/browse/JBIDE-19039 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.2.2.Final > Reporter: Pavol Srna > Assignee: Snjezana Peco > Attachments: forge-scaffold-window.png, other-wizard.png > > > Wizard window size shouldn't be computed proportionally to 'display' size. But instead it should be aligned with the components that are in the wizard. > You can see on the screenshots how it looks when you have your monitor in portrait orientation. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19040) Software update: Item hidden under table header

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19040?page=com.atlassian.jira.plugi... ] Len DiMaggio reassigned JBIDE-19040: ------------------------------------ Assignee: Nick Boldt > Software update: Item hidden under table header > ----------------------------------------------- > > Key: JBIDE-19040 > URL: https://issues.jboss.org/browse/JBIDE-19040 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: upstream > Affects Versions: 4.2.2.Final > Reporter: Martin Malina > Assignee: Nick Boldt > Attachments: update-hidden.png, update-shown.png > > > This is probably an upstream issue and I'm not sure if/how much we can do here. But I'd like to have this reported anyway. > When JBDS notifies me of updates and I want to install the updates, the "Available Updates" window seems empty: > !update-hidden.png! > What's happening is that there is only one item and it's hidden at the very top behind the table header. With my mouse, I can scroll to see it: > !update-shown.png! > What's worse, the hidden item can only be made visible by scrolling a mouse, not using touchpad. So unless I have a mouse connected, I'm out of luck. > This happens in other places as well, notably in the software update sites page in Preferences. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19051) Show warning in case of ambiguous RESTful web services path

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19051?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-19051: -------------------------------------- Assignee: Xavier Coulon > Show warning in case of ambiguous RESTful web services path > ----------------------------------------------------------- > > Key: JBIDE-19051 > URL: https://issues.jboss.org/browse/JBIDE-19051 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: webservices > Affects Versions: 4.2.2.Final > Reporter: Marián Labuda > Assignee: Xavier Coulon > Priority: Minor > Labels: jax-rs > > If I have two classes which both follow same structure and there are some JAX-RS web services mapping to same path in JAX-RS Web Services node in Project Explorer, there should be warning on both such places where it occurs and in Problems view. Warning should be about ambigous path for JAX-RS web services. > It's possible to have multiple items under JAX-RS Web Services node with same label. > Even though there are strategies to resolve order of evaluating path, there could be some cases where it's not enough. And such solution could help developer to find out if there are such flaws in design. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19051) Show warning in case of ambiguous RESTful web services path

by Marián Labuda (JIRA)

Marián Labuda created JBIDE-19051: ------------------------------------- Summary: Show warning in case of ambiguous RESTful web services path Key: JBIDE-19051 URL: https://issues.jboss.org/browse/JBIDE-19051 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: webservices Affects Versions: 4.2.2.Final Reporter: Marián Labuda Priority: Minor If I have two classes which both follow same structure and there are some JAX-RS web services mapping to same path in JAX-RS Web Services node in Project Explorer, there should be warning on both such places where it occurs and in Problems view. Warning should be about ambigous path for JAX-RS web services. It's possible to have multiple items under JAX-RS Web Services node with same label e.g. "/rest/vehicle/{id:long}". Even though there are strategies to resolve order of evaluating path, there could be some cases where it's not enough. And such solution could help developer to find out if there are such flaws in design. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-384) Cannot install all BPMN2 features from JBDS-IS 8.0.0.CR1-earlyaccess into JBDS-IS 8.0.0.Beta2a

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-384?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky commented on JBTIS-384: ----------------------------------------- I think it would be good to document it. > Cannot install all BPMN2 features from JBDS-IS 8.0.0.CR1-earlyaccess into JBDS-IS 8.0.0.Beta2a > ---------------------------------------------------------------------------------------------- > > Key: JBTIS-384 > URL: https://issues.jboss.org/browse/JBTIS-384 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 8.0.0.CR1 > Reporter: Andrej Podhradsky > Priority: Minor > > If you try to install all BPMN2 features from JBDS-IS 8.0.0.CR1-earlyaccess to the IDE with already installed BPMN2 features from JBDS-IS 8.0.0.Beta2a then you will get the following error > Cannot complete the install because of a conflicting dependency. > Software being installed: BPMN2 Metamodel 1.0.0.201412192138 (org.eclipse.bpmn2.feature.group 1.0.0.201412192138) > Software currently installed: BPMN2 Project Feature 0.7.0.201308220617 (org.eclipse.bpmn2.feature.feature.group 0.7.0.201308220617) > Only one of the following can be installed at once: > BPMN2 Model 0.7.0.201308220617 (org.eclipse.bpmn2 0.7.0.201308220617) > BPMN2 Model 1.0.0.201412192138 (org.eclipse.bpmn2 1.0.0.201412192138) > Cannot satisfy dependency: > From: BPMN2 Project Feature 0.7.0.201308220617 (org.eclipse.bpmn2.feature.feature.group 0.7.0.201308220617) > To: org.eclipse.bpmn2 [0.7.0.201308220617] > Cannot satisfy dependency: > From: BPMN2 Metamodel 1.0.0.201412192138 (org.eclipse.bpmn2.feature.group 1.0.0.201412192138) > To: org.eclipse.bpmn2 [1.0.0.201412192138] > This is caused by renaming org.eclipse.bpmn2.feature to org.eclipse.bpmn2 (without "feature" suffix). -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19051) Show warning in case of ambiguous RESTful web services path

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19051?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-19051: ---------------------------------- Labels: jax-rs (was: ) > Show warning in case of ambiguous RESTful web services path > ----------------------------------------------------------- > > Key: JBIDE-19051 > URL: https://issues.jboss.org/browse/JBIDE-19051 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: webservices > Affects Versions: 4.2.2.Final > Reporter: Marián Labuda > Priority: Minor > Labels: jax-rs > > If I have two classes which both follow same structure and there are some JAX-RS web services mapping to same path in JAX-RS Web Services node in Project Explorer, there should be warning on both such places where it occurs and in Problems view. Warning should be about ambigous path for JAX-RS web services. > It's possible to have multiple items under JAX-RS Web Services node with same label e.g. "/rest/vehicle/{id:long}". > Even though there are strategies to resolve order of evaluating path, there could be some cases where it's not enough. And such solution could help developer to find out if there are such flaws in design. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19051) Show warning in case of ambiguous RESTful web services path

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19051?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-19051: ---------------------------------- Description: If I have two classes which both follow same structure and there are some JAX-RS web services mapping to same path in JAX-RS Web Services node in Project Explorer, there should be warning on both such places where it occurs and in Problems view. Warning should be about ambigous path for JAX-RS web services. It's possible to have multiple items under JAX-RS Web Services node with same label. Even though there are strategies to resolve order of evaluating path, there could be some cases where it's not enough. And such solution could help developer to find out if there are such flaws in design. was: If I have two classes which both follow same structure and there are some JAX-RS web services mapping to same path in JAX-RS Web Services node in Project Explorer, there should be warning on both such places where it occurs and in Problems view. Warning should be about ambigous path for JAX-RS web services. It's possible to have multiple items under JAX-RS Web Services node with same label e.g. "/rest/vehicle/{id:long}". Even though there are strategies to resolve order of evaluating path, there could be some cases where it's not enough. And such solution could help developer to find out if there are such flaws in design. > Show warning in case of ambiguous RESTful web services path > ----------------------------------------------------------- > > Key: JBIDE-19051 > URL: https://issues.jboss.org/browse/JBIDE-19051 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: webservices > Affects Versions: 4.2.2.Final > Reporter: Marián Labuda > Priority: Minor > Labels: jax-rs > > If I have two classes which both follow same structure and there are some JAX-RS web services mapping to same path in JAX-RS Web Services node in Project Explorer, there should be warning on both such places where it occurs and in Problems view. Warning should be about ambigous path for JAX-RS web services. > It's possible to have multiple items under JAX-RS Web Services node with same label. > Even though there are strategies to resolve order of evaluating path, there could be some cases where it's not enough. And such solution could help developer to find out if there are such flaws in design. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-384) Cannot install all BPMN2 features from JBDS-IS 8.0.0.CR1-earlyaccess into JBDS-IS 8.0.0.Beta2a

by Andrej Podhradsky (JIRA)

Andrej Podhradsky created JBTIS-384: --------------------------------------- Summary: Cannot install all BPMN2 features from JBDS-IS 8.0.0.CR1-earlyaccess into JBDS-IS 8.0.0.Beta2a Key: JBTIS-384 URL: https://issues.jboss.org/browse/JBTIS-384 Project: JBoss Tools Integration Stack Issue Type: Bug Components: distribution Affects Versions: 8.0.0.CR1 Reporter: Andrej Podhradsky Priority: Minor If you try to install all BPMN2 features from JBDS-IS 8.0.0.CR1-earlyaccess to the IDE with already installed BPMN2 features from JBDS-IS 8.0.0.Beta2a then you will get the following error Cannot complete the install because of a conflicting dependency. Software being installed: BPMN2 Metamodel 1.0.0.201412192138 (org.eclipse.bpmn2.feature.group 1.0.0.201412192138) Software currently installed: BPMN2 Project Feature 0.7.0.201308220617 (org.eclipse.bpmn2.feature.feature.group 0.7.0.201308220617) Only one of the following can be installed at once: BPMN2 Model 0.7.0.201308220617 (org.eclipse.bpmn2 0.7.0.201308220617) BPMN2 Model 1.0.0.201412192138 (org.eclipse.bpmn2 1.0.0.201412192138) Cannot satisfy dependency: From: BPMN2 Project Feature 0.7.0.201308220617 (org.eclipse.bpmn2.feature.feature.group 0.7.0.201308220617) To: org.eclipse.bpmn2 [0.7.0.201308220617] Cannot satisfy dependency: From: BPMN2 Metamodel 1.0.0.201412192138 (org.eclipse.bpmn2.feature.group 1.0.0.201412192138) To: org.eclipse.bpmn2 [1.0.0.201412192138] This is caused by renaming org.eclipse.bpmn2.feature to org.eclipse.bpmn2 (without "feature" suffix). -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19050) BrowserSim will not start with Oracle JDK 9 EA

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19050?page=com.atlassian.jira.plugi... ] Martin Malina updated JBIDE-19050: ---------------------------------- Attachment: jdk9-mac-paths.txt [~kmarmaliykov], I'm attaching a file with all the paths: jdk9-mac-paths.txt > BrowserSim will not start with Oracle JDK 9 EA > ---------------------------------------------- > > Key: JBIDE-19050 > URL: https://issues.jboss.org/browse/JBIDE-19050 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: browsersim > Affects Versions: 4.2.2.Final > Reporter: Martin Malina > Assignee: Konstantin Marmalyukov > Fix For: 4.3.0.Alpha1 > > Attachments: jdk9-mac-paths.txt > > > Today I briefly tried out Oracle JDK 9 Early Access from here: > https://jdk9.java.net/download/ > {code} > nattura:8.0.2 rasp$ java -version > java version "1.9.0-ea" > Java(TM) SE Runtime Environment (build 1.9.0-ea-b45) > Java HotSpot(TM) 64-Bit Server VM (build 1.9.0-ea-b45, mixed mode) > {code} > When I had JBDS 8.0.2 running with this Java and then clicked the BrowserSim button, I got this error: > {code} > javafx/embed/swt/FXCanvas > Stack trace: > java.lang.NoClassDefFoundError: javafx/embed/swt/FXCanvas > at java.lang.ClassLoader.defineClass1(Native Method) > at java.lang.ClassLoader.defineClass(ClassLoader.java:759) > at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142) > at java.net.URLClassLoader.defineClass(URLClassLoader.java:467) > at java.net.URLClassLoader.access$100(URLClassLoader.java:73) > at java.net.URLClassLoader$1.run(URLClassLoader.java:368) > at java.net.URLClassLoader$1.run(URLClassLoader.java:362) > at java.security.AccessController.doPrivileged(Native Method) > at java.net.URLClassLoader.findClass(URLClassLoader.java:361) > at java.lang.ClassLoader.loadClass(ClassLoader.java:423) > at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:262) > at java.lang.ClassLoader.loadClass(ClassLoader.java:356) > at org.jboss.tools.vpe.browsersim.browser.WebKitBrowserFactory.createBrowser(WebKitBrowserFactory.java:28) > at org.jboss.tools.vpe.browsersim.ui.skin.ResizableSkin.createControls(ResizableSkin.java:92) > at org.jboss.tools.vpe.browsersim.ui.BrowserSim.initSkin(BrowserSim.java:183) > at org.jboss.tools.vpe.browsersim.ui.BrowserSim.open(BrowserSim.java:162) > at org.jboss.tools.vpe.browsersim.ui.BrowserSim.open(BrowserSim.java:137) > at org.jboss.tools.vpe.browsersim.BrowserSimRunner.main(BrowserSimRunner.java:105) > Caused by: java.lang.ClassNotFoundException: javafx.embed.swt.FXCanvas > at java.net.URLClassLoader.findClass(URLClassLoader.java:381) > at java.lang.ClassLoader.loadClass(ClassLoader.java:423) > at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:262) > at java.lang.ClassLoader.loadClass(ClassLoader.java:356) > ... 18 more > {code} > This seems like JavaFX might be missing. But on the download page, there are many mentions of JavaFX, so I'm not sure. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18508) EAR Maven project loses lib/ artifacts deployed to EAP broken after closing/reopening

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18508?page=com.atlassian.jira.plugi... ] Fred Bricon resolved JBIDE-18508. --------------------------------- Resolution: Done Resolving as there won't be an m2e-wtp release for Luna SR2. This issue isn't that severe and there's a workaround. Resolving for 4.3.0.Alpha1 > EAR Maven project loses lib/ artifacts deployed to EAP broken after closing/reopening > ------------------------------------------------------------------------------------- > > Key: JBIDE-18508 > URL: https://issues.jboss.org/browse/JBIDE-18508 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven, upstream > Affects Versions: 4.1.2.Final > Reporter: Marek Schmidt > Assignee: Fred Bricon > Labels: f2f2014 > Fix For: 4.3.0.Alpha1 > > Attachments: seam-restbay-src.zip > > > EAR Maven project loses lib/ artifacts deployed to EAP after closing/reopening > 0. setup the redhat techpreview/all maven repository > 1. Import the (attached) project as Maven project > 2. Deploy the restbay-ear project to EAP 6.2 (or 6.3) > 3. Close all 4 subprojects of the restbay project > 4. reopen all the restbay projects > 5. now the application will automatically redeploy > 6. this redeployment will result in a failure. > If you compare the deployment folders before/after the closing/reopening of the project, you will notice some of the restbay-ear.ear/lib/ libraries are missing. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 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 January 2015