June 2018 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-26118) Cannot Create JSF2 Composite component from current selected source

by Ondrej Dockal (JIRA)

Ondrej Dockal created JBIDE-26118: ------------------------------------- Summary: Cannot Create JSF2 Composite component from current selected source Key: JBIDE-26118 URL: https://issues.jboss.org/browse/JBIDE-26118 Project: Tools (JBoss Tools) Issue Type: Bug Components: jsf Affects Versions: 4.6.0.AM3 Reporter: Ondrej Dockal Assignee: Jeff MAURY Priority: Critical There is missing context menu item "Create JSF2 Composite" in JBoss HTML editor viewing some xhtml file. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26078) Properties: edit resource context menu is erroneously labeled "Resources..." (missing "Edit")

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26078?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-26078: ------------------------------------- Fix Version/s: 4.6.0.Final (was: 4.6.0.AM3) > Properties: edit resource context menu is erroneously labeled "Resources..." (missing "Edit") > --------------------------------------------------------------------------------------------- > > Key: JBIDE-26078 > URL: https://issues.jboss.org/browse/JBIDE-26078 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.6.0.AM2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: edit_resource_editor, properties > Fix For: 4.6.0.Final > > Attachments: edit-resource-command.png, image-2018-06-04-15-56-08-882.png > > > steps: > # ASSERT: have a resource on OpenShift (buildconfig, deplyoment config, build, etc.) > # ASSERT: have "Properties" view opened > # EXEC: in explorer: select the project that contains the resource > # EXEC: in "Properties" view: have the tab selected that contains your resource, select the resource and open up the context menu > Result: > !image-2018-06-04-15-56-08-882.png! > The entry for editing the resource is labeled "Resource...", it should be labeled "Edit Resource..." or be in the submenu "Edit" like it is in OpenShift explorer. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26078) Properties: edit resource context menu is erroneously labeled "Resources..." (missing "Edit")

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26078?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-26078: ------------------------------------------ [~jkopriva] oh, gotcha. You're right, I can reproduce this. re-targeting to 4.6.0.Final. > Properties: edit resource context menu is erroneously labeled "Resources..." (missing "Edit") > --------------------------------------------------------------------------------------------- > > Key: JBIDE-26078 > URL: https://issues.jboss.org/browse/JBIDE-26078 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.6.0.AM2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: edit_resource_editor, properties > Fix For: 4.6.0.Final > > Attachments: edit-resource-command.png, image-2018-06-04-15-56-08-882.png > > > steps: > # ASSERT: have a resource on OpenShift (buildconfig, deplyoment config, build, etc.) > # ASSERT: have "Properties" view opened > # EXEC: in explorer: select the project that contains the resource > # EXEC: in "Properties" view: have the tab selected that contains your resource, select the resource and open up the context menu > Result: > !image-2018-06-04-15-56-08-882.png! > The entry for editing the resource is labeled "Resource...", it should be labeled "Edit Resource..." or be in the submenu "Edit" like it is in OpenShift explorer. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26047) CDI New and Noteworthy for 4.6.0.AM3

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26047?page=com.atlassian.jira.plugi... ] Jeff MAURY closed JBIDE-26047. ------------------------------ Resolution: Rejected > CDI New and Noteworthy for 4.6.0.AM3 > --------------------------------------------------- > > Key: JBIDE-26047 > URL: https://issues.jboss.org/browse/JBIDE-26047 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: cdi > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Priority: Critical > Labels: task > Fix For: 4.6.0.AM3 > > > Jeff MAURY, > Search for your component's New and Noteworthy issues: > Queries: > * [Completed CDI JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [All Completed JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [N&N Task JIRAs for this milestone|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Not...] > * [All N&N Task JIRAs|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Notewor...] > If no N&N issues are found for CDI, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for CDI by submitting a pull request against: > * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio... > If your PR's commit comment is of the form... {code}JBIDE-26045 #comment Create N&N for CDI 4.6.0.AM3 #close{code}... and your github user's email address is the same as your JIRA one, then this JIRA should be closed automatically when the PR is applied. > If there is nothing new or noteworthy for CDI for this milestone, please *reject* and *close* this issue. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4710) Central page is not showing proper content after page refresh

by Vojtech Prusa (JIRA)

[ https://issues.jboss.org/browse/JBDS-4710?page=com.atlassian.jira.plugin.... ] Vojtech Prusa commented on JBDS-4710: ------------------------------------- Hello [~fbricon], component owner, should i comment anybody or anything else? > Central page is not showing proper content after page refresh > ------------------------------------------------------------- > > Key: JBDS-4710 > URL: https://issues.jboss.org/browse/JBDS-4710 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: central > Affects Versions: 12.0.0.AM3 > Reporter: Vojtech Prusa > Attachments: image-2018-06-19-10-04-56-516.png, image-2018-06-19-10-06-27-472.png > > > Refreshing the central page (Getting Started tab) does not load content for project examples. > Jenkins itests fails as well > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/central.... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4710) Central page is not showing proper content after page refresh

by Vojtech Prusa (JIRA)

Vojtech Prusa created JBDS-4710: ----------------------------------- Summary: Central page is not showing proper content after page refresh Key: JBDS-4710 URL: https://issues.jboss.org/browse/JBDS-4710 Project: Red Hat JBoss Developer Studio (devstudio) Issue Type: Bug Components: central Affects Versions: 12.0.0.AM3 Reporter: Vojtech Prusa Attachments: image-2018-06-19-10-04-56-516.png, image-2018-06-19-10-06-27-472.png Refreshing the central page (Getting Started tab) does not load content for project examples. Jenkins itests fails as well https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/central.... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26069) Spring Boot Project configurator: Creating child module for main project fails

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26069?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-26069: ------------------------------------------ [~jeffmaury] do you have new insights for this? I asked [~jkopriva] to please verify this in Windows, hopefully we'll found out something new (so far I am absoultely unable to reproduce it, neither in MacOS nor Linux) > Spring Boot Project configurator: Creating child module for main project fails > ------------------------------------------------------------------------------- > > Key: JBIDE-26069 > URL: https://issues.jboss.org/browse/JBIDE-26069 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.6.0.AM2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Critical > Labels: project_configurator, springboot > Fix For: 4.6.0.Final > > Attachments: image-2018-05-30-22-31-37-635.png > > > steps: > # ASSERT: We dont know for now, really. We can only reproduce this on [~jeffmaury]'s machine (happens to him in Windows and Linux - doesn't for others in Linux nor Mac). > # EXEC: import the 2 maven projects that are attached to JBIDE-25504 (camel-ose-springboot-xml and penguins > # EXEC: in project properties for project *camel-ose-springboot-xml*: pick "Deployment Assembly" > # ASSERT: verify that *penguins* is defined as child module > Result: > !image-2018-05-30-22-31-37-635.png! -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25504) Support hot deploy for workspace dependencies for SpringBoot applications on OpenShift

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25504?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-25504: ------------------------------------------ [~jkopriva] This jira wasn't closed. Can you (re-)confirm that this works as expected? If you're at it, could you please test this in Windows, too ([~jeffmaury] reported issues in Windows. But then he also has them in Linux)? > Support hot deploy for workspace dependencies for SpringBoot applications on OpenShift > -------------------------------------------------------------------------------------- > > Key: JBIDE-25504 > URL: https://issues.jboss.org/browse/JBIDE-25504 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.5.2.AM2 > Reporter: Jeff MAURY > Assignee: Andre Dietisheim > Labels: openshift, openshift_v3, server_adapter > Fix For: 4.6.0.AM2 > > Attachments: springboot-dependencies.zip > > > When a SpringBoot application is being deployed on OpenShift with the server adapter, we should support the following use case: > * the SpringBoot app has a dependency which is avalailable in the workspace > * when a modifiction is done on the dependency code, it should be synced to OpenShift by the server adapter -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22138) Server adapter: doesn't respect openshift maven profile

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22138?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22138: ------------------------------------- Fix Version/s: 4.6.0.Final (was: 4.6.x) > Server adapter: doesn't respect openshift maven profile > ------------------------------------------------------- > > Key: JBIDE-22138 > URL: https://issues.jboss.org/browse/JBIDE-22138 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Environment: JBoss Developer Studio (Core Features) 9.1.0.GA-v20160403-1700-B477 > Openshift plugin 3.1.0.Final-v20160401-2357-B263 > Reporter: Rafael Benevides > Assignee: Andre Dietisheim > Labels: openshift_v3, server_adapter > Fix For: 4.6.0.Final > > > This is a follow up on JBIDE-22128. > The maven profile is never read to determine the actual archive name. That will require more coupling to m2e, in order to load the pom.xml model using the openshift profile, if it exists, in order to determine the archive name. This will be a long running operation and will require more significant changes > steps: > # EXEC: follow steps outlined in https://github.com/redhat-helloworld-msa/helloworld-msa/blob/master/hello... (deploying with fabric8 maven plugin doesn't work, you end up having the pod failing with ImagePullBack error. You need to take the alternative road where you deploy via "oc new-build", "oc new-app", "oc expose" etc.) > # EXEC: import the app into your Eclipse workspace > # EXEC: "hello" (workspace) project: Properties > Maven > Active Maven Profile: set "openshift" > # EXEC: create a server adapter and start it > # ASSERT: adapter starts syncing, verify what war is used > Result: > The war that's created locally and then synced to the pod is "hello.war" even though the profile specifies "ROOT.war" -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22138) Server adapter: doesn't respect openshift maven profile

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22138?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-22138: ------------------------------------------ [~rob.stryker], [~fbricon] can you please comment on https://issues.jboss.org/browse/JBIDE-22138?focusedCommentId=13590444&pag... > Server adapter: doesn't respect openshift maven profile > ------------------------------------------------------- > > Key: JBIDE-22138 > URL: https://issues.jboss.org/browse/JBIDE-22138 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Environment: JBoss Developer Studio (Core Features) 9.1.0.GA-v20160403-1700-B477 > Openshift plugin 3.1.0.Final-v20160401-2357-B263 > Reporter: Rafael Benevides > Assignee: Andre Dietisheim > Labels: openshift_v3, server_adapter > Fix For: 4.6.x > > > This is a follow up on JBIDE-22128. > The maven profile is never read to determine the actual archive name. That will require more coupling to m2e, in order to load the pom.xml model using the openshift profile, if it exists, in order to determine the archive name. This will be a long running operation and will require more significant changes > steps: > # EXEC: follow steps outlined in https://github.com/redhat-helloworld-msa/helloworld-msa/blob/master/hello... (deploying with fabric8 maven plugin doesn't work, you end up having the pod failing with ImagePullBack error. You need to take the alternative road where you deploy via "oc new-build", "oc new-app", "oc expose" etc.) > # EXEC: import the app into your Eclipse workspace > # EXEC: "hello" (workspace) project: Properties > Maven > Active Maven Profile: set "openshift" > # EXEC: create a server adapter and start it > # ASSERT: adapter starts syncing, verify what war is used > Result: > The war that's created locally and then synced to the pod is "hello.war" even though the profile specifies "ROOT.war" -- 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