December 2014 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-2175) Some UI components can not be seen

by Jerome B (JIRA)

[ https://issues.jboss.org/browse/FORGE-2175?page=com.atlassian.jira.plugin... ] Jerome B updated FORGE-2175: ---------------------------- Environment: linux JDS 8.0.0GA, graphic mode, developping a custom addon was: linux JDS 8.0.0GA, graphic mode > Some UI components can not be seen > ---------------------------------- > > 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

1
0
0 / 0

[JBoss JIRA] (FORGE-2175) Some UI components can not be seen

by Jerome B (JIRA)

[ https://issues.jboss.org/browse/FORGE-2175?page=com.atlassian.jira.plugin... ] Jerome B updated FORGE-2175: ---------------------------- Description: 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. was: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. > Some UI components can not be seen > ---------------------------------- > > 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 > 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

1
0
0 / 0

[JBoss JIRA] (FORGE-2175) Some UI components can not be seen

by Jerome B (JIRA)

Jerome B created FORGE-2175: ------------------------------- Summary: Some UI components can not be seen 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 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. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2171) UIInput<Boolean> doesn't work when user try to set value

by Daniel Cunha (soro) (JIRA)

[ https://issues.jboss.org/browse/FORGE-2171?page=com.atlassian.jira.plugin... ] Daniel Cunha (soro) commented on FORGE-2171: -------------------------------------------- work fine with: --option=true/false > UIInput<Boolean> doesn't work when user try to set value > -------------------------------------------------------- > > Key: FORGE-2171 > URL: https://issues.jboss.org/browse/FORGE-2171 > Project: Forge > Issue Type: Bug > Components: UI - API > Affects Versions: 2.13.1.Final > Reporter: Daniel Cunha (soro) > Assignee: Daniel Cunha (soro) > > When I run it: > arquillian-create-test --targets org.teste.model.Soro > Result: > http://pastebin.com/EJ2DwcE6 > When I run it: > arquillian-create-test --targets org.teste.model.Soro --enableJPA false > Result: > http://pastebin.com/B1MfijwC > --enableJPA has "false" as default value, but when I try to set value, Forge always set the value as "true". -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2171) UIInput<Boolean> doesn't work when user try to set value

by Daniel Cunha (soro) (JIRA)

[ https://issues.jboss.org/browse/FORGE-2171?page=com.atlassian.jira.plugin... ] Daniel Cunha (soro) closed FORGE-2171. -------------------------------------- Resolution: Done > UIInput<Boolean> doesn't work when user try to set value > -------------------------------------------------------- > > Key: FORGE-2171 > URL: https://issues.jboss.org/browse/FORGE-2171 > Project: Forge > Issue Type: Bug > Components: UI - API > Affects Versions: 2.13.1.Final > Reporter: Daniel Cunha (soro) > Assignee: Daniel Cunha (soro) > > When I run it: > arquillian-create-test --targets org.teste.model.Soro > Result: > http://pastebin.com/EJ2DwcE6 > When I run it: > arquillian-create-test --targets org.teste.model.Soro --enableJPA false > Result: > http://pastebin.com/B1MfijwC > --enableJPA has "false" as default value, but when I try to set value, Forge always set the value as "true". -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2171) UIInput<Boolean> doesn't work when user try to set value

by Daniel Cunha (soro) (JIRA)

[ https://issues.jboss.org/browse/FORGE-2171?page=com.atlassian.jira.plugin... ] Daniel Cunha (soro) reassigned FORGE-2171: ------------------------------------------ Assignee: Daniel Cunha (soro) > UIInput<Boolean> doesn't work when user try to set value > -------------------------------------------------------- > > Key: FORGE-2171 > URL: https://issues.jboss.org/browse/FORGE-2171 > Project: Forge > Issue Type: Bug > Components: UI - API > Affects Versions: 2.13.1.Final > Reporter: Daniel Cunha (soro) > Assignee: Daniel Cunha (soro) > > When I run it: > arquillian-create-test --targets org.teste.model.Soro > Result: > http://pastebin.com/EJ2DwcE6 > When I run it: > arquillian-create-test --targets org.teste.model.Soro --enableJPA false > Result: > http://pastebin.com/B1MfijwC > --enableJPA has "false" as default value, but when I try to set value, Forge always set the value as "true". -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2174) The first experience for a new contributor should be easier

by Jason Porter (JIRA)

Jason Porter created FORGE-2174: ----------------------------------- Summary: The first experience for a new contributor should be easier Key: FORGE-2174 URL: https://issues.jboss.org/browse/FORGE-2174 Project: Forge Issue Type: Quality Risk Components: Documentation Reporter: Jason Porter First experience: 1. Go to forge.jboss.org 2. Scroll down to "Get Involved" 3. Click on "Improve Forge Code" 4. Land on GitHub 5. Uh, um, what now guys? The current workflow seems to expect people to meta: Know how to use git 1. know how to get code 2. know which workflow to follow 3. know which repository of the 54 current repositories in the organization to use. Next, assuming I'm still with you, and found the repository I want to contribute to, there may or may not be a CONTRIBUTING file in the repo. In the case of core, if I click the CONTRIBUTING file, it tells me to look at the README file if I want to contribute to Forge 2. Why wouldn't I want to contribute to Forge 2? What's Forge 1? Why should I contribute there? I'm so confused. After skimming the README file on Core, it doesn't have any information about contributing that I would expect. I see how to create tests, how to create an addon, etc. All good info, but you're still assuming I understand what I'm doing, AND that I'm writing an addon. If I'm not doing that, I'm left out in the cold. All of this sort of info should be on the main site. If I'm building an addon, and I click on the "Build an Addon" link I'm sent to http://forge.jboss.org/document/develop-an-addon, which is great (It's just the README from the repo it looks like, but it gives me info I need to know), aside from the small text. I would expect the "Improve Forge Code" to go to another page on the Forge website with information about how to down the code, walk me through the workflow, and basically get me all setup to contribute. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2173) Furnace maven plugin could support command execution

by Samuel Tauil (JIRA)

Samuel Tauil created FORGE-2173: ----------------------------------- Summary: Furnace maven plugin could support command execution Key: FORGE-2173 URL: https://issues.jboss.org/browse/FORGE-2173 Project: Forge Issue Type: Feature Request Components: Build Tools - Maven Reporter: Samuel Tauil Priority: Optional Command execution within the furnace plugin would be interesting to have so another plugin related to a specific addon could be executed after too. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2073) File input should be relative to current directory, not ${user.dir}

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-2073?page=com.atlassian.jira.plugin... ] Lincoln Baxter III closed FORGE-2073. ------------------------------------- Fix Version/s: 2.13.1.Final Resolution: Done This issue is resolved in FORGE-2170 - please retest Windup and re-open the issue with a test case if the problem persists. Otherwise, re-open the issue in windup if the issue cannot be reproduced in a test case or proven to be a forge issue. > File input should be relative to current directory, not ${user.dir} > ------------------------------------------------------------------- > > Key: FORGE-2073 > URL: https://issues.jboss.org/browse/FORGE-2073 > Project: Forge > Issue Type: Enhancement > Reporter: Ondrej Zizka > Assignee: George Gastaldi > Fix For: 2.13.1.Final > > > Steps to reproduce: > {code} > cd myDir > touch foo.ear > forge > cd .. > windup-migrate-app myDir/foo.ear > ***ERROR*** Input path does not exist > windup-migrate-app foo.ear > (this works...) > {code} > This is IMO illogical. The relative path should be relative to the directory of the shell. Currently it is relative to the directory where Forge was started. > This i -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2073) File input should be relative to current directory, not ${user.dir}

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-2073?page=com.atlassian.jira.plugin... ] Lincoln Baxter III reassigned FORGE-2073: ----------------------------------------- Assignee: George Gastaldi > File input should be relative to current directory, not ${user.dir} > ------------------------------------------------------------------- > > Key: FORGE-2073 > URL: https://issues.jboss.org/browse/FORGE-2073 > Project: Forge > Issue Type: Enhancement > Reporter: Ondrej Zizka > Assignee: George Gastaldi > > Steps to reproduce: > {code} > cd myDir > touch foo.ear > forge > cd .. > windup-migrate-app myDir/foo.ear > ***ERROR*** Input path does not exist > windup-migrate-app foo.ear > (this works...) > {code} > This is IMO illogical. The relative path should be relative to the directory of the shell. Currently it is relative to the directory where Forge was started. > This i -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 4 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues December 2014