[JBoss JIRA] (JBIDE-21357) Missing dialog messages for publishing via server adapter on OpenShift 2 applications
by Marián Labuda (JIRA)
Marián Labuda created JBIDE-21357:
-------------------------------------
Summary: Missing dialog messages for publishing via server adapter on OpenShift 2 applications
Key: JBIDE-21357
URL: https://issues.jboss.org/browse/JBIDE-21357
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.3.1.Beta1
Reporter: Marián Labuda
Attachments: publish_msg.png, publish_msg_no_changes.png
When I am trying to publish code to OpenShift 2 application via server adapter, there are dialogs which contains missing msg info instead of message. First one is in case of publishing no changes, another one is when I create a new OpenShift 2 application from local eclipse project via deploying to OpenShift in context menu of the eclipse project and then select Publish in context menu of server adapter. See attached screenshots.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (JBIDE-20761) Support editing Build Configuration parameters
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20761?page=com.atlassian.jira.plugi... ]
Marián Labuda closed JBIDE-20761.
---------------------------------
Verified in JBDS 9.1.0.Beta1 build ID B197.
> Support editing Build Configuration parameters
> ----------------------------------------------
>
> Key: JBIDE-20761
> URL: https://issues.jboss.org/browse/JBIDE-20761
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.3.0.CR1
> Reporter: Fred Bricon
> Assignee: Fred Bricon
> Labels: new_and_noteworthy
> Fix For: 4.3.1.Beta1
>
>
> As a developer I want to be able to update the git url used in my existing OpenShift application buildconfig to use a different repository than what the default template used so I can publish my own changes to OS
> Pre-Req:
> - An application is deployed on OpenShift, using git for its source repository
> Goal:
> - Modify the git source url used to build and redeploy the application
> Build Config parameters should be editable from either the Properties view (but how exactly?) or another mechanism from OpenShift Explorer (TBD)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (JBIDE-21346) [RHMAP] Exported mobile app cannot be built in rhmap cloud
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21346?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-21346:
-----------------------------------
Fix Version/s: 4.3.1.Beta2
(was: 4.3.1.Beta1)
> [RHMAP] Exported mobile app cannot be built in rhmap cloud
> ----------------------------------------------------------
>
> Key: JBIDE-21346
> URL: https://issues.jboss.org/browse/JBIDE-21346
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid
> Affects Versions: 4.3.1.Beta1
> Reporter: Pavol Srna
> Fix For: 4.3.1.Beta2
>
> Attachments: Screen Shot 2015-12-17 at 10.53.56.png
>
>
> {code}
> [BUILD] Copy application files...
> [BUILD] Copy asset files...
> [BUILD] Adding build task to queue
> [BUILD] Creating project...
> [BUILD] Creating directories...
> [BUILD] Downloading files...
> [BUILD] Unzip files...
> [BUILD] Creating native project...
> [BUILD] Project created. Applying configuration changes and copying app files...
> { [Error: ENOENT, no such file or directory '/data/fh-digger/data/tmp/2d20da63-2d05-442a-8888-558e418202be/unzip/files/plugins/android.json']
> errno: 34,
> code: 'ENOENT',
> path: '/data/fh-digger/data/tmp/2d20da63-2d05-442a-8888-558e418202be/unzip/files/plugins/android.json',
> syscall: 'open' }
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (JBIDE-21346) [RHMAP] Exported mobile app cannot be built in rhmap cloud
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21346?page=com.atlassian.jira.plugi... ]
Alexey Kazakov reassigned JBIDE-21346:
--------------------------------------
Assignee: Gorkem Ercan
> [RHMAP] Exported mobile app cannot be built in rhmap cloud
> ----------------------------------------------------------
>
> Key: JBIDE-21346
> URL: https://issues.jboss.org/browse/JBIDE-21346
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid
> Affects Versions: 4.3.1.Beta1
> Reporter: Pavol Srna
> Assignee: Gorkem Ercan
> Fix For: 4.3.1.Beta2
>
> Attachments: Screen Shot 2015-12-17 at 10.53.56.png
>
>
> {code}
> [BUILD] Copy application files...
> [BUILD] Copy asset files...
> [BUILD] Adding build task to queue
> [BUILD] Creating project...
> [BUILD] Creating directories...
> [BUILD] Downloading files...
> [BUILD] Unzip files...
> [BUILD] Creating native project...
> [BUILD] Project created. Applying configuration changes and copying app files...
> { [Error: ENOENT, no such file or directory '/data/fh-digger/data/tmp/2d20da63-2d05-442a-8888-558e418202be/unzip/files/plugins/android.json']
> errno: 34,
> code: 'ENOENT',
> path: '/data/fh-digger/data/tmp/2d20da63-2d05-442a-8888-558e418202be/unzip/files/plugins/android.json',
> syscall: 'open' }
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (JBTIS-541) Not able to specify Target runtime while creating Switchyard project.
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBTIS-541?page=com.atlassian.jira.plugin.... ]
Alexey Kazakov updated JBTIS-541:
---------------------------------
Project: JBoss Tools Integration Stack (was: Tools (JBoss Tools))
Key: JBTIS-541 (was: JBIDE-21344)
Component/s: switchyard
(was: switchyard)
Affects Version/s: (was: 2.0.1)
> Not able to specify Target runtime while creating Switchyard project.
> ---------------------------------------------------------------------
>
> Key: JBTIS-541
> URL: https://issues.jboss.org/browse/JBTIS-541
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: switchyard
> Reporter: Abhijit Humbe
> Assignee: Brian Fitzpatrick
>
> When we try to create switchyard project, we cannot select Target Runtime.
> We can see same behavior enven after runtime environment is configured. The list for "Target Runtime" has only "<None>".
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (JBIDE-20761) Support editing Build Configuration parameters
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20761?page=com.atlassian.jira.plugi... ]
Fred Bricon commented on JBIDE-20761:
-------------------------------------
2. It's not my expectation to have the editor reopen the resources properties on workspace restart, so I don't feel like restoring it is mandatory here. If you strongly feel the opposite, please open a new ticket and let's discuss that there.
3. I reckon that was probably not obvious but yes, we're expecting to use the future Eclipse default json editor in the long term. However, that won't be available until Neon so we certainly need to make it more robust. See JBIDE-21356
As for fined-grained properties edition, I opened JBIDE-21355.
Thanks [~scabanovich], I very much appreciate your input, and your PRs are always welcome :-)
[~mlabuda] feel free to close this one.
> Support editing Build Configuration parameters
> ----------------------------------------------
>
> Key: JBIDE-20761
> URL: https://issues.jboss.org/browse/JBIDE-20761
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.3.0.CR1
> Reporter: Fred Bricon
> Assignee: Fred Bricon
> Labels: new_and_noteworthy
> Fix For: 4.3.1.Beta1
>
>
> As a developer I want to be able to update the git url used in my existing OpenShift application buildconfig to use a different repository than what the default template used so I can publish my own changes to OS
> Pre-Req:
> - An application is deployed on OpenShift, using git for its source repository
> Goal:
> - Modify the git source url used to build and redeploy the application
> Build Config parameters should be editable from either the Properties view (but how exactly?) or another mechanism from OpenShift Explorer (TBD)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (JBIDE-21356) Make OpenShift 3 resource edition more robust
by Fred Bricon (JIRA)
Fred Bricon created JBIDE-21356:
-----------------------------------
Summary: Make OpenShift 3 resource edition more robust
Key: JBIDE-21356
URL: https://issues.jboss.org/browse/JBIDE-21356
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: openshift
Affects Versions: 4.3.0.Beta1
Reporter: Fred Bricon
Following [~scabanovich]'s comment in JBIDE-20761:
{quote}
My concern is that the default editor is called if it is set for .json without a fallback for a case of failure of that unknown editor. We cannot be sure what editor a user may have set to be default for .json. That editor may be expecting some specific instance of editor input object and fail on what is provided. As it is, then json will not be opened at all, neither fancy nor plain text. However, if it is just temporal, till the expected contribution to jsdt, and that editor is going to be hardcoded to be opened, then no problem.
{quote}
Until we can rely on Eclipse's upcoming JSON editor (in Neon), we should try to harden editor detection/opening
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months