[JBoss JIRA] (FORGE-2176) Ability set VERBOSE=true when running the commands in IDE like Intellij
by Jyothiprasad Buddha (JIRA)
[ https://issues.jboss.org/browse/FORGE-2176?page=com.atlassian.jira.plugin... ]
Jyothiprasad Buddha updated FORGE-2176:
---------------------------------------
Issue Type: Feature Request (was: Enhancement)
> Ability set VERBOSE=true when running the commands in IDE like Intellij
> -----------------------------------------------------------------------
>
> Key: FORGE-2176
> URL: https://issues.jboss.org/browse/FORGE-2176
> Project: Forge
> Issue Type: Feature Request
> Components: Addon Development, UI - Eclipse, UI - IntelliJ IDEA
> Environment: IntelliJ, Eclipse
> Reporter: Jyothiprasad Buddha
> Labels: eclipse, intellij, logging, plugins
>
> I'm trying to develop addons and I'm just a beginner, so I may be missing if this feature is already there. However I can't find any info about this so far in any forums or documentation.
> If I'm running a command from command line, I can set VERBOSE=true that can print information on where the failure is. But if I'm running it from ide plugin, this doesn't work and it only shows single like like NullPointerException etc., Ability to set VERBOSE=true in plugin setting dialog.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 3 months
[JBoss JIRA] (FORGE-2176) Ability set VERBOSE=true when running the commands in IDE like Intellij
by Jyothiprasad Buddha (JIRA)
Jyothiprasad Buddha created FORGE-2176:
------------------------------------------
Summary: Ability set VERBOSE=true when running the commands in IDE like Intellij
Key: FORGE-2176
URL: https://issues.jboss.org/browse/FORGE-2176
Project: Forge
Issue Type: Enhancement
Components: Addon Development, UI - Eclipse, UI - IntelliJ IDEA
Environment: IntelliJ, Eclipse
Reporter: Jyothiprasad Buddha
I'm trying to develop addons and I'm just a beginner, so I may be missing if this feature is already there. However I can't find any info about this so far in any forums or documentation.
If I'm running a command from command line, I can set VERBOSE=true that can print information on where the failure is. But if I'm running it from ide plugin, this doesn't work and it only shows single like like NullPointerException etc., Ability to set VERBOSE=true in plugin setting dialog.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 3 months
[JBoss JIRA] (FORGE-2072) Setting servletVersion to 3.1 generate as many <error-page> as entity scaffolds
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-2072?page=com.atlassian.jira.plugin... ]
George Gastaldi closed FORGE-2072.
----------------------------------
Resolution: Done
> Setting servletVersion to 3.1 generate as many <error-page> as entity scaffolds
> -------------------------------------------------------------------------------
>
> Key: FORGE-2072
> URL: https://issues.jboss.org/browse/FORGE-2072
> Project: Forge
> Issue Type: Bug
> Components: Java EE
> Affects Versions: 2.12.0.Final
> Reporter: Antonio Goncalves
> Assignee: Daniel Cunha (soro)
> Fix For: 2.13.1.Final
>
>
> Take the following scripts. It creates a project, sets up servlet version to 3.1, generates two entities and scaffolds them.
> {code}
> project-new --named testwebxml
> servlet-setup --servletVersion 3.1
> jpa-new-entity --named Category ;
> jpa-new-field --named name --length 100 ;
> scaffold-generate --webRoot /admin --targets org.testwebxml.model.Category
> jpa-new-entity --named Publisher ;
> jpa-new-field --named name --length 30 ;
> scaffold-generate --webRoot /admin --targets org.testwebxml.model.Publisher
> {code}
> We end up with a {{web.xml}} file that has the {{<error-page>}} duplicated. In fact, Forge will duplicate this block each time we scaffold an entity.
> {code}
> <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
> <web-app xmlns="http://xmlns.jcp.org/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" version="3.1" xsi:schemaLocation="http://xmlns.jcp.org/xml/ns/javaee http://xmlns.jcp.org/xml/ns/javaee/web-app_3_1.xsd">
> <display-name>module07</display-name>
> <session-config>
> <session-timeout>30</session-timeout>
> </session-config>
> <mime-mapping>
> <extension>ico</extension>
> <mime-type>image/x-icon</mime-type>
> </mime-mapping>
> <error-page>
> <error-code>404</error-code>
> <location>/faces/error.xhtml</location>
> </error-page>
> <error-page>
> <error-code>500</error-code>
> <location>/faces/error.xhtml</location>
> </error-page>
> <context-param>
> <param-name>javax.faces.DATETIMECONVERTER_DEFAULT_TIMEZONE_IS_SYSTEM_TIMEZONE</param-name>
> <param-value>true</param-value>
> </context-param>
> <error-page>
> <error-code>404</error-code>
> <location>/faces/error.xhtml</location>
> </error-page>
> <error-page>
> <error-code>500</error-code>
> <location>/faces/error.xhtml</location>
> </error-page>
> </web-app>
> {code}
> If you don't setup the servlet to 3.1 but leave the default (3.0) then it works fine, the {{<error-page>}} block is not duplicated
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 4 months
[JBoss JIRA] (FORGE-2072) Setting servletVersion to 3.1 generate as many <error-page> as entity scaffolds
by Daniel Cunha (soro) (JIRA)
[ https://issues.jboss.org/browse/FORGE-2072?page=com.atlassian.jira.plugin... ]
Daniel Cunha (soro) updated FORGE-2072:
---------------------------------------
Fix Version/s: 2.13.1.Final
(was: 2.x Future)
> Setting servletVersion to 3.1 generate as many <error-page> as entity scaffolds
> -------------------------------------------------------------------------------
>
> Key: FORGE-2072
> URL: https://issues.jboss.org/browse/FORGE-2072
> Project: Forge
> Issue Type: Bug
> Components: Java EE
> Affects Versions: 2.12.0.Final
> Reporter: Antonio Goncalves
> Assignee: Daniel Cunha (soro)
> Fix For: 2.13.1.Final
>
>
> Take the following scripts. It creates a project, sets up servlet version to 3.1, generates two entities and scaffolds them.
> {code}
> project-new --named testwebxml
> servlet-setup --servletVersion 3.1
> jpa-new-entity --named Category ;
> jpa-new-field --named name --length 100 ;
> scaffold-generate --webRoot /admin --targets org.testwebxml.model.Category
> jpa-new-entity --named Publisher ;
> jpa-new-field --named name --length 30 ;
> scaffold-generate --webRoot /admin --targets org.testwebxml.model.Publisher
> {code}
> We end up with a {{web.xml}} file that has the {{<error-page>}} duplicated. In fact, Forge will duplicate this block each time we scaffold an entity.
> {code}
> <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
> <web-app xmlns="http://xmlns.jcp.org/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" version="3.1" xsi:schemaLocation="http://xmlns.jcp.org/xml/ns/javaee http://xmlns.jcp.org/xml/ns/javaee/web-app_3_1.xsd">
> <display-name>module07</display-name>
> <session-config>
> <session-timeout>30</session-timeout>
> </session-config>
> <mime-mapping>
> <extension>ico</extension>
> <mime-type>image/x-icon</mime-type>
> </mime-mapping>
> <error-page>
> <error-code>404</error-code>
> <location>/faces/error.xhtml</location>
> </error-page>
> <error-page>
> <error-code>500</error-code>
> <location>/faces/error.xhtml</location>
> </error-page>
> <context-param>
> <param-name>javax.faces.DATETIMECONVERTER_DEFAULT_TIMEZONE_IS_SYSTEM_TIMEZONE</param-name>
> <param-value>true</param-value>
> </context-param>
> <error-page>
> <error-code>404</error-code>
> <location>/faces/error.xhtml</location>
> </error-page>
> <error-page>
> <error-code>500</error-code>
> <location>/faces/error.xhtml</location>
> </error-page>
> </web-app>
> {code}
> If you don't setup the servlet to 3.1 but leave the default (3.0) then it works fine, the {{<error-page>}} block is not duplicated
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 4 months
[JBoss JIRA] (FORGE-2072) Setting servletVersion to 3.1 generate as many <error-page> as entity scaffolds
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-2072?page=com.atlassian.jira.plugin... ]
George Gastaldi reopened FORGE-2072:
------------------------------------
> Setting servletVersion to 3.1 generate as many <error-page> as entity scaffolds
> -------------------------------------------------------------------------------
>
> Key: FORGE-2072
> URL: https://issues.jboss.org/browse/FORGE-2072
> Project: Forge
> Issue Type: Bug
> Components: Java EE
> Affects Versions: 2.12.0.Final
> Reporter: Antonio Goncalves
> Assignee: Daniel Cunha (soro)
> Fix For: 2.x Future
>
>
> Take the following scripts. It creates a project, sets up servlet version to 3.1, generates two entities and scaffolds them.
> {code}
> project-new --named testwebxml
> servlet-setup --servletVersion 3.1
> jpa-new-entity --named Category ;
> jpa-new-field --named name --length 100 ;
> scaffold-generate --webRoot /admin --targets org.testwebxml.model.Category
> jpa-new-entity --named Publisher ;
> jpa-new-field --named name --length 30 ;
> scaffold-generate --webRoot /admin --targets org.testwebxml.model.Publisher
> {code}
> We end up with a {{web.xml}} file that has the {{<error-page>}} duplicated. In fact, Forge will duplicate this block each time we scaffold an entity.
> {code}
> <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
> <web-app xmlns="http://xmlns.jcp.org/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" version="3.1" xsi:schemaLocation="http://xmlns.jcp.org/xml/ns/javaee http://xmlns.jcp.org/xml/ns/javaee/web-app_3_1.xsd">
> <display-name>module07</display-name>
> <session-config>
> <session-timeout>30</session-timeout>
> </session-config>
> <mime-mapping>
> <extension>ico</extension>
> <mime-type>image/x-icon</mime-type>
> </mime-mapping>
> <error-page>
> <error-code>404</error-code>
> <location>/faces/error.xhtml</location>
> </error-page>
> <error-page>
> <error-code>500</error-code>
> <location>/faces/error.xhtml</location>
> </error-page>
> <context-param>
> <param-name>javax.faces.DATETIMECONVERTER_DEFAULT_TIMEZONE_IS_SYSTEM_TIMEZONE</param-name>
> <param-value>true</param-value>
> </context-param>
> <error-page>
> <error-code>404</error-code>
> <location>/faces/error.xhtml</location>
> </error-page>
> <error-page>
> <error-code>500</error-code>
> <location>/faces/error.xhtml</location>
> </error-page>
> </web-app>
> {code}
> If you don't setup the servlet to 3.1 but leave the default (3.0) then it works fine, the {{<error-page>}} block is not duplicated
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 4 months
[JBoss JIRA] (FORGE-2072) Setting servletVersion to 3.1 generate as many <error-page> as entity scaffolds
by Daniel Cunha (soro) (JIRA)
[ https://issues.jboss.org/browse/FORGE-2072?page=com.atlassian.jira.plugin... ]
Daniel Cunha (soro) closed FORGE-2072.
--------------------------------------
> Setting servletVersion to 3.1 generate as many <error-page> as entity scaffolds
> -------------------------------------------------------------------------------
>
> Key: FORGE-2072
> URL: https://issues.jboss.org/browse/FORGE-2072
> Project: Forge
> Issue Type: Bug
> Components: Java EE
> Affects Versions: 2.12.0.Final
> Reporter: Antonio Goncalves
> Assignee: Daniel Cunha (soro)
> Fix For: 2.x Future
>
>
> Take the following scripts. It creates a project, sets up servlet version to 3.1, generates two entities and scaffolds them.
> {code}
> project-new --named testwebxml
> servlet-setup --servletVersion 3.1
> jpa-new-entity --named Category ;
> jpa-new-field --named name --length 100 ;
> scaffold-generate --webRoot /admin --targets org.testwebxml.model.Category
> jpa-new-entity --named Publisher ;
> jpa-new-field --named name --length 30 ;
> scaffold-generate --webRoot /admin --targets org.testwebxml.model.Publisher
> {code}
> We end up with a {{web.xml}} file that has the {{<error-page>}} duplicated. In fact, Forge will duplicate this block each time we scaffold an entity.
> {code}
> <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
> <web-app xmlns="http://xmlns.jcp.org/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" version="3.1" xsi:schemaLocation="http://xmlns.jcp.org/xml/ns/javaee http://xmlns.jcp.org/xml/ns/javaee/web-app_3_1.xsd">
> <display-name>module07</display-name>
> <session-config>
> <session-timeout>30</session-timeout>
> </session-config>
> <mime-mapping>
> <extension>ico</extension>
> <mime-type>image/x-icon</mime-type>
> </mime-mapping>
> <error-page>
> <error-code>404</error-code>
> <location>/faces/error.xhtml</location>
> </error-page>
> <error-page>
> <error-code>500</error-code>
> <location>/faces/error.xhtml</location>
> </error-page>
> <context-param>
> <param-name>javax.faces.DATETIMECONVERTER_DEFAULT_TIMEZONE_IS_SYSTEM_TIMEZONE</param-name>
> <param-value>true</param-value>
> </context-param>
> <error-page>
> <error-code>404</error-code>
> <location>/faces/error.xhtml</location>
> </error-page>
> <error-page>
> <error-code>500</error-code>
> <location>/faces/error.xhtml</location>
> </error-page>
> </web-app>
> {code}
> If you don't setup the servlet to 3.1 but leave the default (3.0) then it works fine, the {{<error-page>}} block is not duplicated
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 4 months
[JBoss JIRA] (FORGE-2072) Setting servletVersion to 3.1 generate as many <error-page> as entity scaffolds
by Daniel Cunha (soro) (JIRA)
[ https://issues.jboss.org/browse/FORGE-2072?page=com.atlassian.jira.plugin... ]
Daniel Cunha (soro) updated FORGE-2072:
---------------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
> Setting servletVersion to 3.1 generate as many <error-page> as entity scaffolds
> -------------------------------------------------------------------------------
>
> Key: FORGE-2072
> URL: https://issues.jboss.org/browse/FORGE-2072
> Project: Forge
> Issue Type: Bug
> Components: Java EE
> Affects Versions: 2.12.0.Final
> Reporter: Antonio Goncalves
> Assignee: Daniel Cunha (soro)
> Fix For: 2.x Future
>
>
> Take the following scripts. It creates a project, sets up servlet version to 3.1, generates two entities and scaffolds them.
> {code}
> project-new --named testwebxml
> servlet-setup --servletVersion 3.1
> jpa-new-entity --named Category ;
> jpa-new-field --named name --length 100 ;
> scaffold-generate --webRoot /admin --targets org.testwebxml.model.Category
> jpa-new-entity --named Publisher ;
> jpa-new-field --named name --length 30 ;
> scaffold-generate --webRoot /admin --targets org.testwebxml.model.Publisher
> {code}
> We end up with a {{web.xml}} file that has the {{<error-page>}} duplicated. In fact, Forge will duplicate this block each time we scaffold an entity.
> {code}
> <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
> <web-app xmlns="http://xmlns.jcp.org/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" version="3.1" xsi:schemaLocation="http://xmlns.jcp.org/xml/ns/javaee http://xmlns.jcp.org/xml/ns/javaee/web-app_3_1.xsd">
> <display-name>module07</display-name>
> <session-config>
> <session-timeout>30</session-timeout>
> </session-config>
> <mime-mapping>
> <extension>ico</extension>
> <mime-type>image/x-icon</mime-type>
> </mime-mapping>
> <error-page>
> <error-code>404</error-code>
> <location>/faces/error.xhtml</location>
> </error-page>
> <error-page>
> <error-code>500</error-code>
> <location>/faces/error.xhtml</location>
> </error-page>
> <context-param>
> <param-name>javax.faces.DATETIMECONVERTER_DEFAULT_TIMEZONE_IS_SYSTEM_TIMEZONE</param-name>
> <param-value>true</param-value>
> </context-param>
> <error-page>
> <error-code>404</error-code>
> <location>/faces/error.xhtml</location>
> </error-page>
> <error-page>
> <error-code>500</error-code>
> <location>/faces/error.xhtml</location>
> </error-page>
> </web-app>
> {code}
> If you don't setup the servlet to 3.1 but leave the default (3.0) then it works fine, the {{<error-page>}} block is not duplicated
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 4 months
[JBoss JIRA] (FORGE-2072) Setting servletVersion to 3.1 generate as many <error-page> as entity scaffolds
by Daniel Cunha (soro) (JIRA)
[ https://issues.jboss.org/browse/FORGE-2072?page=com.atlassian.jira.plugin... ]
Daniel Cunha (soro) updated FORGE-2072:
---------------------------------------
Status: Pull Request Sent (was: Open)
Git Pull Request: https://github.com/forge/core/pull/526
> Setting servletVersion to 3.1 generate as many <error-page> as entity scaffolds
> -------------------------------------------------------------------------------
>
> Key: FORGE-2072
> URL: https://issues.jboss.org/browse/FORGE-2072
> Project: Forge
> Issue Type: Bug
> Components: Java EE
> Affects Versions: 2.12.0.Final
> Reporter: Antonio Goncalves
> Assignee: Daniel Cunha (soro)
> Fix For: 2.x Future
>
>
> Take the following scripts. It creates a project, sets up servlet version to 3.1, generates two entities and scaffolds them.
> {code}
> project-new --named testwebxml
> servlet-setup --servletVersion 3.1
> jpa-new-entity --named Category ;
> jpa-new-field --named name --length 100 ;
> scaffold-generate --webRoot /admin --targets org.testwebxml.model.Category
> jpa-new-entity --named Publisher ;
> jpa-new-field --named name --length 30 ;
> scaffold-generate --webRoot /admin --targets org.testwebxml.model.Publisher
> {code}
> We end up with a {{web.xml}} file that has the {{<error-page>}} duplicated. In fact, Forge will duplicate this block each time we scaffold an entity.
> {code}
> <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
> <web-app xmlns="http://xmlns.jcp.org/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" version="3.1" xsi:schemaLocation="http://xmlns.jcp.org/xml/ns/javaee http://xmlns.jcp.org/xml/ns/javaee/web-app_3_1.xsd">
> <display-name>module07</display-name>
> <session-config>
> <session-timeout>30</session-timeout>
> </session-config>
> <mime-mapping>
> <extension>ico</extension>
> <mime-type>image/x-icon</mime-type>
> </mime-mapping>
> <error-page>
> <error-code>404</error-code>
> <location>/faces/error.xhtml</location>
> </error-page>
> <error-page>
> <error-code>500</error-code>
> <location>/faces/error.xhtml</location>
> </error-page>
> <context-param>
> <param-name>javax.faces.DATETIMECONVERTER_DEFAULT_TIMEZONE_IS_SYSTEM_TIMEZONE</param-name>
> <param-value>true</param-value>
> </context-param>
> <error-page>
> <error-code>404</error-code>
> <location>/faces/error.xhtml</location>
> </error-page>
> <error-page>
> <error-code>500</error-code>
> <location>/faces/error.xhtml</location>
> </error-page>
> </web-app>
> {code}
> If you don't setup the servlet to 3.1 but leave the default (3.0) then it works fine, the {{<error-page>}} block is not duplicated
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 4 months
[JBoss JIRA] (FORGE-2072) Setting servletVersion to 3.1 generate as many <error-page> as entity scaffolds
by Daniel Cunha (soro) (JIRA)
[ https://issues.jboss.org/browse/FORGE-2072?page=com.atlassian.jira.plugin... ]
Daniel Cunha (soro) reassigned FORGE-2072:
------------------------------------------
Assignee: Daniel Cunha (soro)
> Setting servletVersion to 3.1 generate as many <error-page> as entity scaffolds
> -------------------------------------------------------------------------------
>
> Key: FORGE-2072
> URL: https://issues.jboss.org/browse/FORGE-2072
> Project: Forge
> Issue Type: Bug
> Components: Java EE
> Affects Versions: 2.12.0.Final
> Reporter: Antonio Goncalves
> Assignee: Daniel Cunha (soro)
> Fix For: 2.x Future
>
>
> Take the following scripts. It creates a project, sets up servlet version to 3.1, generates two entities and scaffolds them.
> {code}
> project-new --named testwebxml
> servlet-setup --servletVersion 3.1
> jpa-new-entity --named Category ;
> jpa-new-field --named name --length 100 ;
> scaffold-generate --webRoot /admin --targets org.testwebxml.model.Category
> jpa-new-entity --named Publisher ;
> jpa-new-field --named name --length 30 ;
> scaffold-generate --webRoot /admin --targets org.testwebxml.model.Publisher
> {code}
> We end up with a {{web.xml}} file that has the {{<error-page>}} duplicated. In fact, Forge will duplicate this block each time we scaffold an entity.
> {code}
> <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
> <web-app xmlns="http://xmlns.jcp.org/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" version="3.1" xsi:schemaLocation="http://xmlns.jcp.org/xml/ns/javaee http://xmlns.jcp.org/xml/ns/javaee/web-app_3_1.xsd">
> <display-name>module07</display-name>
> <session-config>
> <session-timeout>30</session-timeout>
> </session-config>
> <mime-mapping>
> <extension>ico</extension>
> <mime-type>image/x-icon</mime-type>
> </mime-mapping>
> <error-page>
> <error-code>404</error-code>
> <location>/faces/error.xhtml</location>
> </error-page>
> <error-page>
> <error-code>500</error-code>
> <location>/faces/error.xhtml</location>
> </error-page>
> <context-param>
> <param-name>javax.faces.DATETIMECONVERTER_DEFAULT_TIMEZONE_IS_SYSTEM_TIMEZONE</param-name>
> <param-value>true</param-value>
> </context-param>
> <error-page>
> <error-code>404</error-code>
> <location>/faces/error.xhtml</location>
> </error-page>
> <error-page>
> <error-code>500</error-code>
> <location>/faces/error.xhtml</location>
> </error-page>
> </web-app>
> {code}
> If you don't setup the servlet to 3.1 but leave the default (3.0) then it works fine, the {{<error-page>}} block is not duplicated
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 4 months
[JBoss JIRA] (FORGE-2175) Some UI components can not be seen when there is too many of them
by Jerome B (JIRA)
[ https://issues.jboss.org/browse/FORGE-2175?page=com.atlassian.jira.plugin... ]
Jerome B updated FORGE-2175:
----------------------------
Summary: Some UI components can not be seen when there is too many of them (was: Some UI components can not be seen)
> Some UI components can not be seen when there is too many of them
> -----------------------------------------------------------------
>
> Key: FORGE-2175
> URL: https://issues.jboss.org/browse/FORGE-2175
> Project: Forge
> Issue Type: Enhancement
> Components: UI - Eclipse
> Affects Versions: 2.12.1.Final
> Environment: linux
> JDS 8.0.0GA, graphic mode, developping a custom addon
> Reporter: Jerome B
>
> I presume this depends of the vertical estate of the screen used but on my laptop with 16/10 display, if I want to display a list of 10 couples of inputs (a directory picker and a UISelectOne<String>) then only 8 of them are displayed.
> The container should be scrollable.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 4 months