May 2020 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-18402) Explore action for management-profile servers should open management console

by Josef Kopriva (Jira)

[ https://issues.redhat.com/browse/JBIDE-18402?page=com.atlassian.jira.plug... ] Josef Kopriva closed JBIDE-18402. --------------------------------- Closing, nothing to do. > Explore action for management-profile servers should open management console > ---------------------------------------------------------------------------- > > Key: JBIDE-18402 > URL: https://issues.redhat.com/browse/JBIDE-18402 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: server > Affects Versions: 4.2.1.Final > Reporter: Rob Stryker > Assignee: Rob Stryker > Priority: Major > Fix For: 4.2.x > > > Link: https://issues.jboss.org/browse/JBIDE-18367 > Currently explore action does nothing for management profile deployments. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-10143) AS Tools: Extend JBoss Perspective

by Josef Kopriva (Jira)

[ https://issues.redhat.com/browse/JBIDE-10143?page=com.atlassian.jira.plug... ] Josef Kopriva closed JBIDE-10143. --------------------------------- Closing, nothing to do. > AS Tools: Extend JBoss Perspective > ---------------------------------- > > Key: JBIDE-10143 > URL: https://issues.redhat.com/browse/JBIDE-10143 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: server > Reporter: Alexey Kazakov > Assignee: Rob Stryker > Priority: Minor > Fix For: 3.3.0.M5 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-9151) What is the difference between this creation and what comes just below under //create temp deploy folder ?

by Josef Kopriva (Jira)

[ https://issues.redhat.com/browse/JBIDE-9151?page=com.atlassian.jira.plugi... ] Josef Kopriva closed JBIDE-9151. -------------------------------- Closing, nothing to do. > What is the difference between this creation and what comes just below under //create temp deploy folder ? > ---------------------------------------------------------------------------------------------------------- > > Key: JBIDE-9151 > URL: https://issues.redhat.com/browse/JBIDE-9151 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: server > Affects Versions: 3.3.0.M1 > Reporter: Fisheye JIRA Integration > Fix For: 3.3.0.M2 > > > Created by Max Rydahl Andersen from Crucible comment on ServerUtil.java line 110 https://source.jboss.org/cru/REV-JBIDE-1#c1 : > What is the difference between this creation and what comes just below under //create temp deploy folder ? -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-6102) Server deployment status synchronization improvements

by Josef Kopriva (Jira)

[ https://issues.redhat.com/browse/JBIDE-6102?page=com.atlassian.jira.plugi... ] Josef Kopriva closed JBIDE-6102. -------------------------------- Closing, nothing to do. > Server deployment status synchronization improvements > ----------------------------------------------------- > > Key: JBIDE-6102 > URL: https://issues.redhat.com/browse/JBIDE-6102 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Reporter: Dominik Pospisil > Assignee: Rob Stryker > Priority: Major > Fix For: 3.2.0.M1 > > > I can see couple of ways how the project deployment status could be improved. > 1) Currently, project deployment status could get easily out of sync. > Once the JBT successfully initiates project deployment, it always assumes that the deployment was successful. JBT does not detect deployment failures and If something went wrong it gets out of sync. JBT should check deployment result. > Also, when a project is manually undeployed / deployed from the server the change is not picked up by JBT. > 2) The server view only displays deployments managed by JBT within current workspace. It would be nice if the user has an overview of projects/applications/resources deployed in different workspaces or externally. It would be really handy e.g. when a user often switches workspaces, deploy various project in different workspaces. It could prevent a user of being confused what actually is or is not deployed. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-6057) Shouldn't "deploy in workspace" be using the "standard" servers projects from WTP

by Josef Kopriva (Jira)

[ https://issues.redhat.com/browse/JBIDE-6057?page=com.atlassian.jira.plugi... ] Josef Kopriva closed JBIDE-6057. -------------------------------- Closing, nothing to do. > Shouldn't "deploy in workspace" be using the "standard" servers projects from WTP > --------------------------------------------------------------------------------- > > Key: JBIDE-6057 > URL: https://issues.redhat.com/browse/JBIDE-6057 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Reporter: Max Andersen > Assignee: Rob Stryker > Priority: Major > Fix For: 3.2.0.M1 > > > When using Tomcat server in WTP the deployment is stored in the WTP Servers Project which seems to make much more sense than somewhere hidden inside eclipse preferences/settings storage ? -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-11751) CLONE - AS Component N&N

by Josef Kopriva (Jira)

[ https://issues.redhat.com/browse/JBIDE-11751?page=com.atlassian.jira.plug... ] Josef Kopriva closed JBIDE-11751. --------------------------------- Closing, nothing to do. > CLONE - AS Component N&N > ------------------------ > > Key: JBIDE-11751 > URL: https://issues.redhat.com/browse/JBIDE-11751 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: server > Affects Versions: 3.3.0.M2 > Reporter: Denis Golovin > Assignee: Rob Stryker > Priority: Major > Fix For: 3.3.0.Beta3 > > > project = "Tools (JBoss Tools)" AND affectedVersion = 12316349 AND fixVersion = "3.3.0.M3" AND component = "JBossAS/Servers" AND status = Resolved -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-983) Console not showing up when staritng a EAP/SOA-P Instance

by Josef Kopriva (Jira)

[ https://issues.redhat.com/browse/JBDS-983?page=com.atlassian.jira.plugin.... ] Josef Kopriva closed JBDS-983. ------------------------------ Closing, nothing to do. > Console not showing up when staritng a EAP/SOA-P Instance > --------------------------------------------------------- > > Key: JBDS-983 > URL: https://issues.redhat.com/browse/JBDS-983 > Project: Red Hat CodeReady Studio (devstudio) > Issue Type: Bug > Components: server > Affects Versions: 3.0.0.M4 > Reporter: Jim Tyrrell > Assignee: Rob Stryker > Priority: Major > Fix For: 3.0.0.CR1 > > > For some reason starting a SOA-P instance by right clicking in the server view does not start/open the console for the output of the server as it is starting. For EAP and Seam projects this does not seem to be the case as often, but I think I have seen it. The current JBDS 3.0 M4 release does seem to not show the console unless I open the console via the Window -> Show View -> General -> Console and then I have to click an icon to enable the "Java Stack Trace Console". Once I have setup the console once as just noted even if I close it it will open as I expect. If I close JBDS and make sure that the console was not left open, I get the same behaviour when I try to right click on the SOA-P instance. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-2919) "...tmp/jbosstoolsTemp" does not exist after rebuilding AS instance

by Josef Kopriva (Jira)

[ https://issues.redhat.com/browse/JBIDE-2919?page=com.atlassian.jira.plugi... ] Josef Kopriva closed JBIDE-2919. -------------------------------- Closing, nothing to do. > "...tmp/jbosstoolsTemp" does not exist after rebuilding AS instance > ------------------------------------------------------------------- > > Key: JBIDE-2919 > URL: https://issues.redhat.com/browse/JBIDE-2919 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 3.0.0.alpha > Reporter: Galder Zamarreño > Assignee: Rob Stryker > Priority: Major > Fix For: 3.0.0.cr1 > > Attachments: Screenshot.png > > > - Create a JBoss Server in JBDS from a configuration such as all. > - Do a build.sh clean of the AS source code and then call build.sh so that all is rebuilt. > - If I know double click on the on the server from the "JBoss Server View", try changing > something and save it, I can't because it says something like: > ..."server/all/tmp/jbosstoolsTemp" does not exist. > JBDS should be able to rebuild the information for that server without > me having to recreate the server. > See attached screenshot for more info. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-9152) What is the difference between this creation and what comes just below under //create temp deploy folder ?

by Josef Kopriva (Jira)

[ https://issues.redhat.com/browse/JBIDE-9152?page=com.atlassian.jira.plugi... ] Josef Kopriva closed JBIDE-9152. -------------------------------- Closing, nothing to do. > What is the difference between this creation and what comes just below under //create temp deploy folder ? > ---------------------------------------------------------------------------------------------------------- > > Key: JBIDE-9152 > URL: https://issues.redhat.com/browse/JBIDE-9152 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: server > Affects Versions: 3.3.0.M1 > Reporter: Fisheye JIRA Integration > Fix For: 3.3.0.M2 > > > Created by Max Rydahl Andersen from Crucible comment on ServerUtil.java line 110 https://source.jboss.org/cru/REV-JBIDE-1#c1 : > What is the difference between this creation and what comes just below under //create temp deploy folder ? -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18523) [JBDS 7.1.1] org.jboss.ide.eclipse.as.core.util.IJBossToolingConstants doesn't include EAP_61

by Josef Kopriva (Jira)

[ https://issues.redhat.com/browse/JBIDE-18523?page=com.atlassian.jira.plug... ] Josef Kopriva closed JBIDE-18523. --------------------------------- Closing, nothing to do. > [JBDS 7.1.1] org.jboss.ide.eclipse.as.core.util.IJBossToolingConstants doesn't include EAP_61 > --------------------------------------------------------------------------------------------- > > Key: JBIDE-18523 > URL: https://issues.redhat.com/browse/JBIDE-18523 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.1.2.Final > Reporter: Rob Stryker > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.1.3.Final > > > When working through JBIDE-16066 for the web services wizard, I discovered that EAP_61 is not included in the array provided by the ALL_JBOSS_RUNTIMES list in org.jboss.ide.eclipse.as.core.util.IJBossToolingConstants. I can work around this on the WS side, but I would imagine that this has a broader impact to other tooling projects using the runtime framework -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 5 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues May 2020