[JBoss JIRA] (JBIDE-25838) Explorer: expand connection to the level that it was expanded to after editing it
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25838?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-25838:
-------------------------------
Sprint: devex #149 May 2018, devex #150 June 2018, devex #151 June 2018 (was: devex #149 May 2018, devex #150 June 2018)
> 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
[JBoss JIRA] (JBIDE-22138) Server adapter: doesn't respect openshift maven profile
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22138?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-22138:
-------------------------------
Sprint: devex #150 June 2018, devex #151 June 2018 (was: devex #150 June 2018)
> 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