March 2015 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-2224) Rename attribute methodName in command java-new-method

by Antonio Goncalves (JIRA)

[ https://issues.jboss.org/browse/FORGE-2224?page=com.atlassian.jira.plugin... ] Antonio Goncalves updated FORGE-2224: ------------------------------------- Parent: FORGE-2277 Issue Type: Sub-task (was: Enhancement) > Rename attribute methodName in command java-new-method > ------------------------------------------------------ > > Key: FORGE-2224 > URL: https://issues.jboss.org/browse/FORGE-2224 > Project: Forge > Issue Type: Sub-task > Components: Java EE > Affects Versions: 2.14.0.Final > Reporter: Antonio Goncalves > Fix For: 3.x Future > > > The {{java-new-method}} has the following attributes : > {code} > $ java-new-method > --targetClass --returnType --parameters --accessType --methodName > {code} > The attribute {{methodName}} should be renamed to {{named}} to follow the Forge naming convention. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (FORGE-2277) Perform a UX review of the Shell experience in Forge 3

by Antonio Goncalves (JIRA)

[ https://issues.jboss.org/browse/FORGE-2277?page=com.atlassian.jira.plugin... ] Antonio Goncalves updated FORGE-2277: ------------------------------------- Fix Version/s: 3.x Future > Perform a UX review of the Shell experience in Forge 3 > ------------------------------------------------------ > > Key: FORGE-2277 > URL: https://issues.jboss.org/browse/FORGE-2277 > Project: Forge > Issue Type: Task > Components: UI - Shell > Affects Versions: 2.x Future > Reporter: Antonio Goncalves > Fix For: 3.x Future > > > Changing the syntax of the CLI commands is not doable in major releases. So we will wait for Forge 3.x to break compatibility and rename some commands if needed. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (FORGE-2277) Perform a UX review of the Shell experience in Forge 3

by Antonio Goncalves (JIRA)

Antonio Goncalves created FORGE-2277: ---------------------------------------- Summary: Perform a UX review of the Shell experience in Forge 3 Key: FORGE-2277 URL: https://issues.jboss.org/browse/FORGE-2277 Project: Forge Issue Type: Task Components: UI - Shell Affects Versions: 2.x Future Reporter: Antonio Goncalves Changing the syntax of the CLI commands is not doable in major releases. So we will wait for Forge 3.x to break compatibility and rename some commands if needed. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (FORGE-2275) Refactor the Java EE Tests with new @AddonDependency

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-2275?page=com.atlassian.jira.plugin... ] George Gastaldi updated FORGE-2275: ----------------------------------- Status: Closed (was: Pull Request Sent) Fix Version/s: 2.15.2.Final (was: 2.x Future) Resolution: Done Thanks! > Refactor the Java EE Tests with new @AddonDependency > ---------------------------------------------------- > > Key: FORGE-2275 > URL: https://issues.jboss.org/browse/FORGE-2275 > Project: Forge > Issue Type: Sub-task > Components: Java EE > Affects Versions: 2.15.1.Final > Reporter: Antonio Goncalves > Assignee: Antonio Goncalves > Fix For: 2.15.2.Final > > > The JPA / Bean Validation / CDI Tests have recently been strenghten. It is important to refactor them with new @AddonDependency management (because these tests are used in the Tutorials and should use the latest dependency management) > Tests should look like this : https://github.com/forge/core/blob/master/maven/tests/src/test/java/org/j... > There is a command to create tests : {{addon-new-test}} > https://github.com/forge/core/blob/master/addons/impl/src/main/java/org/j... > So the tests go from : > {code} > @Deployment > @AddonDeployments({ > @AddonDeployment(name = "org.jboss.forge.addon:ui"), > @AddonDeployment(name = "org.jboss.forge.addon:ui-test-harness"), > @AddonDeployment(name = "org.jboss.forge.addon:shell-test-harness"), > @AddonDeployment(name = "org.jboss.forge.addon:javaee"), > @AddonDeployment(name = "org.jboss.forge.addon:maven") > }) > public static AddonArchive getDeployment() > { > return ShrinkWrap > .create(AddonArchive.class) > .addClass(ProjectHelper.class) > .addBeansXML() > .addAsAddonDependencies( > AddonDependencyEntry.create("org.jboss.forge.furnace.container:cdi"), > AddonDependencyEntry.create("org.jboss.forge.addon:projects"), > AddonDependencyEntry.create("org.jboss.forge.addon:ui"), > AddonDependencyEntry.create("org.jboss.forge.addon:ui-test-harness"), > AddonDependencyEntry.create("org.jboss.forge.addon:shell-test-harness"), > AddonDependencyEntry.create("org.jboss.forge.addon:javaee"), > AddonDependencyEntry.create("org.jboss.forge.addon:maven") > ); > } > {code} > To > {code} > @Deployment > @AddonDependencies({ > @AddonDependency(name = "org.jboss.forge.addon:ui-test-harness"), > @AddonDependency(name = "org.jboss.forge.addon:shell-test-harness"), > @AddonDependency(name = "org.jboss.forge.addon:javaee"), > @AddonDependency(name = "org.jboss.forge.addon:maven"), > @AddonDependency(name = "org.jboss.forge.furnace.container:cdi") > }) > public static AddonArchive getDeployment() > { > return ShrinkWrap.create(AddonArchive.class).addBeansXML().addClass(ProjectHelper.class); > } > {code} > But there is still a problem with the setup commands {{JPASetupWizardTest}}, {{RestSetupTest}} and {{WebSocketSetupWizardTest}} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (FORGE-2275) Refactor the Java EE Tests with new @AddonDependency

by Antonio Goncalves (JIRA)

[ https://issues.jboss.org/browse/FORGE-2275?page=com.atlassian.jira.plugin... ] Antonio Goncalves updated FORGE-2275: ------------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/forge/core/pull/546 > Refactor the Java EE Tests with new @AddonDependency > ---------------------------------------------------- > > Key: FORGE-2275 > URL: https://issues.jboss.org/browse/FORGE-2275 > Project: Forge > Issue Type: Sub-task > Components: Java EE > Affects Versions: 2.15.1.Final > Reporter: Antonio Goncalves > Assignee: Antonio Goncalves > Fix For: 2.x Future > > > The JPA / Bean Validation / CDI Tests have recently been strenghten. It is important to refactor them with new @AddonDependency management (because these tests are used in the Tutorials and should use the latest dependency management) > Tests should look like this : https://github.com/forge/core/blob/master/maven/tests/src/test/java/org/j... > There is a command to create tests : {{addon-new-test}} > https://github.com/forge/core/blob/master/addons/impl/src/main/java/org/j... > So the tests go from : > {code} > @Deployment > @AddonDeployments({ > @AddonDeployment(name = "org.jboss.forge.addon:ui"), > @AddonDeployment(name = "org.jboss.forge.addon:ui-test-harness"), > @AddonDeployment(name = "org.jboss.forge.addon:shell-test-harness"), > @AddonDeployment(name = "org.jboss.forge.addon:javaee"), > @AddonDeployment(name = "org.jboss.forge.addon:maven") > }) > public static AddonArchive getDeployment() > { > return ShrinkWrap > .create(AddonArchive.class) > .addClass(ProjectHelper.class) > .addBeansXML() > .addAsAddonDependencies( > AddonDependencyEntry.create("org.jboss.forge.furnace.container:cdi"), > AddonDependencyEntry.create("org.jboss.forge.addon:projects"), > AddonDependencyEntry.create("org.jboss.forge.addon:ui"), > AddonDependencyEntry.create("org.jboss.forge.addon:ui-test-harness"), > AddonDependencyEntry.create("org.jboss.forge.addon:shell-test-harness"), > AddonDependencyEntry.create("org.jboss.forge.addon:javaee"), > AddonDependencyEntry.create("org.jboss.forge.addon:maven") > ); > } > {code} > To > {code} > @Deployment > @AddonDependencies({ > @AddonDependency(name = "org.jboss.forge.addon:ui-test-harness"), > @AddonDependency(name = "org.jboss.forge.addon:shell-test-harness"), > @AddonDependency(name = "org.jboss.forge.addon:javaee"), > @AddonDependency(name = "org.jboss.forge.addon:maven"), > @AddonDependency(name = "org.jboss.forge.furnace.container:cdi") > }) > public static AddonArchive getDeployment() > { > return ShrinkWrap.create(AddonArchive.class).addBeansXML().addClass(ProjectHelper.class); > } > {code} > But there is still a problem with the setup commands {{JPASetupWizardTest}}, {{RestSetupTest}} and {{WebSocketSetupWizardTest}} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (FORGE-2275) Refactor the Java EE Tests with new @AddonDependency

by Antonio Goncalves (JIRA)

[ https://issues.jboss.org/browse/FORGE-2275?page=com.atlassian.jira.plugin... ] Antonio Goncalves updated FORGE-2275: ------------------------------------- Summary: Refactor the Java EE Tests with new @AddonDependency (was: Refactor the JPA / Bean Validation / CDI Tests with new @AddonDependency) > Refactor the Java EE Tests with new @AddonDependency > ---------------------------------------------------- > > Key: FORGE-2275 > URL: https://issues.jboss.org/browse/FORGE-2275 > Project: Forge > Issue Type: Sub-task > Components: Java EE > Affects Versions: 2.15.1.Final > Reporter: Antonio Goncalves > Assignee: Antonio Goncalves > Fix For: 2.x Future > > > The JPA / Bean Validation / CDI Tests have recently been strenghten. It is important to refactor them with new @AddonDependency management (because these tests are used in the Tutorials and should use the latest dependency management) > Tests should look like this : https://github.com/forge/core/blob/master/maven/tests/src/test/java/org/j... > There is a command to create tests : {{addon-new-test}} > https://github.com/forge/core/blob/master/addons/impl/src/main/java/org/j... > So the tests go from : > {code} > @Deployment > @AddonDeployments({ > @AddonDeployment(name = "org.jboss.forge.addon:ui"), > @AddonDeployment(name = "org.jboss.forge.addon:ui-test-harness"), > @AddonDeployment(name = "org.jboss.forge.addon:shell-test-harness"), > @AddonDeployment(name = "org.jboss.forge.addon:javaee"), > @AddonDeployment(name = "org.jboss.forge.addon:maven") > }) > public static AddonArchive getDeployment() > { > return ShrinkWrap > .create(AddonArchive.class) > .addClass(ProjectHelper.class) > .addBeansXML() > .addAsAddonDependencies( > AddonDependencyEntry.create("org.jboss.forge.furnace.container:cdi"), > AddonDependencyEntry.create("org.jboss.forge.addon:projects"), > AddonDependencyEntry.create("org.jboss.forge.addon:ui"), > AddonDependencyEntry.create("org.jboss.forge.addon:ui-test-harness"), > AddonDependencyEntry.create("org.jboss.forge.addon:shell-test-harness"), > AddonDependencyEntry.create("org.jboss.forge.addon:javaee"), > AddonDependencyEntry.create("org.jboss.forge.addon:maven") > ); > } > {code} > To > {code} > @Deployment > @AddonDependencies({ > @AddonDependency(name = "org.jboss.forge.addon:ui-test-harness"), > @AddonDependency(name = "org.jboss.forge.addon:shell-test-harness"), > @AddonDependency(name = "org.jboss.forge.addon:javaee"), > @AddonDependency(name = "org.jboss.forge.addon:maven"), > @AddonDependency(name = "org.jboss.forge.furnace.container:cdi") > }) > public static AddonArchive getDeployment() > { > return ShrinkWrap.create(AddonArchive.class).addBeansXML().addClass(ProjectHelper.class); > } > {code} > But there is still a problem with the setup commands {{JPASetupWizardTest}}, {{RestSetupTest}} and {{WebSocketSetupWizardTest}} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (FORGE-2275) Refactor the JPA / Bean Validation / CDI Tests with new @AddonDependency

by Antonio Goncalves (JIRA)

[ https://issues.jboss.org/browse/FORGE-2275?page=com.atlassian.jira.plugin... ] Antonio Goncalves updated FORGE-2275: ------------------------------------- Description: The JPA / Bean Validation / CDI Tests have recently been strenghten. It is important to refactor them with new @AddonDependency management (because these tests are used in the Tutorials and should use the latest dependency management) Tests should look like this : https://github.com/forge/core/blob/master/maven/tests/src/test/java/org/j... There is a command to create tests : {{addon-new-test}} https://github.com/forge/core/blob/master/addons/impl/src/main/java/org/j... So the tests go from : {code} @Deployment @AddonDeployments({ @AddonDeployment(name = "org.jboss.forge.addon:ui"), @AddonDeployment(name = "org.jboss.forge.addon:ui-test-harness"), @AddonDeployment(name = "org.jboss.forge.addon:shell-test-harness"), @AddonDeployment(name = "org.jboss.forge.addon:javaee"), @AddonDeployment(name = "org.jboss.forge.addon:maven") }) public static AddonArchive getDeployment() { return ShrinkWrap .create(AddonArchive.class) .addClass(ProjectHelper.class) .addBeansXML() .addAsAddonDependencies( AddonDependencyEntry.create("org.jboss.forge.furnace.container:cdi"), AddonDependencyEntry.create("org.jboss.forge.addon:projects"), AddonDependencyEntry.create("org.jboss.forge.addon:ui"), AddonDependencyEntry.create("org.jboss.forge.addon:ui-test-harness"), AddonDependencyEntry.create("org.jboss.forge.addon:shell-test-harness"), AddonDependencyEntry.create("org.jboss.forge.addon:javaee"), AddonDependencyEntry.create("org.jboss.forge.addon:maven") ); } {code} To {code} @Deployment @AddonDependencies({ @AddonDependency(name = "org.jboss.forge.addon:ui-test-harness"), @AddonDependency(name = "org.jboss.forge.addon:shell-test-harness"), @AddonDependency(name = "org.jboss.forge.addon:javaee"), @AddonDependency(name = "org.jboss.forge.addon:maven"), @AddonDependency(name = "org.jboss.forge.furnace.container:cdi") }) public static AddonArchive getDeployment() { return ShrinkWrap.create(AddonArchive.class).addBeansXML().addClass(ProjectHelper.class); } {code} But there is still a problem with the setup commands {{JPASetupWizardTest}}, {{RestSetupTest}} and {{WebSocketSetupWizardTest}} was: The JPA / Bean Validation / CDI Tests have recently been strenghten. It is important to refactor them with new @AddonDependency management (because these tests are used in the Tutorials and should use the latest dependency management) Tests should look like this : https://github.com/forge/core/blob/master/maven/tests/src/test/java/org/j... There is a command to create tests : {{addon-new-test}} https://github.com/forge/core/blob/master/addons/impl/src/main/java/org/j... > Refactor the JPA / Bean Validation / CDI Tests with new @AddonDependency > ------------------------------------------------------------------------ > > Key: FORGE-2275 > URL: https://issues.jboss.org/browse/FORGE-2275 > Project: Forge > Issue Type: Sub-task > Components: Java EE > Affects Versions: 2.15.1.Final > Reporter: Antonio Goncalves > Assignee: Antonio Goncalves > Fix For: 2.x Future > > > The JPA / Bean Validation / CDI Tests have recently been strenghten. It is important to refactor them with new @AddonDependency management (because these tests are used in the Tutorials and should use the latest dependency management) > Tests should look like this : https://github.com/forge/core/blob/master/maven/tests/src/test/java/org/j... > There is a command to create tests : {{addon-new-test}} > https://github.com/forge/core/blob/master/addons/impl/src/main/java/org/j... > So the tests go from : > {code} > @Deployment > @AddonDeployments({ > @AddonDeployment(name = "org.jboss.forge.addon:ui"), > @AddonDeployment(name = "org.jboss.forge.addon:ui-test-harness"), > @AddonDeployment(name = "org.jboss.forge.addon:shell-test-harness"), > @AddonDeployment(name = "org.jboss.forge.addon:javaee"), > @AddonDeployment(name = "org.jboss.forge.addon:maven") > }) > public static AddonArchive getDeployment() > { > return ShrinkWrap > .create(AddonArchive.class) > .addClass(ProjectHelper.class) > .addBeansXML() > .addAsAddonDependencies( > AddonDependencyEntry.create("org.jboss.forge.furnace.container:cdi"), > AddonDependencyEntry.create("org.jboss.forge.addon:projects"), > AddonDependencyEntry.create("org.jboss.forge.addon:ui"), > AddonDependencyEntry.create("org.jboss.forge.addon:ui-test-harness"), > AddonDependencyEntry.create("org.jboss.forge.addon:shell-test-harness"), > AddonDependencyEntry.create("org.jboss.forge.addon:javaee"), > AddonDependencyEntry.create("org.jboss.forge.addon:maven") > ); > } > {code} > To > {code} > @Deployment > @AddonDependencies({ > @AddonDependency(name = "org.jboss.forge.addon:ui-test-harness"), > @AddonDependency(name = "org.jboss.forge.addon:shell-test-harness"), > @AddonDependency(name = "org.jboss.forge.addon:javaee"), > @AddonDependency(name = "org.jboss.forge.addon:maven"), > @AddonDependency(name = "org.jboss.forge.furnace.container:cdi") > }) > public static AddonArchive getDeployment() > { > return ShrinkWrap.create(AddonArchive.class).addBeansXML().addClass(ProjectHelper.class); > } > {code} > But there is still a problem with the setup commands {{JPASetupWizardTest}}, {{RestSetupTest}} and {{WebSocketSetupWizardTest}} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (FORGE-2228) Cannot create a method on a Java Interface

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-2228?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-2228. ---------------------------------- Assignee: George Gastaldi Fix Version/s: 2.15.2.Final (was: 2.x Future) Resolution: Done > Cannot create a method on a Java Interface > ------------------------------------------ > > Key: FORGE-2228 > URL: https://issues.jboss.org/browse/FORGE-2228 > Project: Forge > Issue Type: Enhancement > Components: Java EE > Affects Versions: 2.14.0.Final > Reporter: Antonio Goncalves > Assignee: George Gastaldi > Fix For: 2.15.2.Final > > > With [FORGE-1842] we can now create methods on Java classes. But it doesn't work on Java interface. > {code} > [util]$ java-new-interface --named MyInterface > [MyInterface.java]$ java-new-method --methodName generateNumber --returnType String --accessType public > ***INFO*** Required inputs not satisfied, entering interactive mode > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (ROASTER-65) JavaInterfaceSource doesn't allow setting supertypes

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/ROASTER-65?page=com.atlassian.jira.plugin... ] George Gastaldi updated ROASTER-65: ----------------------------------- Affects Version/s: 2.13.0.Final > JavaInterfaceSource doesn't allow setting supertypes > ---------------------------------------------------- > > Key: ROASTER-65 > URL: https://issues.jboss.org/browse/ROASTER-65 > Project: Roaster > Issue Type: Feature Request > Components: API, JDT > Affects Versions: 2.13.0.Final > Reporter: George Gastaldi > Fix For: 2.x Future > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (ROASTER-65) JavaInterfaceSource doesn't allow setting supertypes

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/ROASTER-65?page=com.atlassian.jira.plugin... ] George Gastaldi updated ROASTER-65: ----------------------------------- Fix Version/s: 2.x Future > JavaInterfaceSource doesn't allow setting supertypes > ---------------------------------------------------- > > Key: ROASTER-65 > URL: https://issues.jboss.org/browse/ROASTER-65 > Project: Roaster > Issue Type: Feature Request > Components: API, JDT > Affects Versions: 2.13.0.Final > Reporter: George Gastaldi > Fix For: 2.x Future > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues March 2015