September 2013 - jbosstools-issues

[JBoss JIRA] (JBIDE-15389) User should be able have its custom tail-command persisted so that he doesnt have to re-type it every time.

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15389?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-15389: ------------------------------------- Attachment: tail-files.png > User should be able have its custom tail-command persisted so that he doesnt have to re-type it every time. > ----------------------------------------------------------------------------------------------------------- > > Key: JBIDE-15389 > URL: https://issues.jboss.org/browse/JBIDE-15389 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.1.0.Final > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.1.1.Alpha2 > > Attachments: tail-files.png > > > Whe doing tail-files for an app the user gets the tail-command in a dialog. He then can provide his very own cmd. > !tail-files.png! > Unfortunately whatever he's providing is not persisted. He has to re-type it every time he wants to tail the files. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15337) Cleanup server editor callback api

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15337?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-15337: -------------------------------- Fix Version/s: 4.2.0.Alpha1 (was: 4.1.1.Final) > Cleanup server editor callback api > ---------------------------------- > > Key: JBIDE-15337 > URL: https://issues.jboss.org/browse/JBIDE-15337 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: server > Affects Versions: 4.1.0.Final > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.2.0.Alpha1 > > > There exists a hack API inside DeploymentModuleOptionCompositeAssistant which has been replaced by a cleaner API inside 'core' and which is no longer useful at all. This must be cleaned out and the references to it should be removed. > Luckily only 2 areas in all of our code use such an API, as.ui and as.rse.ui. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15337) Cleanup server editor callback api

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15337?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-15337. --------------------------------- Resolution: Done This has been pushed to master > Cleanup server editor callback api > ---------------------------------- > > Key: JBIDE-15337 > URL: https://issues.jboss.org/browse/JBIDE-15337 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: server > Affects Versions: 4.1.0.Final > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.2.0.Alpha1 > > > There exists a hack API inside DeploymentModuleOptionCompositeAssistant which has been replaced by a cleaner API inside 'core' and which is no longer useful at all. This must be cleaned out and the references to it should be removed. > Luckily only 2 areas in all of our code use such an API, as.ui and as.rse.ui. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-11319) Use Eclipse-SourceReferences

by Mickael Istria (JIRA)

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15287) Allow customization of automatically-added deployment scanner attributes

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15287?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-15287: ------------------------------------- As Max indicated in the forum post, this is probably closer to an enhancement. And since it depends on API additions which will be made only in master, this issue will not be fixed in maintenance without substantial lobbying. Sorry for any inconvenience. > Allow customization of automatically-added deployment scanner attributes > ------------------------------------------------------------------------ > > Key: JBIDE-15287 > URL: https://issues.jboss.org/browse/JBIDE-15287 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: server > Affects Versions: 4.1.0.Final > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.2.0.Alpha1 > > > Specifically timeouts. https://community.jboss.org/message/758366#758366 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15287) Allow customization of automatically-added deployment scanner attributes

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15287?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-15287: -------------------------------- Fix Version/s: 4.2.0.Alpha1 (was: 4.1.1.Final) > Allow customization of automatically-added deployment scanner attributes > ------------------------------------------------------------------------ > > Key: JBIDE-15287 > URL: https://issues.jboss.org/browse/JBIDE-15287 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: server > Affects Versions: 4.1.0.Final > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.2.0.Alpha1 > > > Specifically timeouts. https://community.jboss.org/message/758366#758366 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15312) Update all AS versions AND manifest.mf dependency version ranges

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15312?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-15312. --------------------------------- Resolution: Done seems forgot to close the issue > Update all AS versions AND manifest.mf dependency version ranges > ----------------------------------------------------------------- > > Key: JBIDE-15312 > URL: https://issues.jboss.org/browse/JBIDE-15312 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: server > Affects Versions: 4.1.0.Final > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.1.1.Final, 4.2.0.Alpha1 > > > API has been added in both branch and master. THis requires an update of version ranges. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13445) Enable possibility of deployment scanner additions for remote servers

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13445?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-13445: ------------------------------------- these api additions are significant enough to be what i'd consider suitable for master only. > Enable possibility of deployment scanner additions for remote servers > --------------------------------------------------------------------- > > Key: JBIDE-13445 > URL: https://issues.jboss.org/browse/JBIDE-13445 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: server > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.2.0.Alpha1 > > > Currently, additions tot he deployment scanners are limited to locally running servers. This is due to a lack of API allowing accurate discovery of what folders need to be added for remote servers, specifically no way for as.core classes to discover what the remote server home is, what the remote configuration folder is, etc. There is a lack of api here, and that will need to be fixed before this issue can work. > Remember: If a remote server is not running with its management ports exposed, do not attempt to add the scanners, as the management connections will fail. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13445) Enable possibility of deployment scanner additions for remote servers

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13445?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-13445: -------------------------------- Fix Version/s: 4.2.0.Alpha1 (was: 4.1.x) > Enable possibility of deployment scanner additions for remote servers > --------------------------------------------------------------------- > > Key: JBIDE-13445 > URL: https://issues.jboss.org/browse/JBIDE-13445 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: server > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.2.0.Alpha1 > > > Currently, additions tot he deployment scanners are limited to locally running servers. This is due to a lack of API allowing accurate discovery of what folders need to be added for remote servers, specifically no way for as.core classes to discover what the remote server home is, what the remote configuration folder is, etc. There is a lack of api here, and that will need to be fixed before this issue can work. > Remember: If a remote server is not running with its management ports exposed, do not attempt to add the scanners, as the management connections will fail. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2745) Support installation of Early Access / Experimental / Incubating plugins

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-2745?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-2745: ------------------------------------------- I've set this for 8.0 release since it is not something that fit into 7.1.x release plan. > Support installation of Early Access / Experimental / Incubating plugins > ------------------------------------------------------------------------ > > Key: JBDS-2745 > URL: https://issues.jboss.org/browse/JBDS-2745 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Central > Affects Versions: 7.1.0.Alpha1 > Reporter: Nick Boldt > Assignee: Burr Sutter > > It's been suggested that it would be nice to have Central available to install non-GA content. How might this appear? > [~burrsutter], [~maxandersen], are we talking about: > * an additional dialog warning users about untested content? (that might be ignored / blindclicked) > * an additional tab in Central for this type of content (what label would you use?) > * relabelling the content's feature descriptions / titles / copyright / license terms to be clear it's unstable content? (might be ignored) > * some other workflow? > See also JBDS-2068. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 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 2013