[JBoss JIRA] (TOOLSDOC-573) Ensure consistent use of > for Preference options across all how tos
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-573?page=com.atlassian.jira.plug... ]
Michelle Murray updated TOOLSDOC-573:
-------------------------------------
Sprint: 2014/S23 (8-Dec > 21-Dec)
> Ensure consistent use of > for Preference options across all how tos
> --------------------------------------------------------------------
>
> Key: TOOLSDOC-573
> URL: https://issues.jboss.org/browse/TOOLSDOC-573
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Bug
> Components: General documentation issues
> Affects Versions: 4.2.0.Final
> Reporter: Michelle Murray
> Assignee: Michelle Murray
>
> Some articles write "Click Window > preferences > General > SSH" but some write "Click Window > Preferences, expand General and click SSH." One consistent wording and markup should be used across all JBT/JBDS docs.
> The first option also aligns with TOOLSDOC-439. So in creating all the how tos now would be an ideal time to fix before porting them to the CP.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 6 months
[JBoss JIRA] (TOOLSDOC-573) Ensure consistent use of > for Preference options across all how tos
by Michelle Murray (JIRA)
Michelle Murray created TOOLSDOC-573:
----------------------------------------
Summary: Ensure consistent use of > for Preference options across all how tos
Key: TOOLSDOC-573
URL: https://issues.jboss.org/browse/TOOLSDOC-573
Project: Documentation for JBoss Tools and Developer Studio
Issue Type: Bug
Components: General documentation issues
Affects Versions: 4.2.0.Final
Reporter: Michelle Murray
Assignee: Michelle Murray
Some articles write "Click Window > preferences > General > SSH" but some write "Click Window > Preferences, expand General and click SSH." One consistent wording and markup should be used across all JBT/JBDS docs.
The first option also aligns with TOOLSDOC-439. So in creating all the how tos now would be an ideal time to fix before porting them to the CP.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 6 months
[JBoss JIRA] (TOOLSDOC-572) OpenShift How To: Add info on workspace assumptions across how tos
by Michelle Murray (JIRA)
Michelle Murray created TOOLSDOC-572:
----------------------------------------
Summary: OpenShift How To: Add info on workspace assumptions across how tos
Key: TOOLSDOC-572
URL: https://issues.jboss.org/browse/TOOLSDOC-572
Project: Documentation for JBoss Tools and Developer Studio
Issue Type: Enhancement
Components: User Guide - OpenShift Tools
Affects Versions: 4.2.0.Final
Reporter: Michelle Murray
Assignee: Michelle Murray
* *Configure SSH* assumes connection is listed in OpenShift Explorer view for 2 options
* *Debug OSO App* assumes app is imported (so listed in Project Explorer view)
* *Custom Publish* assumes app is imported (so listed in Project Explorer view)
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 6 months
[JBoss JIRA] (JBDS-3284) Ionic Palette - version selection, detection
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBDS-3284?page=com.atlassian.jira.plugin.... ]
Alexey Kazakov edited comment on JBDS-3284 at 12/9/14 7:51 PM:
---------------------------------------------------------------
Ionic is still in 1.0.0.Beta. I don't think we should support multiple versions until at least two final version released. WDYT?
was (Author: akazakov):
Ionic is still in Beta. I don't think we should support multiple versions until at least two final version released. WDYT?
> Ionic Palette - version selection, detection
> --------------------------------------------
>
> Key: JBDS-3284
> URL: https://issues.jboss.org/browse/JBDS-3284
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Reporter: Burr Sutter
>
> As a Cordova-focused hybrid mobile app developer, I need to be able to import existing Ionic projects and modify the version of the Ionic framework, where the Palette is flexible enough to handle version changes, including addition/subtraction of specific widgets only available in particular versions.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 6 months
[JBoss JIRA] (JBDS-3284) Ionic Palette - version selection, detection
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBDS-3284?page=com.atlassian.jira.plugin.... ]
Alexey Kazakov reassigned JBDS-3284:
------------------------------------
Assignee: Alexey Kazakov
> Ionic Palette - version selection, detection
> --------------------------------------------
>
> Key: JBDS-3284
> URL: https://issues.jboss.org/browse/JBDS-3284
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Reporter: Burr Sutter
> Assignee: Alexey Kazakov
>
> As a Cordova-focused hybrid mobile app developer, I need to be able to import existing Ionic projects and modify the version of the Ionic framework, where the Palette is flexible enough to handle version changes, including addition/subtraction of specific widgets only available in particular versions.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 6 months
[JBoss JIRA] (JBDS-3284) Ionic Palette - version selection, detection
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBDS-3284?page=com.atlassian.jira.plugin.... ]
Alexey Kazakov commented on JBDS-3284:
--------------------------------------
Ionic is still in Beta. I don't think we should support multiple versions until at least two final version released. WDYT?
> Ionic Palette - version selection, detection
> --------------------------------------------
>
> Key: JBDS-3284
> URL: https://issues.jboss.org/browse/JBDS-3284
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Reporter: Burr Sutter
>
> As a Cordova-focused hybrid mobile app developer, I need to be able to import existing Ionic projects and modify the version of the Ionic framework, where the Palette is flexible enough to handle version changes, including addition/subtraction of specific widgets only available in particular versions.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 6 months
[JBoss JIRA] (JBDS-3268) New Cordova Project via JBDS with git push to FH
by Gorkem Ercan (JIRA)
[ https://issues.jboss.org/browse/JBDS-3268?page=com.atlassian.jira.plugin.... ]
Gorkem Ercan commented on JBDS-3268:
------------------------------------
This is what I call "Share (export) to FeedHenry" wizard. I have some doubts about it though. At the moment, we only have a single project template that generates a modified version of the hello world app from Apache Cordova. However FeedHenry Cordova apps depend heavily on the functionality provided by feedhenry.js to integrate wit the FH back end. So I think there is not much value in this functionality, if we do not have some kind of FH related templates to create the project or a clever way to inject feedhenry.js.
This can provide value if you just want to use the FH build farm though. I am not sure if that is the main purpose here.
> New Cordova Project via JBDS with git push to FH
> ------------------------------------------------
>
> Key: JBDS-3268
> URL: https://issues.jboss.org/browse/JBDS-3268
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Reporter: Burr Sutter
>
> As a HTML5-focused mobile application developer, I wish to use JBoss Tools and JBDS to craft my AngularJS+Ionic or jQuery Mobile-based application, testing it via CordovaSim, deploy the application to my iOS and/or Android phone and when I feel it is "about right", push it to FeedHenry's git URL.
> It is currently unclear how an end-user takes his/her JBDS Hybrid Mobile (Cordova) project and sets it up to support a git push to FH.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 6 months
[JBoss JIRA] (JBDS-3285) Git: Easy Import
by Burr Sutter (JIRA)
Burr Sutter created JBDS-3285:
---------------------------------
Summary: Git: Easy Import
Key: JBDS-3285
URL: https://issues.jboss.org/browse/JBDS-3285
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Feature Request
Reporter: Burr Sutter
As a Java EE developer, in some cases using Git for the first time (or only familiar with command line git), I find it very difficult to clone and import a project correctly into JBDS, having the appropriate facets configured, if it has a maven pom.xml, correctly setting the build path, where it is easily deployable to a localhost EAP instance.
The mission here is to make the Git experience much more user friendly.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 6 months
[JBoss JIRA] (JBDS-3285) Git: Easy Import
by CDW Engine (JIRA)
[ https://issues.jboss.org/browse/JBDS-3285?page=com.atlassian.jira.plugin.... ]
CDW Engine updated JBDS-3285:
-----------------------------
CDW pm_ack: ?
CDW release: ?
> Git: Easy Import
> ----------------
>
> Key: JBDS-3285
> URL: https://issues.jboss.org/browse/JBDS-3285
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Reporter: Burr Sutter
>
> As a Java EE developer, in some cases using Git for the first time (or only familiar with command line git), I find it very difficult to clone and import a project correctly into JBDS, having the appropriate facets configured, if it has a maven pom.xml, correctly setting the build path, where it is easily deployable to a localhost EAP instance.
> The mission here is to make the Git experience much more user friendly.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 6 months