June 2018 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-25597) TP: create target platforms based on Eclipse Photon

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25597?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-25597: ------------------------------------ [checkUnresolvedIssues.py] Slip to fixversion = *4.6.x* > TP: create target platforms based on Eclipse Photon > --------------------------------------------------- > > Key: JBIDE-25597 > URL: https://issues.jboss.org/browse/JBIDE-25597 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: target-platform > Affects Versions: 4.5.2.Final > Reporter: Jeff MAURY > Assignee: Nick Boldt > Labels: target-platform > Fix For: 4.6.0.Final, 4.6.x > > Attachments: base.log > > > In order to start Photon based builds, we need a working Photon based target platform > For sprint 148 / AM1: Photon.0.M6 > For sprint 149 / AM2: Photon.0.M7 > For sprint 150 / AM3: Photon.0.RC3 > For sprint 151 / GA: Photon.0.GA -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25109) Server adapter editor: provide ability to only change debug port (and not the debug port key)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25109?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-25109: ------------------------------- Fix Version/s: 4.6.x (was: 4.6.0.AM3) > Server adapter editor: provide ability to only change debug port (and not the debug port key) > --------------------------------------------------------------------------------------------- > > Key: JBIDE-25109 > URL: https://issues.jboss.org/browse/JBIDE-25109 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.5.1.AM2 > Reporter: Andre Dietisheim > Assignee: Dmitrii Bocharov > Labels: openshift_v3, server_adapter_editor > Fix For: 4.6.x > > > Currently there's only 1 checkbox to allow the user to set the debugging key and port. If one only wants to set a custom debug port only, he cannot, he also has to provide the debug key at the same time. We should provide an additional checkbox to enable the debug port only, changing the existing one to only enable/disable the debug key. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25109) Server adapter editor: provide ability to only change debug port (and not the debug port key)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25109?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-25109: ------------------------------------ [checkUnresolvedIssues.py] Slip to fixversion = *4.6.x* > Server adapter editor: provide ability to only change debug port (and not the debug port key) > --------------------------------------------------------------------------------------------- > > Key: JBIDE-25109 > URL: https://issues.jboss.org/browse/JBIDE-25109 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.5.1.AM2 > Reporter: Andre Dietisheim > Assignee: Dmitrii Bocharov > Labels: openshift_v3, server_adapter_editor > Fix For: 4.6.x > > > Currently there's only 1 checkbox to allow the user to set the debugging key and port. If one only wants to set a custom debug port only, he cannot, he also has to provide the debug key at the same time. We should provide an additional checkbox to enable the debug port only, changing the existing one to only enable/disable the debug key. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4684) Remove "standalone" from installation jar

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4684?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-4684: ----------------------------- Fix Version/s: 12.0.0.GA (was: 12.x) > Remove "standalone" from installation jar > ----------------------------------------- > > Key: JBDS-4684 > URL: https://issues.jboss.org/browse/JBDS-4684 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: installer > Affects Versions: 11.3.0.AM2 > Reporter: Josef Kopriva > Assignee: Nick Boldt > Priority: Optional > Fix For: 12.0.0.GA > > > Change jar filename from "devstudio-11.3.0.AM2-v20180301-2015-B2134-installer-standalone.jar" to "devstudio-11.3.0.AM2-v20180301-2015-B2134-installer.jar". > I do not see a reason to have "standalone" in filename as we do not have jar with bundled EAP for some time. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26031) org.jboss.tools.jst.web.kb.FaceletValidatorExclude references validator ids that do not exist in org.eclipse.jst.jsf

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26031?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-26031: ------------------------------- Fix Version/s: 4.6.x (was: 4.6.0.AM3) > org.jboss.tools.jst.web.kb.FaceletValidatorExclude references validator ids that do not exist in org.eclipse.jst.jsf > -------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-26031 > URL: https://issues.jboss.org/browse/JBIDE-26031 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: visual-page-editor-core > Affects Versions: 4.6.0.AM1 > Reporter: Nick Boldt > Assignee: Jeff MAURY > Fix For: 4.6.x > > > Two validator IDs are referenced which do not exist. > {code} > 15:54:54 !MESSAGE Plug-in configuration error, extension "org.jboss.tools.jst.web.kb.FaceletValidatorExclude" > references validator id "org.eclipse.jst.jsf.facelet.ui.FaceletHTMLValidator" but this id does not exist.{code} > {code} > 15:54:54 !MESSAGE Plug-in configuration error, extension "org.jboss.tools.jst.web.kb.FaceletValidatorExclude" > references validator id "org.eclipse.jst.jsf.ui.JSFNonELAttributeValueValidator" but this id does not exist.{code} > As seen in 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26034) test failures in archives.ui.bot.*

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26034?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-26034: ------------------------------------ [checkUnresolvedIssues.py] Slip to fixversion = *4.6.x* > test failures in archives.ui.bot.* > ---------------------------------- > > Key: JBIDE-26034 > URL: https://issues.jboss.org/browse/JBIDE-26034 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: archives, server > Affects Versions: 4.6.0.AM2 > Reporter: Nick Boldt > Assignee: Rastislav Wagner > Fix For: 4.6.0.Final > > > 9 tests have been failing for 25 builds: > {code} > org.jboss.ide.eclipse.archives.ui.test.bot.FolderTest.testCreatingFolder no-configuration 2.4 sec 25 > org.jboss.ide.eclipse.archives.ui.test.bot.FolderTest.testModifyingFolder no-configuration 2.7 sec 25 > org.jboss.ide.eclipse.archives.ui.test.bot.FilesetTest.testCreatingFileset no-configuration 2.8 sec 25 > org.jboss.ide.eclipse.archives.ui.test.bot.FilesetTest.testModifyingFileset no-configuration 3 sec 25 > org.jboss.ide.eclipse.archives.ui.test.bot.FilesetTest.testDeletingFileset no-configuration 2.8 sec 25 > org.jboss.ide.eclipse.archives.ui.test.bot.UserLibrariesFilesetTest.testCreatingUserLibraryFileset no-configuration 1.8 sec 25 > org.jboss.ide.eclipse.archives.ui.test.bot.CreatingArchiveTest.testCreatingArchiveWithExplorer no-configuration 0.8 sec 25 > org.jboss.ide.eclipse.archives.ui.test.bot.DeletingArchiveTest.testDeletingArchiveWithExplorer no-configuration 1 sec 25 > org.jboss.ide.eclipse.archives.ui.test.bot.ModifyingArchiveTest.testModifyingArchiveWithExplorer no-configuration 1 sec 25 > {code} > These 3 failures are newer: > {code} > org.jboss.ide.eclipse.archives.ui.test.bot.BuildingArchiveTest.testBuildingArchiveWithView no-configuration 0.75 sec 1 > org.jboss.ide.eclipse.archives.ui.test.bot.FolderTest.testDeletingFolder no-configuration 3.4 sec 2 > org.jboss.ide.eclipse.archives.ui.test.bot.BuildingProjectTest.testBuildingProjectWithExplorer no-configuration 0.66 sec 12 > {code} > -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26031) org.jboss.tools.jst.web.kb.FaceletValidatorExclude references validator ids that do not exist in org.eclipse.jst.jsf

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26031?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-26031: ------------------------------------ [checkUnresolvedIssues.py] Slip to fixversion = *4.6.x* > org.jboss.tools.jst.web.kb.FaceletValidatorExclude references validator ids that do not exist in org.eclipse.jst.jsf > -------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-26031 > URL: https://issues.jboss.org/browse/JBIDE-26031 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: visual-page-editor-core > Affects Versions: 4.6.0.AM1 > Reporter: Nick Boldt > Assignee: Jeff MAURY > Fix For: 4.6.x > > > Two validator IDs are referenced which do not exist. > {code} > 15:54:54 !MESSAGE Plug-in configuration error, extension "org.jboss.tools.jst.web.kb.FaceletValidatorExclude" > references validator id "org.eclipse.jst.jsf.facelet.ui.FaceletHTMLValidator" but this id does not exist.{code} > {code} > 15:54:54 !MESSAGE Plug-in configuration error, extension "org.jboss.tools.jst.web.kb.FaceletValidatorExclude" > references validator id "org.eclipse.jst.jsf.ui.JSFNonELAttributeValueValidator" but this id does not exist.{code} > As seen in 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, 9 months

1
0
0 / 0

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

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26029?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-26029: ------------------------------- Fix Version/s: 4.6.x (was: 4.6.0.AM3) > 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.x > > > 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, 9 months

1
0
0 / 0

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

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26029?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-26029: ------------------------------------ [checkUnresolvedIssues.py] Slip to fixversion = *4.6.x* > 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.x > > > 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25838) Explorer: expand connection to the level that it was expanded to after editing it

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25838?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-25838: ------------------------------- Fix Version/s: 4.6.x (was: 4.6.0.AM3) > Explorer: expand connection to the level that it was expanded to after editing it > --------------------------------------------------------------------------------- > > Key: JBIDE-25838 > URL: https://issues.jboss.org/browse/JBIDE-25838 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.5.2.AM3 > Reporter: Andre Dietisheim > Assignee: Dmitrii Bocharov > Labels: connection, explorer > Fix For: 4.6.x > > > steps: > # ASSERT: in OpenShift Explorer: have a connection that is expanded to at least show a/all the projects > # EXEC: edit the connection, change the url, hit "Finish" > Result: > Connection is updated (refreshed) but collapsed, wont show the/all the projects > Expected result: > Connection is updated (refreshed) and expanded like it was before editing it, showing the project(s) (and even service(s) if it was expanded to that level before editing it) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

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