[JBoss JIRA] (JBIDE-22045) Wrong Source Path when creating OS3 Server Adapter for multiple applications
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22045?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-22045:
------------------------------------------
cherry-picked into master
> Wrong Source Path when creating OS3 Server Adapter for multiple applications
> ----------------------------------------------------------------------------
>
> Key: JBIDE-22045
> URL: https://issues.jboss.org/browse/JBIDE-22045
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Alexey Kazakov
> Assignee: Andre Dietisheim
> Priority: Blocker
> Labels: openshift_v3, server_adapter_wizard
> Fix For: 4.4.0.Alpha1
>
> Attachments: launch_config.png, Screenshot 2016-03-31 14.34.47.png, server-adapter.png
>
>
> 1.
> !server-adapter.png|thumbnail!
> 2. Even selecting the correct source manually doesn't help. The eclipse project is still incorrect in the launch config.
> !launch_config.png|thumbnail!
> Maybe it's because the nodejs eclipse project is not a wtp project and the server adapter picks up the only available wtp module - eap-app.
> The only way to create a proper server adapter for the nodejs-example is to delete the eap eclipse project from the workspace.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-22045) Wrong Source Path when creating OS3 Server Adapter for multiple applications
by Andre Dietisheim (JIRA)
Andre Dietisheim created JBIDE-22045:
----------------------------------------
Summary: Wrong Source Path when creating OS3 Server Adapter for multiple applications
Key: JBIDE-22045
URL: https://issues.jboss.org/browse/JBIDE-22045
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.3.1.CR1
Reporter: Alexey Kazakov
Assignee: Andre Dietisheim
Priority: Blocker
Fix For: 4.3.1.CR1
1.
!server-adapter.png|thumbnail!
2. Even selecting the correct source manually doesn't help. The eclipse project is still incorrect in the launch config.
!launch_config.png|thumbnail!
Maybe it's because the nodejs eclipse project is not a wtp project and the server adapter picks up the only available wtp module - eap-app.
The only way to create a proper server adapter for the nodejs-example is to delete the eap eclipse project from the workspace.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-21984) Wrong Source Path when creating OS3 Server Adapter for multiple applications
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21984?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-21984:
------------------------------------------
merged into jbosstools-4.3.x
> Wrong Source Path when creating OS3 Server Adapter for multiple applications
> ----------------------------------------------------------------------------
>
> Key: JBIDE-21984
> URL: https://issues.jboss.org/browse/JBIDE-21984
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Alexey Kazakov
> Assignee: Andre Dietisheim
> Priority: Blocker
> Labels: openshift_v3, server_adapter_wizard
> Fix For: 4.3.1.CR1
>
> Attachments: launch_config.png, Screenshot 2016-03-31 14.34.47.png, server-adapter.png
>
>
> 1.
> !server-adapter.png|thumbnail!
> 2. Even selecting the correct source manually doesn't help. The eclipse project is still incorrect in the launch config.
> !launch_config.png|thumbnail!
> Maybe it's because the nodejs eclipse project is not a wtp project and the server adapter picks up the only available wtp module - eap-app.
> The only way to create a proper server adapter for the nodejs-example is to delete the eap eclipse project from the workspace.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-21953) 10.1.2.2 as host private network IP not working on (RH) VPN
by Hardy Ferentschik (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21953?page=com.atlassian.jira.plugi... ]
Hardy Ferentschik updated JBIDE-21953:
--------------------------------------
Summary: 10.1.2.2 as host private network IP not working on (RH) VPN (was: 10.1.2.2.* not working on Windows from RH network)
> 10.1.2.2 as host private network IP not working on (RH) VPN
> -----------------------------------------------------------
>
> Key: JBIDE-21953
> URL: https://issues.jboss.org/browse/JBIDE-21953
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk, openshift, upstream
> Affects Versions: 4.3.1.CR1
> Reporter: Martin Malina
> Assignee: Hardy Ferentschik
> Priority: Critical
> Fix For: 4.4.x
>
>
> This is definitely an upstream issue, but I think it's worth having it here and gather information from others.
> Marian tried openshift with cdk today on our Windows laptop and the url generated for the app he deployed didn't work.
> So I tried something simple like "ping 10.1.2.2.xip.io" from command line and it didn't work.
> "ping xip.io" worked.
> On my OS X laptop, this works as expected:
> {code}
> $ ping 10.1.2.2.xip.io
> PING 10.1.2.2.xip.io (10.1.2.2): 56 data bytes
> Request timeout for icmp_seq 0
> {code}
> Whereas on windows I only get:
> Ping request could not find host 10.1.2.2.xip.io. Please check the name and try again.
> I'm not sure if it's just a problem with our laptop, but it needs investigating in any case.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-21984) Wrong Source Path when creating OS3 Server Adapter for multiple applications
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21984?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-21984 at 3/31/16 8:55 AM:
-------------------------------------------------------------------
The patch takes the following approach:
# If you start the wizard from explorer:
the service that is selected is used, the workspace project is inferred from it by comparing the git uri in the buildConfig (of the selected service) with the git remotes of the workspace projects
# if you start the wizard from "Servers" view or "New wizards"/main menu:
the workspace project that's selected will be used, the service is inferred from it by comparing the git uri in the buildConfigs of the available services with the git remote of the (selected) workspace project
was (Author: adietish):
The patch takes the following approach:
# If you start the wizard from explorer:
## the service that is selected is used, the workspace project is inferred from it by comparing the git uri in the buildConfig (of the selected service) with the git remotes of the workspace projects
# if you start the wizard from "Servers" view or "New wizards"/main menu:
## the workspace project that's selected will be used, the service is inferred from it by comparing the git uri in the buildConfigs of the available services with the git remote of the (selected) workspace project
> Wrong Source Path when creating OS3 Server Adapter for multiple applications
> ----------------------------------------------------------------------------
>
> Key: JBIDE-21984
> URL: https://issues.jboss.org/browse/JBIDE-21984
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Alexey Kazakov
> Assignee: Andre Dietisheim
> Priority: Blocker
> Labels: openshift_v3, server_adapter_wizard
> Fix For: 4.3.1.CR1
>
> Attachments: launch_config.png, Screenshot 2016-03-31 14.34.47.png, server-adapter.png
>
>
> 1.
> !server-adapter.png|thumbnail!
> 2. Even selecting the correct source manually doesn't help. The eclipse project is still incorrect in the launch config.
> !launch_config.png|thumbnail!
> Maybe it's because the nodejs eclipse project is not a wtp project and the server adapter picks up the only available wtp module - eap-app.
> The only way to create a proper server adapter for the nodejs-example is to delete the eap eclipse project from the workspace.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months