[forge-issues] [JBoss JIRA] (FORGE-2232) Documenting how to create and test a command that creates Java code
Antonio Goncalves (JIRA)
issues at jboss.org
Wed Mar 4 06:26:49 EST 2015
[ https://issues.jboss.org/browse/FORGE-2232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13046136#comment-13046136 ]
Antonio Goncalves commented on FORGE-2232:
------------------------------------------
Google Document here : https://docs.google.com/document/d/11Y-zcl2-fp-Kxdq1wq8gM37_AUeWX6SQiYV65d7H5es
> 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)
More information about the forge-issues
mailing list