July 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-17686) get TCF and RSE terminals to coexist without bad UX of multiple terminals

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17686?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-17686: ---------------------------------------- Summary: get TCF and RSE terminals to coexist without bad UX of multiple terminals (was: ensure TCF terminal is in jboss tools/devstudio) changed title since the issue has moved since then. > get TCF and RSE terminals to coexist without bad UX of multiple terminals > ------------------------------------------------------------------------- > > Key: JBIDE-17686 > URL: https://issues.jboss.org/browse/JBIDE-17686 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: target-platform > Affects Versions: 4.2.0.Beta2 > Reporter: Max Rydahl Andersen > Assignee: Max Rydahl Andersen > Fix For: 4.2.0.CR1 > > Attachments: eclipse-can-has-many-consoles.png > > > luna has new Eclipse TCF terminal that brings better Terminal support. > I would assume it is in there but I couldn't find a way to actually open it. Maybe we havent included the full set of plugins. > http://marketplace.eclipse.org/content/tcf-terminals#.U6sJ92Vp7wV > http://eclipsesource.com/blogs/2014/06/17/tcf-terminal-top-eclipse-luna-f... -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-17686) ensure TCF terminal is in jboss tools/devstudio

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17686?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-17686: --------------------------------------------- Yes, you are correct this is the problem and no I do not have a implementation suggestion since I have not looked into the details of how it works. I fear it is not doable. I responded with what I knew and it now turns out TCF and RSE are not done in a coherent way thus this issue cannot be solved trivially. The issue is currently assigned to me to look at. If you want to look that would be great and suggest how to fix on RSE/TCF side that would be great but I do not expect it to be fixed in Luna timeframe at this time. > ensure TCF terminal is in jboss tools/devstudio > ----------------------------------------------- > > Key: JBIDE-17686 > URL: https://issues.jboss.org/browse/JBIDE-17686 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: target-platform > Affects Versions: 4.2.0.Beta2 > Reporter: Max Rydahl Andersen > Assignee: Max Rydahl Andersen > Fix For: 4.2.0.CR1 > > Attachments: eclipse-can-has-many-consoles.png > > > luna has new Eclipse TCF terminal that brings better Terminal support. > I would assume it is in there but I couldn't find a way to actually open it. Maybe we havent included the full set of plugins. > http://marketplace.eclipse.org/content/tcf-terminals#.U6sJ92Vp7wV > http://eclipsesource.com/blogs/2014/06/17/tcf-terminal-top-eclipse-luna-f... -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-14713) jcip.annotations have wrong license in locus

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14713?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-14713: --------------------------------------------- [~b.eckenfels] we dont actually use jcip.annotations outside our test suite and we do obey the license by mentioning it in the feature. Not sure what you mean by "for the AS modules" itself ? we don't use this in any of the jboss server tools plugins. > jcip.annotations have wrong license in locus > -------------------------------------------- > > Key: JBIDE-14713 > URL: https://issues.jboss.org/browse/JBIDE-14713 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build, locus > Reporter: Max Rydahl Andersen > Assignee: Max Rydahl Andersen > Fix For: 4.1.0.CR1 > > > jcip.annotations is actually not common creative, its common creative attribution license. Also means anyone that uses this needs to include the copyright notice in their feature.xml > see https://github.com/nickboldt/jbosstools-locus/pull/4 -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-17960) "The specified JRE installation does not exist"

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17960?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-17960: ------------------------------------- Beta3 has been released. Feel free to let us know how this works :) > "The specified JRE installation does not exist" > ----------------------------------------------- > > Key: JBIDE-17960 > URL: https://issues.jboss.org/browse/JBIDE-17960 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Reporter: Karl Pietrzak > Priority: Minor > Fix For: 4.2.0.CR1 > > Attachments: jbossastools-bad.jre.swf > > > h3. What > If you get a ""The specified JRE installation does not exist" error, JBoss Tools puts the entry in the Servers section as "Starting...", which is inaccurate. > h3. Screencast > !jbossastools-bad.jre.swf! > If the above embedded SWF doesn't work for you, you can watch it at http://screencast.com/t/bytN53lp -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-17686) ensure TCF terminal is in jboss tools/devstudio

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17686?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-17686 at 7/29/14 9:29 AM: ------------------------------------------------------------- OK, so if I understand your comment correctly, you want us to fix upstream RSE to: a) include TCF in default RSE install b) fix usability so there are fewer terminal views c) NOT include a new connector in Central for the TCF terminal d) NOT include a dependency on the TCF terminal in any of our features/plugins e) change nothing in JBT or JBDS to resolve this issue. Please confirm if I've understood your problem statement and the implementation you require. In future, can you focus on stating IMPLEMENTATION details, rather than just restating the PROBLEM using overloaded pronouns like "it" ? (My biggest confusion here is that the JIRA title is "ensure TCF terminal is in jboss tools/devstudio" but every time I suggest how to implement that I'm met with non-answers and more confusion. The JIRA Description isn't much help either.) was (Author: nickboldt): OK, so if I understand your comment correctly, you want us to fix upstream RSE to: a) include TCF in default RSE install b) fix usability so there are fewer terminal views c) NOT include a new connector in Central for the TCF terminal d) NOT include a dependency on the TCF terminal in any of our features/plugins e) change nothing in JBT or JBDS to resolve this issue. Please confirm if I've understood your problem statement and the implementation you require. In future, can you focus on stating IMPLEMENTATION details, rather than just restating the PROBLEM using overloaded pronouns like "it" ? > ensure TCF terminal is in jboss tools/devstudio > ----------------------------------------------- > > Key: JBIDE-17686 > URL: https://issues.jboss.org/browse/JBIDE-17686 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: target-platform > Affects Versions: 4.2.0.Beta2 > Reporter: Max Rydahl Andersen > Assignee: Max Rydahl Andersen > Fix For: 4.2.0.CR1 > > Attachments: eclipse-can-has-many-consoles.png > > > luna has new Eclipse TCF terminal that brings better Terminal support. > I would assume it is in there but I couldn't find a way to actually open it. Maybe we havent included the full set of plugins. > http://marketplace.eclipse.org/content/tcf-terminals#.U6sJ92Vp7wV > http://eclipsesource.com/blogs/2014/06/17/tcf-terminal-top-eclipse-luna-f... -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-17903) Explorer, Server Adapter: add show in > project explorer for openshift apps

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17903?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-17903: ------------------------------------- Issue Type: Enhancement (was: Bug) > Explorer, Server Adapter: add show in > project explorer for openshift apps > --------------------------------------------------------------------------- > > Key: JBIDE-17903 > URL: https://issues.jboss.org/browse/JBIDE-17903 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.2.0.Beta3 > Reporter: Max Rydahl Andersen > Labels: explorer, server_adapter > Fix For: 4.2.0.CR1 > > > couldn't we have "show in" project explorer enabled for openshift applications ? > If 0 found -> open dialog "Application 'xyz' not found in workspace. Do you want to import it ?" > if 1 found -> have it selected in project explorer > if >1 found -> open dialog "Multiple projects found mapped to application 'xyz' which one do you want ?" (is this even technically possible since the project names would be the same...? - I guess if they are on different branches with different .project names then yes) > maybe just pick the first found in the >1 found case to keep it simple? -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-17960) "The specified JRE installation does not exist"

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17960?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-17960: -------------------------------- Fix Version/s: 4.2.0.CR1 > "The specified JRE installation does not exist" > ----------------------------------------------- > > Key: JBIDE-17960 > URL: https://issues.jboss.org/browse/JBIDE-17960 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Reporter: Karl Pietrzak > Priority: Minor > Fix For: 4.2.0.CR1 > > Attachments: jbossastools-bad.jre.swf > > > h3. What > If you get a ""The specified JRE installation does not exist" error, JBoss Tools puts the entry in the Servers section as "Starting...", which is inaccurate. > h3. Screencast > !jbossastools-bad.jre.swf! > If the above embedded SWF doesn't work for you, you can watch it at http://screencast.com/t/bytN53lp -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-17903) Explorer, Server Adapter: add show in > project explorer for openshift apps

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17903?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-17903: ------------------------------------- Fix Version/s: 4.2.0.CR1 > Explorer, Server Adapter: add show in > project explorer for openshift apps > --------------------------------------------------------------------------- > > Key: JBIDE-17903 > URL: https://issues.jboss.org/browse/JBIDE-17903 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.2.0.Beta3 > Reporter: Max Rydahl Andersen > Labels: explorer, server_adapter > Fix For: 4.2.0.CR1 > > > couldn't we have "show in" project explorer enabled for openshift applications ? > If 0 found -> open dialog "Application 'xyz' not found in workspace. Do you want to import it ?" > if 1 found -> have it selected in project explorer > if >1 found -> open dialog "Multiple projects found mapped to application 'xyz' which one do you want ?" (is this even technically possible since the project names would be the same...? - I guess if they are on different branches with different .project names then yes) > maybe just pick the first found in the >1 found case to keep it simple? -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-17686) ensure TCF terminal is in jboss tools/devstudio

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17686?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-17686: ------------------------------------ OK, so if I understand your comment correctly, you want us to fix upstream RSE to: a) include TCF in default RSE install b) fix usability so there are fewer terminal views c) NOT include a new connector in Central for the TCF terminal d) NOT include a dependency on the TCF terminal in any of our features/plugins e) change nothing in JBT or JBDS to resolve this issue. Please confirm if I've understood your problem statement and the implementation you require. In future, can you focus on stating IMPLEMENTATION details, rather than just restating the PROBLEM using overloaded pronouns like "it" ? > ensure TCF terminal is in jboss tools/devstudio > ----------------------------------------------- > > Key: JBIDE-17686 > URL: https://issues.jboss.org/browse/JBIDE-17686 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: target-platform > Affects Versions: 4.2.0.Beta2 > Reporter: Max Rydahl Andersen > Assignee: Max Rydahl Andersen > Fix For: 4.2.0.CR1 > > Attachments: eclipse-can-has-many-consoles.png > > > luna has new Eclipse TCF terminal that brings better Terminal support. > I would assume it is in there but I couldn't find a way to actually open it. Maybe we havent included the full set of plugins. > http://marketplace.eclipse.org/content/tcf-terminals#.U6sJ92Vp7wV > http://eclipsesource.com/blogs/2014/06/17/tcf-terminal-top-eclipse-luna-f... -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-17976) Problem markers are not removed on related Parameter Aggregators

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17976?page=com.atlassian.jira.plugi... ] Xavier Coulon updated JBIDE-17976: ---------------------------------- Issue Type: Bug (was: Feature Request) > Problem markers are not removed on related Parameter Aggregators > ---------------------------------------------------------------- > > Key: JBIDE-17976 > URL: https://issues.jboss.org/browse/JBIDE-17976 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Affects Versions: 4.2.0.Beta3 > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Fix For: 4.2.0.CR1 > > > Let's have those 2 classes: > {code} > @Path("/rest") > public class RestService { > @POST > @Path("{id}") > public void post(@BeanParam BeanClass bean) { > > } > } > {code} > and > {code} > public class BeanClass { > > @PathParam("id") > private Integer id; > > } > {code} > if the users changes {{@Path("{id}")}} to {{@Path("{i}")}} in the {{RestService}}, a problem marker will be set on {{@PathParam("id") }} in {{BeanClass}}, which is fine. > If the user changes {{@Path("{i}")}} back to {{@Path("{id}")}}, the problem marker is not removed :( -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues July 2014