September 2012 - forge-issues - Jboss List Archives

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

by Jason Porter (JIRA)

Jason Porter created FORGE-569: ---------------------------------- Summary: 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 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: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 5 months

4
6
0 / 0

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

by Thomas Frühbeck (JIRA)

Thomas Frühbeck created FORGE-581: ------------------------------------- Summary: 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 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: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 5 months

4
7
0 / 0

[JBoss JIRA] (FORGE-576) Refactor RunUrlPluginTest

by George Gastaldi (JIRA)

George Gastaldi created FORGE-576: ------------------------------------- Summary: Refactor RunUrlPluginTest Key: FORGE-576 URL: https://issues.jboss.org/browse/FORGE-576 Project: Forge Issue Type: Enhancement Reporter: George Gastaldi org.jboss.forge.shell.test.plugins.builtin.RunUrlPluginTest should be refactored to boot up an embedded server and host a single file from it. The idea is to test it locally, though still using HTTP. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 5 months

3
4
0 / 0

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

by Lincoln Baxter III (JIRA)

Lincoln Baxter III created FORGE-565: ---------------------------------------- Summary: 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 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: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 5 months

3
4
0 / 0

[JBoss JIRA] (FORGE-554) Tab AutoCompletion in forge ignores already typed options

by George Gastaldi (JIRA)

George Gastaldi created FORGE-554: ------------------------------------- Summary: Tab AutoCompletion in forge ignores already typed options Key: FORGE-554 URL: https://issues.jboss.org/browse/FORGE-554 Project: Forge Issue Type: Bug Reporter: George Gastaldi Inside a project, when you "cd" and press <TAB> to navigate between nested folders, the prompt resets to "cd" only, losing the folders previously selected when typing. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 5 months

4
8
0 / 0

[JBoss JIRA] (FORGE-553) Forge Console does not display special characters

by George Gastaldi (JIRA)

George Gastaldi created FORGE-553: ------------------------------------- Summary: Forge Console does not display special characters Key: FORGE-553 URL: https://issues.jboss.org/browse/FORGE-553 Project: Forge Issue Type: Bug Reporter: George Gastaldi When you try typing accented characters, like áéíóú, they are erroneously displayed in Forge console. There must be a way to set the encoding or leave as default -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 5 months

4
13
0 / 0

[JBoss JIRA] (FORGE-659) MovePlugin fails while moving java classes

by George Gastaldi (JIRA)

George Gastaldi created FORGE-659: ------------------------------------- Summary: MovePlugin fails while moving java classes Key: FORGE-659 URL: https://issues.jboss.org/browse/FORGE-659 Project: Forge Issue Type: Bug Components: Builtin Plugins Reporter: George Gastaldi Fix For: 2.0.0.Alpha1 Having a class in a package, when you try to move that class to another package, the following error is thrown: {code:java} [exemplo] model $ ls Cidade.java UnidadeFederativa.java [exemplo] model $ mv Cidade.java ex01/Cidade.java ***ERROR*** [mv] no such child: null {code} Probably we should give a better description, or say that this feature isn't supported yet. Moving a class to another package includes refactoring the whole project, in order to avoid compilation errors. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 5 months

2
4
0 / 0

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

by Dan Allen (JIRA)

Dan Allen created FORGE-606: ------------------------------- Summary: 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 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: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 5 months

4
5
0 / 0

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

by Ryan Bradley (JIRA)

Ryan Bradley created FORGE-601: ---------------------------------- Summary: 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: Future 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: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 5 months

3
5
0 / 0

[JBoss JIRA] (FORGE-593) Forge swallows first character of user input after restarting (typically from plugin installation)

by Lincoln Baxter III (JIRA)

11 years, 5 months

3
5
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues September 2012