April 2018 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-24963) Create CDI 2 integration tests

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24963?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-24963: ------------------------------- Fix Version/s: 4.6.x (was: 4.5.x) > Create CDI 2 integration tests > ------------------------------ > > Key: JBIDE-24963 > URL: https://issues.jboss.org/browse/JBIDE-24963 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: cdi, integration-tests > Affects Versions: 4.5.1.AM2 > Reporter: Lukáš Valach > Assignee: Ondrej Dockal > Fix For: 4.6.x > > > The support for CDI 2.0 has been added recently, see JBIDE-24949. > Spec: > http://docs.jboss.org/cdi/spec/2.0/cdi-spec.html > Change log: > https://issues.jboss.org/secure/ReleaseNote.jspa?version=12325406&styleNa... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24495) Provide the equivalent to "oc new-build" && "oc start-build" && "oc expose"

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24495?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-24495: ------------------------------- Fix Version/s: 4.6.x (was: 4.5.x) > Provide the equivalent to "oc new-build" && "oc start-build" && "oc expose" > --------------------------------------------------------------------------- > > Key: JBIDE-24495 > URL: https://issues.jboss.org/browse/JBIDE-24495 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.4.4.Final > Reporter: Andre Dietisheim > Fix For: 4.6.x > > > [Helloworld MSA|https://cdn.rawgit.com/redhat-helloworld-msa/helloworld-msa/master/re...] - the reference examples for openshift - is using the command line client "oc" to create the applications in OpenShift. > A typical approach is doing the following: > {code} > $ oc new-build --binary --name=hola -l app=hola > $ mvn package; oc start-build hola --from-dir=. --follow > $ oc new-app hola -l app=hola,hystrix.enabled=true > $ oc expose service hola > {code} > For people to be able to run those with Eclipse tooling people should be able to run the equivalent in Eclipse. > The alternative approach, that's currently available in Eclipse is imbo less evident: Users can currently build docker images locally and deploy them to OpenShift. > The tricky part though - for now - is that the CDK is not providing access to the docker registry from the outside: the docker registry address is a private IP that's only reachable within OpenShift. Users can get around this limitation by building docker images using the docker daemon in OpenShift, which is publicly reachable. Once available in the OpenShift docker daemon it can be pushed to the OpenShift docker registry. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20529) Master JIRA for XML Validation Problems

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20529?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-20529: ------------------------------- Fix Version/s: 4.6.x (was: 4.5.x) > Master JIRA for XML Validation Problems > --------------------------------------- > > Key: JBIDE-20529 > URL: https://issues.jboss.org/browse/JBIDE-20529 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: project-examples, server > Reporter: Rob Stryker > Labels: xtriage > Fix For: 4.6.x > > > This JIRA is meant to be a master container jira for all xml validation issues. These include identifying projects that are enganging in bad xml behavior, projects that point to namespaces or xsd locations that no longer exist, example projects using relative paths for linking to other xsd, and others. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20972) As a user I want to see relevant but simple info about my OpenShift v3 server adapter in the servers view

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20972?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-20972: ------------------------------- Fix Version/s: 4.6.x (was: 4.5.x) > As a user I want to see relevant but simple info about my OpenShift v3 server adapter in the servers view > --------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20972 > URL: https://issues.jboss.org/browse/JBIDE-20972 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.Alpha1 > Reporter: Jeff Cantrill > Labels: openshift_v3, server_adapter > Fix For: 4.6.x > > Attachments: 2015-10-13 19.03.bmml, 2015-10-13 19.03.png, Console of 'App' with the pieces wired.png, Pipeline view mockup.bmml > > > Add an alternate view in the openshift v3 explorer to try to 'link' resources in a similiar fashion to the web console -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25316) JSF integration tests support, usage of the tooling

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25316?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-25316: ------------------------------- Fix Version/s: 4.6.x (was: 4.5.x) > JSF integration tests support, usage of the tooling > --------------------------------------------------- > > Key: JBIDE-25316 > URL: https://issues.jboss.org/browse/JBIDE-25316 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: jsf > Affects Versions: 4.5.2.AM1 > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Fix For: 4.6.x > > > Find out usage of JSF tooling, to what extent we should be supporting/testing the tooling as there seems to be no more development and issue are not being solved, if there are any. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22904) NoStackTrace in CDICoreValidator.init

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22904?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-22904: ------------------------------- Fix Version/s: 4.6.x (was: 4.5.x) > NoStackTrace in CDICoreValidator.init > ------------------------------------- > > Key: JBIDE-22904 > URL: https://issues.jboss.org/browse/JBIDE-22904 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdi > Affects Versions: 4.3.1.Final > Reporter: Automated Error Reporting Bot > Assignee: Viacheslav Kabanovich > Fix For: 4.6.x > > > The following problem was reported via the automated error reporting: > Message: Trying to validate P/claim-api-test but there is no CDI Nature in the project. > {noformat} > com.ctrlflow.aer.NoStackTrace: This event was logged without a stack trace. A synthetic stack trace was hence inserted. > at org.jboss.tools.cdi.internal.core.validation.CDICoreValidator.init(CDICoreValidator.java:308) > at org.jboss.tools.cdi.internal.core.validation.CDICoreValidator.validate(CDICoreValidator.java:566) > at org.jboss.tools.common.validation.AsYouTypeValidatorManager.validate(AsYouTypeValidatorManager.java:183) > at org.jboss.tools.common.validation.AsYouTypeValidatorManager.validateString(AsYouTypeValidatorManager.java:205) > at org.jboss.tools.common.validation.AsYouTypeValidatorManager.validateString(AsYouTypeValidatorManager.java:200) > at org.jboss.tools.common.validation.AsYouTypeValidatorManager.validate(AsYouTypeValidatorManager.java:254) > at org.eclipse.wst.sse.ui.internal.reconcile.validator.ReconcileStepForValidator.validate(ReconcileStepForValidator.java:381) > at org.eclipse.wst.sse.ui.internal.reconcile.validator.ReconcileStepForValidator.reconcileModel(ReconcileStepForValidator.java:259) > at org.eclipse.jface.text.reconciler.AbstractReconcileStep.reconcile(AbstractReconcileStep.java:95) > at org.eclipse.wst.sse.ui.internal.reconcile.validator.ValidatorStrategy.reconcile(ValidatorStrategy.java:269) > at org.eclipse.wst.sse.ui.internal.reconcile.DocumentRegionProcessor.process(DocumentRegionProcessor.java:321) > at org.eclipse.wst.sse.ui.internal.reconcile.StructuredRegionProcessor.process(StructuredRegionProcessor.java:258) > at org.eclipse.wst.sse.ui.internal.reconcile.DirtyRegionProcessor$BackgroundThread.run(DirtyRegionProcessor.java:691) > {noformat} > Bundles: > | org.eclipse.core.jobs | 3.7.0.v20150330-2103 | 3.7.0.v20150330-2103 | > | org.eclipse.jface.text | 3.10.0.v20150603-1752 | 3.11.0.v20160505-1301 | > | org.eclipse.wst.sse.ui | 1.3.401.v201510130005 | 1.3.500.v201605120129 | > | org.eclipse.wst.validation | 1.2.700.v201508251749 | 1.2.700.v201508251749 | > | org.jboss.tools.cdi.core | 1.7.1.Final-v20160330-2256-B84 | 1.8.0.Final-v20160610-0126-B1 | > | org.jboss.tools.common.validation | 3.7.1.Final-v20160408-2358-B112 | 3.8.0.Final-v20160610-1533-B7 | > Operating Systems: > | Linux | 3.11.0 | 4.4.15 | > | MacOSX | 10.11.5 | 10.11.5 | > | Windows | 6.1.0 | 10.0.0 | > The above information is a snapshot of the collected data. Visit [this page|https://redhat.ctrlflow.com/reviewers/#!/problems/57228358e4b0a54983...] for the latest data. > Thank you for your assistance. > Your friendly error-reports-inbox. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24899) Deploy Docker Image wizard: Image not found

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24899?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-24899: ------------------------------- Fix Version/s: 4.6.x (was: 4.5.x) > Deploy Docker Image wizard: Image not found > ------------------------------------------- > > Key: JBIDE-24899 > URL: https://issues.jboss.org/browse/JBIDE-24899 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk, docker, openshift > Affects Versions: 4.5.1.AM1 > Reporter: Josef Kopriva > Assignee: Jeff MAURY > Labels: deploy_docker_wizard, openshift_v3 > Fix For: 4.6.x > > Attachments: image-2017-08-29-09-50-20-927.png > > > Exception in Error log: > {code:java} > Failed to inspect image: '172.30.1.1:5000/test/hola:latest' > com.spotify.docker.client.exceptions.ImageNotFoundException: Image not found: 172.30.1.1:5000/test/hola:latest > at com.spotify.docker.client.DefaultDockerClient.inspectImage(DefaultDockerClient.java:1330) > at org.eclipse.linuxtools.internal.docker.core.DockerConnection.getImageInfo(DockerConnection.java:896) > at org.jboss.tools.openshift.internal.ui.wizard.deployimage.DeployImageWizardModel.lookupImageMetadata(DeployImageWizardModel.java:655) > at org.jboss.tools.openshift.internal.ui.wizard.deployimage.DeployImageWizardModel.initializeContainerInfo(DeployImageWizardModel.java:354) > at org.jboss.tools.openshift.internal.ui.wizard.deployimage.DeployImagePage$1ImageValidatorJob.run(DeployImagePage.java:154) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56) > Caused by: com.spotify.docker.client.exceptions.DockerRequestException: Request error: GET https://192.168.42.121:2376/images/172.30.1.1:5000/test/hola:latest/json: 404 > at com.spotify.docker.client.DefaultDockerClient.propagate(DefaultDockerClient.java:2084) > at com.spotify.docker.client.DefaultDockerClient.request(DefaultDockerClient.java:2023) > at com.spotify.docker.client.DefaultDockerClient.inspectImage(DefaultDockerClient.java:1326) > ... 5 more > Caused by: javax.ws.rs.NotFoundException: HTTP 404 Not Found > at org.glassfish.jersey.client.JerseyInvocation.convertToException(JerseyInvocation.java:1008) > at org.glassfish.jersey.client.JerseyInvocation.translate(JerseyInvocation.java:816) > at org.glassfish.jersey.client.JerseyInvocation.access$700(JerseyInvocation.java:92) > at org.glassfish.jersey.client.JerseyInvocation$5.completed(JerseyInvocation.java:773) > at org.glassfish.jersey.client.ClientRuntime.processResponse(ClientRuntime.java:198) > at org.glassfish.jersey.client.ClientRuntime.access$300(ClientRuntime.java:79) > at org.glassfish.jersey.client.ClientRuntime$2.run(ClientRuntime.java:180) > at org.glassfish.jersey.internal.Errors$1.call(Errors.java:271) > at org.glassfish.jersey.internal.Errors$1.call(Errors.java:267) > at org.glassfish.jersey.internal.Errors.process(Errors.java:315) > at org.glassfish.jersey.internal.Errors.process(Errors.java:297) > at org.glassfish.jersey.internal.Errors.process(Errors.java:267) > at org.glassfish.jersey.process.internal.RequestScope.runInScope(RequestScope.java:340) > at org.glassfish.jersey.client.ClientRuntime$3.run(ClientRuntime.java:210) > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > at java.lang.Thread.run(Thread.java:748) > eclipse.buildId=11.1.0.AM1-v20170824-1835-B873 > java.version=1.8.0_141 > java.vendor=Oracle Corporation > BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US > Framework arguments: -product com.jboss.devstudio.core.product > Command-line arguments: -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18329) Ionic, tabs, CordovaSim, LiveReload, lost back button

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18329?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-18329: ------------------------------- Fix Version/s: 4.6.x (was: 4.5.x) > Ionic, tabs, CordovaSim, LiveReload, lost back button > ----------------------------------------------------- > > Key: JBIDE-18329 > URL: https://issues.jboss.org/browse/JBIDE-18329 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cordovasim > Affects Versions: 4.2.0.CR1 > Reporter: Burr Sutter > Assignee: Ilya Buziuk > Labels: upstream > Fix For: 4.6.x > > > Using Ionic tabs starter/template > LiveReload > CordovaSim > to edit friend-detail.html > works almost awesome...but for the disappearing Back button > http://www.screencast.com/t/APqNTq7K3c > upsteam issue - https://github.com/driftyco/ionic/issues/3222 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24981) Server adapter: fails to start if app has no dc but only a rc

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24981?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-24981: ------------------------------- Fix Version/s: 4.6.x (was: 4.5.x) > Server adapter: fails to start if app has no dc but only a rc > ------------------------------------------------------------- > > Key: JBIDE-24981 > URL: https://issues.jboss.org/browse/JBIDE-24981 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.1.AM1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: openhift_v3, server_adapter > Fix For: 4.6.x > > Attachments: eap-without-service-nor-deploymentconfig.json, image-2017-09-04-22-15-46-383.png, image-2017-09-04-22-17-26-655.png, started-even-though-failed-starting.png > > > # ASSERT: make sure that you have an app that has NO deployment config, just a replication controller > (EXEC: if you dont, create it via the attached custom template [^eap-without-service-nor-deploymentconfig.json]) > # EXEC: in explorer: once your app is created, create a server adapter for it, binding the imported source to the replication controller that's available > # ASSERT: the server adapter is starting up > !image-2017-09-04-22-15-46-383.png! > Result: > The server adapter keeps starting up without reaching "[Started]", waiting at 7%. Finally - > after a few minutes, it fails with the following error: > !image-2017-09-04-22-17-26-655.png! > > Furthermore, once you close the error dialog the server is in state "[Started]" even though it errored while starting up > !started-even-though-failed-starting.png! -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18983) Project cannot be built. Possible open file handle

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18983?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-18983: ------------------------------- Fix Version/s: 4.6.x (was: 4.5.x) > Project cannot be built. Possible open file handle > -------------------------------------------------- > > Key: JBIDE-18983 > URL: https://issues.jboss.org/browse/JBIDE-18983 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsp/jsf/xml/html-source-editing, maven > Affects Versions: 4.2.1.Final > Environment: luna x64 windows 8.1 x64 > java 8u25 x64 > Reporter: Cody Lerum > Assignee: Jeff MAURY > Fix For: 4.6.x > > > Frequently when working in a Java EE7 project I will get an error like. > "The project was not built due to "Could not delete '/gp-server/target/classes/META-INF`.". Fix the problem, then try refreshing this project and building since it may be inconsistent. > I've looked into a process explorer in windows and then this case is happening there is always a javaw.exe process with a file handle to "V:\workspace\gp-server\target\classes\META-INF\persistence.xml > It looks like either jboss tools or eclipse is holding on to a file handle for this. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 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 April 2018