May 2014 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-1836) Refactor towards JDK 1.7 enhancements

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1836?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-1836. ---------------------------------- Fix Version/s: 2.6.1.Final (was: 2.x Future) Resolution: Done > Refactor towards JDK 1.7 enhancements > ------------------------------------- > > Key: FORGE-1836 > URL: https://issues.jboss.org/browse/FORGE-1836 > Project: Forge > Issue Type: Task > Affects Versions: 2.5.0.Final > Reporter: Daniel Cunha > Assignee: Daniel Cunha > Priority: Optional > Fix For: 2.6.1.Final > > > It has class that implements AutoCloseable, but we're still using finally to close streams and etc. > We can use (eg): > try (stream) { > } > and kill the finally block. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1857) Upgrade to Aesh 0.55

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1857?page=com.atlassian.jira.plugin... ] George Gastaldi updated FORGE-1857: ----------------------------------- Status: Closed (was: Pull Request Sent) Fix Version/s: 2.6.1.Final (was: 2.x Future) Resolution: Done Thanks! > Upgrade to Aesh 0.55 > -------------------- > > Key: FORGE-1857 > URL: https://issues.jboss.org/browse/FORGE-1857 > Project: Forge > Issue Type: Component Upgrade > Components: UI - Shell > Affects Versions: 2.6.0.Final > Reporter: George Gastaldi > Assignee: Daniel Cunha > Fix For: 2.6.1.Final > > -- This message was sent by Atlassian JIRA (v6.2.3#6260)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1857) Upgrade to Aesh 0.55

by Daniel Cunha (JIRA)

[ https://issues.jboss.org/browse/FORGE-1857?page=com.atlassian.jira.plugin... ] Daniel Cunha reassigned FORGE-1857: ----------------------------------- Assignee: Daniel Cunha > Upgrade to Aesh 0.55 > -------------------- > > Key: FORGE-1857 > URL: https://issues.jboss.org/browse/FORGE-1857 > Project: Forge > Issue Type: Component Upgrade > Components: UI - Shell > Affects Versions: 2.6.0.Final > Reporter: George Gastaldi > Assignee: Daniel Cunha > Fix For: 2.x Future > > -- This message was sent by Atlassian JIRA (v6.2.3#6260)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1857) Upgrade to Aesh 0.55

by Daniel Cunha (JIRA)

[ https://issues.jboss.org/browse/FORGE-1857?page=com.atlassian.jira.plugin... ] Daniel Cunha updated FORGE-1857: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/forge/core/pull/463 > Upgrade to Aesh 0.55 > -------------------- > > Key: FORGE-1857 > URL: https://issues.jboss.org/browse/FORGE-1857 > Project: Forge > Issue Type: Component Upgrade > Components: UI - Shell > Affects Versions: 2.6.0.Final > Reporter: George Gastaldi > Assignee: Daniel Cunha > Fix For: 2.x Future > > -- This message was sent by Atlassian JIRA (v6.2.3#6260)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1550) Set up a CI build server that is publicly visible and works.

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1550?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-1550. ---------------------------------- Resolution: Done Inspite of having a Cloudbees instance available (http://forge.ci.cloudbees.com/), we are using TeamCity > Set up a CI build server that is publicly visible and works. > ------------------------------------------------------------ > > Key: FORGE-1550 > URL: https://issues.jboss.org/browse/FORGE-1550 > Project: Forge > Issue Type: Task > Reporter: Lincoln Baxter III > Priority: Critical > -- This message was sent by Atlassian JIRA (v6.2.3#6260)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1857) Upgrade to Aesh 0.55

by George Gastaldi (JIRA)

George Gastaldi created FORGE-1857: -------------------------------------- Summary: Upgrade to Aesh 0.55 Key: FORGE-1857 URL: https://issues.jboss.org/browse/FORGE-1857 Project: Forge Issue Type: Component Upgrade Components: UI - Shell Affects Versions: 2.6.0.Final Reporter: George Gastaldi Fix For: 2.x Future -- This message was sent by Atlassian JIRA (v6.2.3#6260)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1787) When scaffolding with --webRoot parameter, pageTemplate.xhtml and search.xhtml are not right

by Antonio Goncalves (JIRA)

[ https://issues.jboss.org/browse/FORGE-1787?page=com.atlassian.jira.plugin... ] Antonio Goncalves commented on FORGE-1787: ------------------------------------------ Perfect !!! > When scaffolding with --webRoot parameter, pageTemplate.xhtml and search.xhtml are not right > -------------------------------------------------------------------------------------------- > > Key: FORGE-1787 > URL: https://issues.jboss.org/browse/FORGE-1787 > Project: Forge > Issue Type: Bug > Components: Scaffold > Affects Versions: 2.5.0.Final > Reporter: Antonio Goncalves > Assignee: Ivan St. Ivanov > Priority: Blocker > Fix For: 2.6.1.Final > > > When scaffolding a JSF application, without using a {{--webRoot}} parameter, the navigation in the {{pageTemplate.xhtml}} works as expected : > {code} > scaffold-setup ; > scaffold-generate --targets org.agoncal.training.javaee6adv.model.Author ; > scaffold-generate --targets org.agoncal.training.javaee6adv.model.CD ; > {code} > The template navigation looks like : > {code} > <ul> > <li> > <h:link outcome="/CD/search" value="CD"/> > </li> > <li> > <h:link outcome="/author/search" value="Author"/> > </li> > </ul> > {code} > But if I specify the {{--webRoot}} parameter, then the navigation does not work as there is a {{/}} missing : > {code} > scaffold-setup ; > scaffold-generate --webRoot admin --targets org.agoncal.training.javaee6adv.model.Author ; > scaffold-generate --webRoot admin --targets org.agoncal.training.javaee6adv.model.CD ; > {code} > The template : > {code} > <ul> > <li> > <h:link outcome="admin/CD/search" value="CD"/> > </li> > <li> > <h:link outcome="admin/author/search" value="Author"/> > </li> > </ul> > {code} > The correct navigation would be : > {code} > <ul> > <li> > <h:link outcome="/admin/CD/search" value="CD"/> > </li> > <li> > <h:link outcome="/admin/author/search" value="Author"/> > </li> > </ul> > {code} > The only way to make it work is to add a {{/}} to the {{webroot}}, which is not very intuitive : > {code} > scaffold-setup ; > scaffold-generate --webRoot /admin --targets org.agoncal.training.javaee6adv.model.Author ; > scaffold-generate --webRoot /admin --targets org.agoncal.training.javaee6adv.model.CD ; > {code} > But this trick doesn't work for the {{search.xhtml}} page. The generated code is : > {code} > <h:link outcome="/genre/view"> > <f:param name="id" value="#{_item.id}"/> > <h:outputText id="itemName" value="#{_item.name}"/> > </h:link> > {code} > The {{outcome}} is not right, and should contain a {{/admin}} > {code} > <h:link outcome="/admin/genre/view"> > <f:param name="id" value="#{_item.id}"/> > <h:outputText id="itemName" value="#{_item.name}"/> > </h:link> > {code} -- This message was sent by Atlassian JIRA (v6.2.3#6260)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1848) IDE loses defaultValue on dependent field update

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1848?page=com.atlassian.jira.plugin... ] George Gastaldi updated FORGE-1848: ----------------------------------- Summary: IDE loses defaultValue on dependent field update (was: IDE loose defaultValue on dependent field update) > IDE loses defaultValue on dependent field update > ------------------------------------------------ > > Key: FORGE-1848 > URL: https://issues.jboss.org/browse/FORGE-1848 > Project: Forge > Issue Type: Bug > Components: UI - Eclipse > Reporter: Aslak Knutsen > Assignee: Lincoln Baxter III > Fix For: 2.6.0.Final > > > Setup: > 2 DropDown lists, where the second DropDown's value depend on the value of the first DropDown. > Steps: > 1. Select a value from DropDown 1 > 2. DropDown 2 now has the defaultValue selected > 3. Select a new value from DropDown 1 > Step 4 - Expected: > DropDown 2 should now have the new defaultValue selected > Step 4 - Behavior: > DropDown 2's valueChoices are updated, but no defaultSelection is done > Example command: > https://github.com/aslakknutsen/plugin-arquillian/blob/8e3dfd162126cada80... -- This message was sent by Atlassian JIRA (v6.2.3#6260)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1848) IDE loose defaultValue on dependent field update

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-1848?page=com.atlassian.jira.plugin... ] Lincoln Baxter III commented on FORGE-1848: ------------------------------------------- I re-opened this issue, but I am unable to reproduce this. I installed the arquillian addon, and went through all of the steps, including selecting test framework and container adapter, and the version list population worked fine. > IDE loose defaultValue on dependent field update > ------------------------------------------------ > > Key: FORGE-1848 > URL: https://issues.jboss.org/browse/FORGE-1848 > Project: Forge > Issue Type: Bug > Components: UI - Eclipse > Reporter: Aslak Knutsen > Assignee: Lincoln Baxter III > Fix For: 2.6.0.Final > > > Setup: > 2 DropDown lists, where the second DropDown's value depend on the value of the first DropDown. > Steps: > 1. Select a value from DropDown 1 > 2. DropDown 2 now has the defaultValue selected > 3. Select a new value from DropDown 1 > Step 4 - Expected: > DropDown 2 should now have the new defaultValue selected > Step 4 - Behavior: > DropDown 2's valueChoices are updated, but no defaultSelection is done > Example command: > https://github.com/aslakknutsen/plugin-arquillian/blob/8e3dfd162126cada80... -- This message was sent by Atlassian JIRA (v6.2.3#6260)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1848) IDE loose defaultValue on dependent field update

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-1848?page=com.atlassian.jira.plugin... ] Lincoln Baxter III reopened FORGE-1848: --------------------------------------- > IDE loose defaultValue on dependent field update > ------------------------------------------------ > > Key: FORGE-1848 > URL: https://issues.jboss.org/browse/FORGE-1848 > Project: Forge > Issue Type: Bug > Components: UI - Eclipse > Reporter: Aslak Knutsen > Assignee: Lincoln Baxter III > Fix For: 2.6.0.Final > > > Setup: > 2 DropDown lists, where the second DropDown's value depend on the value of the first DropDown. > Steps: > 1. Select a value from DropDown 1 > 2. DropDown 2 now has the defaultValue selected > 3. Select a new value from DropDown 1 > Step 4 - Expected: > DropDown 2 should now have the new defaultValue selected > Step 4 - Behavior: > DropDown 2's valueChoices are updated, but no defaultSelection is done > Example command: > https://github.com/aslakknutsen/plugin-arquillian/blob/8e3dfd162126cada80... -- This message was sent by Atlassian JIRA (v6.2.3#6260)

9 years, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues May 2014