May 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22329) JavaModelException below JdtUtils.findDeclaringNode (thrown in JavaElement.newNotPresentException)

by Automated Error Reporting Bot (JIRA)

Automated Error Reporting Bot created JBIDE-22329: ----------------------------------------------------- Summary: JavaModelException below JdtUtils.findDeclaringNode (thrown in JavaElement.newNotPresentException) Key: JBIDE-22329 URL: https://issues.jboss.org/browse/JBIDE-22329 Project: Tools (JBoss Tools) Issue Type: Bug Components: webservices Reporter: Automated Error Reporting Bot The following problem was reported via the automated error reporting: Message: Failed to build or refresh the JAX-RS metamodel {noformat} org.eclipse.jdt.core.JavaModelException: submt(HttpServletRequest, int) [in PublicWS [in [Working copy] PublicWS.java [in be.fromprison.ws.endpoints [in src/main/java [in from-prison]]]]] does not exist at org.eclipse.jdt.internal.core.JavaElement.newNotPresentException(JavaElement.java:556) at org.eclipse.jdt.internal.core.JavaElement.openWhenClosed(JavaElement.java:590) at org.eclipse.jdt.internal.core.JavaElement.getElementInfo(JavaElement.java:316) at org.eclipse.jdt.internal.core.JavaElement.getElementInfo(JavaElement.java:302) at org.eclipse.jdt.internal.core.SourceRefElement.getSourceRange(SourceRefElement.java:218) at org.jboss.tools.ws.jaxrs.core.jdt.JdtUtils.findDeclaringNode(JdtUtils.java:494) at org.jboss.tools.ws.jaxrs.core.jdt.JdtUtils.resolveAllAnnotations(JdtUtils.java:373) at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsResourceMethod$Builder.buildInResource(JaxrsResourceMethod.java:153) at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsElementFactory.createElements(JaxrsElementFactory.java:211) at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsElementFactory.createElements(JaxrsElementFactory.java:65) at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsMetamodel.processJavaElementChange(JaxrsMetamodel.java:420) at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsMetamodel.processJavaElementChange(JaxrsMetamodel.java:392) at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JavaElementChangedBuildJob.run(JavaElementChangedBuildJob.java:73) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) {noformat} Bundles: | org.eclipse.core.jobs | 3.7.0.v20150330-2103 | 3.7.0.v20150330-2103 | | org.eclipse.jdt.core | 3.11.2.v20160128-0629 | 3.11.2.v_OTDT_r242_201601310642 | | org.eclipse.wst.sse.ui | 1.3.401.v201510130005 | 1.3.401.v201510130005 | | org.jboss.tools.common.validation | 3.7.1.Final-v20160408-2358-B112 | 3.7.1.Final-v20160408-2358-B112 | | org.jboss.tools.ws.jaxrs.core | 1.8.1.Final-v20160331-0952-B76 | 1.8.1.Final-v20160331-0952-B76 | | org.jboss.tools.ws.jaxrs.ui | 1.8.1.Final-v20160331-0952-B76 | 1.8.1.Final-v20160331-0952-B76 | Operating Systems: | Linux | 3.16.0 | 4.4.7.fc23 | | MacOSX | 10.11.4 | 10.11.4 | | 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/571dd2b8e4b08bd809...] for the latest data. Thank you for your assistance. Your friendly error-reports-inbox. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21587) Move OpenShift databinding utils to common

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21587?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-21587: ------------------------------------------ The PR should get different improvements for the javadocs and tests. And then it should be corrected to move the classes to foundation, not commons. > Move OpenShift databinding utils to common > ------------------------------------------ > > Key: JBIDE-21587 > URL: https://issues.jboss.org/browse/JBIDE-21587 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: common/jst/core, openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Andre Dietisheim > Assignee: Alexey Kazakov > Fix For: 4.4.x > > > We have databinding utils in OpenShift that we want to move to commons/base -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22324) LiveRelead needs to update to newer Jetty

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22324?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-22324: ---------------------------------------- thanks! > LiveRelead needs to update to newer Jetty > ----------------------------------------- > > Key: JBIDE-22324 > URL: https://issues.jboss.org/browse/JBIDE-22324 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build, livereload, target-platform > Affects Versions: 4.4.0.Alpha2 > Reporter: Mickael Istria > Assignee: Xavier Coulon > Priority: Blocker > Fix For: 4.4.0.Alpha2 > > > With move to M7, livereload build fails: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-livereloa... > It has to be updated to use newer version of Jetty. in TP (9.3.6). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22318) Create JMX PoC Connection to Openshift EAP

by Thomas Mäder (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22318?page=com.atlassian.jira.plugi... ] Thomas Mäder commented on JBIDE-22318: -------------------------------------- There is an $ADMIN_USERNAME and $ADMIN_PASSWORD parameter that is used in the start script. > Create JMX PoC Connection to Openshift EAP > ------------------------------------------ > > Key: JBIDE-22318 > URL: https://issues.jboss.org/browse/JBIDE-22318 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: openshift > Reporter: Thomas Mäder > Assignee: Thomas Mäder > Fix For: 4.4.x > > > Find out what is needed to connect to an EAP instance inside an Openshift pod -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22318) Create JMX PoC Connection to Openshift EAP

by Thomas Mäder (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22318?page=com.atlassian.jira.plugi... ] Thomas Mäder commented on JBIDE-22318: -------------------------------------- It's not clear how to do #3 externally yet. The approach to debugging is to change the deployment config to restart the pod in debug mode. Can we set up mangement credentials in the deployment config? > Create JMX PoC Connection to Openshift EAP > ------------------------------------------ > > Key: JBIDE-22318 > URL: https://issues.jboss.org/browse/JBIDE-22318 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: openshift > Reporter: Thomas Mäder > Assignee: Thomas Mäder > Fix For: 4.4.x > > > Find out what is needed to connect to an EAP instance inside an Openshift pod -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22318) Create JMX PoC Connection to Openshift EAP

by Thomas Mäder (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22318?page=com.atlassian.jira.plugi... ] Thomas Mäder edited comment on JBIDE-22318 at 5/11/16 3:54 AM: --------------------------------------------------------------- Was able to connect JConsole to Openshift. Here are the steps that are to do: # Had to create my own run script for s2i the start script uses standalone-openshift.sh, which adds "-bmanagement 127.0.0.1" to the command line. This makes it impossible to forward to that port from localhost. # Had to add the port 9999 to the forwardable ports of the pod in the deployment config # Had to add username/password for a managment user via add-user.sh # Start port forwarding for the pod was (Author: tmader): Was able to connect JConsole to Openshift. Here are the steps that are to do: # Had to create my own run script for s2i the start script uses standalone-openshift.sh, which adds "-bmanagement 127.0.0.1" to the command line. This makes it impossible to forward to that port from localhost. # Had to add the port 9999 to the forwardable ports of the pod in the deployment config # Had to add username/password for a managment user via add-user.sh > Create JMX PoC Connection to Openshift EAP > ------------------------------------------ > > Key: JBIDE-22318 > URL: https://issues.jboss.org/browse/JBIDE-22318 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: openshift > Reporter: Thomas Mäder > Assignee: Thomas Mäder > Fix For: 4.4.x > > > Find out what is needed to connect to an EAP instance inside an Openshift pod -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22318) Create JMX PoC Connection to Openshift EAP

by Thomas Mäder (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22318?page=com.atlassian.jira.plugi... ] Thomas Mäder commented on JBIDE-22318: -------------------------------------- Was able to connect JConsole to Openshift. Here are the steps that are to do: # Had to create my own run script for s2i the start script uses standalone-openshift.sh, which adds "-bmanagement 127.0.0.1" to the command line. This makes it impossible to forward to that port from localhost. # Had to add the port 9999 to the forwardable ports of the pod in the deployment config # Had to add username/password for a managment user via add-user.sh > Create JMX PoC Connection to Openshift EAP > ------------------------------------------ > > Key: JBIDE-22318 > URL: https://issues.jboss.org/browse/JBIDE-22318 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: openshift > Reporter: Thomas Mäder > Fix For: 4.4.x > > > Find out what is needed to connect to an EAP instance inside an Openshift pod -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22318) Create JMX PoC Connection to Openshift EAP

by Thomas Mäder (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22318?page=com.atlassian.jira.plugi... ] Thomas Mäder reassigned JBIDE-22318: ------------------------------------ Assignee: Thomas Mäder > Create JMX PoC Connection to Openshift EAP > ------------------------------------------ > > Key: JBIDE-22318 > URL: https://issues.jboss.org/browse/JBIDE-22318 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: openshift > Reporter: Thomas Mäder > Assignee: Thomas Mäder > Fix For: 4.4.x > > > Find out what is needed to connect to an EAP instance inside an Openshift pod -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22253) Update to SWTBot 2.4.0

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22253?page=com.atlassian.jira.plugi... ] Jan Richter closed JBIDE-22253. ------------------------------- Verified with 4.4.0.Alpha1 (4.60.0.Alpha1 TP) > Update to SWTBot 2.4.0 > ---------------------- > > Key: JBIDE-22253 > URL: https://issues.jboss.org/browse/JBIDE-22253 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: qa, target-platform > Affects Versions: 4.3.1.Final > Reporter: Mickael Istria > Assignee: Mickael Istria > Priority: Minor > Fix For: 4.4.0.Alpha1 > > > *Reason:* SWTBot 2.4.0 comes with several fixes (about menus) and other that JBT/JBDS can probably take advantage of > *Project page/sources:* http://eclipse.org/swtbot > *Version:* 2.4.0 > *License and owner:* EPL, Eclipse.org > *Original p2 repo:* http://download.eclipse.org/technology/swtbot/releases/2.4.0 > *JBoss mirror:* http://download.jboss.org/jbosstools/updates/requirements/swtbot/2.4.0/ > *Include Sources:* No > *Affected JBoss Tools components:* tests > *Include in JBDS:* No > *Type of dependency:* testing > *List of bundles added/removed:* > {code} > {code} > If applicable: > *non-p2 repository:* ... > *non-p2 ids:* ... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22317) Cannot build jbosstools-central locally

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22317?page=com.atlassian.jira.plugi... ] Mickael Istria resolved JBIDE-22317. ------------------------------------ Resolution: Done SNAPSHOT are volatile and can be removed any time depending on the remote repository settings. I don't know what's the rules for Nexus@JBoss but I guess it just thought the SNAPSHOT was too old. Anyway, now you published it again, it works. Thanks! PS: is this going to change by next versions? In case it changes rarely, it would be worth considering a release of that artifact so it gets persisted. > Cannot build jbosstools-central locally > --------------------------------------- > > Key: JBIDE-22317 > URL: https://issues.jboss.org/browse/JBIDE-22317 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, central > Affects Versions: 4.4.0.Alpha1 > Reporter: Mickael Istria > Assignee: Fred Bricon > Priority: Blocker > Fix For: 4.4.0.Alpha2 > > > With a clean jbosstools-central, "mvn clean verify" fails locally with > {code} > [ERROR] Failed to execute goal org.apache.maven.plugins:maven-dependency-plugin:2.7:copy (copy-central-webpage) on project org.jboss.tools.central: Unable to find artifact. Could not find artifact org.jboss.tools.central:jbosstools-central-webpage:zip:2.0.0-SNAPSHOT in jboss-public-repository-group (http://repository.jboss.org/nexus/content/groups/public/) > [ERROR] > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 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 May 2016