[JBoss JIRA] (JBIDE-16059) Disable Parameters Add button when no Feature is added and Remove buttons if nothing is selected
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16059?page=com.atlassian.jira.plugi... ]
Denis Golovin updated JBIDE-16059:
----------------------------------
Summary: Disable Parameters Add button when no Feature is added and Remove buttons if nothing is selected (was: Disable Parameters Add button when no Feature is added)
> Disable Parameters Add button when no Feature is added and Remove buttons if nothing is selected
> ------------------------------------------------------------------------------------------------
>
> Key: JBIDE-16059
> URL: https://issues.jboss.org/browse/JBIDE-16059
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: aerogear-hybrid
> Affects Versions: 4.1.1.CR1
> Environment: JBDS7.1.0.CR1 CR1-v20131116-1929-B543
> Reporter: Vlado Pakan
> Assignee: Denis Golovin
> Priority: Minor
> Fix For: 4.2.0.Beta2
>
>
> 1. Create Hybrid Mobile project
> 2. Open config.xml file in Cordova Configuration Editor
> Button Add... for adding parameters should be disabled when there is no Feature added because in that case choosing Add... button does nothing
> Button Remove for removing parameters should be disabled when there is no parameter selected
--
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
[JBoss JIRA] (JBIDE-16901) Error when starting a remote EAP 6.2 - updating deployment scanners
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16901?page=com.atlassian.jira.plugi... ]
Rob Stryker resolved JBIDE-16901.
---------------------------------
Labels: (was: respin-a)
Resolution: Done
fixed by other commits recently.
> Error when starting a remote EAP 6.2 - updating deployment scanners
> -------------------------------------------------------------------
>
> Key: JBIDE-16901
> URL: https://issues.jboss.org/browse/JBIDE-16901
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.2.0.Beta1
> Environment: JBDS 8.0.0.Beta1 B78
> Reporter: Rob Stryker
> Assignee: Rob Stryker
> Fix For: 4.2.0.Beta2
>
>
> I created a remote runtime-less EAP 6.2 with management port enabled.
> When I started the server and entered the password, I got this error:
> An internal error occurred during: "Updating Deployment Scanners for Server: JBoss EAP 6.2 marvin".
> null argument:
> !updating-deployment-scanners.png!
> This is in the log:
> {code}
> !ENTRY org.eclipse.core.jobs 4 2 2014-03-26 10:03:47.204
> !MESSAGE An internal error occurred during: "Updating Deployment Scanners for Server: JBoss EAP 6.2 marvin".
> !STACK 0
> org.eclipse.core.runtime.AssertionFailedException: null argument:
> at org.eclipse.core.runtime.Assert.isNotNull(Assert.java:85)
> at org.eclipse.core.runtime.Assert.isNotNull(Assert.java:73)
> at org.jboss.ide.eclipse.as.core.util.RemotePath.initialize(RemotePath.java:642)
> at org.jboss.ide.eclipse.as.core.util.RemotePath.<init>(RemotePath.java:197)
> at org.jboss.tools.as.core.internal.modules.ModuleDeploymentPrefsUtil.getModuleNestedDeployPath(ModuleDeploymentPrefsUtil.java:159)
> at org.jboss.tools.as.core.internal.modules.ModuleDeploymentPrefsUtil.getModuleTreeDestinationFullPath(ModuleDeploymentPrefsUtil.java:65)
> at org.jboss.tools.as.core.server.controllable.subsystems.internal.ModuleDeployPathController.getDeployDirectory(ModuleDeployPathController.java:110)
> at org.jboss.ide.eclipse.as.core.server.internal.DeployableServer.getDeploymentLocation(DeployableServer.java:254)
> at org.jboss.ide.eclipse.as.core.server.internal.AbstractDeploymentScannerAdditions.getDeployLocationFolders(AbstractDeploymentScannerAdditions.java:161)
> at org.jboss.ide.eclipse.as.core.server.internal.AbstractDeploymentScannerAdditions.updateDeploymentScanners(AbstractDeploymentScannerAdditions.java:57)
> at org.jboss.ide.eclipse.as.core.server.internal.AbstractDeploymentScannerAdditions$1.run(AbstractDeploymentScannerAdditions.java:68)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
> {code}
--
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
[JBoss JIRA] (JBIDE-16940) Add test and supporting code for Mylyn/Jenkins plugin (org.jboss.tools.mylyn.hudson.reddeer)
by Len DiMaggio (JIRA)
Len DiMaggio created JBIDE-16940:
------------------------------------
Summary: Add test and supporting code for Mylyn/Jenkins plugin (org.jboss.tools.mylyn.hudson.reddeer)
Key: JBIDE-16940
URL: https://issues.jboss.org/browse/JBIDE-16940
Project: Tools (JBoss Tools)
Issue Type: Task
Components: qa
Affects Versions: 4.2.0.Beta1
Reporter: Len DiMaggio
Assignee: Len DiMaggio
Fix For: 4.2.0.Beta1
Files to be added:
jbosstools-integration-tests/plugins//org.jboss.tools.mylyn.hudson.reddeer/src/org/jboss/tools/mylyn/hudson/reddeer/mylynBuild/MylynBuild.java
jbosstools-integration-tests/plugins/org.jboss.tools.mylyn.hudson.reddeer/src/org/jboss/tools/mylyn/hudson/reddeer/view/MylynBuildView.java
jbosstools-integration-tests/plugins/org.jboss.tools.mylyn.hudson.reddeer/src/org/jboss/tools/mylyn/hudson/reddeer/wizard/BuildServerDialog.java
jbosstools-integration-tests/tests/org.jboss.tools.mylyn.ui.bot.test/src/org/jboss/tools/mylyn/ui/bot/test/MylynTestJenkins.java
--
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
[JBoss JIRA] (JBIDE-16900) Remote EAP 6.2 fails to stop - null argument
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16900?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-16900:
-------------------------------------
I've pushed this to master. The changes I made are as follows:
1) rse.mgmt profile will now by default NOT add or remove scanners on startup or shutdown, and
2) In the event a user somehow enables that option, I have fixed the npe's by simply checking for nulls and returning appropriately.
Hopefully I've cleaned the jira up a bit... sorry I got a bit confused here.
> Remote EAP 6.2 fails to stop - null argument
> --------------------------------------------
>
> Key: JBIDE-16900
> URL: https://issues.jboss.org/browse/JBIDE-16900
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.2.0.Beta1
> Environment: JBDS 8.0.0.Beta1 B78
> Reporter: Rob Stryker
> Assignee: Rob Stryker
> Priority: Blocker
> Fix For: 4.2.0.Beta2
>
>
> I cannot stop a remote server. It's EAP 6.2 without a runtime and with management operations enabled.
> When I click stop, I get this error:
> !null-argument.png!
> And this is in the workspace log:
> {code}
> !ENTRY org.eclipse.core.jobs 4 2 2014-03-26 11:39:00.141
> !MESSAGE An internal error occurred during: "Stopping JBoss EAP 6.2 marvin".
> !STACK 0
> org.eclipse.core.runtime.AssertionFailedException: null argument:
> at org.eclipse.core.runtime.Assert.isNotNull(Assert.java:85)
> at org.eclipse.core.runtime.Assert.isNotNull(Assert.java:73)
> at org.jboss.ide.eclipse.as.core.util.RemotePath.initialize(RemotePath.java:642)
> at org.jboss.ide.eclipse.as.core.util.RemotePath.<init>(RemotePath.java:197)
> at org.jboss.tools.as.core.internal.modules.ModuleDeploymentPrefsUtil.getModuleNestedDeployPath(ModuleDeploymentPrefsUtil.java:159)
> at org.jboss.tools.as.core.internal.modules.ModuleDeploymentPrefsUtil.getModuleTreeDestinationFullPath(ModuleDeploymentPrefsUtil.java:65)
> at org.jboss.tools.as.core.server.controllable.subsystems.internal.ModuleDeployPathController.getDeployDirectory(ModuleDeployPathController.java:110)
> at org.jboss.ide.eclipse.as.core.server.internal.DeployableServer.getDeploymentLocation(DeployableServer.java:254)
> at org.jboss.ide.eclipse.as.core.server.internal.AbstractDeploymentScannerAdditions.getDeployLocationFolders(AbstractDeploymentScannerAdditions.java:161)
> at org.jboss.ide.eclipse.as.core.server.internal.AbstractDeploymentScannerAdditions.removeAddedDeploymentScanners(AbstractDeploymentScannerAdditions.java:76)
> at org.jboss.tools.as.core.server.controllable.subsystems.internal.LocalLegacyShutdownController.removeScanners(LocalLegacyShutdownController.java:75)
> at org.jboss.tools.as.core.server.controllable.subsystems.internal.LocalLegacyShutdownController.stop(LocalLegacyShutdownController.java:58)
> at org.jboss.tools.as.core.server.controllable.subsystems.internal.LocalLegacyShutdownController.stop(LocalLegacyShutdownController.java:53)
> at org.jboss.ide.eclipse.as.wtp.core.server.behavior.ControllableServerBehavior.stop(ControllableServerBehavior.java:242)
> at org.eclipse.wst.server.core.internal.Server.stopImpl2(Server.java:3670)
> at org.eclipse.wst.server.core.internal.Server.stopImpl(Server.java:3627)
> at org.eclipse.wst.server.core.internal.Server$StopJob.run(Server.java:403)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
> {code}
> There is no way to stop the server - you can try as many times as you like to click Stop, but each time you get the error and the server is still started.
--
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
[JBoss JIRA] (JBIDE-16900) Remote EAP 6.2 fails to stop - null argument
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16900?page=com.atlassian.jira.plugi... ]
Rob Stryker updated JBIDE-16900:
--------------------------------
Fix Version/s: 4.2.0.Beta2
(was: 4.2.0.Beta1)
> Remote EAP 6.2 fails to stop - null argument
> --------------------------------------------
>
> Key: JBIDE-16900
> URL: https://issues.jboss.org/browse/JBIDE-16900
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.2.0.Beta1
> Environment: JBDS 8.0.0.Beta1 B78
> Reporter: Rob Stryker
> Assignee: Rob Stryker
> Priority: Blocker
> Fix For: 4.2.0.Beta2
>
>
> I cannot stop a remote server. It's EAP 6.2 without a runtime and with management operations enabled.
> When I click stop, I get this error:
> !null-argument.png!
> And this is in the workspace log:
> {code}
> !ENTRY org.eclipse.core.jobs 4 2 2014-03-26 11:39:00.141
> !MESSAGE An internal error occurred during: "Stopping JBoss EAP 6.2 marvin".
> !STACK 0
> org.eclipse.core.runtime.AssertionFailedException: null argument:
> at org.eclipse.core.runtime.Assert.isNotNull(Assert.java:85)
> at org.eclipse.core.runtime.Assert.isNotNull(Assert.java:73)
> at org.jboss.ide.eclipse.as.core.util.RemotePath.initialize(RemotePath.java:642)
> at org.jboss.ide.eclipse.as.core.util.RemotePath.<init>(RemotePath.java:197)
> at org.jboss.tools.as.core.internal.modules.ModuleDeploymentPrefsUtil.getModuleNestedDeployPath(ModuleDeploymentPrefsUtil.java:159)
> at org.jboss.tools.as.core.internal.modules.ModuleDeploymentPrefsUtil.getModuleTreeDestinationFullPath(ModuleDeploymentPrefsUtil.java:65)
> at org.jboss.tools.as.core.server.controllable.subsystems.internal.ModuleDeployPathController.getDeployDirectory(ModuleDeployPathController.java:110)
> at org.jboss.ide.eclipse.as.core.server.internal.DeployableServer.getDeploymentLocation(DeployableServer.java:254)
> at org.jboss.ide.eclipse.as.core.server.internal.AbstractDeploymentScannerAdditions.getDeployLocationFolders(AbstractDeploymentScannerAdditions.java:161)
> at org.jboss.ide.eclipse.as.core.server.internal.AbstractDeploymentScannerAdditions.removeAddedDeploymentScanners(AbstractDeploymentScannerAdditions.java:76)
> at org.jboss.tools.as.core.server.controllable.subsystems.internal.LocalLegacyShutdownController.removeScanners(LocalLegacyShutdownController.java:75)
> at org.jboss.tools.as.core.server.controllable.subsystems.internal.LocalLegacyShutdownController.stop(LocalLegacyShutdownController.java:58)
> at org.jboss.tools.as.core.server.controllable.subsystems.internal.LocalLegacyShutdownController.stop(LocalLegacyShutdownController.java:53)
> at org.jboss.ide.eclipse.as.wtp.core.server.behavior.ControllableServerBehavior.stop(ControllableServerBehavior.java:242)
> at org.eclipse.wst.server.core.internal.Server.stopImpl2(Server.java:3670)
> at org.eclipse.wst.server.core.internal.Server.stopImpl(Server.java:3627)
> at org.eclipse.wst.server.core.internal.Server$StopJob.run(Server.java:403)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
> {code}
> There is no way to stop the server - you can try as many times as you like to click Stop, but each time you get the error and the server is still started.
--
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