August 2018 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-26296) Remove JBoss from maven.apt feature.properties

by Martin Malina (JIRA)

Martin Malina created JBIDE-26296: ------------------------------------- Summary: Remove JBoss from maven.apt feature.properties Key: JBIDE-26296 URL: https://issues.jboss.org/browse/JBIDE-26296 Project: Tools (JBoss Tools) Issue Type: Bug Components: build Affects Versions: 4.9.0.AM2 Reporter: Martin Malina Assignee: Martin Malina Fix For: 4.9.0.AM2 In JBDS-4709 Nick removed all mentions of "JBoss by Red Hat" in feature.properties but there was just one occurrence left: https://github.com/jbosstools/m2e-apt/blob/master/org.jboss.tools.maven.a... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26030) VPE tests times out due to SWT on GTK 2.x: nsIWebBrowser is not available

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26030?page=com.atlassian.jira.plugi... ] Ondrej Dockal closed JBIDE-26030. --------------------------------- Latest vpe tests are mostly green. > VPE tests times out due to SWT on GTK 2.x: nsIWebBrowser is not available > ------------------------------------------------------------------------- > > Key: JBIDE-26030 > URL: https://issues.jboss.org/browse/JBIDE-26030 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: visual-page-editor-core, visual-page-editor-templates > Affects Versions: 4.6.0.AM1 > Reporter: Nick Boldt > Assignee: Jeff MAURY > Priority: Blocker > Fix For: 4.6.0.AM3 > > Attachments: Screenshot_2018-05-22_16-58-14.png, Screenshot_2018-05-22_17-06-17.png, Screenshot_2018-05-23_10-33-11.png, Screenshot_2018-05-23_10-46-44.png, dialog-wrong-engine.png > > > We've been having this problem for a while now with the VPE builds: > {code} > !MESSAGE Could not open the Visual Page Editor: > No more handles because no underlying browser available. > SWT on GTK 2.x detected. It is reccomended to use SWT on GTK 3.x and Webkit2 API. > !STACK 0 > org.eclipse.swt.SWTError: No more handles because no underlying browser available. > SWT on GTK 2.x detected. It is reccomended to use SWT on GTK 3.x and Webkit2 API. > at org.eclipse.swt.SWT.error(SWT.java:4578) > at org.eclipse.swt.browser.Browser.<init>(Browser.java:125) > at org.jboss.tools.vpe.xulrunner.browser.XulRunnerBrowser.<init>(XulRunnerBrowser.java:123) > at org.jboss.tools.vpe.xulrunner.editor.XulRunnerEditor.<init>(XulRunnerEditor.java:128){code} > from https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > or https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > or https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26015) write doc about using ccipush/pull scripts to manage Jenkins jobs on CCI

by Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26015?page=com.atlassian.jira.plugi... ] Josef Kopriva closed JBIDE-26015. --------------------------------- Closing, commits are merged. > write doc about using ccipush/pull scripts to manage Jenkins jobs on CCI > ------------------------------------------------------------------------ > > Key: JBIDE-26015 > URL: https://issues.jboss.org/browse/JBIDE-26015 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, devdoc > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.6.0.Final > > > Need new doc(s) in https://github.com/jbosstools/jbosstools-devdoc/ > * get and build maven tool from https://github.com/nickboldt/maven-plugins/tree/master/hudson-job-sync-pl... > * configure keystore per https://github.com/nickboldt/maven-plugins/blob/master/hudson-job-sync-pl... > * jenkins crumbs - https://stackoverflow.com/questions/16738441/how-to-request-for-crumb-iss... > * set up bash & pom-sync.xml scripts (with examples) > * pull jobs (one by one or batch modes) > * edit jobs / save changes to github repo > * push jobs back to server (one by one or batch push mode) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26071) Add server adapter for WildFly 13

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26071?page=com.atlassian.jira.plugi... ] Pavol Srna closed JBIDE-26071. ------------------------------ > Add server adapter for WildFly 13 > --------------------------------- > > Key: JBIDE-26071 > URL: https://issues.jboss.org/browse/JBIDE-26071 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Affects Versions: 4.6.0.AM2 > Reporter: Martin Malina > Assignee: Rob Stryker > Priority: Blocker > Fix For: 4.6.0.Final > > > It turns out WildFly 13 was released yesterday. They're on a quarterly release cadence now apparently. So I wonder how we should deal with this. Perhaps should group some of the versions if there are no breaking changes for us? Or do you think it's better to stick with our current model of always adding a new adapter and that way you can always update the libs? -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26097) remove TARGET_PLATFORM_CENTRAL_MAX and TARGET_PLATFORM_VERSION_MAX hardcoding in Jenkins jobs; read from parent pom

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26097?page=com.atlassian.jira.plugi... ] Pavol Srna closed JBIDE-26097. ------------------------------ > remove TARGET_PLATFORM_CENTRAL_MAX and TARGET_PLATFORM_VERSION_MAX hardcoding in Jenkins jobs; read from parent pom > ------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-26097 > URL: https://issues.jboss.org/browse/JBIDE-26097 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.6.0.AM3 > > > remove TARGET_PLATFORM_CENTRAL_MAX and TARGET_PLATFORM_VERSION_MAX hardcoding in Jenkins jobs > Instead, read from parent pom like this: > {code} > function getVar() { > file=$1 > var=$2 > getVar_return=$(grep "<${var}>" $file | sed -e "s#.*<${var}>$.\+$</${var}>.*#\1#") > } > wget https://raw.githubusercontent.com/jbosstools/jbosstools-build/master/pare... -O parent-pom.xml > getVar pom.xml TARGET_PLATFORM_VERSION_MAX; TARGET_PLATFORM_VERSION_MAX=$getVar_return > getVar pom.xml TARGET_PLATFORM_CENTRAL_MAX; TARGET_PLATFORM_CENTRAL_MAX=$getVar_return > rm -f parent-pom.xml > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26029) Incorrect warning for @Inject ServletContext

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26029?page=com.atlassian.jira.plugi... ] Pavol Srna closed JBIDE-26029. ------------------------------ > Incorrect warning for @Inject ServletContext > -------------------------------------------- > > Key: JBIDE-26029 > URL: https://issues.jboss.org/browse/JBIDE-26029 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdi > Affects Versions: 4.5.3.Final > Reporter: Rich DiCroce > Assignee: Jeff MAURY > Fix For: 4.6.0.AM3 > > > If you inject ServletContext into a CDI bean, it gets flagged with this warning: > {quote} > No bean is eligible for injection to the injection point [JSR-346 §5.2.2] > {quote} > This warning appears to be correct for CDI 1.0, but not for later versions. From CDI 2.0 spec section 18.8 (also CDI 1.1/1.2 section 3.8): > {quote} > A servlet container must provide the following built-in beans, all of which have qualifier @Default: > * a bean with bean type javax.servlet.http.HttpServletRequest, allowing injection of a reference to the HttpServletRequest > * a bean with bean type javax.servlet.http.HttpSession, allowing injection of a reference to the HttpSession, > * a bean with bean type javax.servlet.ServletContext, allowing injection of a reference to the ServletContext, > {quote} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4724) Replace vendor attribution "JBoss by Red Hat" with "Red Hat" - maven.apt

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBDS-4724?page=com.atlassian.jira.plugin.... ] Martin Malina updated JBDS-4724: -------------------------------- Issue Type: Technical task (was: Sub-task) Workflow: classic default workflow (was: GIT Pull Request workflow ) > Replace vendor attribution "JBoss by Red Hat" with "Red Hat" - maven.apt > ------------------------------------------------------------------------ > > Key: JBDS-4724 > URL: https://issues.jboss.org/browse/JBDS-4724 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Technical task > Components: build > Affects Versions: 12.0.0.AM2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 12.0.0.AM3 > > > In nearly all the plugins/features/product defintion/installer, we use "JBoss by Red Hat" as the vendor / attribution. > It's been suggested we should replace this. Perhaps with "Red Hat" or "Red Hat, Inc." > As IANAL, I'll wait for [~rpdavis], [~fontana] and @jburkitt to weigh in here before proceeding. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4709) Replace vendor attribution "JBoss by Red Hat" with "Red Hat"

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-4709?page=com.atlassian.jira.plugin.... ] Jan Richter closed JBDS-4709. ----------------------------- > Replace vendor attribution "JBoss by Red Hat" with "Red Hat" > ------------------------------------------------------------- > > Key: JBDS-4709 > URL: https://issues.jboss.org/browse/JBDS-4709 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Sub-task > Components: build > Affects Versions: 12.0.0.AM2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 12.0.0.AM3 > > > In nearly all the plugins/features/product defintion/installer, we use "JBoss by Red Hat" as the vendor / attribution. > It's been suggested we should replace this. Perhaps with "Red Hat" or "Red Hat, Inc." > As IANAL, I'll wait for [~rpdavis], [~fontana] and @jburkitt to weigh in here before proceeding. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4724) Replace vendor attribution "JBoss by Red Hat" with "Red Hat" - maven.apt

by Martin Malina (JIRA)

Martin Malina created JBDS-4724: ----------------------------------- Summary: Replace vendor attribution "JBoss by Red Hat" with "Red Hat" - maven.apt Key: JBDS-4724 URL: https://issues.jboss.org/browse/JBDS-4724 Project: Red Hat JBoss Developer Studio (devstudio) Issue Type: Sub-task Components: build Affects Versions: 12.0.0.AM2 Reporter: Nick Boldt Assignee: Nick Boldt Fix For: 12.0.0.AM3 In nearly all the plugins/features/product defintion/installer, we use "JBoss by Red Hat" as the vendor / attribution. It's been suggested we should replace this. Perhaps with "Red Hat" or "Red Hat, Inc." As IANAL, I'll wait for [~rpdavis], [~fontana] and @jburkitt to weigh in here before proceeding. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26040) Error for JAX-RS 2.1 @Context types

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26040?page=com.atlassian.jira.plugi... ] Pavol Srna closed JBIDE-26040. ------------------------------ Verified in Devstudio 12.9.0.AM1 > Error for JAX-RS 2.1 @Context types > ----------------------------------- > > Key: JBIDE-26040 > URL: https://issues.jboss.org/browse/JBIDE-26040 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Affects Versions: 4.5.3.Final > Reporter: Rich DiCroce > Assignee: Jeff MAURY > Fix For: 4.6.0.AM3 > > > JAX-RS 2.1 adds some new types that can be injected into methods using the Context annotation, e.g. Sse and SseEventSink. Currently, JBoss Tools flags these with an error: > {quote} > @Context annotation is only allowed on method parameters of type '[javax.ws.rs.core.HttpHeaders, javax.ws.rs.core.UriInfo, javax.ws.rs.core.Request, javax.servlet.http.HttpServletRequest, javax.servlet.http.HttpServletResponse, javax.servlet.ServletConfig, javax.servlet.ServletContext, javax.ws.rs.core.SecurityContext]'. > {quote} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 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