March 2018 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-25824) Update the dependency of the 'org.jboss.tools.hibernate.orm.test' plugin to the new 5.3 Hibernate runtime

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25824?page=com.atlassian.jira.plugi... ] Koen Aers updated JBIDE-25824: ------------------------------ Fix Version/s: 4.5.3.AM3 > Update the dependency of the 'org.jboss.tools.hibernate.orm.test' plugin to the new 5.3 Hibernate runtime > --------------------------------------------------------------------------------------------------------- > > Key: JBIDE-25824 > URL: https://issues.jboss.org/browse/JBIDE-25824 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: hibernate > Affects Versions: 4.5.3.AM2 > Reporter: Koen Aers > Assignee: Koen Aers > Fix For: 4.5.3.AM3 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25823) Client: release and use 6.0.0.Final

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25823?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-25823: ------------------------------------- Sprint: devex #146 March 2018 > Client: release and use 6.0.0.Final > ----------------------------------- > > Key: JBIDE-25823 > URL: https://issues.jboss.org/browse/JBIDE-25823 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.3.AM2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Blocker > Labels: openshift-restclient-java > Fix For: 4.5.3.AM3 > > > In JBIDE-25506 and JBIDE-25818 we introduced a new client version 6.0.0-SNAPSHOT. So that clients in our tools releases can be identified we should release and use 6.0.0.Final for AM3 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25823) Client: release and use 6.0.0.Final

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25823?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-25823: ------------------------------------- Description: In JBIDE-25506 and JBIDE-25818 we introduced a new client version 6.0.0-SNAPSHOT. So that clients in our tools releases can be identified we should release and use 6.0.0.Final for AM3 (was: In JBIDE-25734 we introduced a new client version 5.9.4-SNAPSHOT. So that clients in our tools releases can be indetifiable we should release and use 5.9.5.Final for AM2) > Client: release and use 6.0.0.Final > ----------------------------------- > > Key: JBIDE-25823 > URL: https://issues.jboss.org/browse/JBIDE-25823 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.3.AM2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Blocker > Labels: openshift-restclient-java > Fix For: 4.5.3.AM3 > > > In JBIDE-25506 and JBIDE-25818 we introduced a new client version 6.0.0-SNAPSHOT. So that clients in our tools releases can be identified we should release and use 6.0.0.Final for AM3 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25823) Client: release and use 6.0.0.Final

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-25823: ---------------------------------------- Summary: Client: release and use 6.0.0.Final Key: JBIDE-25823 URL: https://issues.jboss.org/browse/JBIDE-25823 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.5.3.AM2 Reporter: Andre Dietisheim Assignee: Andre Dietisheim Priority: Blocker Fix For: 4.5.3.AM2 In JBIDE-25734 we introduced a new client version 5.9.4-SNAPSHOT. So that clients in our tools releases can be indetifiable we should release and use 5.9.5.Final for AM2 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25823) Client: release and use 6.0.0.Final

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25823?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-25823: ------------------------------------- Fix Version/s: 4.5.3.AM3 (was: 4.5.3.AM2) > Client: release and use 6.0.0.Final > ----------------------------------- > > Key: JBIDE-25823 > URL: https://issues.jboss.org/browse/JBIDE-25823 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.3.AM2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Blocker > Labels: openshift-restclient-java > Fix For: 4.5.3.AM3 > > > In JBIDE-25734 we introduced a new client version 5.9.4-SNAPSHOT. So that clients in our tools releases can be indetifiable we should release and use 5.9.5.Final for AM2 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25823) Client: release and use 6.0.0.Final

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25823?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-25823: ------------------------------------- Git Pull Request: (was: https://github.com/jbosstools/jbosstools-openshift/pull/1685) > Client: release and use 6.0.0.Final > ----------------------------------- > > Key: JBIDE-25823 > URL: https://issues.jboss.org/browse/JBIDE-25823 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.3.AM2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Blocker > Labels: openshift-restclient-java > Fix For: 4.5.3.AM3 > > > In JBIDE-25734 we introduced a new client version 5.9.4-SNAPSHOT. So that clients in our tools releases can be indetifiable we should release and use 5.9.5.Final for AM2 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25303) Server adapter: support hot-deployment on OpenShift for SpringBoot app

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25303?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-25303: ------------------------------------------ [~jkopriva] thx for testing the updated project. So yes, unfortunately the permission errors are expected. These are an issue with the fabric8/s2i-java docker image as we discussed it in JBIDE-25700. Fabric8 updated their image but I couldnt test it yet, I'll do asap. In other terms, your test confirms that the tooling works. We'll have to re-verify with the updated docker image though. > Server adapter: support hot-deployment on OpenShift for SpringBoot app > ---------------------------------------------------------------------- > > Key: JBIDE-25303 > URL: https://issues.jboss.org/browse/JBIDE-25303 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.5.1.Final > Reporter: Aurélien Pupier > Assignee: Andre Dietisheim > Labels: openshift_v3, server_adapter > Fix For: 4.5.3.AM3 > > Attachments: Image+Pasted+at+2018-1-16+10-58.png, docker-explorer-inspect-image.png, fuse-on-openshift.zip, project-deployment-assembly.png, screenshot-1.png, spring-boot-demo.zip > > > currently, Springboot jar projects (such as Fuse Integration Services) are rsynced with a zipped jar file. > The requirements are: > - rsync unpacked jar > - rsync without the jar name as folder > - it will will work only if springboot devtool are included (so maybe need some dialog guiding user to do i in case it is not activated) > use case "Develop SpringBoot application deployed on OpenShift as any other applications in JBoss Tools": > - there is a SpringBoot app deployed on OpenShift > - the developer want to develop evolution of the SpringBoot app > -- when he/she modifies the project, the application needs to be automatically updated on OpenShift instance > -- Remote java debug should be available when the OpenShift server adapter is in debug mode. > Steps: > # EXEC: create a project in your OpenShift server (ex. camel-ose-springboot) > # EXEC: Import project within fuse-on-openshift.zip into your workspace > # EXEC: open launch configuration and change: > ** -Dkubernetes.master= so that it first your cdk instance > ** -Dkubernetes.namespace= to the name of the project that you create in step 1. > ** -Dfabric8.generator.from=fabric8/s2i-java > # EXEC: run the launch config (that is included in the project), so that the project gets deployed to OpenShift (cdk) > # ASSERT: your project in OpenShift now contains a service **camel-ose-springboot-xml**, the pod for it is running. > # EXEC: in OpenShift Explorer: select this service and create a server adapter for it (*Server Adapter..* in the context menu for the service) > # ASSERT: server adapter is created and is *[started]* > # EXEC: in OpenShift Explorer: pick *Pod Log...* in the context menu for the pod of your service) > # ASSERT: pod log is opened in "Console" view and shows an output with random numbers in the end > {code} > simple-route - >>> 455 > simple-route - >>> 695 > simple-route - >>> 935 > {code} > # EXEC: In Project Explorer: open class MyTransformer and change the transform method > # ASSERT: "Console" view is opened and shows how the server adapter is publishing the MyTransformer class to the pod -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25753) Add links for downloading minishift and cdk in New Server Adapter wizard

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25753?page=com.atlassian.jira.plugi... ] Martin Malina edited comment on JBIDE-25753 at 3/19/18 9:00 AM: ---------------------------------------------------------------- [~rob.stryker], now I have all the latest updates. The disclaimer is gone, that's good. {quote} So I believe strongly: 1) The file now gets downloaded to the tmp folder you chose 2) The file gets renamed to / moved to the real destination folder 3) The file permissions are then changed, and the versioning validation works as expected. {quote} 1) and 2) works - it's moved to the correct folder, but it's still called cdk-3.xx...., but I guess that's ok. 3) works as well: {code} $ ls -l /Users/rasp/tmp/cdk-3.3.0-1-minishift-darwin-amd64 -rwxr--r-- 1 rasp staff 483310592 Mar 19 13:46 /Users/rasp/tmp/cdk-3.3.0-1-minishift-darwin-amd64 {code} (At first I thought it wasn't correct because there is no x for the group which I normally expect. But there is x for the owner which is what matters.) Once I ran setup-cdk manually from CLI, I was able to start cdk from the IDE. Ultimately it failed but that's probably because I already had a pre-existing minishift installation which was replaced by the new one, but some of the virtualbox components were already defined: {code} -- Starting Minishift VM .......... FAIL E0319 13:56:16.418650 47229 start.go:368] Error starting the VM: Error creating the VM. Error creating machine: Error in driver during machine creation: /usr/local/bin/VBoxManage storagectl minishift --name SATA --add sata --hostiocache on failed: VBoxManage: error: Storage controller named 'SATA' already exists VBoxManage: error: Details: code VBOX_E_OBJECT_IN_USE (0x80bb000c), component SessionMachine, interface IMachine, callee nsISupports VBoxManage: error: Context: "AddStorageController(Bstr(pszCtl).raw(), StorageBus_SATA, ctl.asOutParam())" at line 1070 of file VBoxManageStorageController.cpp . Retrying. Error starting the VM: Error creating the VM. Error creating machine: Error in driver during machine creation: /usr/local/bin/VBoxManage storagectl minishift --name SATA --add sata --hostiocache on failed: VBoxManage: error: Storage controller named 'SATA' already exists VBoxManage: error: Details: code VBOX_E_OBJECT_IN_USE (0x80bb000c), component SessionMachine, interface IMachine, callee nsISupports VBoxManage: error: Context: "AddStorageController(Bstr(pszCtl).raw(), StorageBus_SATA, ctl.asOutParam())" at line 1070 of file VBoxManageStorageController.cpp {code} Once I removed everything from VirtualBox and started again, cdk then started correctly. was (Author: mmalina): [~rob.stryker], now I have all the latest updates. The disclaimer is gone, that's good. {quote} So I believe strongly: 1) The file now gets downloaded to the tmp folder you chose 2) The file gets renamed to / moved to the real destination folder 3) The file permissions are then changed, and the versioning validation works as expected. {quote} 1) and 2) works - it's moved to the correct folder, but it's still called cdk-3.xx...., but I guess that's ok. But 3) does not work - it still only has read permissions: {code} $ ls -l /Users/rasp/tmp/cdk-3.3.0-1-minishift-darwin-amd64 -rwxr--r-- 1 rasp staff 483310592 Mar 19 13:46 /Users/rasp/tmp/cdk-3.3.0-1-minishift-darwin-amd64 {code} > Add links for downloading minishift and cdk in New Server Adapter wizard > ------------------------------------------------------------------------ > > Key: JBIDE-25753 > URL: https://issues.jboss.org/browse/JBIDE-25753 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: cdk, server > Affects Versions: 4.5.3.AM2 > Reporter: Josef Kopriva > Assignee: Rob Stryker > Fix For: 4.5.3.AM3 > > Attachments: cdk-dl-error.png > > > In "New Server Adapter" wizard should be buttons/links to download minishift/cdk binaries or similar wizard as it is done for EAP/WildFly servers runtimes. > WDYT [~adietish] [~jeffmaury] ? -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20569) OpenShift Explorer : "Import Application" menu is confusing

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20569?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-20569 at 3/19/18 8:57 AM: ------------------------------------------------------------------- [~jeffmaury] [~jkopriva] reorg is completed. I also added (freeware) icons to *Edit > Resource Limits* and *Edit > Environment Variables* (see screenshot). !screenshot-1.png! I also corrected the labels in the ITests. [~jkopriva] dare to review https://github.com/jbosstools/jbosstools-openshift/pull/1700 please? was (Author: adietish): [~jeffmaury] [~jkopriva] reorg is completed. I also added icon to *Edit > Resource Limits* and *Edit > Environment Variables* (see screenshot). !screenshot-1.png! I also corrected the labels in the ITests. [~jkopriva] dare to review https://github.com/jbosstools/jbosstools-openshift/pull/1700 please? > OpenShift Explorer : "Import Application" menu is confusing > ----------------------------------------------------------- > > Key: JBIDE-20569 > URL: https://issues.jboss.org/browse/JBIDE-20569 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Fred Bricon > Assignee: Andre Dietisheim > Labels: explorer, ux > Fix For: 4.5.3.AM3 > > Attachments: existing-context-menu.png, import-application.png, new-context-menu-2.png, new-context-menu.png, project-explorer-context-menu.png, screenshot-1.png > > > [~sspeiche] finds the "Import Application" menu in OpenShift Explorer is confusing: does it mean import from eclipse to openshift or the other way around (it's the latter). Needs better wording. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20569) OpenShift Explorer : "Import Application" menu is confusing

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20569?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-20569 at 3/19/18 8:56 AM: ------------------------------------------------------------------- [~jeffmaury] [~jkopriva] reorg is completed. I also added icon to *Edit > Resource Limits* and *Edit > Environment Variables* (see screenshot). !screenshot-1.png! I also corrected the labels in the ITests. [~jkopriva] dare to review please? was (Author: adietish): [~jeffmaury] [~jkopriva] reorg is completed. I also added icon to *Edit > Resource Limits* and *Edit > Environment Variables* (see screenshot). !screenshot-1.png! I also corrected the labels in the ITests. > OpenShift Explorer : "Import Application" menu is confusing > ----------------------------------------------------------- > > Key: JBIDE-20569 > URL: https://issues.jboss.org/browse/JBIDE-20569 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Fred Bricon > Assignee: Andre Dietisheim > Labels: explorer, ux > Fix For: 4.5.3.AM3 > > Attachments: existing-context-menu.png, import-application.png, new-context-menu-2.png, new-context-menu.png, project-explorer-context-menu.png, screenshot-1.png > > > [~sspeiche] finds the "Import Application" menu in OpenShift Explorer is confusing: does it mean import from eclipse to openshift or the other way around (it's the latter). Needs better wording. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 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 March 2018