March 2014 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-1672) Creating a nested "Forge Addon" project can break parent POM <modules> definition

by Lincoln Baxter III (JIRA)

Lincoln Baxter III created FORGE-1672: ----------------------------------------- Summary: Creating a nested "Forge Addon" project can break parent POM <modules> definition Key: FORGE-1672 URL: https://issues.jboss.org/browse/FORGE-1672 Project: Forge Issue Type: Bug Reporter: Lincoln Baxter III gastaldi: i found a bug with creating a forge-addon project inside a parent maven project 3:50 gastaldi: we rename the folder to projectx-parent sometimes 3:50 gastaldi: that breaks the parent pom <modules> {code} project-new --named foo project-new --named bar --type addon --furnaceContainer org.jboss.forge.furnace.container:cdi,2.1.2-SNAPSHOT --splitProjects --furnaceVersion 2.1.1.Final {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

12 years

1
0
0 / 0

[JBoss JIRA] (FORGE-1671) Add nested annotation to a constraint annotation

by Antonio Goncalves (JIRA)

[ https://issues.jboss.org/browse/FORGE-1671?page=com.atlassian.jira.plugin... ] Antonio Goncalves updated FORGE-1671: ------------------------------------- Description: At the moment a constraint annotation does not contain a {{List}} of constraints. So, at the moment, the command {{constraint-new-annotation}} generates the following code : {code} @Documented @Constraint(validatedBy = {}) @Target( { METHOD, FIELD, ANNOTATION_TYPE, CONSTRUCTOR, PARAMETER }) @Retention(RUNTIME) @ReportAsSingleViolation public @interface URL { String message() default "Invalid value"; Class<?>[] groups() default { }; Class<? extends Payload>[] payload() default { }; {code} It should add a nested annotation {{List}} of type array of constraint {code} @Documented @Constraint(validatedBy = {}) @Target( { METHOD, FIELD, ANNOTATION_TYPE, CONSTRUCTOR, PARAMETER }) @Retention(RUNTIME) @ReportAsSingleViolation public @interface URL { String message() default "Invalid value"; Class<?>[] groups() default { }; Class<? extends Payload>[] payload() default { }; @Target( { METHOD, FIELD, ANNOTATION_TYPE, CONSTRUCTOR, PARAMETER }) @Retention(RUNTIME) @Documented public @interface List { URL[] value(); } } {code} was: At the moment a constraint annotation does not contain a {{List}} of constraints. So, at the moment, the command {{constraint-new-annotation}} generates the following code : {code} @Documented @Constraint(validatedBy = {}) @Target( { METHOD, FIELD, ANNOTATION_TYPE, CONSTRUCTOR, PARAMETER }) @Retention(RUNTIME) @ReportAsSingleViolation public @interface URL { String message() default "Invalid value"; Class<?>[] groups() default { }; Class<? extends Payload>[] payload() default { }; {code} It should add a nested annotation {{List}} of type array of constraint @Documented @Constraint(validatedBy = {}) @Target( { METHOD, FIELD, ANNOTATION_TYPE, CONSTRUCTOR, PARAMETER }) @Retention(RUNTIME) @ReportAsSingleViolation public @interface URL { String message() default "Invalid value"; Class<?>[] groups() default { }; Class<? extends Payload>[] payload() default { }; @Target( { METHOD, FIELD, ANNOTATION_TYPE, CONSTRUCTOR, PARAMETER }) @Retention(RUNTIME) @Documented public @interface List { URL[] value(); } } > Add nested annotation to a constraint annotation > ------------------------------------------------ > > Key: FORGE-1671 > URL: https://issues.jboss.org/browse/FORGE-1671 > Project: Forge > Issue Type: Sub-task > Components: Java EE > Affects Versions: 2.1.2.Final > Reporter: Antonio Goncalves > Fix For: 2.x Future > > > At the moment a constraint annotation does not contain a {{List}} of constraints. So, at the moment, the command {{constraint-new-annotation}} generates the following code : > {code} > @Documented > @Constraint(validatedBy = {}) > @Target( { METHOD, FIELD, ANNOTATION_TYPE, CONSTRUCTOR, PARAMETER }) > @Retention(RUNTIME) > @ReportAsSingleViolation > public @interface URL { > String message() default "Invalid value"; > Class<?>[] groups() default { }; > Class<? extends Payload>[] payload() default { }; > {code} > It should add a nested annotation {{List}} of type array of constraint > {code} > @Documented > @Constraint(validatedBy = {}) > @Target( { METHOD, FIELD, ANNOTATION_TYPE, CONSTRUCTOR, PARAMETER }) > @Retention(RUNTIME) > @ReportAsSingleViolation > public @interface URL { > String message() default "Invalid value"; > Class<?>[] groups() default { }; > Class<? extends Payload>[] payload() default { }; > @Target( { METHOD, FIELD, ANNOTATION_TYPE, CONSTRUCTOR, PARAMETER }) > @Retention(RUNTIME) > @Documented > public @interface List { > URL[] value(); > } > } > {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

12 years

1
0
0 / 0

[JBoss JIRA] (FORGE-1671) Add nested annotation to a constraint annotation

by Antonio Goncalves (JIRA)

[ https://issues.jboss.org/browse/FORGE-1671?page=com.atlassian.jira.plugin... ] Antonio Goncalves updated FORGE-1671: ------------------------------------- Description: At the moment a constraint annotation does not contain a {{List}} of constraints. So, at the moment, the command {{constraint-new-annotation}} generates the following code : {code} @Documented @Constraint(validatedBy = {}) @Target( { METHOD, FIELD, ANNOTATION_TYPE, CONSTRUCTOR, PARAMETER }) @Retention(RUNTIME) @ReportAsSingleViolation public @interface URL { String message() default "Invalid value"; Class<?>[] groups() default { }; Class<? extends Payload>[] payload() default { }; {code} It should add a nested annotation {{List}} of type array of constraint {code} @Documented @Constraint(validatedBy = {}) @Target( { METHOD, FIELD, ANNOTATION_TYPE, CONSTRUCTOR, PARAMETER }) @Retention(RUNTIME) @ReportAsSingleViolation public @interface URL { String message() default "Invalid value"; Class<?>[] groups() default { }; Class<? extends Payload>[] payload() default { }; @Target( { METHOD, FIELD, ANNOTATION_TYPE, CONSTRUCTOR, PARAMETER }) @Retention(RUNTIME) @Documented public @interface List { URL[] value(); } } {code} See class : {{NewAnnotationCommand}} was: At the moment a constraint annotation does not contain a {{List}} of constraints. So, at the moment, the command {{constraint-new-annotation}} generates the following code : {code} @Documented @Constraint(validatedBy = {}) @Target( { METHOD, FIELD, ANNOTATION_TYPE, CONSTRUCTOR, PARAMETER }) @Retention(RUNTIME) @ReportAsSingleViolation public @interface URL { String message() default "Invalid value"; Class<?>[] groups() default { }; Class<? extends Payload>[] payload() default { }; {code} It should add a nested annotation {{List}} of type array of constraint {code} @Documented @Constraint(validatedBy = {}) @Target( { METHOD, FIELD, ANNOTATION_TYPE, CONSTRUCTOR, PARAMETER }) @Retention(RUNTIME) @ReportAsSingleViolation public @interface URL { String message() default "Invalid value"; Class<?>[] groups() default { }; Class<? extends Payload>[] payload() default { }; @Target( { METHOD, FIELD, ANNOTATION_TYPE, CONSTRUCTOR, PARAMETER }) @Retention(RUNTIME) @Documented public @interface List { URL[] value(); } } {code} > Add nested annotation to a constraint annotation > ------------------------------------------------ > > Key: FORGE-1671 > URL: https://issues.jboss.org/browse/FORGE-1671 > Project: Forge > Issue Type: Sub-task > Components: Java EE > Affects Versions: 2.1.2.Final > Reporter: Antonio Goncalves > Fix For: 2.x Future > > > At the moment a constraint annotation does not contain a {{List}} of constraints. So, at the moment, the command {{constraint-new-annotation}} generates the following code : > {code} > @Documented > @Constraint(validatedBy = {}) > @Target( { METHOD, FIELD, ANNOTATION_TYPE, CONSTRUCTOR, PARAMETER }) > @Retention(RUNTIME) > @ReportAsSingleViolation > public @interface URL { > String message() default "Invalid value"; > Class<?>[] groups() default { }; > Class<? extends Payload>[] payload() default { }; > {code} > It should add a nested annotation {{List}} of type array of constraint > {code} > @Documented > @Constraint(validatedBy = {}) > @Target( { METHOD, FIELD, ANNOTATION_TYPE, CONSTRUCTOR, PARAMETER }) > @Retention(RUNTIME) > @ReportAsSingleViolation > public @interface URL { > String message() default "Invalid value"; > Class<?>[] groups() default { }; > Class<? extends Payload>[] payload() default { }; > @Target( { METHOD, FIELD, ANNOTATION_TYPE, CONSTRUCTOR, PARAMETER }) > @Retention(RUNTIME) > @Documented > public @interface List { > URL[] value(); > } > } > {code} > See class : {{NewAnnotationCommand}} -- 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

12 years

1
0
0 / 0

[JBoss JIRA] (FORGE-1671) Add nested annotation to a constraint annotation

by Antonio Goncalves (JIRA)

Antonio Goncalves created FORGE-1671: ---------------------------------------- Summary: Add nested annotation to a constraint annotation Key: FORGE-1671 URL: https://issues.jboss.org/browse/FORGE-1671 Project: Forge Issue Type: Sub-task Components: Java EE Affects Versions: 2.1.2.Final Reporter: Antonio Goncalves Fix For: 2.x Future At the moment a constraint annotation does not contain a {{List}} of constraints. So, at the moment, the command {{constraint-new-annotation}} generates the following code : {code} @Documented @Constraint(validatedBy = {}) @Target( { METHOD, FIELD, ANNOTATION_TYPE, CONSTRUCTOR, PARAMETER }) @Retention(RUNTIME) @ReportAsSingleViolation public @interface URL { String message() default "Invalid value"; Class<?>[] groups() default { }; Class<? extends Payload>[] payload() default { }; {code} It should add a nested annotation {{List}} of type array of constraint @Documented @Constraint(validatedBy = {}) @Target( { METHOD, FIELD, ANNOTATION_TYPE, CONSTRUCTOR, PARAMETER }) @Retention(RUNTIME) @ReportAsSingleViolation public @interface URL { String message() default "Invalid value"; Class<?>[] groups() default { }; Class<? extends Payload>[] payload() default { }; @Target( { METHOD, FIELD, ANNOTATION_TYPE, CONSTRUCTOR, PARAMETER }) @Retention(RUNTIME) @Documented public @interface List { URL[] value(); } } -- 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

12 years

1
0
0 / 0

[JBoss JIRA] (FORGE-1670) JPA Setup Command should allow explicitly overwriting existing persistence units

by Lincoln Baxter III (JIRA)

Lincoln Baxter III created FORGE-1670: ----------------------------------------- Summary: JPA Setup Command should allow explicitly overwriting existing persistence units Key: FORGE-1670 URL: https://issues.jboss.org/browse/FORGE-1670 Project: Forge Issue Type: Feature Request Components: Builtin Plugins, Java EE Affects Versions: 2.1.1.Final Reporter: Lincoln Baxter III JPA Setup should have an "Overwrite" check-box that is enabled only when a name conflict is detected. -- 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

12 years

1
0
0 / 0

[JBoss JIRA] (FORGE-1670) JPA Setup Command should allow explicitly overwriting existing persistence units

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1670?page=com.atlassian.jira.plugin... ] George Gastaldi updated FORGE-1670: ----------------------------------- Fix Version/s: 2.x Future > JPA Setup Command should allow explicitly overwriting existing persistence units > --------------------------------------------------------------------------------- > > Key: FORGE-1670 > URL: https://issues.jboss.org/browse/FORGE-1670 > Project: Forge > Issue Type: Feature Request > Components: Builtin Plugins, Java EE > Affects Versions: 2.1.1.Final > Reporter: Lincoln Baxter III > Labels: Starter > Fix For: 2.x Future > > > JPA Setup should have an "Overwrite" check-box that is enabled only when a name conflict is detected. -- 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

12 years

1
0
0 / 0

[JBoss JIRA] (FORGE-1670) JPA Setup Command should allow explicitly overwriting existing persistence units

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1670?page=com.atlassian.jira.plugin... ] George Gastaldi updated FORGE-1670: ----------------------------------- Labels: Starter (was: ) > JPA Setup Command should allow explicitly overwriting existing persistence units > --------------------------------------------------------------------------------- > > Key: FORGE-1670 > URL: https://issues.jboss.org/browse/FORGE-1670 > Project: Forge > Issue Type: Feature Request > Components: Builtin Plugins, Java EE > Affects Versions: 2.1.1.Final > Reporter: Lincoln Baxter III > Labels: Starter > > JPA Setup should have an "Overwrite" check-box that is enabled only when a name conflict is detected. -- 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

12 years

1
0
0 / 0

[JBoss JIRA] (FORGE-1669) Allow alternative Interactive Wizard execution style

by Aslak Knutsen (JIRA)

Aslak Knutsen created FORGE-1669: ------------------------------------ Summary: Allow alternative Interactive Wizard execution style Key: FORGE-1669 URL: https://issues.jboss.org/browse/FORGE-1669 Project: Forge Issue Type: Feature Request Components: UI - Shell Affects Versions: 2.1.1.Final Reporter: Aslak Knutsen Allow for the following flow: {code} 01 Wizard.isEnabled 02 Wizard.prompt for UIInput 03 Wizard.execute 04 for each Step in Wizard.next 05 Step.isEnabled 06 Step.prompt for UIInput 07 Step.execute 08 for each Step in Step.next 09 goto 05 {code} as an alternative to the current single command wizard -- 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

12 years

1
0
0 / 0

[JBoss JIRA] (FORGE-1669) Allow alternative Interactive Wizard execution style

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/FORGE-1669?page=com.atlassian.jira.plugin... ] Aslak Knutsen updated FORGE-1669: --------------------------------- Fix Version/s: 2.x Future > Allow alternative Interactive Wizard execution style > ---------------------------------------------------- > > Key: FORGE-1669 > URL: https://issues.jboss.org/browse/FORGE-1669 > Project: Forge > Issue Type: Feature Request > Components: UI - Shell > Affects Versions: 2.1.1.Final > Reporter: Aslak Knutsen > Fix For: 2.x Future > > > Allow for the following flow: > {code} > 01 Wizard.isEnabled > 02 Wizard.prompt for UIInput > 03 Wizard.execute > 04 for each Step in Wizard.next > 05 Step.isEnabled > 06 Step.prompt for UIInput > 07 Step.execute > 08 for each Step in Step.next > 09 goto 05 > {code} > as an alternative to the current single command wizard -- 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

12 years

1
0
0 / 0

[JBoss JIRA] (FORGE-1616) Command constraint-new-annotation to create a new constraint

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1616?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-1616. ---------------------------------- Fix Version/s: 2.1.2.Final (was: 2.x Future) Resolution: Done Merged, thanks! > Command constraint-new-annotation to create a new constraint > ------------------------------------------------------------ > > Key: FORGE-1616 > URL: https://issues.jboss.org/browse/FORGE-1616 > Project: Forge > Issue Type: Sub-task > Components: Java EE > Affects Versions: 2.1.1.Final > Reporter: Antonio Goncalves > Assignee: Antonio Goncalves > Labels: Starter > Fix For: 2.1.2.Final > > > The following command will create a *constraint annotation* with no implementation, and a default *error message* : > {code} > constraint-new-annotation --named URL > {code} > This command first creates the constraint annotation (notice validatedBy = {}) > {code} > @Documented > @Constraint(validatedBy = {}) > @Target( { METHOD, FIELD, ANNOTATION_TYPE, CONSTRUCTOR, PARAMETER }) > @Retention(RUNTIME) > @ReportAsSingleViolation > public @interface URL { > String message() default "Invalid value"; > Class<?>[] groups() default { }; > Class<? extends Payload>[] payload() default { }; > @Target( { METHOD, FIELD, ANNOTATION_TYPE, CONSTRUCTOR, PARAMETER }) > @Retention(RUNTIME) > @Documented > public @interface List { > URL[] value(); > } > } > {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

12 years

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues March 2014