[JBoss JIRA] (FORGE-2232) Documenting how to create and test a command that creates Java code
by Antonio Goncalves (JIRA)
[ https://issues.jboss.org/browse/FORGE-2232?page=com.atlassian.jira.plugin... ]
Antonio Goncalves commented on FORGE-2232:
------------------------------------------
The doc has been reviewed, now it's time to :
1) convert the doc to asciidoc
2) host that doc on github at https://github.com/forge/docs
3) create an entry in https://github.com/forge/website-data/blob/master/docs-tutorials.yaml
> Documenting how to create and test a command that creates Java code
> -------------------------------------------------------------------
>
> Key: FORGE-2232
> URL: https://issues.jboss.org/browse/FORGE-2232
> Project: Forge
> Issue Type: Sub-task
> Components: Documentation
> Affects Versions: 2.14.0.Final
> Reporter: Antonio Goncalves
> Assignee: George Gastaldi
> Fix For: 2.x Future
>
>
> The idea is to document commands that create new code ({{new}} commands). There are several level of complexity and we should go step by step :
> 1. A command to create a [new constraint payload|FORGE-1620] is quite simple. It only generates Java code to a specific directory
> 2. A command to create a [new package info|FORGE-2071] is a bit tricker because the generate Java code is not a class per-se
> 3. A command to create a [new constraint validator|FORGE-1618] have several parameters that can be used ({{type}} and {{targetConstraint}}). The case of the [JPA Listener|FORGE-2093] is also important because the command taks a choice of parameters ({{POST_UPDATE}}, {{PRE_PERSIST}}...)
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 10 months
[JBoss JIRA] (FORGE-2233) Documenting how to create and test a command that updates Java code
by Lincoln Baxter III (JIRA)
[ https://issues.jboss.org/browse/FORGE-2233?page=com.atlassian.jira.plugin... ]
Lincoln Baxter III commented on FORGE-2233:
-------------------------------------------
To publish this doc:
{code}
1) convert the doc to asciidoc
2) host that doc on github at https://github.com/forge/docs
3) create an entry in https://github.com/forge/website-data/blob/master/docs-tutorials.yaml
{code}
> Documenting how to create and test a command that updates Java code
> -------------------------------------------------------------------
>
> Key: FORGE-2233
> URL: https://issues.jboss.org/browse/FORGE-2233
> Project: Forge
> Issue Type: Sub-task
> Components: Documentation
> Affects Versions: 2.14.0.Final
> Reporter: Antonio Goncalves
> Assignee: George Gastaldi
> Fix For: 2.x Future
>
>
> The idea is to document commands that add new code to existing classes ({{add}} commands). Example, the command to add a [CDI producer|FORGE-2079] or add a [CDI injection point|FORGE-2226]
> Draft notes from #IRC
> gastaldi UIContext.getInitialSelection() should return a UISelection of Resource objects
> gastaldi Call get() on it and you should have a JavaResource if the command is executed in the context of a java class
> gastaldi Make it the default value of the targetClass field
> agoncal What does the Callable do in the initializeUI method do then ?
> gastaldi That should be used when the value changes over the UI interaction
> gastaldi That is not the case afaik
> gastaldi Because once you execute the command, the initial selection will not change
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 10 months
[JBoss JIRA] (FORGE-1751) Support Wildcards for package and class names
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-1751?page=com.atlassian.jira.plugin... ]
George Gastaldi updated FORGE-1751:
-----------------------------------
Priority: Critical (was: Major)
> Support Wildcards for package and class names
> ---------------------------------------------
>
> Key: FORGE-1751
> URL: https://issues.jboss.org/browse/FORGE-1751
> Project: Forge
> Issue Type: Feature Request
> Components: UI - Shell
> Affects Versions: 2.4.1.Final
> Reporter: George Gastaldi
> Priority: Critical
> Fix For: 2.15.2.Final
>
>
> In Forge 1.x it was possible to do something like:
> {code}
> scaffold-x from ~.model.Customer
> scaffold-x from ~.model.*
> {code}
> That would replace the ~ character with the top level package name.
> This is needed for scripting purposes and also very used.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 10 months
[JBoss JIRA] (FORGE-1751) Support Wildcards for package and class names
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-1751?page=com.atlassian.jira.plugin... ]
George Gastaldi updated FORGE-1751:
-----------------------------------
Fix Version/s: 2.15.2.Final
(was: 2.x Future)
> Support Wildcards for package and class names
> ---------------------------------------------
>
> Key: FORGE-1751
> URL: https://issues.jboss.org/browse/FORGE-1751
> Project: Forge
> Issue Type: Feature Request
> Components: UI - Shell
> Affects Versions: 2.4.1.Final
> Reporter: George Gastaldi
> Priority: Critical
> Fix For: 2.15.2.Final
>
>
> In Forge 1.x it was possible to do something like:
> {code}
> scaffold-x from ~.model.Customer
> scaffold-x from ~.model.*
> {code}
> That would replace the ~ character with the top level package name.
> This is needed for scripting purposes and also very used.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 10 months
[JBoss JIRA] (FORGE-1704) Stale subflow pages are displayed and corresponding commands executed
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-1704?page=com.atlassian.jira.plugin... ]
George Gastaldi closed FORGE-1704.
----------------------------------
Assignee: George Gastaldi
Fix Version/s: (was: 2.x Future)
Resolution: Out of Date
Seems to have been fixed for some time now. Reopen if the problem persists
> Stale subflow pages are displayed and corresponding commands executed
> ---------------------------------------------------------------------
>
> Key: FORGE-1704
> URL: https://issues.jboss.org/browse/FORGE-1704
> Project: Forge
> Issue Type: Bug
> Components: UI - API
> Affects Versions: 2.3.0.Final
> Reporter: Vineet Reynolds
> Assignee: George Gastaldi
>
> This happens in scaffolding, but it is very likely an implementation issue with respect to subflows in the UI-API.
> Stale subflow pages are displayed and their corresponding commands are executed even though they pages should not be displayed and are not relevant to the subflow sequence.
> In scaffolding (see steps to reproduce), when I choose a scaffold provider, subflow pages from the originally selected provider are displayed in combination with the currently selected provider. Additionally, UICommands or WizardSteps from the original provider are executed, resulted in a weird scaffold being generated.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 10 months
[JBoss JIRA] (FORGE-2285) Allow commands to be deprecated
by George Gastaldi (JIRA)
George Gastaldi created FORGE-2285:
--------------------------------------
Summary: Allow commands to be deprecated
Key: FORGE-2285
URL: https://issues.jboss.org/browse/FORGE-2285
Project: Forge
Issue Type: Feature Request
Components: Brainstorming, UI - API
Affects Versions: 2.15.1.Final
Reporter: George Gastaldi
Fix For: 2.x Future
Right now there are situations where we want to rename a command but we don't want to break scripts, same goes for the option names.
There should be a way to preserve the behavior, but in a deprecated way. Eg: suppose we rename {{java-new-method}} to {{java-add-method}}:
Scripts that still use {{java-new-method}} should display a warning saying that the command is deprecated and now you should use {{java-add-method}}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 10 months