October 2015 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-2497) Strange characters on http://forge.jboss.org/document/hands-on-lab (chrome)

by Rino van Wijngaarden (JIRA)

Rino van Wijngaarden created FORGE-2497: ------------------------------------------- Summary: Strange characters on http://forge.jboss.org/document/hands-on-lab (chrome) Key: FORGE-2497 URL: https://issues.jboss.org/browse/FORGE-2497 Project: Forge Issue Type: Quality Risk Environment: *Location*: http://forge.jboss.org/documentation *User-Agent*: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/45.0.2454.101 Safari/537.36 *Referrer*: http://forge.jboss.org/ *Screen Resolution*: 1920 x 1080 Reporter: Rino van Wijngaarden â€™ve spent any time developing Java EEâ€“based projects (or any nontrivial application, for that matter!), youâ€™ve likely invested a good amount of energy in creating the project layout, defining dependencies, and informing the build system of the relevant class paths to be used in compilation and execution. Although Maven enables us to reduce that load as compared with undertaking project setup manually, thereâ€™s typically quite a bit of boilerplate involved in the *Reporter*: Rino *E-mail*: [mailto:rino.van.wijngaarden@gmail.com] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2484) java-new-enum-const should follow the naming convention

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-2484?page=com.atlassian.jira.plugin... ] George Gastaldi commented on FORGE-2484: ---------------------------------------- Pull request updated. Please re-check. It now supports multiple constants > java-new-enum-const should follow the naming convention > ------------------------------------------------------- > > Key: FORGE-2484 > URL: https://issues.jboss.org/browse/FORGE-2484 > Project: Forge > Issue Type: Sub-task > Components: Java EE > Affects Versions: 2.19.1.Final > Reporter: Antonio Goncalves > Assignee: George Gastaldi > Priority: Minor > Fix For: 2.x Future > > > At the moment to add a new constant to an enum we type : > {code} > java-new-enum-const VISA ; > {code} > To follow the other commands, it should have a {{named}} parameter > {code} > java-new-enum-const --named VISA ; > java-new-enum-const --named MASTER_CARD ; > java-new-enum-const --named AMERICAN_EXPRESS ; > {code} > Changing {{new}} to {{add}} we could end up with : > {code} > java-add-enum-const --named VISA ; > java-add-enum-const --named MASTER_CARD ; > java-add-enum-const --named AMERICAN_EXPRESS ; > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2485) Upgrade to Furnace 2.22.4.Final

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-2485?page=com.atlassian.jira.plugin... ] George Gastaldi updated FORGE-2485: ----------------------------------- Summary: Upgrade to Furnace 2.22.4.Final (was: Upgrade to Furnace 2.22.3.Final) > Upgrade to Furnace 2.22.4.Final > ------------------------------- > > Key: FORGE-2485 > URL: https://issues.jboss.org/browse/FORGE-2485 > Project: Forge > Issue Type: Component Upgrade > Components: Furnace (Container) > Affects Versions: 2.19.2.Final > Reporter: George Gastaldi > Assignee: George Gastaldi > Fix For: 2.20.0.Final > > > Support for Jandex index, Weld 2.3.0.Final and Arquillian 1.1.9.Final -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2485) Upgrade to Furnace 2.22.3.Final

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-2485?page=com.atlassian.jira.plugin... ] George Gastaldi reopened FORGE-2485: ------------------------------------ > Upgrade to Furnace 2.22.3.Final > ------------------------------- > > Key: FORGE-2485 > URL: https://issues.jboss.org/browse/FORGE-2485 > Project: Forge > Issue Type: Component Upgrade > Components: Furnace (Container) > Affects Versions: 2.19.2.Final > Reporter: George Gastaldi > Assignee: George Gastaldi > Fix For: 2.20.0.Final > > > Support for Jandex index, Weld 2.3.0.Final and Arquillian 1.1.9.Final -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2496) Deadlock while running tests

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-2496?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-2496. ---------------------------------- Resolution: Done > Deadlock while running tests > ---------------------------- > > Key: FORGE-2496 > URL: https://issues.jboss.org/browse/FORGE-2496 > Project: Forge > Issue Type: Feature Request > Components: Test Harness > Affects Versions: 2.19.2.Final > Reporter: George Gastaldi > Assignee: George Gastaldi > Priority: Blocker > Fix For: 2.20.0.Final > > Attachments: thread_dump.txt, thread_dump2.txt > > > The attached thread dump shows a deadlock while running tests. This is happening in our CI server as well. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2484) java-new-enum-const should follow the naming convention

by Antonio Goncalves (JIRA)

[ https://issues.jboss.org/browse/FORGE-2484?page=com.atlassian.jira.plugin... ] Antonio Goncalves commented on FORGE-2484: ------------------------------------------ [~gastaldi] You should rename the parameter {{enumClass}} with {{targetClass}} : {code} [MyEnum.java]$ java-add-enum-const TAB --enumClass --named {code} I thought deprecated command would not appear when having code completion. It's important to state that the command is deprecated and will soon disappear (like in scripting), but should not be displayed in code completion. WDYT ? : {code} [proj]$ java-new-enum --named MyEnum [MyEnum.java]$ java-new-enum TAB java-new-enum java-new-enum-const [MyEnum.java]$ java-add-enum TAB java-add-enum-const [MyEnum.java]$ java-new-enum-const TEST ***WARNING*** The command 'Java: New Enum Const' is deprecated and will be removed in future versions. Use 'java-add-enum-const --named' instead ***SUCCESS*** Enum constants [TEST] created in org.proj.MyEnum {code} You mentioned the possibility to add several enums in a single command. I would be nice to still have it actually. This is not the case : {code} [MyEnum.java]$ java-add-enum-const --named VISA ***SUCCESS*** Enum constant 'VISA' added in org.myenum.MyEnum [MyEnum.java]$ java-add-enum-const --named VISA1 VISA2 VISA3 ***SUCCESS*** Enum constant 'VISA1' added in org.myenum.MyEnum // Only VISA1 is created {code} We have this behavior with methods in JPA entity listeners where we use plural : {{lifecycles}} instead of {{lifecycle}}. If we follow this naming convention, that would be like renaming all the commands {{name}} and {{names}} instead of {{named}}. So we could have : {code} $ java-add-enum-const --name VISA1 $ java-add-enum-const --names VISA1 VISA2 VISA3 $ jpa-new-entity-listener --lifecycles PRE_PERSIST PRE_REMOVE PRE_UPDATE {code} Too much refactoring :o( > java-new-enum-const should follow the naming convention > ------------------------------------------------------- > > Key: FORGE-2484 > URL: https://issues.jboss.org/browse/FORGE-2484 > Project: Forge > Issue Type: Sub-task > Components: Java EE > Affects Versions: 2.19.1.Final > Reporter: Antonio Goncalves > Assignee: George Gastaldi > Priority: Minor > Fix For: 2.x Future > > > At the moment to add a new constant to an enum we type : > {code} > java-new-enum-const VISA ; > {code} > To follow the other commands, it should have a {{named}} parameter > {code} > java-new-enum-const --named VISA ; > java-new-enum-const --named MASTER_CARD ; > java-new-enum-const --named AMERICAN_EXPRESS ; > {code} > Changing {{new}} to {{add}} we could end up with : > {code} > java-add-enum-const --named VISA ; > java-add-enum-const --named MASTER_CARD ; > java-add-enum-const --named AMERICAN_EXPRESS ; > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2496) Deadlock while running tests

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-2496?page=com.atlassian.jira.plugin... ] Work on FORGE-2496 started by George Gastaldi. ---------------------------------------------- > Deadlock while running tests > ---------------------------- > > Key: FORGE-2496 > URL: https://issues.jboss.org/browse/FORGE-2496 > Project: Forge > Issue Type: Feature Request > Components: Test Harness > Affects Versions: 2.19.2.Final > Reporter: George Gastaldi > Assignee: George Gastaldi > Priority: Blocker > Fix For: 2.20.0.Final > > Attachments: thread_dump.txt, thread_dump2.txt > > > The attached thread dump shows a deadlock while running tests. This is happening in our CI server as well. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2496) Deadlock while running tests

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-2496?page=com.atlassian.jira.plugin... ] George Gastaldi updated FORGE-2496: ----------------------------------- Attachment: thread_dump2.txt > Deadlock while running tests > ---------------------------- > > Key: FORGE-2496 > URL: https://issues.jboss.org/browse/FORGE-2496 > Project: Forge > Issue Type: Feature Request > Components: Test Harness > Affects Versions: 2.19.2.Final > Reporter: George Gastaldi > Assignee: George Gastaldi > Priority: Blocker > Fix For: 2.20.0.Final > > Attachments: thread_dump.txt, thread_dump2.txt > > > The attached thread dump shows a deadlock while running tests. This is happening in our CI server as well. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2496) Deadlock while running tests

by George Gastaldi (JIRA)

George Gastaldi created FORGE-2496: -------------------------------------- Summary: Deadlock while running tests Key: FORGE-2496 URL: https://issues.jboss.org/browse/FORGE-2496 Project: Forge Issue Type: Feature Request Components: Test Harness Affects Versions: 2.19.2.Final Reporter: George Gastaldi Assignee: George Gastaldi Priority: Blocker Fix For: 2.20.0.Final Attachments: thread_dump.txt The attached thread dump shows a deadlock while running tests. This is happening in our CI server as well. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2495) WizardCommandController does not execute all steps when execute is called directly

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-2495?page=com.atlassian.jira.plugin... ] George Gastaldi updated FORGE-2495: ----------------------------------- Description: The following code does not execute all the steps: {code} try (WizardCommandController controller = uiTestHarness.createWizardController(JPASetupWizard.class, project.getRoot())) { controller.initialize(); controller.execute(); } {code} That is because {{controller.execute()}} does not call {{refreshFlow()}}. If {{controller.canExecute()}} is called before {{controller.execute()}}, then it works. The solution is to call {{refreshFlow()}} in the {{execute()}} method. was: The following code does not execute all the steps: {code} try (WizardCommandController controller = uiTestHarness.createWizardController(JPASetupWizard.class, project.getRoot())) { controller.initialize(); controller.execute(); } {code} That is because {{canExecute()}} calls {{refreshFlow()}}. If canExecute is called before execute, then it works. The solution is to call refreshFlow() in the execute() method. > WizardCommandController does not execute all steps when execute is called directly > ---------------------------------------------------------------------------------- > > Key: FORGE-2495 > URL: https://issues.jboss.org/browse/FORGE-2495 > Project: Forge > Issue Type: Bug > Components: UI - API > Affects Versions: 2.19.2.Final > Reporter: George Gastaldi > Assignee: George Gastaldi > Fix For: 2.20.0.Final > > > The following code does not execute all the steps: > {code} > try (WizardCommandController controller = uiTestHarness.createWizardController(JPASetupWizard.class, > project.getRoot())) > { > controller.initialize(); > controller.execute(); > } > {code} > That is because {{controller.execute()}} does not call {{refreshFlow()}}. If {{controller.canExecute()}} is called before {{controller.execute()}}, then it works. The solution is to call {{refreshFlow()}} in the {{execute()}} method. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues October 2015