May 2014 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-1796) JTA facets should not be necessary for activating EJB facets.

by Vineet Reynolds (JIRA)

Vineet Reynolds created FORGE-1796: -------------------------------------- Summary: JTA facets should not be necessary for activating EJB facets. Key: FORGE-1796 URL: https://issues.jboss.org/browse/FORGE-1796 Project: Forge Issue Type: Bug Components: Java EE Affects Versions: 2.5.0.Final Reporter: Vineet Reynolds If the JTA API is missing from the POM on an existing project the EJB facet won't be installed. This is not right, EJB is very usable without JTA. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1793) Commands faces-new-validator and faces-new-converter do not work with faces-setup

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-1793?page=com.atlassian.jira.plugin... ] Lincoln Baxter III closed FORGE-1793. ------------------------------------- Fix Version/s: 2.5.1.Final Resolution: Done > Commands faces-new-validator and faces-new-converter do not work with faces-setup > --------------------------------------------------------------------------------- > > Key: FORGE-1793 > URL: https://issues.jboss.org/browse/FORGE-1793 > Project: Forge > Issue Type: Feature Request > Components: Java EE > Affects Versions: 2.5.0.Final > Reporter: Antonio Goncalves > Assignee: Lincoln Baxter III > Fix For: 2.5.1.Final > > > Both commands {{faces-new-validator}} and {{faces-new-converter}} generate Java code but which doesn't build. That's because {{faces-setup}} needs to be executed first to add the dependency on JSF on the {{pom.xml}}. > Maybe both commands need to {{implements PrerequisiteCommandsProvider}} and override the method {{getPrerequisiteCommands}} as : > {code} > @Override > public NavigationResult getPrerequisiteCommands(UIContext context) > { > NavigationResultBuilder builder = NavigationResultBuilder.create(); > Project project = getSelectedProject(context); > if (project != null) > { > if (!project.hasFacet(FacesFacet.class)) > { > builder.add(FacesSetupWizard.class); > } > } > return builder.build(); > } > {code} -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1793) Commands faces-new-validator and faces-new-converter do not work with faces-setup

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-1793?page=com.atlassian.jira.plugin... ] Lincoln Baxter III reassigned FORGE-1793: ----------------------------------------- Assignee: Lincoln Baxter III > Commands faces-new-validator and faces-new-converter do not work with faces-setup > --------------------------------------------------------------------------------- > > Key: FORGE-1793 > URL: https://issues.jboss.org/browse/FORGE-1793 > Project: Forge > Issue Type: Feature Request > Components: Java EE > Affects Versions: 2.5.0.Final > Reporter: Antonio Goncalves > Assignee: Lincoln Baxter III > Fix For: 2.5.1.Final > > > Both commands {{faces-new-validator}} and {{faces-new-converter}} generate Java code but which doesn't build. That's because {{faces-setup}} needs to be executed first to add the dependency on JSF on the {{pom.xml}}. > Maybe both commands need to {{implements PrerequisiteCommandsProvider}} and override the method {{getPrerequisiteCommands}} as : > {code} > @Override > public NavigationResult getPrerequisiteCommands(UIContext context) > { > NavigationResultBuilder builder = NavigationResultBuilder.create(); > Project project = getSelectedProject(context); > if (project != null) > { > if (!project.hasFacet(FacesFacet.class)) > { > builder.add(FacesSetupWizard.class); > } > } > return builder.build(); > } > {code} -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1795) UITestHarness usage of UIPrompt should be configurable

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1795?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-1795. ---------------------------------- Resolution: Done > UITestHarness usage of UIPrompt should be configurable > ------------------------------------------------------ > > Key: FORGE-1795 > URL: https://issues.jboss.org/browse/FORGE-1795 > Project: Forge > Issue Type: Feature Request > Components: Test Harness > Affects Versions: 2.5.0.Final > Reporter: George Gastaldi > Assignee: George Gastaldi > Fix For: 2.5.1.Final > > > The UIPrompt in the UITestHarness always returns default values. It should be possible to override these values so the test can have a deterministic behavior. > I propose the inclusion of a Map<String,String> attribute to UITestHarness in which the key will be a regexp to the message shown when calling UIPrompt.prompt(String message) and the value the value to be returned -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1795) UITestHarness usage of UIPrompt should be configurable

by George Gastaldi (JIRA)

George Gastaldi created FORGE-1795: -------------------------------------- Summary: UITestHarness usage of UIPrompt should be configurable Key: FORGE-1795 URL: https://issues.jboss.org/browse/FORGE-1795 Project: Forge Issue Type: Feature Request Components: Test Harness Affects Versions: 2.5.0.Final Reporter: George Gastaldi Assignee: George Gastaldi Fix For: 2.5.1.Final The UIPrompt in the UITestHarness always returns default values. It should be possible to override these values so the test can have a deterministic behavior. I propose the inclusion of a Map<String,String> attribute to UITestHarness in which the key will be a regexp to the message shown when calling UIPrompt.prompt(String message) and the value the value to be returned -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-273) Create project from Maven archetype

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-273?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III commented on FORGE-273: ------------------------------------------ >From [~jstrachan1] {quote} We added an archetype generator a while back into eclipse so it was easy for folks to start projects & we pre-baked all our camel/fuse archetypes - as using the maven archetype:generate command line is so utterly awful. Here’s the code to create an archetype from the mvn coordinates of the archetype distro: https://github.com/fabric8io/fabric8/blob/master/tooling/camel-tooling-ut... e.g. here’s a test case that creates a bunch of archetypes - no maven is required etc: https://github.com/fabric8io/fabric8/blob/master/tooling/camel-tooling-ut... I was hoping we could cobble something like this into a standard command; then have nice tab completion on the list of archetypes we ship by default in Forge which groks all the jboss / fuse / apache archetypes we want to prime it with; and make it easy for folks to add/load/configure others. e.g. JBoss Fuse ships with a bunch of archetypes (but they are not sync’d to maven central); so it’d be nice if all jboss products that have archetypes were baked into Forge (e.g. EAP / Fuse / Fuse Service Works / BRMS etc). Hope that helps - would love to port the code to plain java ;) but I guess whats another massive jar dependency on spring-library between friends ;) {quote} > Create project from Maven archetype > ----------------------------------- > > Key: FORGE-273 > URL: https://issues.jboss.org/browse/FORGE-273 > Project: Forge > Issue Type: Feature Request > Components: Blessed Plugins > Reporter: Dan Allen > Assignee: Rodney Russ > Priority: Minor > Fix For: 2.x Future > > > Since the catalog of Maven archetypes is substantial, and the archetype plugin interface is so abysmal, Forge could benefit from being a stand-in replacement to archetype:generate. A command in Forge to create a new project from a Maven archetype would certainly offer a nice complement to the more basic "new-project" command. It could just be an additional flag to the new-project command, such as: > new-project --named MyProject --fromArchetype org.jboss.weld.archetypes:jboss-javaee6-webapp > Using the interactive prompts, you may be able to provide a list of archetypes, perhaps w/ a filtering mechanism. You could also just do a best guess based on what's found in the catalog. > new-project --named MyProject --fromArchetype jboss-javaee6-webapp > You could just delegate to Maven by building up the "mvn archetype:generate" command from Forge. Long term we could consider emulating the archetype:generate plugin so as just to consume the projects that are out there already w/o any linkage to Maven. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1794) addon-git-install fails to checkout a remote branch

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1794?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-1794. ---------------------------------- Resolution: Done > addon-git-install fails to checkout a remote branch > --------------------------------------------------- > > Key: FORGE-1794 > URL: https://issues.jboss.org/browse/FORGE-1794 > Project: Forge > Issue Type: Bug > Components: Addon Manager > Affects Versions: 2.5.0.Final > Reporter: George Gastaldi > Assignee: George Gastaldi > Fix For: 2.5.1.Final > > > When a --branch is specified in the addon-git-install command, the command fails saying that {{***ERROR*** Ref branchName can not be resolved}} -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1794) addon-git-install fails to checkout a remote branch

by George Gastaldi (JIRA)

George Gastaldi created FORGE-1794: -------------------------------------- Summary: addon-git-install fails to checkout a remote branch Key: FORGE-1794 URL: https://issues.jboss.org/browse/FORGE-1794 Project: Forge Issue Type: Bug Components: Addon Manager Affects Versions: 2.5.0.Final Reporter: George Gastaldi Assignee: George Gastaldi Fix For: 2.5.1.Final When a --branch is specified in the addon-git-install command, the command fails saying that {{***ERROR*** Ref branchName can not be resolved}} -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ROASTER-13) PropertyImpl is not checking return type/parameter type in isAccessor() isMutator() methods

by Matej Briskar (JIRA)

[ https://issues.jboss.org/browse/ROASTER-13?page=com.atlassian.jira.plugin... ] Matej Briskar reassigned ROASTER-13: ------------------------------------ Assignee: Matej Briskar > PropertyImpl is not checking return type/parameter type in isAccessor() isMutator() methods > ------------------------------------------------------------------------------------------- > > Key: ROASTER-13 > URL: https://issues.jboss.org/browse/ROASTER-13 > Project: Roaster > Issue Type: Bug > Reporter: Matej Briskar > Assignee: Matej Briskar > -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ROASTER-13) PropertyImpl is not checking return type/parameter type in isAccessor() isMutator() methods

by Matej Briskar (JIRA)

Matej Briskar created ROASTER-13: ------------------------------------ Summary: PropertyImpl is not checking return type/parameter type in isAccessor() isMutator() methods Key: ROASTER-13 URL: https://issues.jboss.org/browse/ROASTER-13 Project: Roaster Issue Type: Bug Reporter: Matej Briskar -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 7 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues May 2014