June 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-24551) reactivate Sonarcloud.io updates for jbosstools-server

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24551?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-24551: ------------------------------------- [~aurelien.pupier] screenshot not available? Mind fixing it? > reactivate Sonarcloud.io updates for jbosstools-server > ------------------------------------------------------ > > Key: JBIDE-24551 > URL: https://issues.jboss.org/browse/JBIDE-24551 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build, server > Reporter: Aurélien Pupier > > last update was the 21 February > !image-2017-06-08-11-44-59-190.png|thumbnail! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24490) access.redhat.com in credentials prefpage shows drupal icon

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24490?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-24490: ------------------------------------- Upstream issue (linked bz) was marked as 'verified QE' - no idea what this means. I emailed the guy listed on the bug to get clarification. > access.redhat.com in credentials prefpage shows drupal icon > ----------------------------------------------------------- > > Key: JBIDE-24490 > URL: https://issues.jboss.org/browse/JBIDE-24490 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: foundation, upstream > Affects Versions: 4.5.0.AM1 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.5.0.AM1 > > > This is an upstream issue, but their favicon.ico is a drupal image. On the website it's fine, but the url access.redhat.com/favicon.ico is wrong. This makes our tools load the wrong image. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24491) CDK Server adapter: allow users to look up the address of the docker registry

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24491?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-24491: ------------------------------------- [~adietish] So, we need to direct this issue a bit. We already do this for manually CDK server adapter: https://github.com/jbosstools/jbosstools-openshift/blob/888688f43b754be98... So my questions are: 1) Is the current code not working for you? 2) If it's working, what more needs to be done? 3) Do we need an upstream bug to allow discovery for the online version? Thanks. > CDK Server adapter: allow users to look up the address of the docker registry > ----------------------------------------------------------------------------- > > Key: JBIDE-24491 > URL: https://issues.jboss.org/browse/JBIDE-24491 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: cdk > Affects Versions: 4.4.4.Final > Reporter: Andre Dietisheim > Fix For: 4.5.0.AM1 > > > if you want to push a docker image to the docker registry within OpenShift you need the address of the docker registry. > When launching the cdk in Eclipse our tooling creates the OpenShift connection for the tooling filling out that address. > Users that didnt launch the cdk via the server adapter or had their connection already defined when launching it, would have to look the address up manually. One does this on the command line via {code}./minishift openshift registry{code} > It would be nice if the server adapter would offer a way to look it up so that the user does not have to go the command line. > I dont know yet how to look it up for the OpenShift online variant though. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24535) itests are not run for server in Jenkins

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24535?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-24535: ------------------------------------- OK it's not running the itests. I was misreading things. Yes, we definitely need an itests job. My real question is why am i the only one with this issue? Why does nobody else have integration tests? ;) > itests are not run for server in Jenkins > ---------------------------------------- > > Key: JBIDE-24535 > URL: https://issues.jboss.org/browse/JBIDE-24535 > 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 wanted to verify JBIDE-24483 which added itests for incremental deployment via management. But it turns out none of the itests are run here: > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > Shouldn't they be run? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24521) Errors publishing a large deployment to a remote server (EAP 7.1 management)

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24521?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-24521: ------------------------------------- Upstream issue: https://issues.jboss.org/browse/WFCORE-2946 > 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.x > > > 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24535) itests are not run for server in Jenkins

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24535?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-24535: ------------------------------------- I'm a bit confused. The output of https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... seems to indicate it's running itests? Or did you already do the work? > itests are not run for server in Jenkins > ---------------------------------------- > > Key: JBIDE-24535 > URL: https://issues.jboss.org/browse/JBIDE-24535 > 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 wanted to verify JBIDE-24483 which added itests for incremental deployment via management. But it turns out none of the itests are run here: > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > Shouldn't they be run? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4440) Add sources to the JBDS target platform

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBDS-4440?page=com.atlassian.jira.plugin.... ] Rob Stryker commented on JBDS-4440: ----------------------------------- +1 I support always including sources :D > Add sources to the JBDS target platform > --------------------------------------- > > Key: JBDS-4440 > URL: https://issues.jboss.org/browse/JBDS-4440 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: target-platform > Affects Versions: 11.0.0.AM1 > Reporter: Lukáš Valach > Assignee: Nick Boldt > Fix For: 11.0.0.AM1 > > Attachments: p2diff_JBT_JBDS_TPs.txt, p2diff_JBT_JBDS_TPs_filtered.txt > > > We are maintaining target platfroms for JBT [1] and for JBDS [2] separatelly. The only difference is that TP for JBT includes sources but TP for JBDS doesn't. > Consequently, JBT users can install plugins including sources but JBDS users can't. In my opinion both should have sources. > [1] http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.7... > [2] https://devstudio.redhat.com/targetplatforms/jbdevstudiotarget/4.70.0.AM1... > If we decide to add sources to JBDS TP, we'd be able to drop one of the TPs entirely and just build one for both JBT and JBDS, saving time and disk. > I will ask people at jbosstools-dev for their opinions. > CC: [~nickboldt] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4362) Eliminate devstudio EAP installer bundle; move EAP installation functionality into devsuite installer

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4362?page=com.atlassian.jira.plugin.... ] Nick Boldt edited comment on JBDS-4362 at 6/12/17 11:40 AM: ------------------------------------------------------------ FYI, we'll have to remove this section of the install guide [1] for 11.0, as EAP installation as part of devstudio 11.0 is now a feature of devsuite 2.0 [2] [1] https://access.redhat.com/documentation/en-us/red_hat_jboss_developer_stu... [2] https://access.redhat.com/documentation/en-us/red_hat_development_suite/1... cc: [~supriya.bharadwaj] [~rkratky] [~dgolovin] [~psargent] I can open JIRAs for these doc changes if you tell me where to report them. was (Author: nickboldt): FYI, we'll have to remove this section of the install guide [1] for 11.0, as EAP installation as part of devstudio 11.0 is now a feature of devsuite 2.0 [2] [1] https://access.redhat.com/documentation/en-us/red_hat_jboss_developer_stu... [2] https://access.redhat.com/documentation/en-us/red_hat_development_suite/1... cc: [~supriya.bharadwaj] [~rkratky] [~dgolovin] [~psargent] > Eliminate devstudio EAP installer bundle; move EAP installation functionality into devsuite installer > ----------------------------------------------------------------------------------------------------- > > Key: JBDS-4362 > URL: https://issues.jboss.org/browse/JBDS-4362 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: installer, integration-platform > Affects Versions: 10.4.0.AM3 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 11.0.0.AM1 > > Attachments: devstudio-install-add-servers-01.png, devstudio-install-add-servers-02.png, devstudio-install-add-servers-03.png, devstudio-install-add-servers-04.png, devstudio-install-add-servers-05.png > > > For devstudio 11, we might want to eliminate the devstudio EAP installer. > If we could do so, we would no longer require an internal-facing server (eg., www.qa or wonka.mw) since everything in devstudio would be completely open source and free. > This would also make releases simpler and faster as I wouldn't have to push bits to BOTH the internal and external staging servers - we could stage 100% on the public devstudio.redhat.com server. > Since EAP releases don't align very well with devstudio releases, maybe it's time to decouple entirely? > That way only the devSUITE installer would include EAP. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4362) Eliminate devstudio EAP installer bundle; move EAP installation functionality into devsuite installer

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4362?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-4362: ---------------------------------- FYI, we'll have to remove this section of the install guide [1] for 11.0, as EAP installation as part of devstudio 11.0 is now a feature of devsuite 2.0 [2] [1] https://access.redhat.com/documentation/en-us/red_hat_jboss_developer_stu... [2] https://access.redhat.com/documentation/en-us/red_hat_development_suite/1... cc: [~supriya.bharadwaj] [~rkratky] [~dgolovin] [~psargent] > Eliminate devstudio EAP installer bundle; move EAP installation functionality into devsuite installer > ----------------------------------------------------------------------------------------------------- > > Key: JBDS-4362 > URL: https://issues.jboss.org/browse/JBDS-4362 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: installer, integration-platform > Affects Versions: 10.4.0.AM3 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 11.0.0.AM1 > > Attachments: devstudio-install-add-servers-01.png, devstudio-install-add-servers-02.png, devstudio-install-add-servers-03.png, devstudio-install-add-servers-04.png, devstudio-install-add-servers-05.png > > > For devstudio 11, we might want to eliminate the devstudio EAP installer. > If we could do so, we would no longer require an internal-facing server (eg., www.qa or wonka.mw) since everything in devstudio would be completely open source and free. > This would also make releases simpler and faster as I wouldn't have to push bits to BOTH the internal and external staging servers - we could stage 100% on the public devstudio.redhat.com server. > Since EAP releases don't align very well with devstudio releases, maybe it's time to decouple entirely? > That way only the devSUITE installer would include EAP. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4440) Add sources to the JBDS target platform

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4440?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-4440: ---------------------------------- We used to maintain some subtle differences between the TP definitions... JBT had sources and test bundles, JBDS had testng... but recently I merged these changes so that the TPs are now identical except for the fact that one includes sources and one does not. Note that this will mean that the offline devstudio install-from-zips solution will require larger downloads, as without sources, the TP is 522M, and with sources, it's 818M. Looking at the install guide [0], I see no mention of the target platform zip - just the devstudio `Update Site Zip` - so we should fix that for 11.0. cc: [~supriya.bharadwaj] [0] https://access.redhat.com/documentation/en-us/red_hat_jboss_developer_stu... > Add sources to the JBDS target platform > --------------------------------------- > > Key: JBDS-4440 > URL: https://issues.jboss.org/browse/JBDS-4440 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: target-platform > Affects Versions: 11.0.0.AM1 > Reporter: Lukáš Valach > Assignee: Nick Boldt > Fix For: 11.0.0.AM1 > > Attachments: p2diff_JBT_JBDS_TPs.txt, p2diff_JBT_JBDS_TPs_filtered.txt > > > We are maintaining target platfroms for JBT [1] and for JBDS [2] separatelly. The only difference is that TP for JBT includes sources but TP for JBDS doesn't. > Consequently, JBT users can install plugins including sources but JBDS users can't. In my opinion both should have sources. > [1] http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.7... > [2] https://devstudio.redhat.com/targetplatforms/jbdevstudiotarget/4.70.0.AM1... > If we decide to add sources to JBDS TP, we'd be able to drop one of the TPs entirely and just build one for both JBT and JBDS, saving time and disk. > I will ask people at jbosstools-dev for their opinions. > CC: [~nickboldt] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 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 June 2017