January 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-19136) Missing icon for Import FeedHenry wizard

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19136?page=com.atlassian.jira.plugi... ] Pavol Srna updated JBIDE-19136: ------------------------------- Attachment: missing-icon.png > Missing icon for Import FeedHenry wizard > ---------------------------------------- > > Key: JBIDE-19136 > URL: https://issues.jboss.org/browse/JBIDE-19136 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid > Affects Versions: 4.2.3.Beta1 > Reporter: Pavol Srna > Fix For: 4.2.3.Beta1 > > Attachments: missing-icon.png > > > See screenshot for more information. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-19136) Missing icon for Import FeedHenry wizard

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19136?page=com.atlassian.jira.plugi... ] Pavol Srna updated JBIDE-19136: ------------------------------- Fix Version/s: 4.2.3.Beta1 > Missing icon for Import FeedHenry wizard > ---------------------------------------- > > Key: JBIDE-19136 > URL: https://issues.jboss.org/browse/JBIDE-19136 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid > Affects Versions: 4.2.3.Beta1 > Reporter: Pavol Srna > Fix For: 4.2.3.Beta1 > > Attachments: missing-icon.png > > > See screenshot for more information. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-19061) JAX-RS Web Services node sometimes does not show properly path changes

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19061?page=com.atlassian.jira.plugi... ] Xavier Coulon updated JBIDE-19061: ---------------------------------- Fix Version/s: 4.3.x > JAX-RS Web Services node sometimes does not show properly path changes > ---------------------------------------------------------------------- > > Key: JBIDE-19061 > URL: https://issues.jboss.org/browse/JBIDE-19061 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Affects Versions: 4.2.2.Final > Reporter: Marián Labuda > Assignee: Xavier Coulon > Priority: Minor > Labels: jax-rs > Fix For: 4.3.x > > > If I am using for @PathParam injection of fields, sometimes changes are not shown properly. > First issue is with showing error validation mark. This mark (red cross in left bottom corner of Tree Item) is shown in case of deletion of injection field with their @PathParam annotations. If I have a method annotated with {code}@Path("{first}/{second}"){code} and I have fields annotated @PathParam("first") and @PathParam("second"), after removing those fields (holding backspace or marking whole area and delete) AND not saving opened java file in editor, then the mentioned marker is shown. After saving class, marker is removed, but nothing else is happened, even sometimes there should happen something (e.g. propagating of changes of path params types in real time). > Second issue is showing correctly current content of editor in JAX-RS Web Services node. Sometimes the change are not progapated correctly in real time and type of one or both parameters are not correct. This is related to JBIDE-17663, but work flow in specified JIRA is working for that issue. This is more like "clicking and trying to break it" attempts which lead to inconsistencies. So far I have not noticed something what could me tell specific use case to get broken URI matching patterns in JAX-RS Web Services node. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-19136) Missing icon for Import FeedHenry wizard

by Pavol Srna (JIRA)

Pavol Srna created JBIDE-19136: ---------------------------------- Summary: Missing icon for Import FeedHenry wizard Key: JBIDE-19136 URL: https://issues.jboss.org/browse/JBIDE-19136 Project: Tools (JBoss Tools) Issue Type: Bug Components: aerogear-hybrid Affects Versions: 4.2.3.Beta1 Reporter: Pavol Srna See screenshot for more information. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-19108) Choosing OpenShift Server adapter and then another server in create server wizard list causes impossibility to run server

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19108?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-19108: ------------------------------------------ I can confirm this. It only happens if I first select the OpenShift server adapter in the new server wizard (type) and then switch to the Wildfly server (type). If I go straight to widlfy the bug wont occurr. [~rob.stryker] any thoughts? > Choosing OpenShift Server adapter and then another server in create server wizard list causes impossibility to run server > ------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-19108 > URL: https://issues.jboss.org/browse/JBIDE-19108 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift, server > Affects Versions: 4.2.2.Final > Reporter: Marián Labuda > Attachments: server_already_running.png > > > If I am creating new server in Servers view via New Server wizard and I select in tree at first OpenShift Server Adapter and then e.g. Wildfly 8.x server, then created server cannot be started. There is a warning there there is server running on openshift.redhat.com:8080. User has to delete such server from servers view and create a new one without selecting OpenShift Server Adapter in server type selection. > !server_already_running.png! -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-19108) Choosing OpenShift Server adapter and then another server in create server wizard list causes impossibility to run server

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19108?page=com.atlassian.jira.plugi... ] Andre Dietisheim reassigned JBIDE-19108: ---------------------------------------- Assignee: Andre Dietisheim > Choosing OpenShift Server adapter and then another server in create server wizard list causes impossibility to run server > ------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-19108 > URL: https://issues.jboss.org/browse/JBIDE-19108 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift, server > Affects Versions: 4.2.2.Final > Reporter: Marián Labuda > Assignee: Andre Dietisheim > Attachments: server_already_running.png > > > If I am creating new server in Servers view via New Server wizard and I select in tree at first OpenShift Server Adapter and then e.g. Wildfly 8.x server, then created server cannot be started. There is a warning there there is server running on openshift.redhat.com:8080. User has to delete such server from servers view and create a new one without selecting OpenShift Server Adapter in server type selection. > !server_already_running.png! -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-19108) Choosing OpenShift Server adapter and then another server in create server wizard list causes impossibility to run server

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19108?page=com.atlassian.jira.plugi... ] Andre Dietisheim reassigned JBIDE-19108: ---------------------------------------- Assignee: Rob Stryker (was: Andre Dietisheim) > Choosing OpenShift Server adapter and then another server in create server wizard list causes impossibility to run server > ------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-19108 > URL: https://issues.jboss.org/browse/JBIDE-19108 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift, server > Affects Versions: 4.2.2.Final > Reporter: Marián Labuda > Assignee: Rob Stryker > Attachments: server_already_running.png > > > If I am creating new server in Servers view via New Server wizard and I select in tree at first OpenShift Server Adapter and then e.g. Wildfly 8.x server, then created server cannot be started. There is a warning there there is server running on openshift.redhat.com:8080. User has to delete such server from servers view and create a new one without selecting OpenShift Server Adapter in server type selection. > !server_already_running.png! -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-19108) Choosing OpenShift Server adapter and then another server in create server wizard list causes impossibility to run server

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19108?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19108: ------------------------------------- Steps to Reproduce: 1. EXEC: Open New Server wizard via context menu in Servers view 2. EXEC: Select OpenShift - OpenShift Server Adapter 3. EXEC: Select WildFly 8.x server and proceed through wizard. 4. ASSERT: Server has been creted. 5. EXEC: Start server RESULT: Warning that there is a server running on 8080 is shown. EXPECTED RESULT: Server is started. was: 1. EXEC: Open New Server wizard in Servers view 2. EXEC: Select OpenShift - OpenShift Server Adapter 3. EXEC: Select WildFly 8.x server and proceed through wizard. 4. ASSERT: Server has been creted. 5. EXEC: Start server RESULT: Warning that there is a server running on 8080 is shown. EXPECTED RESULT: Server is started. > Choosing OpenShift Server adapter and then another server in create server wizard list causes impossibility to run server > ------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-19108 > URL: https://issues.jboss.org/browse/JBIDE-19108 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift, server > Affects Versions: 4.2.2.Final > Reporter: Marián Labuda > Attachments: server_already_running.png > > > If I am creating new server in Servers view via New Server wizard and I select in tree at first OpenShift Server Adapter and then e.g. Wildfly 8.x server, then created server cannot be started. There is a warning there there is server running on openshift.redhat.com:8080. User has to delete such server from servers view and create a new one without selecting OpenShift Server Adapter in server type selection. > !server_already_running.png! -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-19025) Separate JBT and JBDS Central and EA sites

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19025?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-19025: ------------------------------- Fix Version/s: 4.3.0.Alpha1 > Separate JBT and JBDS Central and EA sites > ------------------------------------------ > > Key: JBIDE-19025 > URL: https://issues.jboss.org/browse/JBIDE-19025 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: discovery > Affects Versions: 4.2.2.Final > Reporter: Mickael Istria > Fix For: 4.3.0.Alpha1 > > > Currently, we have to repeat (and update very often) some JBT artifacts in the Central .target files because JBDS needs them. > This adds some long steps to the JBT staging process ( https://github.com/jbdevstudio/jbdevstudio-devdoc/blob/master/release_gui... ), whereas this is a JBDS need. > So we should split the content of Central/EA update sites for JBT and JBDS, and have them separated in distinct .target files: a Central/EA couple for JBT and another Central/EA couple for JBDS. JBDS only would add the necessary addition that are part of JBT but not part of JBDS. > Since we're there, it would even be cleaner to have those artifacts in distinct repo, so that JBDS wouldn't leak in JBT. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-19025) Separate JBT and JBDS Central and EA sites

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19025?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-19025: ------------------------------- Affects Version/s: 4.2.2.Final > Separate JBT and JBDS Central and EA sites > ------------------------------------------ > > Key: JBIDE-19025 > URL: https://issues.jboss.org/browse/JBIDE-19025 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: discovery > Affects Versions: 4.2.2.Final > Reporter: Mickael Istria > Fix For: 4.3.0.Alpha1 > > > Currently, we have to repeat (and update very often) some JBT artifacts in the Central .target files because JBDS needs them. > This adds some long steps to the JBT staging process ( https://github.com/jbdevstudio/jbdevstudio-devdoc/blob/master/release_gui... ), whereas this is a JBDS need. > So we should split the content of Central/EA update sites for JBT and JBDS, and have them separated in distinct .target files: a Central/EA couple for JBT and another Central/EA couple for JBDS. JBDS only would add the necessary addition that are part of JBT but not part of JBDS. > Since we're there, it would even be cleaner to have those artifacts in distinct repo, so that JBDS wouldn't leak in JBT. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

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