[JBoss JIRA] (JBIDE-21315) CDK: Missing PATH for vagrant and VBoxManage on Mac
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21315?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-21315:
--------------------------------
Fix Version/s: 4.3.1.Beta2
> CDK: Missing PATH for vagrant and VBoxManage on Mac
> ---------------------------------------------------
>
> Key: JBIDE-21315
> URL: https://issues.jboss.org/browse/JBIDE-21315
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.3.1.Beta2
>
>
> It seems there is no JIRA to track this specifically yet.
> The problem is that CDK tooling relies on PATH to find vagrant. And the "vagrant up" command in turn depends on PATH to find e.g. VBoxManage.
> On Mac, when you start your Eclipse / JBDS as an app by double-clicking an icon on your Desktop or in Finder, the Eclipse instance will have no PATH env variable.
> One workaround is to start your Eclipse from command line by going inside the package:
> {code}
> cd Eclipse.app/Contents/MacOS
> ./eclipse
> {code}
> But this is definitely not the recommended way to start Eclipse - I'm not sure if eclipse.ini is located properly in this case. But at least PATH is correct then.
> There is actually one more workaround. To add your PATH to the Environment tab in Launch config. That works for me.
> So that might be a potential solution to this problem - have a predefined PATH for each OS in case there is none defined in the Eclipse process.
> Previous related JIRAs:
> JBIDE-21175 [CDK] Require better logic to find vagrant.exe / vagrant command
> JBIDE-21172 CDK server in Starting state and cannot be stopped with wrong path to vagrant
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (JBIDE-19978) Docker Images and Containers view do not display count at the top of the view
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19978?page=com.atlassian.jira.plugi... ]
Martin Malina resolved JBIDE-19978.
-----------------------------------
Fix Version/s: 4.3.1.Beta1
(was: 4.3.x)
Resolution: Done
I believe this has been fixed upstream. Works correctly in JBDS 9.1.0.Beta1.
> Docker Images and Containers view do not display count at the top of the view
> -----------------------------------------------------------------------------
>
> Key: JBIDE-19978
> URL: https://issues.jboss.org/browse/JBIDE-19978
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: docker, upstream
> Affects Versions: 4.3.0.Beta1
> Reporter: Martin Malina
> Assignee: Xavier Coulon
> Fix For: 4.3.1.Beta1
>
> Attachments: docker-no-count.png, images-count-missing.png
>
>
> After establishing a connection to my Docker instance, the Docker Images view shows active images. At the top, it should display something like (4/31 Images), but at first it doesn't show this.
> If I selected Show all images, and then uncheck it again, the numbers are now shown.
> In a previous attempt, during the download of the wildfly image, the numbers were shown, but once the pulling finished, the numbers disappeared.
> Similarly, in the Docker Containers view, when you first create a docker connection, the numbers are not there. But once I check Show all containers and uncheck it again, it will properly show (0/1 Containers).
> Upstream BZ is here: https://bugs.eclipse.org/bugs/show_bug.cgi?id=469628
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (JBIDE-19978) Docker Images and Containers view do not display count at the top of the view
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19978?page=com.atlassian.jira.plugi... ]
Martin Malina closed JBIDE-19978.
---------------------------------
> Docker Images and Containers view do not display count at the top of the view
> -----------------------------------------------------------------------------
>
> Key: JBIDE-19978
> URL: https://issues.jboss.org/browse/JBIDE-19978
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: docker, upstream
> Affects Versions: 4.3.0.Beta1
> Reporter: Martin Malina
> Assignee: Xavier Coulon
> Fix For: 4.3.1.Beta1
>
> Attachments: docker-no-count.png, images-count-missing.png
>
>
> After establishing a connection to my Docker instance, the Docker Images view shows active images. At the top, it should display something like (4/31 Images), but at first it doesn't show this.
> If I selected Show all images, and then uncheck it again, the numbers are now shown.
> In a previous attempt, during the download of the wildfly image, the numbers were shown, but once the pulling finished, the numbers disappeared.
> Similarly, in the Docker Containers view, when you first create a docker connection, the numbers are not there. But once I check Show all containers and uncheck it again, it will properly show (0/1 Containers).
> Upstream BZ is here: https://bugs.eclipse.org/bugs/show_bug.cgi?id=469628
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (JBIDE-21193) runtime detection detects *any* folder as a CDK and jboss multiple times
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21193?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-21193:
---------------------------------------
Cool, thanks.
> runtime detection detects *any* folder as a CDK and jboss multiple times
> ------------------------------------------------------------------------
>
> Key: JBIDE-21193
> URL: https://issues.jboss.org/browse/JBIDE-21193
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: runtime-detection
> Reporter: Max Rydahl Andersen
> Assignee: Rob Stryker
> Priority: Blocker
> Fix For: 4.3.1.Beta1
>
> Attachments: Java_EE_-_jboss-eap-6_1_CDK_Server_-_Eclipse.png
>
>
> with build from last week I now get this list of runtime detected in my folder of servers.
> At first I thought it was the CDK being weird but something is also very weird about the basic runtime detection since I seem to have multiple WildFly 8.0's...as opposed to using the folder name.
> Here is the content of my folder
> {code}
> apache-karaf-2.3.5
> apache-tomcat-7.0.35
> app.js
> app.js.1
> fsw-6
> jboss as 7
> jboss-5.1.0.GA
> jboss-as-7.0.1.Final
> jboss-as-7.1.0.Final
> jboss-as-7.1.1.Final
> jboss-as-web-7.0.0.Final
> jboss-as-web-7.0.2.Final
> jboss-eap-6.0.1
> jboss-eap-6.1
> weld-1.1.0.Final
> weld-1.1.5.Final
> wildfly-10.0.0.CR4
> wildfly-8.0.0.Beta1
> wildfly-8.0.0.Final
> wildfly-8.1.0.Final
> wildfly-8.2.0
> wildfly-core-8.0.0.Final
> {code}
> and attached is the list I get.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (JBDS-3552) Developer - be able to incrementally deploy changes to docker containers
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBDS-3552?page=com.atlassian.jira.plugin.... ]
Xavier Coulon reassigned JBDS-3552:
-----------------------------------
Assignee: Fred Bricon (was: Xavier Coulon)
Assigning to [~fbricon] for the OpenShift part of the tooling.
> Developer - be able to incrementally deploy changes to docker containers
> -------------------------------------------------------------------------
>
> Key: JBDS-3552
> URL: https://issues.jboss.org/browse/JBDS-3552
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Story
> Components: docker
> Reporter: Max Rydahl Andersen
> Assignee: Fred Bricon
> Fix For: 9.1.0.Beta1, 10.0.0.Alpha1
>
>
> User Story:
> As a Developer I want to be able to incrementally deploy changes to my running application without building from scratch so I can see changes quickly.
> Acceptance Criteria:
> * Once the initial application is deployed changes made in the IDE should be deployed over to the containers filesystem/deployment.
> * Changes that the runtime support to pickup dynamically (i.e. html/js for JavaEE) should take effect immediatly and be seen in a browser refresh.
> * Changes that the the runtime requires a restart for (i.e. class files) should take effect when restarting the application (which should not require a rebuild from source)
> * Same workflow should work for docker and openshift applications (but each might implement it differently using oc sync or docker rsync or volume mounts etc.)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (JBIDE-20550) New Project Example: Tooltip missing for requirement with a warning triangle
by Radim Hopp (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20550?page=com.atlassian.jira.plugi... ]
Radim Hopp closed JBIDE-20550.
------------------------------
Verified in JBDS 9.1.0.Beta1-v20151212-0638-B189. Closing.
> New Project Example: Tooltip missing for requirement with a warning triangle
> ----------------------------------------------------------------------------
>
> Key: JBIDE-20550
> URL: https://issues.jboss.org/browse/JBIDE-20550
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: project-examples
> Affects Versions: 4.3.0.CR1
> Reporter: Martin Malina
> Assignee: Fred Bricon
> Fix For: 4.3.1.Beta1
>
> Attachments: empty-tooltip.png
>
>
> When you open a new project example wizard and there is a requirement which is not really met, a yellow warning triangle may be shown.
> I wanted to know what this means so I pointed my mouse at it a an empty tooltip was shown. We should put some text into the tooltip explaining what's going on.
> The screenshot below already shows the empty tooltip when you hover over the triangle:
> !empty-tooltip.png!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (JBIDE-21202) Central is stuck on "Loading JBoss Central" when offline
by Radim Hopp (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21202?page=com.atlassian.jira.plugi... ]
Radim Hopp closed JBIDE-21202.
------------------------------
Verified in JBDS 9.1.0.Beta1-v20151212-0638-B189
> Central is stuck on "Loading JBoss Central" when offline
> --------------------------------------------------------
>
> Key: JBIDE-21202
> URL: https://issues.jboss.org/browse/JBIDE-21202
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.3.1.Beta1
> Environment: JBDS 9.1.0.Beta1-v20151208-1226-B169
> Reporter: Radim Hopp
> Assignee: Fred Bricon
> Priority: Blocker
> Fix For: 4.3.1.Beta1
>
>
> When started without internet access, Central is stuck on "Loading JBoss Central, please wait..." and error pops up:
> {noformat}
> Unable to open /resources/jbosstools-central-webpage.zip
> Can't find embedded central zip
> {noformat}
> even though studio/plugins/org.jboss.tools.central_2.0.1.Beta1-v20151116-2016-B57/resources/jbosstools-central-webpage.zip is present on file system.
> In JBDS 9.0.0.GA Central can be loaded without issues when offline.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months