[JBoss JIRA] (JBIDE-7004) Add support for externalization of all string from web page
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-7004?page=com.atlassian.jira.plugin... ]
Alexey Kazakov reassigned JBIDE-7004:
-------------------------------------
Assignee: Jeff MAURY (was: Alexey Kazakov)
> Add support for externalization of all string from web page
> -----------------------------------------------------------
>
> Key: JBIDE-7004
> URL: https://issues.jboss.org/browse/JBIDE-7004
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: jsp/jsf/xml/html-source-editing
> Affects Versions: 3.3.0.M1
> Reporter: Maxim Areshkau
> Assignee: Jeff MAURY
> Labels: new_and_noteworthy
> Fix For: LATER
>
> Attachments: Externalize All Strings From Page Dlg.bmml, Externalize All Strings From Page Dlg.bmml, Externalize All Strings From Page Dlg.bmml, Externalize All Strings From Page Dlg.png, JBIDE7004-CONTEXT_MENU.png, JBIDE7004-PAGE1_BROWSE.png, JBIDE7004-PAGE1_LIST.png, JBIDE7004-PAGE2_STRINGS.png, JBIDE7004-PAGE3_BUNDLE.png
>
>
> The dialog to externalize all strings contains 3 pages.
> After user has selected "Externalize all strings.. " menu item
> !JBIDE7004-CONTEXT_MENU.png|width=400px!
> the dialog will appear:
> 1) On "Page1" user selects the bundle's *.properties file from the project
> !JBIDE7004-PAGE1_BROWSE.png|width=400px!
> All the properties from that file are shown in the table
> !JBIDE7004-PAGE1_LIST.png|width=400px!
> 2) Then "Page2" shows the list of all not-externalized strings along with generated keys for them. User can edit key directly in the table
> !JBIDE7004-PAGE2_STRINGS.png|width=400px!
> Validation for keys and values is performed instantly.
> 3) On the last "Page3" user selects the way how to register the resource bundle on the page: manually, in faces-config, via f:loadBundle
> !JBIDE7004-PAGE3_BUNDLE.png|width=400px!.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months
[JBoss JIRA] (JBIDE-18678) Make dependencies to org.jboss.tools.usage optional
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18678?page=com.atlassian.jira.plugi... ]
Alexey Kazakov reassigned JBIDE-18678:
--------------------------------------
Assignee: Jeff MAURY (was: Alexey Kazakov)
> Make dependencies to org.jboss.tools.usage optional
> ---------------------------------------------------
>
> Key: JBIDE-18678
> URL: https://issues.jboss.org/browse/JBIDE-18678
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: browsersim, usage
> Affects Versions: 4.2.0.CR1
> Reporter: Kaloyan Raev
> Assignee: Jeff MAURY
> Fix For: 4.4.x
>
>
> I am interested in adopting the CordovaSim feature in our product. However, most of the browsersim bundles have a strong dependency to org.jboss.tools.usage bundle, which force a Usage Reporting popup on startup. I want to avoid this and have the org.jboss.tools.usage excluded from my build.
> Is it possible to make the dependencies to org.jboss.tools.usage optional?
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months
[JBoss JIRA] (JBIDE-15480) Keep data for ICategoryProvider in KB model
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15480?page=com.atlassian.jira.plugi... ]
Alexey Kazakov reassigned JBIDE-15480:
--------------------------------------
Assignee: Jeff MAURY (was: Alexey Kazakov)
> Keep data for ICategoryProvider in KB model
> -------------------------------------------
>
> Key: JBIDE-15480
> URL: https://issues.jboss.org/browse/JBIDE-15480
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: common
> Reporter: Viacheslav Kabanovich
> Assignee: Jeff MAURY
> Fix For: 4.5.0.AM1
>
>
> Interface ICategoryProvider was created to sort attributes in Property View by categories and by priority. Currently, there is just one implementation for JQuery, but it was designed to have more implementations for other HTML 5 libraries. The first experience showed that this approach is resulting in repeating attribute data that otherwise could be encapsulated in KB model.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months
[JBoss JIRA] (JBIDE-1797) JBDS doesn't suggest to add not included capabilities if user uses in code or DnD a component from JBoss Tools Pallete
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-1797?page=com.atlassian.jira.plugin... ]
Alexey Kazakov reassigned JBIDE-1797:
-------------------------------------
Assignee: Jeff MAURY (was: Alexey Kazakov)
> JBDS doesn't suggest to add not included capabilities if user uses in code or DnD a component from JBoss Tools Pallete
> ----------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-1797
> URL: https://issues.jboss.org/browse/JBIDE-1797
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: jsp/jsf/xml/html-source-editing
> Affects Versions: 2.0.1
> Reporter: Andrei Scherbovich
> Assignee: Jeff MAURY
> Priority: Minor
> Fix For: LATER
>
>
> JBDS doesn't suggest to add not included capabilities if user uses in code or DnD a component from JBoss Tools Pallete
> Steps to reproduce:
> 1. EXECUTE: Create KickStart JSF project
> 2. EXECUTE: Open hello.jsp page and DnD from JBoss Tools Pallete <rich:calendar> component
> 3. ASSERT: <%@ taglib uri="http://richfaces.org/rich" prefix="rich"%> inserted by JBDS. But RichFaces capabilities are not available in the project.
> It would be handy if JBDS suggests to add RichFaces capabilities after 2-nd step e.g.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months
[JBoss JIRA] (JBIDE-16272) Having both RichFaces 4.5 and 5.x taglibs in one JSF project malfunction components auto completion
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16272?page=com.atlassian.jira.plugi... ]
Alexey Kazakov reassigned JBIDE-16272:
--------------------------------------
Assignee: Jeff MAURY (was: Alexey Kazakov)
> Having both RichFaces 4.5 and 5.x taglibs in one JSF project malfunction components auto completion
> ---------------------------------------------------------------------------------------------------
>
> Key: JBIDE-16272
> URL: https://issues.jboss.org/browse/JBIDE-16272
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsf
> Affects Versions: 4.1.1.Final
> Reporter: Juraj Húska
> Assignee: Jeff MAURY
> Fix For: 4.3.x
>
> Attachments: a4jTagLibCtrlClick.png, jbtca.png, jbthtml.png, jsfTagProposals.png, myAutocompletion1.png, myAutocompletion2.png, myAutocompletion3.png, scr.png, scr2.png, scr3.png, tagLibraries1.png, taglib2.png
>
>
> When I create new JSF project, where I add RichFaces libraries needed to create _RichFaces 4.5_ (a special version which should be some kind of bridge between RichFaces 4 and 5) application:
> * richfaces-5.0.0.Alpha2.jar
> * richfaces-components-a4j-4.5.0.Alpha1.jar
> * richfaces-components-rich-4.5.0.Alpha1.jar
> Then if you have all supported namespaces included, auto completion triggered e.g. on {{<a4j:}} will provides also non existing components, like {{<a4j:calendar}} (it should be {{<rich:calendar}} )
> Please see steps to reproduce.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months
[JBoss JIRA] (JBIDE-17920) Tag Libs are not added when externalizing strings
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17920?page=com.atlassian.jira.plugi... ]
Alexey Kazakov reassigned JBIDE-17920:
--------------------------------------
Assignee: Jeff MAURY (was: Alexey Kazakov)
> Tag Libs are not added when externalizing strings
> -------------------------------------------------
>
> Key: JBIDE-17920
> URL: https://issues.jboss.org/browse/JBIDE-17920
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: jsp/jsf/xml/html-source-editing
> Affects Versions: 4.2.0.Beta3
> Environment: JBDS Beta3-v20140712-0200-B178
> Reporter: Vlado Pakan
> Assignee: Jeff MAURY
> Priority: Minor
> Fix For: 4.3.x
>
>
> *Test case 1*
> 1. Create JSF 1.2 Kick Start project
> 2. Open inputUserName.jsp
> 3. Delete line <%@ taglib uri="http://java.sun.com/jsf/core" prefix="f" %>
> 4. Select "User" string within <title> tag
> 5. Click on Externalize selected string... toolitem
> 6. Check Create a new properties file check box
> 7. Click Next> two times
> 8. Select via <f:loadBundle> tag on current page
> 9. Click OK
> ERROR: Tag lib defintion for 'f' name space is not added to web page
> *Test case 2*
> ERROR: The same applies for inputname.xhtml page created within JSF 2.0 Kick Start project
> *Test case 3*
> 1. Create JSF 1.2 Kick Start project
> 2. Open inputUserName.jsp
> 3. Change taglib prefix in line <%@ taglib uri="http://java.sun.com/jsf/core" prefix="f" %> to "d"
> 4. Select "User" string within <title> tag
> 5. Click on Externalize selected string... toolitem
> 6. Check Create a new properties file check box
> 7. Click Next> two times
> 8. Select via <f:loadBundle> tag on current page
> 9. Click OK
> ASSERT:
> <d:loadBundle tag should be added
> *Test case 3*
> The same applies for inputname.xhtml page created within JSF 2.0 Kick Start project
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months
[JBoss JIRA] (JBDS-3434) Kubernetes editor & wizard
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBDS-3434?page=com.atlassian.jira.plugin.... ]
Alexey Kazakov reassigned JBDS-3434:
------------------------------------
Assignee: Jeff MAURY (was: Alexey Kazakov)
> Kubernetes editor & wizard
> --------------------------
>
> Key: JBDS-3434
> URL: https://issues.jboss.org/browse/JBDS-3434
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 8.x
> Reporter: Charles Moulliard
> Assignee: Jeff MAURY
> Fix For: 10.x
>
>
> To deploy a project on Openshift3, it will be required to edit/generate a kubernetes.json file. The fabric8 project has created a maven plugin to generate the kubernetes.json file and next to deploy the project on OS" (= maven fabic8:install) but it could be interesteting also that we propose :
> - a kubernetes editor within JBDS to update the YAML or JSON file and
> - a wizard to create a kubernetes template file using some criteria like the API version, name, ports to be exposed, volumes to mount, ...
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months