August 2018 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-26180) TP: create target platform based on Eclipse 4.9 (Simrel 2018-09)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26180?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-26180: ------------------------------------ Additional change pushed by Aurelien and Mat, to fix JBDS-4727: https://github.com/jbosstools/jbosstools-target-platforms/commit/438fb3a7... This pulls a newer version of ASM bundles from I-build of Orbit. > TP: create target platform based on Eclipse 4.9 (Simrel 2018-09) > ---------------------------------------------------------------- > > Key: JBIDE-26180 > URL: https://issues.jboss.org/browse/JBIDE-26180 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform, upstream > Affects Versions: 4.9.0.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.9.0.AM1, 4.9.0.AM2, 4.9.0.AM3, 4.9.0.Final > > Attachments: am1-vs-am2.p2diff.txt > > > In order to start Eclipse 4.9-based builds, we need an updated target platform. > For sprint 152 / AM1: simrel M1 > For sprint 153 / AM2: simrel M2 > For sprint 154 / AM3: simrel M3 > For sprint 155 / GA: simrel RC2/GA -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4727) Incompatible Java (1.8) version for com.spotify.docker.client plugin and its dependencies

by Aurélien Pupier (JIRA)

[ https://issues.jboss.org/browse/JBDS-4727?page=com.atlassian.jira.plugin.... ] Aurélien Pupier reassigned JBDS-4727: ------------------------------------- Assignee: Aurélien Pupier (was: Nick Boldt) > Incompatible Java (1.8) version for com.spotify.docker.client plugin and its dependencies > ----------------------------------------------------------------------------------------- > > Key: JBDS-4727 > URL: https://issues.jboss.org/browse/JBDS-4727 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: installer > Affects Versions: 12.9.0.AM2 > Reporter: Ondrej Dockal > Assignee: Aurélien Pupier > Priority: Blocker > Fix For: 12.9.0.AM2 > > Attachments: DevstudioIncompatibleJavaVersion.png, devstudio_12.9.0.AM2-v20180812-1704-B3167.log > > > I got following warning dialog after fresh start of devstudio: > !DevstudioIncompatibleJavaVersion.png|thumbnail! -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26307) Add support for EAP 7.2

by Martin Malina (JIRA)

Martin Malina created JBIDE-26307: ------------------------------------- Summary: Add support for EAP 7.2 Key: JBIDE-26307 URL: https://issues.jboss.org/browse/JBIDE-26307 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: server Affects Versions: 4.9.0.AM2 Reporter: Martin Malina Assignee: Rob Stryker EAP 7.2 Beta has been released, so it would be good to have a server adapter for that and maybe there is more that needs to be done to support that server. I checked that I can add EAP 7.2 via runtime detection - it will correctly detect the version as 7.2 and allow me to add the server. Under the hood it will use EAP 7.1 server adapter. When I tried to create a server manually using the EAP 7.1 adapter, it allows me to do that and doesn't even complain which is surprising - the new runtime wizard says EAP 7.1 at the top of the screen. Anyway, we'll either need to rename the existing adapter to 7.1+ or create a new one. The announcement article is here: https://access.redhat.com/articles/3548991 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26306) Server adapter: deleting server adapter after project causes NPE

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-26306: ---------------------------------------- Summary: Server adapter: deleting server adapter after project causes NPE Key: JBIDE-26306 URL: https://issues.jboss.org/browse/JBIDE-26306 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.9.0.AM1 Reporter: Andre Dietisheim Attachments: image-2018-08-14-11-57-17-905.png steps: # ASSERT: have an application running in OpenShift that you created via the eap70-basic-s2i template # ASSERT: have the project imported into workspace, have the server adapter created for it # EXEC: delete the project in workspace # EXEC: delete the server (have it stopped before being deleted - the checkbox checked for this sake) Result: Error dialog reports an NPE !image-2018-08-14-11-57-17-905.png! {code} java.lang.NullPointerException at org.jboss.tools.openshift.core.server.behavior.OpenShiftShutdownController.updateProject(OpenShiftShutdownController.java:71) at org.jboss.tools.openshift.core.server.behavior.OpenShiftShutdownController.stop(OpenShiftShutdownController.java:58) at org.jboss.ide.eclipse.as.wtp.core.server.behavior.ControllableServerBehavior.stop(ControllableServerBehavior.java:255) at org.eclipse.wst.server.core.internal.Server.stopImpl2(Server.java:3698) at org.eclipse.wst.server.core.internal.Server.stopImpl(Server.java:3655) at org.eclipse.wst.server.core.internal.Server$StopJob.run(Server.java:413) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:60) {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26306) Server adapter: deleting server adapter after project causes NPE

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26306?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-26306: ------------------------------------- Fix Version/s: 4.9.0.AM3 > Server adapter: deleting server adapter after project causes NPE > ----------------------------------------------------------------- > > Key: JBIDE-26306 > URL: https://issues.jboss.org/browse/JBIDE-26306 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.9.0.AM1 > Reporter: Andre Dietisheim > Labels: server_adapter > Fix For: 4.9.0.AM3 > > Attachments: image-2018-08-14-11-57-17-905.png > > > steps: > # ASSERT: have an application running in OpenShift that you created via the eap70-basic-s2i template > # ASSERT: have the project imported into workspace, have the server adapter created for it > # EXEC: delete the project in workspace > # EXEC: delete the server (have it stopped before being deleted - the checkbox checked for this sake) > Result: > Error dialog reports an NPE > !image-2018-08-14-11-57-17-905.png! > {code} > java.lang.NullPointerException > at org.jboss.tools.openshift.core.server.behavior.OpenShiftShutdownController.updateProject(OpenShiftShutdownController.java:71) > at org.jboss.tools.openshift.core.server.behavior.OpenShiftShutdownController.stop(OpenShiftShutdownController.java:58) > at org.jboss.ide.eclipse.as.wtp.core.server.behavior.ControllableServerBehavior.stop(ControllableServerBehavior.java:255) > at org.eclipse.wst.server.core.internal.Server.stopImpl2(Server.java:3698) > at org.eclipse.wst.server.core.internal.Server.stopImpl(Server.java:3655) > at org.eclipse.wst.server.core.internal.Server$StopJob.run(Server.java:413) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:60) > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4727) Incompatible Java (1.8) version for com.spotify.docker.client plugin and its dependencies

by Aurélien Pupier (JIRA)

[ https://issues.jboss.org/browse/JBDS-4727?page=com.atlassian.jira.plugin.... ] Aurélien Pupier commented on JBDS-4727: --------------------------------------- The bad news is that the version of asm from orbit for Eclipse Milestone 2 is buggy. it requires Java 9. See https://bugs.eclipse.org/bugs/show_bug.cgi?id=537751 The good news is that a fix has been already merged on master. For now only integration orbit repository contains a correct asm version: http://download.eclipse.org/tools/orbit/downloads/drops/I20180809175338/ > Incompatible Java (1.8) version for com.spotify.docker.client plugin and its dependencies > ----------------------------------------------------------------------------------------- > > Key: JBDS-4727 > URL: https://issues.jboss.org/browse/JBDS-4727 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: installer > Affects Versions: 12.9.0.AM2 > Reporter: Ondrej Dockal > Assignee: Nick Boldt > Priority: Blocker > Fix For: 12.9.0.AM2 > > Attachments: DevstudioIncompatibleJavaVersion.png, devstudio_12.9.0.AM2-v20180812-1704-B3167.log > > > I got following warning dialog after fresh start of devstudio: > !DevstudioIncompatibleJavaVersion.png|thumbnail! -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26283) Baseline and reactor have same fully qualified version, but with different content in jbosstools-base plugins/features

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26283?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-26283: ---------------------------------------- An error like this should not be worked around nor skipped and pushed back to GA imo. Doing this adds a serious amount of technical debt and the errors given by the comparator can result in major bugs if not taken care of properly. The comparator here tells clearly which bundles something changed, it's necessary to find out what it is and what changed. For example, comment from [~jeffmaury] about a nested jar changing in size while keeping same name and version should be investigated as it's a suspicious behavior. If this is acceptable, then version of the bundle should be bumped to reflect that it's indeed different content as before. About the Eclipse-SourceReference being different, it's a bit strange that this changed and nothing else. It could be a non-payload file that was modified. In such case, I think Tycho offers the control to declare such non-payload file to the generation of Eclipse-SourceReferences so it would allow to stick to the exact same bundle. > Baseline and reactor have same fully qualified version, but with different content in jbosstools-base plugins/features > ---------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-26283 > URL: https://issues.jboss.org/browse/JBIDE-26283 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.9.0.AM1 > Reporter: Josef Kopriva > Assignee: Nick Boldt > Priority: Blocker > Fix For: 4.9.0.AM2 > > Attachments: diff-baseline-with-local-build-commented-timestamps.png, diff-baseline-with-local-build-sourcereferences-cause-problem.png > > > Job https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... is red for one week. > More info: https://github.com/jbosstools/jbosstools-devdoc/blob/master/source/build_... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26175) Cannot create server adapter for eap71-basic-s2i template from CDK

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26175?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-26175: ------------------------------------- Fix Version/s: 4.9.0.AM2 (was: 4.9.0.AM1) > Cannot create server adapter for eap71-basic-s2i template from CDK > ------------------------------------------------------------------ > > Key: JBIDE-26175 > URL: https://issues.jboss.org/browse/JBIDE-26175 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk, openshift > Affects Versions: 4.6.0.Final > Environment: CDK: CDK v3.5.0-1 > Red Hat Developer Studio > Version: 12.0.0.GA > Build id: GA-v20180706-1014-B2970 > OS: Linux, v.4.17.3-200.fc28.x86_64, x86_64 / gtk 3.22.30, WebKit 2.20.3 > Java version: 1.8.0_172 > Reporter: Josef Kopriva > Assignee: Dmitrii Bocharov > Priority: Critical > Labels: regression, upstream > Fix For: 4.9.0.AM2 > > > I was not able to create server adapter for eap71-basic-s2i template application. > Pod error log: > {code:java} > --> Scaling eap-app-1 down to zero > --> Scaling eap-app-2 to 1 before performing acceptance check > error: update acceptor rejected eap-app-2: pods for rc 'myproject/eap-app-2' took longer than 600 seconds to become available > {code} > Error log from OpenShift console: > {code:java} > Readiness probe failed: { > "probe.eap.dmr.EapProbe": { > "probe.eap.dmr.ServerStatusTest": "running", > "probe.eap.dmr.DeploymentTest": "Exception executing test: unorderable types: Status() < Status()", > "probe.eap.dmr.BootErrorsTest": [ > { > "failed-operation": { > "operation": "deploy", > "address": [ > { > "deployment": "kitchensink.war" > } > ] > }, > "failure-description": "{\"WFLYCTL0080: Failed services\" => {\"jboss.deployment.unit.\\\"kitchensink.war\\\".FIRST_MODULE_USE\" => \"WFLYSRV0153: Failed to process phase FIRST_MODULE_USE of deployment \\\"kitchensink.war\\\"\n Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYJCA0064: Exception deploying datasource java:jboss/datasources/KitchensinkQuickstartDS\n Caused by: org.jboss.msc.service.DuplicateServiceException: Service jboss.data-source.\\\"jboss.naming.context.java.jboss.datasources.KitchensinkQuickstartDS\\\".statistics is already registered\"}}", > "failed-services": { > "jboss.deployment.unit.\"kitchensink.war\".FIRST_MODULE_USE": "WFLYSRV0153: Failed to process phase FIRST_MODULE_USE of deployment \"kitchensink.war\"\n Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYJCA0064: Exception deploying datasource java:jboss/datasources/KitchensinkQuickstartDS\n Caused by: org.jboss.msc.service.DuplicateServiceException: Service jboss.data-source.\"jboss.naming.context.java.jboss.datasources.KitchensinkQuickstartDS\".statistics is already registered" > } > } > ] > } > } > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26305) Jars inside an EAR application are not compressed

by Martin Malina (JIRA)

Martin Malina created JBIDE-26305: ------------------------------------- Summary: Jars inside an EAR application are not compressed Key: JBIDE-26305 URL: https://issues.jboss.org/browse/JBIDE-26305 Project: Tools (JBoss Tools) Issue Type: Bug Components: server Reporter: Martin Malina Assignee: Rob Stryker A customer has reported an issue where an ear project, when deployed to EAP 7.1, contains exploded jars which then breaks his app. It seems that in his case it happens both in the case of a jar inside a war inside an ear, as well as just a jar inside an ear. Also, when the customer deploys the same app in the same workspace and same eclipse to EAP 6.4, it works fine - all the jars are zipped. The customer reports that he can change this behavior in the Deployments tab of the server editor, but it would be nice to be able to define this beforehand in a config file. I tried to reproduce this in devstudio 12 and in my case the behavior was the same with both EAP 6.4 and 7.1 - in both cases an included jar was exploded which I think is wrong. So two main things to consider: 1. Is this a bug? I believe it is - a jar lib should always be zipped by default. Or do you disagree? 2. Is there a way to specify if a module of an EAP is zipped or not in a config file? If not, can this be added? -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4727) Incompatible Java (1.8) version for com.spotify.docker.client plugin and its dependencies

by Aurélien Pupier (JIRA)

[ https://issues.jboss.org/browse/JBDS-4727?page=com.atlassian.jira.plugin.... ] Aurélien Pupier commented on JBDS-4727: --------------------------------------- the version on orbit has been put by Evgeny Mandrikov. Do you know where is the repository for this orbit bundle? To try to find why a Java 9 requirements has been added. because I see none in asm project itself (but I might have missed it) > Incompatible Java (1.8) version for com.spotify.docker.client plugin and its dependencies > ----------------------------------------------------------------------------------------- > > Key: JBDS-4727 > URL: https://issues.jboss.org/browse/JBDS-4727 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: installer > Affects Versions: 12.9.0.AM2 > Reporter: Ondrej Dockal > Assignee: Nick Boldt > Priority: Blocker > Fix For: 12.9.0.AM2 > > Attachments: DevstudioIncompatibleJavaVersion.png, devstudio_12.9.0.AM2-v20180812-1704-B3167.log > > > I got following warning dialog after fresh start of devstudio: > !DevstudioIncompatibleJavaVersion.png|thumbnail! -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 7 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 August 2018