[JBoss JIRA] (JBIDE-22138) Server adapter: doesn't respect openshift maven profile
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22138?page=com.atlassian.jira.plugi... ]
Fred Bricon commented on JBIDE-22138:
-------------------------------------
If the project's .settings/org.eclipse.wst.common.component contains the proper <wb-module deploy-name="ROOT">, then m2e-wtp has done its job and the problem lies within the server adapter which ignores that value
> 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
>
> Attachments: image-2018-06-22-19-02-57-247.png
>
>
> 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
[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 edited comment on JBIDE-22138 at 6/22/18 1:11 PM:
-------------------------------------------------------------------
[~fbricon], [~rawb] to me this smells like a bug:
Setting the maven profile for my project wont change the module name. I have to go into the project properties and have a look at some module related items and hit "Apply and Close" to see the module being renamed:
See here: https://youtu.be/A-N3D_VYqfk
# EXE: "hello" project: Propererties > Maven > "Active Maven Profile: set it to "openshift"
(I see WebProjectConfiguratorDelegate#configureDeployedName - which is inherited from AbstractProjectConfiguratorDelegate - being invoked with the correct deployedFileName "ROOT". See https://github.com/eclipse/m2e.wtp/blob/master/org.eclipse.m2e.wtp/src/or...)
# EXEC: "Servers" view: select OpenShift server adapter, pick "Add and Remove..." in the ctx menu and look at the available modules
# ASSERT: "hello" project is still listed as "hello" (where it should be "hello (ROOT)").
# EXEC: open properties for project "hello", selet ex. "Web Content Settings" and hit "Apply and Close".
# EXEC: in "Servers" view: select OpenShift server adapter, pick "Add and Remove..." in ctx menu and check the "Available" modules.
# ASSERT: module name now is "hello (ROOT)"
Any idea what's the issue here?
was (Author: adietish):
[~fbricon], [~rawb] to me this smells like a bug:
As soon as I set the maven profile to "openshift" in the project properties (hello project), I see WebProjectConfiguratorDelegate#configureDeployedName (which is inherited from AbstractProjectConfiguratorDelegate) being invoked with the correct deployedFileName "ROOT". See https://github.com/eclipse/m2e.wtp/blob/master/org.eclipse.m2e.wtp/src/or...
When I then get to the OpenShift server adapter (or any other server adapter) and pick "Add and Remove...", where I see all available modules listed in "Available", the hello project is still listed as "hello" (where it should be "hello (ROOT)"). To fix this I have to go into the properties for project "hello", look at ex. "Web Content Settings" and hit "Apply and Close". Once I did that I now see the correct module name "hello (ROOT)" in "Add and Remove...".
See here: https://youtu.be/A-N3D_VYqfk
Any idea what's the issue here?
> 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
>
> Attachments: image-2018-06-22-19-02-57-247.png
>
>
> 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
[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 edited comment on JBIDE-22138 at 6/22/18 1:04 PM:
-------------------------------------------------------------------
[~fbricon], [~rawb] to me this smells like a bug:
As soon as I set the maven profile to "openshift" in the project properties (hello project), I see WebProjectConfiguratorDelegate#configureDeployedName (which is inherited from AbstractProjectConfiguratorDelegate) being invoked with the correct deployedFileName "ROOT". See https://github.com/eclipse/m2e.wtp/blob/master/org.eclipse.m2e.wtp/src/or...
When I then get to the OpenShift server adapter (or any other server adapter) and pick "Add and Remove...", where I see all available modules listed in "Available", the hello project is still listed as "hello" (where it should be "hello (ROOT)"). To fix this I have to go into the properties for project "hello", look at ex. "Web Content Settings" and hit "Apply and Close". Once I did that I now see the correct module name "hello (ROOT)" in "Add and Remove...".
See here: https://youtu.be/A-N3D_VYqfk
Any idea what's the issue here?
was (Author: adietish):
[~fbricon], [~rawb] to me this smells like a bug:
As soon as I set the maven profile to "openshift" in the project properties (hello project), I see WebProjectConfiguratorDelegate#configureDeployedName (which is inherited from AbstractProjectConfiguratorDelegate) being invoked with the correct deployedFileName "ROOT". See https://github.com/eclipse/m2e.wtp/blob/master/org.eclipse.m2e.wtp/src/or...
When I then get to the OpenShift server adapter (or any other server adapter) and pick "Add and Remove...", where I see all available modules listed in "Available", the hello project is still listed as "hello" (where it should be "hello (ROOT)"). To fix this I have to go into the properties for project "hello", look at ex. "Web Content Settings" and hit "Apply and Close". Once I did that I now see the correct module name "hello (ROOT)" in "Add and Remove...".
!image-2018-06-22-19-02-57-247.png! (or https://youtu.be/A-N3D_VYqfk)
Any idea what's the issue here?
> 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
>
> Attachments: image-2018-06-22-19-02-57-247.png
>
>
> 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
[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 edited comment on JBIDE-22138 at 6/22/18 1:03 PM:
-------------------------------------------------------------------
[~fbricon], [~rawb] to me this smells like a bug:
As soon as I set the maven profile to "openshift" in the project properties (hello project), I see WebProjectConfiguratorDelegate#configureDeployedName (which is inherited from AbstractProjectConfiguratorDelegate) being invoked with the correct deployedFileName "ROOT". See https://github.com/eclipse/m2e.wtp/blob/master/org.eclipse.m2e.wtp/src/or...
When I then get to the OpenShift server adapter (or any other server adapter) and pick "Add and Remove...", where I see all available modules listed in "Available", the hello project is still listed as "hello" (where it should be "hello (ROOT)"). To fix this I have to go into the properties for project "hello", look at ex. "Web Content Settings" and hit "Apply and Close". Once I did that I now see the correct module name "hello (ROOT)" in "Add and Remove...".
!image-2018-06-22-19-02-57-247.png! (or https://youtu.be/A-N3D_VYqfk)
Any idea what's the issue here?
was (Author: adietish):
[~fbricon], [~rawb] to me this smells like a bug:
As soon as I set the maven profile to "openshift" in the project properties (hello project), I see WebProjectConfiguratorDelegate#configureDeployedName (which is inherited from AbstractProjectConfiguratorDelegate) being invoked with the correct deployedFileName "ROOT". See https://github.com/eclipse/m2e.wtp/blob/master/org.eclipse.m2e.wtp/src/or...
When I then get to the OpenShift server adapter (or any other server adapter) and pick "Add and Remove...", where I see all available modules listed in "Available", the hello project is still listed as "hello" (where it should be "hello (ROOT)"). To fix this I have to go into the project properties for project hello and hit "Apply and Close". Once I did that and get back to "Add and Remove..." (server adapter) I now see "hello (ROOT)".
Any idea what's the issue here?
> 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
>
> Attachments: image-2018-06-22-19-02-57-247.png
>
>
> 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
[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:
------------------------------------------
[~fbricon], [~rawb] to me this smells like a bug:
As soon as I set the maven profile to "openshift" in the project properties (hello project), I see WebProjectConfiguratorDelegate#configureDeployedName (which is inherited from AbstractProjectConfiguratorDelegate) being invoked with the correct deployedFileName "ROOT". See https://github.com/eclipse/m2e.wtp/blob/master/org.eclipse.m2e.wtp/src/or...
When I then get to the OpenShift server adapter (or any other server adapter) and pick "Add and Remove...", where I see all available modules listed in "Available", the hello project is still listed as "hello" (where it should be "hello (ROOT)"). To fix this I have to go into the project properties for project hello and hit "Apply and Close". Once I did that and get back to "Add and Remove..." (server adapter) I now see "hello (ROOT)".
Any idea what's the issue here?
> 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
[JBoss JIRA] (JBIDE-26083) Validation Issues for Batch files
by Cody Lerum (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26083?page=com.atlassian.jira.plugi... ]
Cody Lerum commented on JBIDE-26083:
------------------------------------
[~jeffmaury] FYI It has shown up and gone away a few times since and I believe it has something to do with the Java EE8 api's being on the project. It tends to appears when I switch to my EE8 and Wildfly 13 migration branch.
> Validation Issues for Batch files
> ---------------------------------
>
> Key: JBIDE-26083
> URL: https://issues.jboss.org/browse/JBIDE-26083
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: batch
> Affects Versions: 4.5.3.Final
> Reporter: Cody Lerum
> Assignee: Jeff MAURY
> Fix For: 4.6.0.Final
>
> Attachments: Capture.PNG
>
>
> After the latest update the tooling is showing warnings for batchlet not found and partition mapper not found.
> These are working batch files and previously did not show warnings.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (JBDS-4702) Multiple warnings when opening Spring perspective
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4702?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-4702:
----------------------------------
According to [~jkopriva] this is still happening with latest Photon RC4a and Spring IDE 3.9.5.
Do these warnings impact your ability to do anything? It's just a deprecation warning, right?
Is there more of a stack trace so we can pinpoint which class is deprecated? I see in your original report that this is happening in 3 places:
* org.eclipse.contribution.xref.ui.views.XReferenceView
* org.springframework.ide.eclipse.aop.ui.navigator.aopReferenceModelNavigator
* org.eclipse.jdt.junit.ResultView
Also, do these warnings appear before installing Spring IDE, or only after installing it?
> Multiple warnings when opening Spring perspective
> -------------------------------------------------
>
> Key: JBDS-4702
> URL: https://issues.jboss.org/browse/JBDS-4702
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: 3rd-party-certification, central-update, upstream
> Affects Versions: 12.0.0.AM1
> Reporter: Josef Kopriva
> Assignee: Josef Kopriva
> Priority: Optional
> Fix For: 12.0.0.GA
>
>
> {code:java}
> eclipse.buildId=12.0.0.AM1-v20180508-1631-B2428
> java.version=1.8.0_171
> java.vendor=Oracle Corporation
> BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
> Framework arguments: -product com.jboss.devstudio.core.product
> Command-line arguments: -data file:/home/jkopriva/devstudio_B2428_3/workspace/ -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product
> org.eclipse.ui
> Warning
> Wed May 09 11:50:19 CEST 2018
> org.eclipse.contribution.xref.ui.views.XReferenceView: Deprecated relationship "fast" should be converted to "stack".
> {code}
> {code:java}
> eclipse.buildId=12.0.0.AM1-v20180508-1631-B2428
> java.version=1.8.0_171
> java.vendor=Oracle Corporation
> BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
> Framework arguments: -product com.jboss.devstudio.core.product
> Command-line arguments: -data file:/home/jkopriva/devstudio_B2428_3/workspace/ -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product
> org.eclipse.ui
> Warning
> Wed May 09 11:50:19 CEST 2018
> org.springframework.ide.eclipse.aop.ui.navigator.aopReferenceModelNavigator: Deprecated relationship "fast" should be converted to "stack".
> {code}
> {code:java}
> eclipse.buildId=12.0.0.AM1-v20180508-1631-B2428
> java.version=1.8.0_171
> java.vendor=Oracle Corporation
> BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
> Framework arguments: -product com.jboss.devstudio.core.product
> Command-line arguments: -data file:/home/jkopriva/devstudio_B2428_3/workspace/ -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product
> org.eclipse.ui
> Warning
> Wed May 09 11:50:19 CEST 2018
> org.eclipse.jdt.junit.ResultView: Deprecated relationship "fast" should be converted to "stack".
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months