March 2013 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-565) Persistence plugin needs to better guide users through a custom database configuration

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-565?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-565: ---------------------------------- Fix Version/s: 1.2.3.Final (was: 1.2.2.Final) > Persistence plugin needs to better guide users through a custom database configuration > -------------------------------------------------------------------------------------- > > Key: FORGE-565 > URL: https://issues.jboss.org/browse/FORGE-565 > Project: Forge > Issue Type: Enhancement > Components: Builtin Plugins > Affects Versions: 1.0.4.Final > Reporter: Lincoln Baxter III > Priority: Minor > Labels: Starter > Fix For: 1.2.3.Final > > > In order to use the PostgreSQL (or any custom) database, you'll need to skip the --container JBOSS_AS7 parameter; otherwise, this will override the data-source configuration as seen in the INFO messages: > {code}***INFO*** Setting transaction-type="JTA" > ***INFO*** Using example data source [java:jboss/datasources/ExampleDS]{code} > We should probably make this more clear, or perhaps create a warning or error scenario instead of INFO. When you remove the --container parameter. > It should be much clearer that you may need to use some of the extended parameters like --jndiName and so forth. > This can probably be done by updating the PersistencePlugin and related classes: > https://github.com/forge/core/blob/master/javaee-impl/src/main/java/org/j... -- 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (FORGE-518) projectFactory.createProjet doesn't work out of embeded plugins

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-518?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-518: ---------------------------------- Fix Version/s: 1.2.3.Final (was: 1.2.2.Final) > projectFactory.createProjet doesn't work out of embeded plugins > --------------------------------------------------------------- > > Key: FORGE-518 > URL: https://issues.jboss.org/browse/FORGE-518 > Project: Forge > Issue Type: Bug > Components: Builtin Plugins, Forge Build > Affects Versions: 1.0.0.Final > Environment: Windows XP Professional Service Pack 3 - 32 bits > Reporter: Guillaume Gustin > Labels: projectFactory.createProject > Fix For: 1.2.3.Final > > Attachments: ajf-forge.zip, aTest-compacted.zip, forge-screenshot.png > > > I want to create a new plugin which allow to create a solution (set of projects) based on a specific solution model. But when the forge execute the project building code "projectFactory.createProject(targetProjectDir, DependencyFacet.class, MetadataFacet.class, JavaSourceFacet.class, ResourceFacet.class)" i receive the exception "org.jboss.forge.project.ProjectModelException" with the message "Could not create Maven project building request" > When i fire my new plugin, my forge promps is "[no project] myTempdir $ ", I have the same exception when I copy the "new-project plugin" as "new-new-project plugin". -- 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (FORGE-524) Scaffolding an entity with enum uses a <f:selectItem> for each enum value

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-524?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-524: ---------------------------------- Fix Version/s: 1.2.3.Final (was: 1.2.2.Final) > Scaffolding an entity with enum uses a <f:selectItem> for each enum value > ------------------------------------------------------------------------- > > Key: FORGE-524 > URL: https://issues.jboss.org/browse/FORGE-524 > Project: Forge > Issue Type: Bug > Components: Scaffold > Affects Versions: 1.0.6.Final > Reporter: George Gastaldi > Fix For: 1.2.3.Final > > > When scaffolding an entity with a enumeration as an attribute (displaying it as a selectOneMenu), the enum values are placed directly inside the XHTML. > This is a bad thing, since when you modify the enumeration you MUST change the XHTML also. The scaffolding should use <f:selectItems> instead -- 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (FORGE-604) Add support for Java EE 6 Full Profile

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-604?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-604: ---------------------------------- Fix Version/s: 1.2.3.Final (was: 1.2.2.Final) > Add support for Java EE 6 Full Profile > -------------------------------------- > > Key: FORGE-604 > URL: https://issues.jboss.org/browse/FORGE-604 > Project: Forge > Issue Type: Task > Components: Java EE APIs > Affects Versions: 1.0.5.Final > Environment: All > Reporter: Christopher Volk > Fix For: 1.2.3.Final > > > Add support for Java EE 6 Full profile, including multi-module support (cli/maven/ear) and EAR packaging. > The EAR packaging should be fairly "easy" to implement. The maven side of multi-module should be similarly "easy". CLI multi-module support is something I would expect to take up most of this effort. > I believe this to be a critical feature - serious enterprise software requires Full Profile, and Forge would be even more useful for bootstrapping and developing against the Full Profile than even the Web Profile. I know that almost all the apps I work on professionally require Full Profile. > This would be a real home run, IMHO, especially in the wake of JBoss AS7.1's Full Profile Compliance :-) -- 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (FORGE-607) ResourceException after pick-up command and subsequently hitting 'up arrow' and 'tab'

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-607?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-607: ---------------------------------- Fix Version/s: 1.2.3.Final (was: 1.2.2.Final) > ResourceException after pick-up command and subsequently hitting 'up arrow' and 'tab' > ------------------------------------------------------------------------------------- > > Key: FORGE-607 > URL: https://issues.jboss.org/browse/FORGE-607 > Project: Forge > Issue Type: Bug > Components: Shell > Affects Versions: 1.0.5.Final > Reporter: Koen Aers > Fix For: 1.2.3.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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (FORGE-581) Scaffold source generation fails if project groupId not a valid package name

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-581?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-581: ---------------------------------- Fix Version/s: 1.2.3.Final (was: 1.2.2.Final) > Scaffold source generation fails if project groupId not a valid package name > ---------------------------------------------------------------------------- > > Key: FORGE-581 > URL: https://issues.jboss.org/browse/FORGE-581 > Project: Forge > Issue Type: Bug > Components: Builtin Plugins > Affects Versions: 1.0.4.Final > Reporter: Thomas Frühbeck > Labels: HackNight > Fix For: 1.2.3.Final > > > MavenJavaSourceFacet too optimistic about naming of the artifact groupId. > The automatically generated package name is syntactically unchecked: > @Override > public String getBasePackage() > { > return project.getFacet(MavenCoreFacet.class).getMavenProject().getGroupId(); > } > . > . > [regress-pkg] regress-pkg $ scaffold from-entity at.tfr.regress.model.* > ***INFO*** Using currently installed scaffold [faces] > ***ERROR*** [scaffold from-entity] Error generating default scaffolding: null > ??? > [regress-pkg] regress-pkg $ set VERBOSE true > [regress-pkg] regress-pkg $ scaffold from-entity at.tfr.regress.model.* > ***INFO*** Using currently installed scaffold [faces] > ***ERROR*** [scaffold from-entity] Error generating default scaffolding: null > org.jboss.forge.shell.exceptions.CommandExecutionException: Error generating default scaffolding: null > at org.jboss.forge.shell.command.Execution.perform(Execution.java:154) > at org.jboss.forge.shell.command.fshparser.FSHRuntime.run(FSHRuntime.java:125) > at org.jboss.forge.shell.command.fshparser.FSHRuntime.run(FSHRuntime.java:63) > <SNIP> > at java.lang.Thread.run(Thread.java:722) > Caused by: java.lang.reflect.InvocationTargetException > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.jboss.forge.shell.command.Execution.perform(Execution.java:150) > ... 31 more > Caused by: java.lang.RuntimeException: Error generating default scaffolding: null > at org.jboss.forge.scaffold.faces.FacesScaffold.generateFromEntity(FacesScaffold.java:341) > at org.jboss.forge.scaffold.plugins.ScaffoldPlugin.generateFromEntity(ScaffoldPlugin.java:187) > ... 36 more > Caused by: java.lang.IllegalArgumentException > at org.eclipse.jdt.core.dom.SimpleName.setIdentifier(SimpleName.java:190) > at org.eclipse.jdt.core.dom.AST.newSimpleName(AST.java:1269) > at org.eclipse.jdt.core.dom.AST.newName(AST.java:1389) > at org.jboss.forge.parser.java.impl.AbstractJavaSource.setPackage(AbstractJavaSource.java:491) > at org.jboss.forge.parser.java.impl.AbstractJavaSource.setPackage(AbstractJavaSource.java:65) > at org.jboss.forge.scaffold.faces.FacesScaffold.generateFromEntity(FacesScaffold.java:275) -- 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (FORGE-606) Provide interactive command to resolve cyclic graphs in REST endpoints generated from entities

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-606?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-606: ---------------------------------- Fix Version/s: 1.2.3.Final (was: 1.2.2.Final) > Provide interactive command to resolve cyclic graphs in REST endpoints generated from entities > ---------------------------------------------------------------------------------------------- > > Key: FORGE-606 > URL: https://issues.jboss.org/browse/FORGE-606 > Project: Forge > Issue Type: Feature Request > Components: Blessed Plugins > Reporter: Dan Allen > Assignee: Vineet Reynolds > Fix For: 1.2.3.Final > > > Currently the REST plugin generates broken endpoints if there are cyclic references in the JPA entities. Forge should provide a plugin to hep the developer resolve these references to get past this bump in the road. -- 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (FORGE-569) Skipping an installed plugin when asking to install a plugin or provide a test for installed plugins

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-569?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-569: ---------------------------------- Fix Version/s: 1.2.3.Final (was: 1.2.2.Final) > Skipping an installed plugin when asking to install a plugin or provide a test for installed plugins > ---------------------------------------------------------------------------------------------------- > > Key: FORGE-569 > URL: https://issues.jboss.org/browse/FORGE-569 > Project: Forge > Issue Type: Enhancement > Components: Usability > Affects Versions: 1.0.4.Final > Reporter: Jason Porter > Fix For: 1.2.3.Final > > > When you install a plugin there should be a way to tell it to skip the install if the plugin has been installed already, or provide a command to test for the existence of a plugin. -- 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (FORGE-601) XML Parser should support inclusion of elements beginning with '<!' (e.g. DTDs)

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-601?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-601: ---------------------------------- Fix Version/s: 1.2.3.Final (was: 1.2.2.Final) > XML Parser should support inclusion of elements beginning with '<!' (e.g. DTDs) > ------------------------------------------------------------------------------- > > Key: FORGE-601 > URL: https://issues.jboss.org/browse/FORGE-601 > Project: Forge > Issue Type: Enhancement > Components: Parsers / File Manipulation > Affects Versions: 1.0.5.Final > Environment: Fedora 15 (64-bit), Java 1.7 > Reporter: Ryan Bradley > Fix For: 1.2.3.Final > > > In my plugin, I use Apache Tiles, which require a reference to a DTD in their layouts/views XML declaration files. I am trying to create these files from a template, and then add more view/layout definitions later in the plugin's workflow. > However, depending on how the DTD reference (in the format <!....>) is added, it is either omitted from the generated file or causes an exception when the XML Parser tries to parse the file for the root node. -- 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (FORGE-583) Include Forge JavaDoc in Distribution download.

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-583?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-583: ---------------------------------- Fix Version/s: 1.2.3.Final (was: 1.2.2.Final) > Include Forge JavaDoc in Distribution download. > ----------------------------------------------- > > Key: FORGE-583 > URL: https://issues.jboss.org/browse/FORGE-583 > Project: Forge > Issue Type: Task > Components: Documentation, Forge Build > Affects Versions: 1.0.5.Final > Reporter: Lincoln Baxter III > Assignee: Ivan St. Ivanov > Labels: starter > Fix For: 1.2.3.Final > > > The Forge API JavaDocs should be included in the Forge Distribution. -- 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

13 years, 1 month

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues March 2013