[JBoss JIRA] (FORGE-2085) Improving the cdi-new-bean command
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-2085?page=com.atlassian.jira.plugin... ]
George Gastaldi updated FORGE-2085:
-----------------------------------
Status: Closed (was: Pull Request Sent)
Fix Version/s: 2.12.2.Final
(was: 2.x Future)
Resolution: Done
> Improving the cdi-new-bean command
> ----------------------------------
>
> Key: FORGE-2085
> URL: https://issues.jboss.org/browse/FORGE-2085
> Project: Forge
> Issue Type: Sub-task
> Components: Java EE
> Affects Versions: 2.12.1.Final
> Reporter: Antonio Goncalves
> Assignee: Antonio Goncalves
> Fix For: 2.12.2.Final
>
>
> At the moment the {{cdi-new-bean}} command takes the following parameters :
> {code}
> cdi-new-bean --named --scoped --targetPackage
> {code}
> It would be good to have a few extra ones :
> {code}
> cdi-new-bean --named MyBean --scoped SESSION --qualifier Production --alternative=true --withNamed=true
> {code}
> This would generate :
> {code}
> @SessionScoped
> @Production
> @Alternative
> @Named
> public class MyBean
> {
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 5 months
[JBoss JIRA] (FORGE-2097) Occassionally some files in AngularJS scaffold are created in the wrong directory
by Vineet Reynolds (JIRA)
Vineet Reynolds created FORGE-2097:
--------------------------------------
Summary: Occassionally some files in AngularJS scaffold are created in the wrong directory
Key: FORGE-2097
URL: https://issues.jboss.org/browse/FORGE-2097
Project: Forge
Issue Type: Bug
Affects Versions: 2.12.1.Final
Reporter: Vineet Reynolds
When I select AngularJS as the scaffold provider, and type in {{/admin}} as the web root and proceed to create a scaffold for TicketMonster, sometimes, some of the files are created in directories named {{src/main/webapp/a}}, {{src/main/webapp/adm}} etc. instead of {{src/main/webapp/admin}}.
This is not always reproducible. It seems to depend on the order in which the inputs are entered, and maybe even the speed with which they are entered.
Leaving the component as blank for now, since this could be either in the AngularJS addon, or in the UI-Eclipse addon.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 5 months
[JBoss JIRA] (FORGE-2096) Git patches fail to apply when run as a native command
by Vineet Reynolds (JIRA)
Vineet Reynolds created FORGE-2096:
--------------------------------------
Summary: Git patches fail to apply when run as a native command
Key: FORGE-2096
URL: https://issues.jboss.org/browse/FORGE-2096
Project: Forge
Issue Type: Bug
Components: UI - Shell
Affects Versions: 2.12.1.Final
Reporter: Vineet Reynolds
When I run the following commands to apply a patch in the Shell, the command seems to run fine, but the patch does not seem to be applied on the files:
{{run --command "git apply -v --ignore-whitespace --ignore-space-change patches/admin_layer_functional.patch"}}
{{run --command "git apply -v --ignore-whitespace --ignore-space-change patches/admin_layer_graphics.patch"}}
The patches are from the TicketMonster 2.7.x-develop branch. They apply correctly when I use Eclipse eGit.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 5 months
[JBoss JIRA] (FORGE-2094) Being able to add a listener when creating a new JPA entity
by Antonio Goncalves (JIRA)
Antonio Goncalves created FORGE-2094:
----------------------------------------
Summary: Being able to add a listener when creating a new JPA entity
Key: FORGE-2094
URL: https://issues.jboss.org/browse/FORGE-2094
Project: Forge
Issue Type: Sub-task
Components: Java EE
Affects Versions: 2.12.1.Final
Reporter: Antonio Goncalves
Fix For: 2.x Future
Today the {{jpa-new-entity}} has the following syntax :
{code}
jpa-new-entity --named --targetPackage --idStrategy --tableName
{code}
It would be good to have an extra optional {{listener}} attribute to add a entity listener. For example, the following command :
{code}
jpa-new-entity --named MyEntity --listener DebugListener
{code}
Would generate :
{code}
@Entity
@EntityListeners({ DebugListener.class })
public class MyEntity
{
}
{code}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 5 months
[JBoss JIRA] (FORGE-2093) Being able to create a new JPA listener
by Antonio Goncalves (JIRA)
Antonio Goncalves created FORGE-2093:
----------------------------------------
Summary: Being able to create a new JPA listener
Key: FORGE-2093
URL: https://issues.jboss.org/browse/FORGE-2093
Project: Forge
Issue Type: Sub-task
Components: Java EE
Affects Versions: 2.12.1.Final
Reporter: Antonio Goncalves
Fix For: 2.x Future
It would be good to be able to create a new JPA listener. A basic command could just be :
{code}
jpa-new-listener --named MyListener
{code}
This will generate the following code :
{code}
class MyListener {
}
{code}
Then we would add as many lifecycle events as needed, something like :
{code}
jpa-new-listener --named MyListener --lifecycle PRE_PERSIST, POST_UPDATE, POST_REMOVE
{code}
{code}
class MyListener {
@PrePersist
private void prePersist(Object object)
{
}
@PostUpdate
private void postUpdate(Object object)
{
}
@PostRemove
private void postRemove(Object object)
{
}
}
{code}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 5 months