[JBoss JIRA] (JBIDE-21422) Server adapter editor: details should be editable
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21422?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-21422:
---------------------------------------------
doesn't the latest changes mean that you can deploy things to this app *without* having the "special" project ? then I would say being able to have it use server specific settings are still relevant for V3.
> Server adapter editor: details should be editable
> -------------------------------------------------
>
> Key: JBIDE-21422
> URL: https://issues.jboss.org/browse/JBIDE-21422
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.3.1.Beta1
> Reporter: Marián Labuda
> Labels: openshift_v3, server_adapter
> Fix For: 4.3.1.CR1
>
>
> Currently when I open a server adapter overview (by double click on a server adapter) there is whole section of details to which project it is bind to, paths etc. in the Project Settings section. This area is not editable. It would be nice to allow user modify this, to allow to choose different eclipse project or fix path if it was filled in wrong...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-15630) Have "Report Bug" dialog actually report bugs
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15630?page=com.atlassian.jira.plugi... ]
Alexey Kazakov closed JBIDE-15630.
----------------------------------
Fix Version/s: 4.3.1.CR1
(was: 4.3.x)
Resolution: Rejected
Agree. Closing as not relevant anymore. JBDS-3566 is what we want to do instead.
> Have "Report Bug" dialog actually report bugs
> ---------------------------------------------
>
> Key: JBIDE-15630
> URL: https://issues.jboss.org/browse/JBIDE-15630
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: common/jst/core
> Affects Versions: 4.1.1.Alpha1
> Reporter: Mickael Istria
> Assignee: Alexey Kazakov
> Labels: documentation, new_and_noteworthy
> Fix For: 4.3.1.CR1
>
> Attachments: ReportBugImpl.png
>
>
> When Mylyn/Jira connector is installed, the "Report Error" dialog should provide the possiblity to directly push report as a Jira, just like Mylyn does for Eclipse.
--
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 Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21293?page=com.atlassian.jira.plugi... ]
Alexey Kazakov commented on JBIDE-21293:
----------------------------------------
>> Unfortunnately this is out of our control. We have no ability to do this.
Because of Eclipse Runtime/Server mechanism limitations? We could provide a patch to add this functionality upstream ;)
> 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: openshift
> 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-21293) CDK start timed out due to slow image download
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21293?page=com.atlassian.jira.plugi... ]
Alexey Kazakov edited comment on JBIDE-21293 at 2/15/16 5:21 PM:
-----------------------------------------------------------------
{quote}Unfortunnately this is out of our control. We have no ability to do this.{quote}
Because of Eclipse Runtime/Server mechanism limitations? We could provide a patch to add this functionality upstream ;)
was (Author: akazakov):
>> Unfortunnately this is out of our control. We have no ability to do this.
Because of Eclipse Runtime/Server mechanism limitations? We could provide a patch to add this functionality upstream ;)
> 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: openshift
> 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