[JBoss JIRA] (JBIDE-21937) Application Wizard: if git clone directory already exist i cannot do anything
by Radim Hopp (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21937?page=com.atlassian.jira.plugi... ]
Radim Hopp closed JBIDE-21937.
------------------------------
Verified in JBDS 10.0.0.Alpha1. Closing.
> Application Wizard: if git clone directory already exist i cannot do anything
> -----------------------------------------------------------------------------
>
> Key: JBIDE-21937
> URL: https://issues.jboss.org/browse/JBIDE-21937
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Reporter: Andre Dietisheim
> Assignee: Rob Stryker
> Labels: application_wizard
> Fix For: 4.4.0.Alpha1
>
> Attachments: application-folder-already-exists.png
>
>
> steps to reproduce:
> # EXEC: create and/or import some appliaction from OpenShift to your local workspace using the application/import wizard
> # EXEC: once you have the project imported to your workspace, delete it
> # EXEC: once it is deleted, go and try to re-import the very same application
> Result:
> The 3rd wizard page errors on the git cloning destination. You're told that the destination folder already exists within the clone destination folder. The only way out currently is to choose a different clone destination folder.
> !application-folder-already-exists.png!
> Expected:
> It would help a lot if wizard would allow you to overwrite the existing destination. The wizard could also check if the given folder holds a prior clone and then allow one to "reuse" this folder. The given folder would then simply get imported to Eclipse and we'd fetch instead of cloning.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-22299) Application Wizard: Make OpenShift templates distinquished from builder images more explicit
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22299?page=com.atlassian.jira.plugi... ]
Marián Labuda updated JBIDE-22299:
----------------------------------
Labels: application_wizard openshift_v3 (was: )
> Application Wizard: Make OpenShift templates distinquished from builder images more explicit
> --------------------------------------------------------------------------------------------
>
> Key: JBIDE-22299
> URL: https://issues.jboss.org/browse/JBIDE-22299
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.4.0.Alpha1
> Reporter: Marián Labuda
> Priority: Critical
> Labels: application_wizard, openshift_v3
>
> We are now supporting builder images in New OpenShift Application wizard, they are displayed together in one tree. User has to read labels in parenthesis to know whether its a builder or not (there is not explicit saying whether it is a template or not). It would be nice to have it distinguished more explicit.
> Web UI use flash for templates and build icon for builder images. We could use same in our wizard on the left side of each tree item to be aware of what we are going to work with (because following wizard pages are different for builder images than for templates).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-22299) Application Wizard: Make OpenShift templates distinquished from builder images more explicit
by Marián Labuda (JIRA)
Marián Labuda created JBIDE-22299:
-------------------------------------
Summary: Application Wizard: Make OpenShift templates distinquished from builder images more explicit
Key: JBIDE-22299
URL: https://issues.jboss.org/browse/JBIDE-22299
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: openshift
Affects Versions: 4.4.0.Alpha1
Reporter: Marián Labuda
Priority: Critical
We are now supporting builder images in New OpenShift Application wizard, they are displayed together in one tree. User has to read labels in parenthesis to know whether its a builder or not (there is not explicit saying whether it is a template or not). It would be nice to have it distinguished more explicit.
Web UI use flash for templates and build icon for builder images. We could use same in our wizard on the left side of each tree item to be aware of what we are going to work with (because following wizard pages are different for builder images than for templates).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-21827) If org.jboss.quickstarts.eap is missing, provide quickfix
by Josef Kopriva (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21827?page=com.atlassian.jira.plugi... ]
Josef Kopriva closed JBIDE-21827.
---------------------------------
All kitchensink quickstarts imported without issues in version:
Version: 9.1.0.GA
Build id: GA-v20160414-0124-B497
Build date: 20160414-0124
Closing issue.
> If org.jboss.quickstarts.eap is missing, provide quickfix
> ---------------------------------------------------------
>
> Key: JBIDE-21827
> URL: https://issues.jboss.org/browse/JBIDE-21827
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: maven
> Affects Versions: 4.3.1.CR1
> Reporter: Rob Stryker
> Assignee: Fred Bricon
> Fix For: 4.3.1.CR1
>
>
> When importing kitchensink quickstart, it's possible that the maven redhat repository for "org.jboss.quickstarts.eap" is missing.
> A quickfix should be provided to remedy this situation
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (ERT-124) [ES6] Support for ES exports on Outline view [EBZ#489656]
by Shane Bryzak (JIRA)
[ https://issues.jboss.org/browse/ERT-124?page=com.atlassian.jira.plugin.sy... ]
Shane Bryzak updated ERT-124:
-----------------------------
Fix Version/s: Neon (4.6) M6
> [ES6] Support for ES exports on Outline view [EBZ#489656]
> ---------------------------------------------------------
>
> Key: ERT-124
> URL: https://issues.jboss.org/browse/ERT-124
> Project: Eclipse Release Train
> Issue Type: Task
> Components: JSDT
> Reporter: Nick Boldt
> Assignee: Shane Bryzak
> Priority: Trivial
> Labels: General, bzira
> Fix For: Neon (4.6) M6
>
>
> Outline view should show the ES6 exports in a similar manner to imports. This task involves two parts.
> 1. Enhance IJavaScriptElement model to include Exports. Enhance CompilationUnit.buildStructure() to include exports.
> 2. Enhance the Outline viewer to show the exports.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months