[JBoss JIRA] (FORGE-1152) "forge-addon" classifier for addon qualification should be customizable
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-1152?page=com.atlassian.jira.plugin... ]
George Gastaldi closed FORGE-1152.
----------------------------------
Assignee: George Gastaldi
Fix Version/s: 2.0.0.Alpha12
(was: 2.x Future)
Resolution: Done
Done. now it's possible to set a <classifier> in the maven plugin.
> "forge-addon" classifier for addon qualification should be customizable
> -----------------------------------------------------------------------
>
> Key: FORGE-1152
> URL: https://issues.jboss.org/browse/FORGE-1152
> Project: Forge
> Issue Type: Feature Request
> Components: Furnace (Container)
> Affects Versions: 2.0.0.Alpha11
> Reporter: Lincoln Baxter III
> Assignee: George Gastaldi
> Fix For: 2.0.0.Alpha12
>
>
> It should be possible to configure the maven classifier used to distinguish forge-addon projects from normal maven dependencies. This would allow broader re-use of the Furnace container without Forge branding.
--
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, 4 months
[JBoss JIRA] (FORGE-1148) Support multi-level UIWizard flows.
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-1148?page=com.atlassian.jira.plugin... ]
George Gastaldi reassigned FORGE-1148:
--------------------------------------
Assignee: George Gastaldi
> 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
> Assignee: George Gastaldi
> Labels: difficult
> 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, 4 months
[JBoss JIRA] (FORGE-1148) Support multi-level UIWizard flows.
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-1148?page=com.atlassian.jira.plugin... ]
George Gastaldi updated FORGE-1148:
-----------------------------------
Status: Pull Request Sent (was: Open)
Git Pull Request: https://github.com/forge/core/pull/349
> 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
> Labels: difficult
> 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, 4 months
[JBoss JIRA] (FORGE-1152) "forge-addon" classifier for addon qualification should be customizable
by Lincoln Baxter III (JIRA)
Lincoln Baxter III created FORGE-1152:
-----------------------------------------
Summary: "forge-addon" classifier for addon qualification should be customizable
Key: FORGE-1152
URL: https://issues.jboss.org/browse/FORGE-1152
Project: Forge
Issue Type: Feature Request
Components: Furnace (Container)
Affects Versions: 2.0.0.Alpha11
Reporter: Lincoln Baxter III
Fix For: 2.x Future
It should be possible to configure the maven classifier used to distinguish forge-addon projects from normal maven dependencies. This would allow broader re-use of the Furnace container without Forge branding.
--
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, 4 months