September 2012 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-691) scaffolding does not support entities using a manytomany relationship with a join table

by Kevin Hooke (JIRA)

Kevin Hooke created FORGE-691: --------------------------------- Summary: scaffolding does not support entities using a manytomany relationship with a join table Key: FORGE-691 URL: https://issues.jboss.org/browse/FORGE-691 Project: Forge Issue Type: Feature Request Reporter: Kevin Hooke using field with a relationship type of manytomany does not give the option to generate the relationship using a join table. If you map this relationship by hand with JPA annotations using oneToMany from either side to an association entity, Forge scaffolding does not know how to generate view pages to handle creation of the relationship. It currently attempts to populate a list to allow the user to select an instance of the association class, which doesn't make any sense. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-690) field relationship manytomany doesn't support join tables

by Kevin Hooke (JIRA)

Kevin Hooke created FORGE-690: --------------------------------- Summary: field relationship manytomany doesn't support join tables Key: FORGE-690 URL: https://issues.jboss.org/browse/FORGE-690 Project: Forge Issue Type: Feature Request Reporter: Kevin Hooke Using field with a relationship type of manytomany does not give the option to add JPA mappings using a join table. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-676) Create a maven extension for Forge Addons

by George Gastaldi (JIRA)

George Gastaldi created FORGE-676: ------------------------------------- Summary: Create a maven extension for Forge Addons Key: FORGE-676 URL: https://issues.jboss.org/browse/FORGE-676 Project: Forge Issue Type: Feature Request Reporter: George Gastaldi Fix For: 2.0.0.Alpha1 Forge addons should end with the .far extension, and may contain the following structure besides the binaries: - lib/ - META-INF/forge.xml -- 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, 7 months

1
2
0 / 0

[JBoss JIRA] (FORGE-689) Shell should report "People who used this command also used the following commands: X Y Z"

by Lincoln Baxter III (JIRA)

Lincoln Baxter III created FORGE-689: ---------------------------------------- Summary: Shell should report "People who used this command also used the following commands: X Y Z" Key: FORGE-689 URL: https://issues.jboss.org/browse/FORGE-689 Project: Forge Issue Type: Feature Request Components: Shell Affects Versions: 1.1.0.Final Reporter: Lincoln Baxter III Fix For: 2.0.0.Alpha1 This should probably not be tied to the shell, but use analytics tracking data to report on which commands generally follow which and expose an API that can be used to implement this feature in the shell, IDE, or any UI. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGEPLUGINS-87) JDF plugin should permit bom selection based on runtime

by Rafael Benevides (JIRA)

Rafael Benevides created FORGEPLUGINS-87: -------------------------------------------- Summary: JDF plugin should permit bom selection based on runtime Key: FORGEPLUGINS-87 URL: https://issues.jboss.org/browse/FORGEPLUGINS-87 Project: Forge Plugins Issue Type: Feature Request Reporter: Rafael Benevides Forge plugin was planned prior the JBoss Stacks project ( http://www.jboss.org/jdf/stack/stacks/ ) so I think that we could update the JDF Forge plugin to use the Runtimes and Archetypes information too. Today jdf plugin shows all available boms through command completer: jdf use-stack --stack <TAB> I think we should update jdf plugin to use the Runtime to display only the available BOMs/BomVersions from each Runtime: jdf use-stack --runtime jboss-eap-60 --bom <TAB> (change --stack to --bom) -- 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, 7 months

1
1
0 / 0

[JBoss JIRA] (FORGE-688) Addition of the JavaEE 6 BOM should be encapsulated in a specific Facet

by George Gastaldi (JIRA)

George Gastaldi created FORGE-688: ------------------------------------- Summary: Addition of the JavaEE 6 BOM should be encapsulated in a specific Facet Key: FORGE-688 URL: https://issues.jboss.org/browse/FORGE-688 Project: Forge Issue Type: Enhancement Components: Plugin API Affects Versions: 1.1.0.Final Reporter: George Gastaldi Priority: Minor Fix For: 2.0.0.Alpha1 It would be nice if we have a JavaEE6Facet, which installs the jboss bom. Even though the BaseJavaEEFacet abstract class already does that, this behavior would not be possible if a custom Facet is created extending a specific subclass of BaseFacet and requiring the JavaEE6. The more elegant solution would be to add: {code:java} @RequiresFacet(JavaEE6Facet.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, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-687) PromptType.JAVA_PACKAGE should support default package

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/FORGE-687?page=com.atlassian.jira.plugin.... ] Andre Dietisheim updated FORGE-687: ----------------------------------- Description: If you want to prompt the user to provide some valid java package you'd specify PromptType.JAVA_PACKAGE. Unfortunately this prompt type considers the empty string as invalid package even though I'd argue that this is the default package. If I ask the user for the package, scaffolded resources would get created to, I'd do: {code} prompt.promptCommon(target package: ", PromptType.JAVA_PACKAGE, project.getFacet(JavaSourceFacet.class).getBasePackageResource().toString()) {code} If I have no valid packageResource (ex. forge would return an invalid base package) I'd want to suggest the user to put his sources into the default package (for a maven project: src/main/java). I'd then feed a "" as default to the prompt: {code} prompt.promptCommon(target package: ", PromptType.JAVA_PACKAGE, "") {code} Unfortunately the PromptType.JAVA_PACKAGE would not validate the empty string. It would tell me that this is not a valid package. was:If you want to prompt the user to provide some valid java package you'd specify PromptType.JAVA_PACKAGE. Unfortunately this prompt type considers the empty string as invalid package even though I'd argue that this is the default package. > PromptType.JAVA_PACKAGE should support default package > ------------------------------------------------------ > > Key: FORGE-687 > URL: https://issues.jboss.org/browse/FORGE-687 > Project: Forge > Issue Type: Bug > Components: Shell > Affects Versions: 1.0.5.Final > Reporter: Andre Dietisheim > > If you want to prompt the user to provide some valid java package you'd specify PromptType.JAVA_PACKAGE. Unfortunately this prompt type considers the empty string as invalid package even though I'd argue that this is the default package. > If I ask the user for the package, scaffolded resources would get created to, I'd do: > {code} > prompt.promptCommon(target package: ", PromptType.JAVA_PACKAGE, project.getFacet(JavaSourceFacet.class).getBasePackageResource().toString()) > {code} > If I have no valid packageResource (ex. forge would return an invalid base package) I'd want to suggest the user to put his sources into the default package (for a maven project: src/main/java). I'd then feed a "" as default to the prompt: > {code} > prompt.promptCommon(target package: ", PromptType.JAVA_PACKAGE, "") > {code} > Unfortunately the PromptType.JAVA_PACKAGE would not validate the empty string. It would tell me that this is not a valid package. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-687) PromptType.JAVA_PACKAGE should support default package

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/FORGE-687?page=com.atlassian.jira.plugin.... ] Andre Dietisheim commented on FORGE-687: ---------------------------------------- By default package I mean the source folder root. For a maven project this would be src/main/java. > PromptType.JAVA_PACKAGE should support default package > ------------------------------------------------------ > > Key: FORGE-687 > URL: https://issues.jboss.org/browse/FORGE-687 > Project: Forge > Issue Type: Bug > Components: Shell > Affects Versions: 1.0.5.Final > Reporter: Andre Dietisheim > > If you want to prompt the user to provide some valid java package you'd specify PromptType.JAVA_PACKAGE. Unfortunately this prompt type considers the empty string as invalid package even though I'd argue that this is the default package. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-687) PromptType.JAVA_PACKAGE should support default package

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-687?page=com.atlassian.jira.plugin.... ] George Gastaldi commented on FORGE-687: --------------------------------------- Can you please clarify what do you mean by "default package"? Should it be the current package in shell or the project's main package (specified when a new project is created) ? > PromptType.JAVA_PACKAGE should support default package > ------------------------------------------------------ > > Key: FORGE-687 > URL: https://issues.jboss.org/browse/FORGE-687 > Project: Forge > Issue Type: Bug > Components: Shell > Affects Versions: 1.0.5.Final > Reporter: Andre Dietisheim > > If you want to prompt the user to provide some valid java package you'd specify PromptType.JAVA_PACKAGE. Unfortunately this prompt type considers the empty string as invalid package even though I'd argue that this is the default package. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-686) JavaSourceFacet eventualls returns an invalid base package

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-686?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-686: ---------------------------------- Fix Version/s: 1.1.1.Final > JavaSourceFacet eventualls returns an invalid base package > ---------------------------------------------------------- > > Key: FORGE-686 > URL: https://issues.jboss.org/browse/FORGE-686 > Project: Forge > Issue Type: Bug > Components: Resources API > Affects Versions: 1.0.5.Final > Reporter: Andre Dietisheim > Fix For: 1.1.1.Final > > -- 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, 7 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues September 2012