[JBoss JIRA] (JBDS-3894) Refactoring: discovery plugins/TPs from jbds/jbdevstudio to devstudio
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3894?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-3894:
-----------------------------
Sprint: devex #116 June 2016, devex #128 February 2017, devex #129 March 2017, devex #136 August 2018 (was: devex #116 June 2016, devex #128 February 2017, devex #129 March 2017)
> Refactoring: discovery plugins/TPs from jbds/jbdevstudio to devstudio
> ---------------------------------------------------------------------
>
> Key: JBDS-3894
> URL: https://issues.jboss.org/browse/JBDS-3894
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Task
> Components: central-update, target-platform, updatesite
> Affects Versions: 10.0.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 11.1.0.AM1
>
>
> In https://github.com/jbosstools/jbosstools-discovery/ we should finally adopt consistent naming/branding for the devstudio target platforms, using devstudio instead of jbdevstudio and jbds.
> Affected: publishing/staging/release scripts, discovery sites, jenkins jobs, etc.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months
[JBoss JIRA] (JBIDE-24772) Refactoring: eliminate devstudio target platform; reuse jbosstools target platform
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24772?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-24772:
-------------------------------
Sprint: devex #136 August 2018
> Refactoring: eliminate devstudio target platform; reuse jbosstools target platform
> ----------------------------------------------------------------------------------
>
> Key: JBIDE-24772
> URL: https://issues.jboss.org/browse/JBIDE-24772
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, target-platform
> Affects Versions: 4.5.0.Final
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.5.1.AM1
>
>
> Now that jbosstoolstarget and jbdevstudiotarget are the same - JBDS-444- - we can eliminate one of them and simply reuse the same artifact in two places.
> Changes:
> * jbosstools-discovery repo - remove unneeded configuration / folders
> * job(s) that publish target platforms to dl.jb.o and ds.rh.com - copy the jbosstools TP to ds.rh.com instead of building a different one & publishing that
> * job(s) / release guide steps that rename/copy target platforms to staging / development / stable / static - change source of TPs to copy/rename to reuse the jbosstools artifacts
> * jbdevstudio-product/pom.xml - point at jbosstoolstarget instead of jbdevstudio one
> * refactoring as per JBDS-3894
> * documentation as per JBIDE-23510
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months
[JBoss JIRA] (JBDS-4410) DevSuite 1.4 Installer indicate download size during choice selection
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-4410?page=com.atlassian.jira.plugin.... ]
Denis Golovin reassigned JBDS-4410:
-----------------------------------
Assignee: Mohit Suman (was: Denis Golovin)
> DevSuite 1.4 Installer indicate download size during choice selection
> ---------------------------------------------------------------------
>
> Key: JBDS-4410
> URL: https://issues.jboss.org/browse/JBDS-4410
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: platform-installer
> Environment: DevSuite 1.4 installer, Windows 10 Pro/64
> Reporter: Robert Terzi
> Assignee: Mohit Suman
> Priority: Minor
> Fix For: 11.x
>
>
> During the software selection phase the DevSuite 1.4 installer should indicate the approximate size of the download. The download size is shown during actual installation progress, but by that time it's too late.
> The two use cases I see for this:
> # A minishift/CDK user that is looking to try OpenShift might not want to download and install all of JBoss. Seeing the size of it ahead of time, would avoid some shock later.
> # When trying to decide between enabling Hyper-V or installing VirtualBox, knowing the size might influence the user to just enable Hyper-V.
> Note: I think I filed a bug against a previous version that the installer provides No estimate of the required disk space in order to proceed. Doesn't look like it is still open.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months
[JBoss JIRA] (JBIDE-24521) Errors publishing a large deployment to a remote server (EAP 7.1 management)
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24521?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-24521:
-------------------------------
Fix Version/s: 4.5.1.AM1
(was: 4.5.x)
> Errors publishing a large deployment to a remote server (EAP 7.1 management)
> ----------------------------------------------------------------------------
>
> Key: JBIDE-24521
> URL: https://issues.jboss.org/browse/JBIDE-24521
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.5.0.AM1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Priority: Minor
> Fix For: 4.5.1.AM1
>
>
> I tried to verify EAP 7.1 incremental deployment (JBIDE-23784).
> So I first deployed a simple dynamic web project over management API to a remote EAP 7.1 (on a remote machine). Everything fine so far.
> Then I just copied a big jar (devstudio installer) into the WebContent dir of the project. Then I did a Refresh of the project in Eclipse and I immediately got an error:
> {code}
> Could not publish to the server.
> org.jboss.ide.eclipse.as.management.core.JBoss7ManangerException: java.util.concurrent.ExecutionException: Operation failed
> at org.jboss.ide.eclipse.as.internal.management.wf11.DeploymentOperationResult.getStatus(DeploymentOperationResult.java:68)
> at org.jboss.ide.eclipse.as.internal.management.wf11.WildFly11Manager.waitFor(WildFly11Manager.java:231)
> at org.jboss.ide.eclipse.as.internal.management.wf11.WildFly11Manager.incrementalPublish(WildFly11Manager.java:601)
> at org.jboss.ide.eclipse.as.internal.management.wf11.WildFly11ManagerService.incrementalPublish(WildFly11ManagerService.java:201)
> at org.jboss.ide.eclipse.as.management.core.JBoss7ManagerServiceProxy.incrementalPublish(JBoss7ManagerServiceProxy.java:134)
> at org.jboss.tools.as.core.server.controllable.subsystems.internal.ManagementPublishController$IncrementalManagementPublishRunner.incrementalPublish(ManagementPublishController.java:530)
> at org.jboss.tools.as.core.server.controllable.subsystems.internal.ManagementPublishController.incrementalPublish(ManagementPublishController.java:474)
> at org.jboss.tools.as.core.server.controllable.subsystems.internal.ManagementPublishController.publishModule(ManagementPublishController.java:257)
> at org.jboss.ide.eclipse.as.wtp.core.server.behavior.ControllableServerBehavior.publishModule(ControllableServerBehavior.java:143)
> at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModule(ServerBehaviourDelegate.java:1091)
> at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModules(ServerBehaviourDelegate.java:1183)
> at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:987)
> at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:774)
> at org.eclipse.wst.server.core.internal.Server.publishImpl(Server.java:3182)
> at org.eclipse.wst.server.core.internal.Server$PublishJob.run(Server.java:355)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56)
> Caused by: java.util.concurrent.ExecutionException: Operation failed
> at org.jboss.threads.AsyncFutureTask.operationFailed(AsyncFutureTask.java:74)
> at org.jboss.threads.AsyncFutureTask.get(AsyncFutureTask.java:281)
> at org.jboss.as.controller.client.impl.AbstractDelegatingAsyncFuture.get(AbstractDelegatingAsyncFuture.java:62)
> at org.jboss.as.controller.client.impl.ConvertingDelegatingAsyncFuture.get(ConvertingDelegatingAsyncFuture.java:69)
> at org.jboss.as.controller.client.impl.ConvertingDelegatingAsyncFuture.get(ConvertingDelegatingAsyncFuture.java:41)
> at org.jboss.as.controller.client.helpers.standalone.impl.ServerDeploymentPlanResultFuture.get(ServerDeploymentPlanResultFuture.java:94)
> at org.jboss.as.controller.client.helpers.standalone.impl.ServerDeploymentPlanResultFuture.get(ServerDeploymentPlanResultFuture.java:42)
> at org.jboss.ide.eclipse.as.internal.management.wf11.DeploymentOperationResult.getStatus(DeploymentOperationResult.java:65)
> ... 15 more
> Caused by: java.lang.OutOfMemoryError: Java heap space
> at java.util.Arrays.copyOf(Arrays.java:3236)
> at java.io.ByteArrayOutputStream.grow(ByteArrayOutputStream.java:118)
> at java.io.ByteArrayOutputStream.ensureCapacity(ByteArrayOutputStream.java:93)
> at java.io.ByteArrayOutputStream.write(ByteArrayOutputStream.java:153)
> at org.jboss.as.protocol.StreamUtils.copyStream(StreamUtils.java:52)
> at org.jboss.as.controller.client.impl.InputStreamEntry$InMemoryEntry.initialize(InputStreamEntry.java:76)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient$ReadAttachmentInputStreamRequestHandler$1.execute(AbstractModelControllerClient.java:220)
> at org.jboss.as.protocol.mgmt.ManagementRequestContextImpl$1.doExecute(ManagementRequestContextImpl.java:70)
> at org.jboss.as.protocol.mgmt.ManagementRequestContextImpl$AsyncTaskRunner.run(ManagementRequestContextImpl.java:160)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> at org.jboss.threads.JBossThread.run(JBossThread.java:320)
> {code}
> The server adapter showed [Republish]. So I tried to do a full publish, but that kind of failed. It first showed 19 %, now it's been at 29 % for 5 minutes and nothing seems to be happening. The server adapter says [Started, Publishing...] and the module says [Republish]. And I can't even stop the server, it's stuck.
> I restarted the IDE. Killed the EAP server on the remote host. Started the server again in the IDE. It showed my module is started. The index worked, the jar was not found. So now I did a full publish on the module. I could see that something was being sent over the network. Then the traffic was over and it was at 33 % for a while and finally it finished successfully this time. So at least that. Then I could add another jsp and it redeployed the module without having to send over the big file again. So at least that worked now.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months
[JBoss JIRA] (JBIDE-24521) Errors publishing a large deployment to a remote server (EAP 7.1 management)
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24521?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-24521:
-------------------------------
Sprint: devex #136 August 2018
> Errors publishing a large deployment to a remote server (EAP 7.1 management)
> ----------------------------------------------------------------------------
>
> Key: JBIDE-24521
> URL: https://issues.jboss.org/browse/JBIDE-24521
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.5.0.AM1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Priority: Minor
> Fix For: 4.5.1.AM1
>
>
> I tried to verify EAP 7.1 incremental deployment (JBIDE-23784).
> So I first deployed a simple dynamic web project over management API to a remote EAP 7.1 (on a remote machine). Everything fine so far.
> Then I just copied a big jar (devstudio installer) into the WebContent dir of the project. Then I did a Refresh of the project in Eclipse and I immediately got an error:
> {code}
> Could not publish to the server.
> org.jboss.ide.eclipse.as.management.core.JBoss7ManangerException: java.util.concurrent.ExecutionException: Operation failed
> at org.jboss.ide.eclipse.as.internal.management.wf11.DeploymentOperationResult.getStatus(DeploymentOperationResult.java:68)
> at org.jboss.ide.eclipse.as.internal.management.wf11.WildFly11Manager.waitFor(WildFly11Manager.java:231)
> at org.jboss.ide.eclipse.as.internal.management.wf11.WildFly11Manager.incrementalPublish(WildFly11Manager.java:601)
> at org.jboss.ide.eclipse.as.internal.management.wf11.WildFly11ManagerService.incrementalPublish(WildFly11ManagerService.java:201)
> at org.jboss.ide.eclipse.as.management.core.JBoss7ManagerServiceProxy.incrementalPublish(JBoss7ManagerServiceProxy.java:134)
> at org.jboss.tools.as.core.server.controllable.subsystems.internal.ManagementPublishController$IncrementalManagementPublishRunner.incrementalPublish(ManagementPublishController.java:530)
> at org.jboss.tools.as.core.server.controllable.subsystems.internal.ManagementPublishController.incrementalPublish(ManagementPublishController.java:474)
> at org.jboss.tools.as.core.server.controllable.subsystems.internal.ManagementPublishController.publishModule(ManagementPublishController.java:257)
> at org.jboss.ide.eclipse.as.wtp.core.server.behavior.ControllableServerBehavior.publishModule(ControllableServerBehavior.java:143)
> at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModule(ServerBehaviourDelegate.java:1091)
> at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModules(ServerBehaviourDelegate.java:1183)
> at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:987)
> at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:774)
> at org.eclipse.wst.server.core.internal.Server.publishImpl(Server.java:3182)
> at org.eclipse.wst.server.core.internal.Server$PublishJob.run(Server.java:355)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56)
> Caused by: java.util.concurrent.ExecutionException: Operation failed
> at org.jboss.threads.AsyncFutureTask.operationFailed(AsyncFutureTask.java:74)
> at org.jboss.threads.AsyncFutureTask.get(AsyncFutureTask.java:281)
> at org.jboss.as.controller.client.impl.AbstractDelegatingAsyncFuture.get(AbstractDelegatingAsyncFuture.java:62)
> at org.jboss.as.controller.client.impl.ConvertingDelegatingAsyncFuture.get(ConvertingDelegatingAsyncFuture.java:69)
> at org.jboss.as.controller.client.impl.ConvertingDelegatingAsyncFuture.get(ConvertingDelegatingAsyncFuture.java:41)
> at org.jboss.as.controller.client.helpers.standalone.impl.ServerDeploymentPlanResultFuture.get(ServerDeploymentPlanResultFuture.java:94)
> at org.jboss.as.controller.client.helpers.standalone.impl.ServerDeploymentPlanResultFuture.get(ServerDeploymentPlanResultFuture.java:42)
> at org.jboss.ide.eclipse.as.internal.management.wf11.DeploymentOperationResult.getStatus(DeploymentOperationResult.java:65)
> ... 15 more
> Caused by: java.lang.OutOfMemoryError: Java heap space
> at java.util.Arrays.copyOf(Arrays.java:3236)
> at java.io.ByteArrayOutputStream.grow(ByteArrayOutputStream.java:118)
> at java.io.ByteArrayOutputStream.ensureCapacity(ByteArrayOutputStream.java:93)
> at java.io.ByteArrayOutputStream.write(ByteArrayOutputStream.java:153)
> at org.jboss.as.protocol.StreamUtils.copyStream(StreamUtils.java:52)
> at org.jboss.as.controller.client.impl.InputStreamEntry$InMemoryEntry.initialize(InputStreamEntry.java:76)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient$ReadAttachmentInputStreamRequestHandler$1.execute(AbstractModelControllerClient.java:220)
> at org.jboss.as.protocol.mgmt.ManagementRequestContextImpl$1.doExecute(ManagementRequestContextImpl.java:70)
> at org.jboss.as.protocol.mgmt.ManagementRequestContextImpl$AsyncTaskRunner.run(ManagementRequestContextImpl.java:160)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> at org.jboss.threads.JBossThread.run(JBossThread.java:320)
> {code}
> The server adapter showed [Republish]. So I tried to do a full publish, but that kind of failed. It first showed 19 %, now it's been at 29 % for 5 minutes and nothing seems to be happening. The server adapter says [Started, Publishing...] and the module says [Republish]. And I can't even stop the server, it's stuck.
> I restarted the IDE. Killed the EAP server on the remote host. Started the server again in the IDE. It showed my module is started. The index worked, the jar was not found. So now I did a full publish on the module. I could see that something was being sent over the network. Then the traffic was over and it was at 33 % for a while and finally it finished successfully this time. So at least that. Then I could add another jsp and it redeployed the module without having to send over the big file again. So at least that worked now.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months
[JBoss JIRA] (JBDS-4411) DevSuite 1.4 installer display required disk space
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-4411?page=com.atlassian.jira.plugin.... ]
Denis Golovin reassigned JBDS-4411:
-----------------------------------
Assignee: Mohit Suman (was: Denis Golovin)
> DevSuite 1.4 installer display required disk space
> ---------------------------------------------------
>
> Key: JBDS-4411
> URL: https://issues.jboss.org/browse/JBDS-4411
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Enhancement
> Components: platform-installer
> Environment: DevSuite 1.4 installer, Windows 10 Pro/64
> Reporter: Robert Terzi
> Assignee: Mohit Suman
> Priority: Minor
> Labels: ui
> Fix For: 11.x
>
>
> DevSuite 1.4 installer (online) should display the disk space requirements which should include the calculation for both the downloads and the unpacked/installed files.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months