December 2013 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-1375) Need a `touch` command

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-1375?page=com.atlassian.jira.plugin... ] Lincoln Baxter III closed FORGE-1375. ------------------------------------- Assignee: Lincoln Baxter III Fix Version/s: 2.0.0.Beta4 (was: 2.x Future) Resolution: Done > Need a `touch` command > ---------------------- > > Key: FORGE-1375 > URL: https://issues.jboss.org/browse/FORGE-1375 > Project: Forge > Issue Type: Sub-task > Components: UI - Shell > Affects Versions: 2.0.0.Beta3 > Reporter: Lincoln Baxter III > Assignee: Lincoln Baxter III > Fix For: 2.0.0.Beta4 > > > [Desktop]$ ls > [Desktop]$ touch demo > [Desktop]$ > [Desktop]$ ls > demo > [Desktop]$ -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1365) RmCommand does not warn or inform the user when it can not delete a folder

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-1365?page=com.atlassian.jira.plugin... ] Lincoln Baxter III closed FORGE-1365. ------------------------------------- Assignee: Lincoln Baxter III Fix Version/s: 2.0.0.Beta4 (was: 2.x Future) Resolution: Done > RmCommand does not warn or inform the user when it can not delete a folder > -------------------------------------------------------------------------- > > Key: FORGE-1365 > URL: https://issues.jboss.org/browse/FORGE-1365 > Project: Forge > Issue Type: Bug > Components: UI - Shell > Affects Versions: 2.0.0.Beta3 > Reporter: Lincoln Baxter III > Assignee: Lincoln Baxter III > Fix For: 2.0.0.Beta4 > > > {code} > [Desktop]$ rm demo/ > [Desktop]$ > [Desktop]$ ls > demo > [Desktop]$ rm demo/ > [Desktop]$ ls > demo > [Desktop]$ rm -rf demo/ > [Desktop]$ ls > [Desktop]$ > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1372) WizardCommandController must not cache initialized commands

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1372?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-1372. ---------------------------------- Fix Version/s: 2.0.0.Beta4 (was: 2.x Future) Resolution: Done Fix implemented by Comparing inputs before evicting from the flow list > WizardCommandController must not cache initialized commands > ----------------------------------------------------------- > > Key: FORGE-1372 > URL: https://issues.jboss.org/browse/FORGE-1372 > Project: Forge > Issue Type: Bug > Components: UI - API, UI - Eclipse > Affects Versions: 2.0.0.Beta3 > Reporter: George Gastaldi > Assignee: George Gastaldi > Fix For: 2.0.0.Beta4 > > > Some Wizards call UIBuilder.add() in the initializeUI method with a specific condition. > eg: > {code:java|title=JPASetupConnectionStep} > @Override > public void initializeUI(UIBuilder builder) throws Exception > { > UIContext uiContext = builder.getUIContext(); > PersistenceContainer pc = (PersistenceContainer) uiContext.getAttribute(PersistenceContainer.class); > initDBType(uiContext); > initDatasourceName(uiContext); > initPersistenceUnitName(builder); > builder.add(dbType); > if (pc.isJTASupported()) > { > builder.add(dataSourceName); > } > else > { > builder.add(jdbcDriver).add(databaseURL).add(username).add(password); > } > } > {code} > Therefore, the WizardCommandController shouldn't cache initialized UICommands, since the added fields may differ. > This impacts in the navigation UX, in the fact that already typed information is lost when the previous button is called. One solution would be to re-initialize a different command, and compare if the inputs provided differ from the original initialization. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1375) Need a `touch` command

by Lincoln Baxter III (JIRA)

Lincoln Baxter III created FORGE-1375: ----------------------------------------- Summary: Need a `touch` command Key: FORGE-1375 URL: https://issues.jboss.org/browse/FORGE-1375 Project: Forge Issue Type: Sub-task Components: UI - Shell Affects Versions: 2.0.0.Beta3 Reporter: Lincoln Baxter III Fix For: 2.x Future [Desktop]$ ls [Desktop]$ touch demo [Desktop]$ [Desktop]$ ls demo [Desktop]$ -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1274) Move/Encapsulate Aesh as implementation detail until its APIs better support Proxying

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-1274?page=com.atlassian.jira.plugin... ] Lincoln Baxter III closed FORGE-1274. ------------------------------------- Assignee: Lincoln Baxter III Fix Version/s: 2.0.0.Beta4 (was: 2.x Future) Resolution: Done Implemented in UI API. Also, Aesh no longer defines the types that caused proxying issues. > Move/Encapsulate Aesh as implementation detail until its APIs better support Proxying > ------------------------------------------------------------------------------------- > > Key: FORGE-1274 > URL: https://issues.jboss.org/browse/FORGE-1274 > Project: Forge > Issue Type: Feature Request > Components: UI - Eclipse, UI - Shell > Affects Versions: 2.0.0.Alpha13 > Reporter: Lincoln Baxter III > Assignee: Lincoln Baxter III > Fix For: 2.0.0.Beta4 > > > Because the Aesh APIs do not support proxying particularly well, we need to encapsulate them to prevent Proxy errors from causing failures in external consumers of the Shell. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1374) Need an `mkdir` command

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-1374?page=com.atlassian.jira.plugin... ] Lincoln Baxter III closed FORGE-1374. ------------------------------------- Assignee: Lincoln Baxter III Fix Version/s: 2.0.0.Beta4 (was: 2.x Future) Resolution: Done > Need an `mkdir` command > ----------------------- > > Key: FORGE-1374 > URL: https://issues.jboss.org/browse/FORGE-1374 > Project: Forge > Issue Type: Sub-task > Components: UI - Shell > Affects Versions: 2.0.0.Beta3 > Reporter: Lincoln Baxter III > Assignee: Lincoln Baxter III > Fix For: 2.0.0.Beta4 > > > {code} > [Desktop]$ ls > [Desktop]$ mkdir demo > [Desktop]$ > [Desktop]$ ls > demo > [Desktop]$ > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1374) Need an `mkdir` command

by Lincoln Baxter III (JIRA)

Lincoln Baxter III created FORGE-1374: ----------------------------------------- Summary: Need an `mkdir` command Key: FORGE-1374 URL: https://issues.jboss.org/browse/FORGE-1374 Project: Forge Issue Type: Sub-task Components: UI - Shell Affects Versions: 2.0.0.Beta3 Reporter: Lincoln Baxter III {code} [Desktop]$ ls [Desktop]$ mkdir demo [Desktop]$ [Desktop]$ ls demo [Desktop]$ {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1373) Native Aesh commands do not properly receive/resolve file paths

by Lincoln Baxter III (JIRA)

Lincoln Baxter III created FORGE-1373: ----------------------------------------- Summary: Native Aesh commands do not properly receive/resolve file paths Key: FORGE-1373 URL: https://issues.jboss.org/browse/FORGE-1373 Project: Forge Issue Type: Sub-task Components: UI - Shell Affects Versions: 2.0.0.Beta3 Reporter: Lincoln Baxter III Fix For: 2.0.0.Beta4 {code} [Desktop]$ cd ~ [lb3]$ cd projects/ [projects]$ less .DS_Store jboss/ lincoln_javascript_code_style.xml runtime-EclipseApplication(1)/ talks/ jboss-eclipse-formatting-rules.xml lb3_eclipse_preferences.epf ocpsoft/ runtime-EclipseApplication/ [projects]$ ls .DS_Store jboss/ lincoln_javascript_code_style.xml runtime-EclipseApplication(1)/ talks/ jboss-eclipse-formatting-rules.xml lb3_eclipse_preferences.epf ocpsoft/ runtime-EclipseApplication/ [projects]$ less lincoln_javascript_code_style.xml /Users/lb3/Desktop/lincoln_javascript_code_style.xml: No such file or directory {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1372) WizardCommandController must not cache initialized commands

by George Gastaldi (JIRA)

George Gastaldi created FORGE-1372: -------------------------------------- Summary: WizardCommandController must not cache initialized commands Key: FORGE-1372 URL: https://issues.jboss.org/browse/FORGE-1372 Project: Forge Issue Type: Bug Components: UI - API, UI - Eclipse Affects Versions: 2.0.0.Beta3 Reporter: George Gastaldi Assignee: George Gastaldi Fix For: 2.x Future Some Wizards call UIBuilder.add() in the initializeUI method with a specific condition. eg: {code:java|title=JPASetupConnectionStep} @Override public void initializeUI(UIBuilder builder) throws Exception { UIContext uiContext = builder.getUIContext(); PersistenceContainer pc = (PersistenceContainer) uiContext.getAttribute(PersistenceContainer.class); initDBType(uiContext); initDatasourceName(uiContext); initPersistenceUnitName(builder); builder.add(dbType); if (pc.isJTASupported()) { builder.add(dataSourceName); } else { builder.add(jdbcDriver).add(databaseURL).add(username).add(password); } } {code} Therefore, the WizardCommandController shouldn't cache initialized UICommands, since the added fields may differ. This impacts in the navigation UX, in the fact that already typed information is lost when the previous button is called. One solution would be to re-initialize a different command, and compare if the inputs provided differ from the original initialization. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1347) Subflow order is incorrect when changes are made in the fields of the currently displayed command

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1347?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-1347. ---------------------------------- Assignee: George Gastaldi Fix Version/s: 2.0.0.Beta4 Resolution: Done Resolved in the WizardCommandController implementation. > Subflow order is incorrect when changes are made in the fields of the currently displayed command > ------------------------------------------------------------------------------------------------- > > Key: FORGE-1347 > URL: https://issues.jboss.org/browse/FORGE-1347 > Project: Forge > Issue Type: Bug > Components: UI - Eclipse > Affects Versions: 2.0.0.Beta3 > Reporter: Vineet Reynolds > Assignee: George Gastaldi > Priority: Critical > Fix For: 2.0.0.Beta4 > > > Given a subflow when a change is made in any of the displayed commands/wizard steps, the display order of the individual elements in the subflow changes. > For example, when a subflow containing {{[JPASetupWizard, CDISetupWizard, EJBSetupWizard, ServletSetupWizard, FacesSetupWizard, ExecuteSetupCommand]}} is displayed, if the values in the CDI Setup wizard are modified, then the EJB Setup Wizard is not displayed immediately after the CDI wizard. It will be displayed later, and the Servlet Setup Wizard is chosen to be displayed in it's place. > This behavior is cumulative - if values in other pages are also modified, then multiple subflow components will be displayed out of order and the original subflow order is never adhered to. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 6 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues December 2013