[JBoss JIRA] (JBIDE-21677) Change branding for EAP server types
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21677?page=com.atlassian.jira.plugi... ]
Fred Bricon commented on JBIDE-21677:
-------------------------------------
Much much nicer icon! +1
> Change branding for EAP server types
> ------------------------------------
>
> Key: JBIDE-21677
> URL: https://issues.jboss.org/browse/JBIDE-21677
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: server
> Affects Versions: 4.3.1.Beta2
> Reporter: Rob Stryker
> Assignee: Rob Stryker
> Priority: Critical
> Fix For: 4.3.1.CR1, 4.4.0.Alpha1
>
> Attachments: JBIDE-21677.png, JBIDE-21677_round_shadowman_transparent.png
>
>
> 1) Change branding for EAP small icon to shadowman. Ask Catherine
> 2) Change name to "Red Hat JBoss Enterprise Application Platform x.y"
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21293) CDK start timed out due to slow image download
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21293?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-21293:
--------------------------------
Component/s: cdk
(was: openshift)
> CDK start timed out due to slow image download
> ----------------------------------------------
>
> Key: JBIDE-21293
> URL: https://issues.jboss.org/browse/JBIDE-21293
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk
> Affects Versions: 4.3.1.Beta1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.3.1.CR1
>
>
> I set up a CDK server using https://github.com/redhat-developer-tooling/openshift-vagrant .
> Then I tried to start the server for the first time. Of course this will take quite long as it needs to download the VM image first. I was on a very fast connection, but it still only went around 1 MB/s. So the startup took longer than the default timeout of 450 s. The result was that the startup timed out in the middle followed by an attempted shutdown by the tooling which failed. So in the end I ended up with the running box, but with two unwanted errors.
> I'm not sure what we can do here. Perhaps just increase the timeout to something bigger? Even better would be if could detect that a download is in progress so it will take longer, but I don't think the current mechanism is capable of anything like that.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21315) CDK: Missing PATH for vagrant and VBoxManage on Mac
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21315?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-21315:
-------------------------------------
Component/s: cdk
(was: openshift)
> 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: cdk
> Affects Versions: 4.3.1.Beta1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.3.1.CR1
>
>
> 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, 1 month