[JBoss JIRA] (FORGE-1148) Support multi-level UIWizard flows.
by Lincoln Baxter III (JIRA)
[ https://issues.jboss.org/browse/FORGE-1148?page=com.atlassian.jira.plugin... ]
Lincoln Baxter III updated FORGE-1148:
--------------------------------------
Summary: Support multi-level UIWizard flows. (was: Support high-level)
> Support multi-level UIWizard flows.
> -----------------------------------
>
> Key: FORGE-1148
> URL: https://issues.jboss.org/browse/FORGE-1148
> Project: Forge
> Issue Type: Bug
> Components: UI - API, UI - Eclipse, UI - Shell
> Affects Versions: 2.0.0.Alpha11
> Reporter: Lincoln Baxter III
> Fix For: 2.x Future
>
> Attachments: Screen Shot 2013-08-30 at 3.02.14 PM.png
>
>
> Say for instance I want to create a new entity, but persistence is not set up. I should have the choice to set up persistence, say, via a checkbox.
> but once persistence is set up, then I should be directed to add a new field, for instance. So the flow is this:
> 1. New Entity
> 2. Persistence Setup (Container Selection, Provider Selection)
> 3. New Field
> This means that persistence setup executes in a sub-flow that must return to the next designated step of the original flow when complete.
> {code}return Results.navigate(PersistenceSetup.class, NewField.class){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
11 years, 5 months
[JBoss JIRA] (FORGE-1145) Maven addon needs to allow configuration of native vs. embedded
by Lincoln Baxter III (JIRA)
[ https://issues.jboss.org/browse/FORGE-1145?page=com.atlassian.jira.plugin... ]
Lincoln Baxter III commented on FORGE-1145:
-------------------------------------------
Or because they may have a project that does not build with the version of maven we include, and may need to specify a higher or lower version. But we don't need to add this right away. We should think about this integration and make things as simple as possible to extend.
> Maven addon needs to allow configuration of native vs. embedded
> ---------------------------------------------------------------
>
> Key: FORGE-1145
> URL: https://issues.jboss.org/browse/FORGE-1145
> Project: Forge
> Issue Type: Feature Request
> Components: Maven Plugin, UI - Eclipse
> Affects Versions: 2.0.0.Alpha11
> Reporter: Lincoln Baxter III
> Fix For: 2.x Future
>
>
> Need a way of configuring/selecting the maven version to use, either via users .profile environment by default. Other configurators should include things like inheriting the native eclipse configuration for m2e plugin, and custom config.
--
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
11 years, 5 months
[JBoss JIRA] (FORGE-378) Add "environments" as a first class construct
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/FORGE-378?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen commented on FORGE-378:
-------------------------------------------
"What would happen if someone starts working with a specific version of EE, then sets the "environment" to a different version?" - you mean like you target JavaEE6 explicitly and then targets Wildfly 8 (which would default to JavaEE7?)
I would just expect forge to ask something like:
Current project is targeting JavaEE-6, the default type for Wildfly 8 is JavaEE-7. Do you wish to use JavaEE-7 or continue to use JavaEE-6 ?
> Add "environments" as a first class construct
> ---------------------------------------------
>
> Key: FORGE-378
> URL: https://issues.jboss.org/browse/FORGE-378
> Project: Forge
> Issue Type: Feature Request
> Components: UI - Shell, Usability
> Reporter: Pete Muir
>
> For example:
> {code}
> set environment JBOSS_AS7 --version 7.1.0.Final
> {code}
> Where JBOSS_AS7 is a built in profile that contains necessary info on various versions of JBoss AS 7.
> For example, the persistence plugin could read from this, changing
> {code}
> persistence setup --provider HIBERNATE --container JBOSS_AS7
> {code}
> to
> {code}
> persistence setup
> {code}
> Or, when setting up CDI, this would remove the need to ask ask which API to use (always use the Java EE BOM with JBoss AS), and as the metadata builds, remove the need to ask the version of the spec BOM to use.
> Lot's of other places where this could provide better defaulting, or remove the need to ask questions.
> This also seems fairly consistent with the Forge approach - good understanding of the project in question.
--
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
11 years, 5 months