April 2012 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-220) Forge should listen to filesystem changes on the system and publish events for plugins to observe

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-220?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III updated FORGE-220: ------------------------------------- Fix Version/s: 2.0.0.Alpha1 > Forge should listen to filesystem changes on the system and publish events for plugins to observe > -------------------------------------------------------------------------------------------------- > > Key: FORGE-220 > URL: https://issues.jboss.org/browse/FORGE-220 > Project: Forge > Issue Type: Feature Request > Components: JBoss Tools Integration, Plugin API, Resources API > Affects Versions: 1.0.0.Alpha3 > Reporter: Lincoln Baxter III > Fix For: 2.0.0.Alpha1 > > > {code}Event<ResourceCreated> > Event<ResourceModified> > Event<ResourceDeleted>{code} > etc... -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-217) Need an auto-update feature for plugins and core libraries

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-217?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III updated FORGE-217: ------------------------------------- Fix Version/s: 2.0.0.Alpha1 > Need an auto-update feature for plugins and core libraries > ---------------------------------------------------------- > > Key: FORGE-217 > URL: https://issues.jboss.org/browse/FORGE-217 > Project: Forge > Issue Type: Feature Request > Components: Builtin Plugins > Affects Versions: 1.0.0.Alpha2 > Reporter: Lincoln Baxter III > Fix For: 2.0.0.Alpha1 > > > Ability to tell forge to auto-update and restart itself at runtime. Prevents downloading new distributions every release. Just tell it which version to "become" or "upgrade to". -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-240) Provide ability to reference project settings through EL in Default @Option params:

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-240?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III updated FORGE-240: ------------------------------------- Fix Version/s: 2.0.0.Alpha1 > Provide ability to reference project settings through EL in Default @Option params: > ------------------------------------------------------------------------------------ > > Key: FORGE-240 > URL: https://issues.jboss.org/browse/FORGE-240 > Project: Forge > Issue Type: Feature Request > Components: Plugin API > Affects Versions: 1.0.0.Alpha2 > Reporter: Lincoln Baxter III > Fix For: 2.0.0.Alpha1 > > > @Option(default="org.${project.name}") String defaultPackage -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-525) project add-dependency should accept properties

by Jason Porter (JIRA)

Jason Porter created FORGE-525: ---------------------------------- Summary: project add-dependency should accept properties Key: FORGE-525 URL: https://issues.jboss.org/browse/FORGE-525 Project: Forge Issue Type: Enhancement Components: Maven Integration Affects Versions: 1.0.2.Final Reporter: Jason Porter Here's some sample input: {code} $ project set-property --name arquillian.version --value 1.0.0.CR6 Set property [arquillian.version=1.0.0.CR6] $ project add-dependency org.jboss.arquillian:arquillian-bom:::${arquillian.version} ***INFO*** The command [add-dependency] takes [1] unnamed argument(s), but found [2]. ***INFO*** Swallowed unknown token [{] for command [add-dependency]. ***INFO*** Swallowed unknown token [arquillian.version] for command [add-dependency]. ***INFO*** Swallowed unknown token [}] for command [add-dependency]. ***INFO*** Could not parse [org.jboss.arquillian:arquillian-bom:::$]... please try again... ? [[ groupId:artifactId {:version :scope :packaging} ] (of type org.jboss.forge.project.dependencies.Dependency)]: [killed] ***INFO*** Aborted. $ project add-dependency "org.jboss.arquillian:arquillian-bom:::${arquillian.version}" ***INFO*** Could not parse [org.jboss.arquillian:arquillian-bom:::${arquillian.version}]... please try again... {code} Either one of those two should work. -- 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

12 years, 8 months

2
6
0 / 0

[JBoss JIRA] (FORGE-523) field plugin fails to create enum attribute

by George Gastaldi (JIRA)

George Gastaldi created FORGE-523: ------------------------------------- Summary: field plugin fails to create enum attribute Key: FORGE-523 URL: https://issues.jboss.org/browse/FORGE-523 Project: Forge Issue Type: Bug Reporter: George Gastaldi Having an entity named X and an enumeration named Y, running {code} field custom --named enumAtt --type Y.java {code} creates the following entry: {code} @Column private java enumAtt; .. getters and setters ... {code} it should read: {code} @Column @Enumerated private Y enumAtt; {code} -- 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

12 years, 8 months

3
10
0 / 0

[JBoss JIRA] (FORGE-527) CommandExecutionException while creating new project

by Pavol Srna (JIRA)

Pavol Srna created FORGE-527: -------------------------------- Summary: CommandExecutionException while creating new project Key: FORGE-527 URL: https://issues.jboss.org/browse/FORGE-527 Project: Forge Issue Type: Bug Affects Versions: 1.0.1.Final Reporter: Pavol Srna Priority: Critical Fix For: 1.0.2.Final I hit on this here: https://issues.jboss.org/browse/JBIDE-11178 As Lincoln said the fix should go into 1.0.1 and it is still not there even in 1.0.2. Can you guys please have a look? -- 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

12 years, 8 months

3
9
0 / 0

[JBoss JIRA] (FORGE-532) Maven warning when build starts

by George Gastaldi (JIRA)

George Gastaldi created FORGE-532: ------------------------------------- Summary: Maven warning when build starts Key: FORGE-532 URL: https://issues.jboss.org/browse/FORGE-532 Project: Forge Issue Type: Bug Affects Versions: 1.0.2.Final Reporter: George Gastaldi Assignee: George Gastaldi Priority: Minor Fix For: 1.0.3.Final When you run mvn install on forge, the following warning appears: {code} [INFO] Scanning for projects... [WARNING] [WARNING] Some problems were encountered while building the effective model for org.jboss.forge:forge-test-harness-web:jar:1.0.3-SNAPSHOT [WARNING] 'dependencies.dependency.scope' for org.jboss.arquillian:arquillian-bom:pom must be one of [provided, compile, runtime, test, system] but is 'import'. @ line 57, column 17 [WARNING] [WARNING] It is highly recommended to fix these problems because they threaten the stability of your build. [WARNING] [WARNING] For this reason, future Maven versions might no longer support building such malformed projects. {code} -- 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

12 years, 8 months

1
3
0 / 0

[JBoss JIRA] (FORGE-530) Group Faces Servlet url-patterns into a single servlet-mapping

by George Gastaldi (JIRA)

George Gastaldi created FORGE-530: ------------------------------------- Summary: Group Faces Servlet url-patterns into a single servlet-mapping Key: FORGE-530 URL: https://issues.jboss.org/browse/FORGE-530 Project: Forge Issue Type: Enhancement Reporter: George Gastaldi Priority: Trivial When running faces setup, the following entry is generated on web.xml (if asked so): {code:xml} <servlet-mapping> <servlet-name>Faces Servlet</servlet-name> <url-pattern>*.xhtml</url-pattern> </servlet-mapping> <servlet-mapping> <servlet-name>Faces Servlet</servlet-name> <url-pattern>/faces/*</url-pattern> </servlet-mapping> {code} Since Servlet 2.5, several url-patterns may be grouped into a single servlet-mapping, so that the web.xml becomes smaller: {code:xml} <servlet-mapping> <servlet-name>Faces Servlet</servlet-name> <url-pattern>*.xhtml</url-pattern> <url-pattern>/faces/*</url-pattern> </servlet-mapping> {code} The method _org.jboss.forge.spec.javaee.jsf.ServletMappingHelper.createMappingIfNotExists(Node, Node, String)_ should be reviewed to accomplish that. -- 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

12 years, 8 months

2
5
0 / 0

[JBoss JIRA] (FORGE-522) faces setup ERROR: null without explanation

by Hendy Irawan (JIRA)

Hendy Irawan created FORGE-522: ---------------------------------- Summary: faces setup ERROR: null without explanation Key: FORGE-522 URL: https://issues.jboss.org/browse/FORGE-522 Project: Forge Issue Type: Bug Components: Java EE APIs Affects Versions: 1.0.1.Final Environment: Ubuntu 11.10 64-bit, JBoss AS 7.1.1 Reporter: Hendy Irawan Faces setup not working without any error message : {code} [dsembed] dsembed $ faces setup Warning: The encoding 'UTF-8' is not supported by the Java runtime. ? Do you also want to install the Faces servlet and mapping? [y/N] y Warning: The encoding 'UTF-8' is not supported by the Java runtime. ***ERROR*** [faces setup] null {code} The project to reproduce is here: https://github.com/soluvas/dsembed/zipball/faces-setup-bug The problem is...... I exited Forge then restarted it then I try 'faces setup' again and now it works: {code} faces setup Warning: The encoding 'UTF-8' is not supported by the Java runtime. Warning: The encoding 'UTF-8' is not supported by the Java runtime. ? Do you also want to install the Faces servlet and mapping? [y/N] y Warning: The encoding 'UTF-8' is not supported by the Java runtime. Warning: The encoding 'UTF-8' is not supported by the Java runtime. Warning: The encoding 'UTF-8' is not supported by the Java runtime. ***SUCCESS*** JavaServer Faces is installed. Wrote /home/ceefour/git/dsembed/src/main/webapp/WEB-INF/web.xml {code} So what was it..? -- 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

12 years, 8 months

3
3
0 / 0

[JBoss JIRA] (FORGE-32) FSHParser is too agressive (destroys command input)

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-32?page=com.atlassian.jira.plugin.s... ] Lincoln Baxter III updated FORGE-32: ------------------------------------ Fix Version/s: 1.0.3.Final (was: 1.0.2.Final) > FSHParser is too agressive (destroys command input) > --------------------------------------------------- > > Key: FORGE-32 > URL: https://issues.jboss.org/browse/FORGE-32 > Project: Forge > Issue Type: Bug > Components: Shell > Affects Versions: 1.0.0.Beta2 > Reporter: Lincoln Baxter III > Assignee: Mike Brock > Priority: Critical > Fix For: 1.0.3.Final > > > FSHParser is breaking up statements that clearly are not scripts: > [example] Customer.java $ prettyfaces mapping --resource /scaffold/customer/view.xhtml --pattern /customer/#{id} --id viewCustomer > ***INFO*** The command [mapping] takes [0] unnamed argument(s), but found [1]. > ***INFO*** Swallowed unknown token [{] for command [mapping]. > ***INFO*** Swallowed unknown token [id] for command [mapping]. > ***INFO*** Swallowed unknown token [}] for command [mapping]. > ... etc > [example] Customer.java $ -- 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

12 years, 8 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues April 2012