[JBoss JIRA] (JBIDE-24520) Server editor says I need a valid shutdown poller, but I didn't touch it
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24520?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-24520:
---------------------------------------
It turns out that this is not specific to remote server or EAP 7.1. It is reproducible with a local EAP 7.0 server also. But you need to use the management profile. So simplified steps are here:
1. Create a local EAP 7.0 server adapter, use management profile
2. Open server editor and you will see that the pollers are empty
> Server editor says I need a valid shutdown poller, but I didn't touch it
> ------------------------------------------------------------------------
>
> Key: JBIDE-24520
> URL: https://issues.jboss.org/browse/JBIDE-24520
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.5.0.AM1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.5.0.AM1
>
>
> I just wanted to test the EAP 7.1 adapter in devstudio 11 (devstudio-11.0.0.AM1-v20170529-1745-B180-installer-standalone.jar) and I got surprised by this error when I opened the server editor and then tried to save it:
> The server cannot be saved for the following reasons:
> [Overview] Your server must have a valid shutdown poller selected.
> In fact both startup and shutdown pollers are empty, not sure why.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (JBIDE-24520) Server editor says I need a valid shutdown poller, but I didn't touch it
by Martin Malina (JIRA)
Martin Malina created JBIDE-24520:
-------------------------------------
Summary: Server editor says I need a valid shutdown poller, but I didn't touch it
Key: JBIDE-24520
URL: https://issues.jboss.org/browse/JBIDE-24520
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: server
Affects Versions: 4.5.0.AM1
Reporter: Martin Malina
Assignee: Rob Stryker
Fix For: 4.5.0.AM1
I just wanted to test the EAP 7.1 adapter in devstudio 11 (devstudio-11.0.0.AM1-v20170529-1745-B180-installer-standalone.jar) and I got surprised by this error when I opened the server editor and then tried to save it:
The server cannot be saved for the following reasons:
[Overview] Your server must have a valid shutdown poller selected.
In fact both startup and shutdown pollers are empty, not sure why.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (JBIDE-23784) WF 11 / EAP 7.1 Incremental MGMT publishing
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23784?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-23784:
---------------------------------------
So I have some updates here based on discussion with Rob.
1. This JIRA has fix version of 4.4.4, but in that release this will only work with the WF11 adapter - there is no separate EAP 7.1 there, only the 7.x one, which does not support this. So if you want to use this with EAP 7.1 and the 7.1 server adapter, you will have to wait for JBoss Tools 4.5.0.AM1 (it also works in master today).
2. I expected this to mean that we don't always redeploy the module, just add the file. But currently this is how it works - when deploying using management API, the tools will not copy over the whole thing every time you modify or add a file, so that's the main improvement. But the module will still be redeployed every time on the server. Rob suggested I create a new feature request so he can look at this in the future - so that for example when you just modify a jsp file, you don't need to redeploy the whole module.
I am going to test this improvement (that the whole thing is not copied over all the time) on a remote deployment now.
> WF 11 / EAP 7.1 Incremental MGMT publishing
> -------------------------------------------
>
> Key: JBIDE-23784
> URL: https://issues.jboss.org/browse/JBIDE-23784
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: server
> Reporter: Rob Stryker
> Assignee: Rob Stryker
> Priority: Critical
> Fix For: 4.4.4.Final, 4.5.0.AM2
>
>
> WF 11 and EAP 7.1 will have support for management deployment in an incremental fashion.
> WF 11 nightly builds for the pre-alpha are here: https://developer.jboss.org/thread/224262
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (JBDS-4413) No help content in DevStudio 10.4.0 for CDK, Minishift
by Robert Terzi (JIRA)
[ https://issues.jboss.org/browse/JBDS-4413?page=com.atlassian.jira.plugin.... ]
Robert Terzi commented on JBDS-4413:
------------------------------------
[~adietish] - I just tried the most naive thing: From inside of Dev Studio 10.4 (installed by Dev. Suite installer), I went to the help menu to see if I could get the steps for working with and managing the bundled minishift/cdk.
> No help content in DevStudio 10.4.0 for CDK, Minishift
> ------------------------------------------------------
>
> Key: JBDS-4413
> URL: https://issues.jboss.org/browse/JBDS-4413
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Enhancement
> Components: documentation
> Affects Versions: 10.4.0.AM3
> Environment: DevStudio 10.4.0 GA on Win 10 Pro/64, installed via DevSuite 1.4 installer
> Reporter: Robert Terzi
> Fix For: 11.x
>
>
> There is no relevant help text that can be easily found from within DevStudio to for CDK, minishift, container development kit.
> Note: CDK yields a lot of hits for a different CDK (not red hat container development kit).
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (JBIDE-24484) deprecate jbosstools projects / move to Central ?
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24484?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-24484:
------------------------------------
Based on today's Cabal call, the first pass plan for AM2 will be:
* jbosstools-freemarker: Move to Central; stop building; just include the bits from JBT 4.4.4.Final
* jbosstools-arquillian: Already in Central: JBT Central and devstudio Central EA. Move out of EA so it's in the same place for both JBT/devstudio.
* jbosstools-browsersim: Already in Central; remove from JBT/devstudio Core Tools.
Then for AM3, if we want, we could also do this:
* jbosstools-livereload: Move to Central? [~jeffmaury] to talk to [~akazakov]
* jbosstools-xulrunner: Included in JBT/devstudio but uncategorized; move to Central? [~jeffmaury] to talk to [~akazakov]
> deprecate jbosstools projects / move to Central ?
> -------------------------------------------------
>
> Key: JBIDE-24484
> URL: https://issues.jboss.org/browse/JBIDE-24484
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.5.0.AM1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.5.0.AM2
>
>
> With the upcoming plan for devstudio 11 / jbosstools 4.5, it may be time to consider moving parts of jbosstools / devstudio out of the Core Tools category and into Central as optional installs. Then in future we can deprecate them / remove them.
> Here's the list of projects in jbosstools:
> https://github.com/jbosstools/jbosstools-devdoc/blob/master/list_of_proje...
> https://issues.jboss.org/projects/JBIDE?selectedItem=com.atlassian.jira.j...
> Once we have an idea of which projects could be moved/removed/deprecated, we can open subtasks for those projects.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months