[JBoss JIRA] (JBIDE-22138) Server adapter: doesn't respect openshift maven profile
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22138?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-22138:
-------------------------------------
This seems like it should be a clean fix, but I'll need to investigate it once I'm all caught up from PTO.
> 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.9.0.AM2
>
> 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)
6 years, 2 months
[JBoss JIRA] (JBIDE-26179) New Application Wizard: Add refresh button for project selection/Better selection of projects
by Ondrej Dockal (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26179?page=com.atlassian.jira.plugi... ]
Ondrej Dockal commented on JBIDE-26179:
---------------------------------------
I took these steps to verify implemented functionality, tested on devstudio version: 12.9.0.AM2-v20180815-0130-B3168:
1. Start IDE
2. Create new CDK server adapter 3.2+
3. Start server adapter
4. ASSERT: Adapter is started, OS connection created.
5. Delete all projects under created OS connection
6. File -> New -> OpenShift Application
7. Choose OS connection created by CDK server adapter, Next
8. Dialog for creating new OS project pops up
9. Create OS project called ie. xxx, Finish
10. New Openshift application wizard is at place and fresh "xxx" project is selected in Openshift Project ComboBox
11. Create new project for running openshift under developer connection via oc -> oc login (developer, etc), oc new-project yyy
12. ASSERT: oc get projects shows two existing projects (xxx and yyy)
13. Click refresh in OS app wizard
14. ASSERT: User can choose between xxx and yyy projects in Openshift projects combobox
> New Application Wizard: Add refresh button for project selection/Better selection of projects
> ---------------------------------------------------------------------------------------------
>
> Key: JBIDE-26179
> URL: https://issues.jboss.org/browse/JBIDE-26179
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.6.0.Final
> Environment: F28
> console.engint.openshift.com
> Reporter: Josef Kopriva
> Assignee: Josef Kopriva
> Fix For: 4.9.0.AM1
>
>
> In New Application Wizard could be added button for refresh of projects. The reason is, in some cases this is not refreshed.
> Workflow:
> 1. Create connection to console engint.openshift.com
> 2. Delete all projects in connection
> 3. Open New Application Wizard from File -> New
> 4. Select connection
> 5. When you are asked to create project create it
> 6. Now you should be on New Application Wizard, but project is not selected
> Workaround: You can click on Back and Next afterwards, so you can see now project.
> I suppose this issue is caused with slower server response, so user should be able to to refresh projects list and maybe edit projects(if he enter wrong name...).
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 2 months
[JBoss JIRA] (JBIDE-26179) New Application Wizard: Add refresh button for project selection/Better selection of projects
by Ondrej Dockal (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26179?page=com.atlassian.jira.plugi... ]
Ondrej Dockal closed JBIDE-26179.
---------------------------------
> New Application Wizard: Add refresh button for project selection/Better selection of projects
> ---------------------------------------------------------------------------------------------
>
> Key: JBIDE-26179
> URL: https://issues.jboss.org/browse/JBIDE-26179
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.6.0.Final
> Environment: F28
> console.engint.openshift.com
> Reporter: Josef Kopriva
> Assignee: Josef Kopriva
> Fix For: 4.9.0.AM1
>
>
> In New Application Wizard could be added button for refresh of projects. The reason is, in some cases this is not refreshed.
> Workflow:
> 1. Create connection to console engint.openshift.com
> 2. Delete all projects in connection
> 3. Open New Application Wizard from File -> New
> 4. Select connection
> 5. When you are asked to create project create it
> 6. Now you should be on New Application Wizard, but project is not selected
> Workaround: You can click on Back and Next afterwards, so you can see now project.
> I suppose this issue is caused with slower server response, so user should be able to to refresh projects list and maybe edit projects(if he enter wrong name...).
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 2 months
[JBoss JIRA] (JBIDE-26065) [Red Hat Central] Add connector for nodeclipse
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26065?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-26065 at 8/14/18 4:36 PM:
-------------------------------------------------------------
TP rebuilding [0] to pull in newer mylyn 3.24.1 to match the version in nodeclipse site [1], [2], [3]:
[0] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbosstoo...
[1] http://www.nodeclipse.org/updates/
[2] http://download.eclipse.org/mylyn/releases/latest
[3] http://download.eclipse.org/mylyn/drops/3.24.1/v20180619-2220/
Reopened so we can fix the problem with the p2 director job [4] always failing:
{code}19:32:27 [p2.dir] Cannot complete the install because of a conflicting dependency.
19:32:27 [p2.dir] Software being installed: Mylyn Context Connector: Eclipse IDE 3.24.1.v20180619-2131 (org.eclipse.mylyn.ide_feature.feature.group 3.24.1.v20180619-2131)
19:32:27 [p2.dir] Software currently installed: Mylyn Context Connector: Eclipse IDE 3.24.0.v20170629-2230 (org.eclipse.mylyn.ide_feature.feature.group 3.24.0.v20170629-2230)
19:32:27 [p2.dir] Only one of the following can be installed at once:
19:32:27 [p2.dir] Mylyn Context Connector: Eclipse IDE 3.24.1.v20180619-2131 (org.eclipse.mylyn.ide_feature.feature.jar 3.24.1.v20180619-2131)
19:32:27 [p2.dir] Mylyn Context Connector: Eclipse IDE 3.24.0.v20170629-2230 (org.eclipse.mylyn.ide_feature.feature.jar 3.24.0.v20170629-2230)
{code}
[4] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud...
was (Author: nickboldt):
TP rebuilding [0] to pull in newer mylyn 3.24.1 to match the version in nodeclipse site [1], [2], [3]:
[0] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbosstoo...
[1] http://www.nodeclipse.org/updates/
[2] http://download.eclipse.org/mylyn/releases/latest
[3] http://download.eclipse.org/mylyn/drops/3.24.1/v20180619-2220/
> [Red Hat Central] Add connector for nodeclipse
> ----------------------------------------------
>
> Key: JBIDE-26065
> URL: https://issues.jboss.org/browse/JBIDE-26065
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: build, central-update, updatesite, upstream
> Affects Versions: 4.6.0.AM2
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.6.0.Final
>
> Attachments: devstudio12-central.png, eclipse-marketplace-nodeclipse.png, license-node-asl2.txt, license-node-chromium.txt, license-node-jshint-eclipse-license-unknown.txt, license-node-markdown-editor-EPL-version-unknown.txt, license-nodepluginslist-paul-verest.txt, node-license-agreements.png
>
>
> Steps to perform:
> -a) mirror a copy of the latest Nodeclipse update site onto dl.jb.org for reproduceability-
> -b) add that to the 3rd party target platform used for building RH Central-
> c) create a connector in Central for installing Nodeclipse into BOTH *devstudio* and *jbosstools*
> (Mirroring step removed because we don't yet have confirmation from Legal that we are permitted to redistribute. So instead we'll just link to upstream remote site.)
> The list of features to include will be those recommended in the screenshots here [1], under the *B) UPDATE SITE (BIGGER CHOICE)* section, or can be collected based on the existing Eclipse Marketplace connector provided by nodeclipse [2].
>
> [1] http://www.nodeclipse.org/updates/
> [2] https://marketplace.eclipse.org/content/nodeclipse
> !eclipse-marketplace-nodeclipse.png|thumbnail!
> Installed size is about 111M for these 14 features:
> {code}
> org.nodeclipse_1.0.2.201509250223
> org.nodeclipse.enide.editors.jade.feature_1.0.2.201509250223
> org.nodeclipse.pluginslist.feature_1.0.2.201509250223
> com.eclipsesource.jshint.feature_0.10.1.20160216-0911
> de.bastiankrol.startexplorer.feature_1.7.0
> gitaddon.feature_1.0.0.20140303-0606
> markdown.editor.feature_1.2.0.201501260515
> net.mihai-nita.ansicon_1.3.1.201508091828
> pm.eclipse.editbox.feature_0.70.0.201508180438
> org.chromium.debug_0.3.9.201509250223
> org.chromium.sdk_0.3.9.201509250223
> tern-feature_1.1.0.201511082254
> tern-jsdt-feature_1.1.0.201511082254
> tern-server-nodejs-feature_1.1.0.201511082254
> {code}
> If any of these assumptions / feature brief details are incorrect, please correct them in this description or add comments to this JIRA.
> PR to do mirror, if licenses are allowed:
> https://github.com/jbosstools/jbosstools-download.jboss.org/pull/638
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 2 months
[JBoss JIRA] (JBIDE-26065) [Red Hat Central] Add connector for nodeclipse
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26065?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-26065:
------------------------------------
TP rebuilding [0] to pull in newer mylyn 3.24.1 to match the version in nodeclipse site [1], [2], [3]:
[0] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbosstoo...
[1] http://www.nodeclipse.org/updates/
[2] http://download.eclipse.org/mylyn/releases/latest
[3] http://download.eclipse.org/mylyn/drops/3.24.1/v20180619-2220/
> [Red Hat Central] Add connector for nodeclipse
> ----------------------------------------------
>
> Key: JBIDE-26065
> URL: https://issues.jboss.org/browse/JBIDE-26065
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: build, central-update, updatesite, upstream
> Affects Versions: 4.6.0.AM2
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.6.0.Final
>
> Attachments: devstudio12-central.png, eclipse-marketplace-nodeclipse.png, license-node-asl2.txt, license-node-chromium.txt, license-node-jshint-eclipse-license-unknown.txt, license-node-markdown-editor-EPL-version-unknown.txt, license-nodepluginslist-paul-verest.txt, node-license-agreements.png
>
>
> Steps to perform:
> -a) mirror a copy of the latest Nodeclipse update site onto dl.jb.org for reproduceability-
> -b) add that to the 3rd party target platform used for building RH Central-
> c) create a connector in Central for installing Nodeclipse into BOTH *devstudio* and *jbosstools*
> (Mirroring step removed because we don't yet have confirmation from Legal that we are permitted to redistribute. So instead we'll just link to upstream remote site.)
> The list of features to include will be those recommended in the screenshots here [1], under the *B) UPDATE SITE (BIGGER CHOICE)* section, or can be collected based on the existing Eclipse Marketplace connector provided by nodeclipse [2].
>
> [1] http://www.nodeclipse.org/updates/
> [2] https://marketplace.eclipse.org/content/nodeclipse
> !eclipse-marketplace-nodeclipse.png|thumbnail!
> Installed size is about 111M for these 14 features:
> {code}
> org.nodeclipse_1.0.2.201509250223
> org.nodeclipse.enide.editors.jade.feature_1.0.2.201509250223
> org.nodeclipse.pluginslist.feature_1.0.2.201509250223
> com.eclipsesource.jshint.feature_0.10.1.20160216-0911
> de.bastiankrol.startexplorer.feature_1.7.0
> gitaddon.feature_1.0.0.20140303-0606
> markdown.editor.feature_1.2.0.201501260515
> net.mihai-nita.ansicon_1.3.1.201508091828
> pm.eclipse.editbox.feature_0.70.0.201508180438
> org.chromium.debug_0.3.9.201509250223
> org.chromium.sdk_0.3.9.201509250223
> tern-feature_1.1.0.201511082254
> tern-jsdt-feature_1.1.0.201511082254
> tern-server-nodejs-feature_1.1.0.201511082254
> {code}
> If any of these assumptions / feature brief details are incorrect, please correct them in this description or add comments to this JIRA.
> PR to do mirror, if licenses are allowed:
> https://github.com/jbosstools/jbosstools-download.jboss.org/pull/638
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 2 months