July 2015 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-1355) Ensure website meets upstream requirements

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1355?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-1355. ---------------------------------- Assignee: George Gastaldi Resolution: Done > Ensure website meets upstream requirements > ------------------------------------------ > > Key: FORGE-1355 > URL: https://issues.jboss.org/browse/FORGE-1355 > Project: Forge > Issue Type: Sub-task > Components: Website > Affects Versions: 2.0.0.CR2 > Reporter: Lincoln Baxter III > Assignee: George Gastaldi > Fix For: 2.x Future > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGEPLUGINS-189) The as-setup command should give the version of the server

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGEPLUGINS-189?page=com.atlassian.jira.... ] George Gastaldi commented on FORGEPLUGINS-189: ---------------------------------------------- The provided PR in FORGE-1975 is now merged in master > The as-setup command should give the version of the server > ---------------------------------------------------------- > > Key: FORGEPLUGINS-189 > URL: https://issues.jboss.org/browse/FORGEPLUGINS-189 > Project: Forge Plugins/Addons > Issue Type: Enhancement > Components: JBoss AS Plugin > Reporter: Antonio Goncalves > Assignee: James Perkins > > The {{as-setup}} command has a {{server}} parameter. When pressing TAB the completion shows the app server with version : > {code} > $ as-setup --server > jbossas7 wildfly8 > {code} > But this is confusing because when you choose the appserver, you have the {{version}} parameter : > {code} > $ as-setup --server wildfly8 --version > 8.0.0.Alpha1 8.0.0.Alpha4 8.0.0.Final 8.1.0.Final 9.0.0.Beta1 > 8.0.0.Alpha2 8.0.0.Beta1 8.1.0.CR1 8.2.0.Final 9.0.0.Beta2 > 8.0.0.Alpha3 8.0.0.CR1 8.1.0.CR2 9.0.0.Alpha1 9.0.0.CR1 > {code} > For clarity the {{server}} parameter should only show the app server without version number : > {code} > $ as-setup --server > jbossas wildfly > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2339) Repeated values when auto-completing a UISelectMany component

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-2339?page=com.atlassian.jira.plugin... ] George Gastaldi commented on FORGE-2339: ---------------------------------------- This was still not resolved in Aesh 0.61 > Repeated values when auto-completing a UISelectMany component > ------------------------------------------------------------- > > Key: FORGE-2339 > URL: https://issues.jboss.org/browse/FORGE-2339 > Project: Forge > Issue Type: Bug > Components: UI - Shell > Affects Versions: 2.16.1.Final > Reporter: George Gastaldi > Fix For: 2.x Future > > > Having a command defined as: > {code:java} > import java.util.Arrays; > import javax.inject.Inject; > import org.jboss.forge.addon.ui.command.AbstractUICommand; > import org.jboss.forge.addon.ui.context.UIBuilder; > import org.jboss.forge.addon.ui.context.UIContext; > import org.jboss.forge.addon.ui.context.UIExecutionContext; > import org.jboss.forge.addon.ui.input.UISelectMany; > import org.jboss.forge.addon.ui.metadata.UICommandMetadata; > import org.jboss.forge.addon.ui.result.Result; > import org.jboss.forge.addon.ui.result.Results; > import org.jboss.forge.addon.ui.util.Metadata; > public class Comando extends AbstractUICommand { > @Inject > private UISelectMany<String> source; > @Override > public UICommandMetadata getMetadata(UIContext context) { > return Metadata.forCommand(Comando.class).name("comando"); > } > @Override > public void initializeUI(UIBuilder builder) throws Exception { > source.setValueChoices(Arrays.asList("Spring")).setDefaultValue( > Arrays.asList("Java")); > builder.add(source); > } > @Override > public Result execute(UIExecutionContext context) throws Exception { > return Results.success("Result: " + source.getValue()); > } > } > {code} > When running in the shell, type: > {code} > comando --source Spring > {code} > Keep pressing {{<TAB>}} and you should see Spring repeated over and over -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1266) Implement IgnoreEOF in Forge 2 Shell

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1266?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-1266. ---------------------------------- Fix Version/s: 2.17.1.Final (was: 2.x Future) Resolution: Done > Implement IgnoreEOF in Forge 2 Shell > ------------------------------------ > > Key: FORGE-1266 > URL: https://issues.jboss.org/browse/FORGE-1266 > Project: Forge > Issue Type: Feature Request > Components: UI - Shell > Affects Versions: 2.0.0.Alpha13, 2.7.0.Final > Reporter: Lincoln Baxter III > Assignee: George Gastaldi > Fix For: 2.17.1.Final > > > See current IGNOREEOF behavior in Forge 1 -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1975) Upgrade to Aesh 0.61

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1975?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-1975. ---------------------------------- Fix Version/s: 2.17.1.Final (was: 2.x Future) Resolution: Done Merged in https://github.com/forge/core/commit/8dbc065fa, thanks! > Upgrade to Aesh 0.61 > -------------------- > > Key: FORGE-1975 > URL: https://issues.jboss.org/browse/FORGE-1975 > Project: Forge > Issue Type: Component Upgrade > Components: UI - Shell > Affects Versions: 2.7.2.Final > Reporter: George Gastaldi > Assignee: Jeremie Lagarde > Fix For: 2.17.1.Final > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1975) Upgrade to Aesh 0.61

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1975?page=com.atlassian.jira.plugin... ] George Gastaldi commented on FORGE-1975: ---------------------------------------- Fixed. Had to add this to ShellImpl: {code:java} // This conflicts with the provided Man in ForgeCommandRegistry newSettings.enableMan(false); {code} > Upgrade to Aesh 0.61 > -------------------- > > Key: FORGE-1975 > URL: https://issues.jboss.org/browse/FORGE-1975 > Project: Forge > Issue Type: Component Upgrade > Components: UI - Shell > Affects Versions: 2.7.2.Final > Reporter: George Gastaldi > Assignee: Jeremie Lagarde > Fix For: 2.x Future > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1975) Upgrade to Aesh 0.61

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1975?page=com.atlassian.jira.plugin... ] George Gastaldi commented on FORGE-1975: ---------------------------------------- Some commands appear more than once when <TAB> is pressed. Eg: man, grep. Coincidentally, they are all Aesh commands. > Upgrade to Aesh 0.61 > -------------------- > > Key: FORGE-1975 > URL: https://issues.jboss.org/browse/FORGE-1975 > Project: Forge > Issue Type: Component Upgrade > Components: UI - Shell > Affects Versions: 2.7.2.Final > Reporter: George Gastaldi > Assignee: Jeremie Lagarde > Fix For: 2.x Future > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1975) Upgrade to Aesh 0.61

by George Gastaldi (JIRA)

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

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (FURNACE-63) PostStartup bug, or should be documented better

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FURNACE-63?page=com.atlassian.jira.plugin... ] George Gastaldi commented on FURNACE-63: ---------------------------------------- Yeah, I agree the name should be improved. We can consider that for Furnace 3.0 (or create AddonStarted as a subclass of PostStartup) . For the mean time, I changed the javadoc with the first sentence only. The @Local qualifier also explains abouy itself in its javadoc. > PostStartup bug, or should be documented better > ----------------------------------------------- > > Key: FURNACE-63 > URL: https://issues.jboss.org/browse/FURNACE-63 > Project: Forge: Furnace > Issue Type: Bug > Components: Runtime > Affects Versions: 2.20.1.Final > Reporter: Ondrej Zizka > Assignee: George Gastaldi > Fix For: 2.20.2.Final > > > STR: > Check out the 1a89b1c commit from > https://github.com/OndraZizka/windup/commit/1a89b1cac3f76e519571fd08c0cf3... > And run the WindupUpdateRulesetTest. > That will fail in RulesetUpdateChecker, because the PostStartup is fired for all (?) addons, even those which do not depend on windup-exec, and therefore the @Inject fails with "IllegalStateException: Addon service [...RulesetUpdater] is not registered". > I am not quite sure if that's how it should behave. Shouldn't it be called for the "current addon" as stated in the javadoc of PostStartup? > Or if not, then please specify better when this is called and what is the state of the addons. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (FURNACE-63) PostStartup bug, or should be documented better

by Jess Sightler (JIRA)

[ https://issues.jboss.org/browse/FURNACE-63?page=com.atlassian.jira.plugin... ] Jess Sightler commented on FURNACE-63: -------------------------------------- I still think it is a useful line (or at least something like it). Although even the first line alone is a good improvement, IMO. I'm also not sure that "PostStartup" is the best name for this event. Isn't it more like "AddonStarted"? > PostStartup bug, or should be documented better > ----------------------------------------------- > > Key: FURNACE-63 > URL: https://issues.jboss.org/browse/FURNACE-63 > Project: Forge: Furnace > Issue Type: Bug > Components: Runtime > Affects Versions: 2.20.1.Final > Reporter: Ondrej Zizka > Assignee: George Gastaldi > Fix For: 2.20.2.Final > > > STR: > Check out the 1a89b1c commit from > https://github.com/OndraZizka/windup/commit/1a89b1cac3f76e519571fd08c0cf3... > And run the WindupUpdateRulesetTest. > That will fail in RulesetUpdateChecker, because the PostStartup is fired for all (?) addons, even those which do not depend on windup-exec, and therefore the @Inject fails with "IllegalStateException: Addon service [...RulesetUpdater] is not registered". > I am not quite sure if that's how it should behave. Shouldn't it be called for the "current addon" as stated in the javadoc of PostStartup? > Or if not, then please specify better when this is called and what is the state of the addons. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues July 2015