August 2012 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-629) Forge should allow filtering dependencies

by George Gastaldi (JIRA)

George Gastaldi created FORGE-629: ------------------------------------- Summary: Forge should allow filtering dependencies Key: FORGE-629 URL: https://issues.jboss.org/browse/FORGE-629 Project: Forge Issue Type: Feature Request Reporter: George Gastaldi Assignee: George Gastaldi Forge should have an API which allows filtering dependencies, like for example, ignoring snapshots when prompting for a version. -- 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

13 years, 8 months

1
4
0 / 0

[JBoss JIRA] (FORGE-624) Source folder are not read from POM

by Jérémie Lagarde (JIRA)

Jérémie Lagarde created FORGE-624: ------------------------------------- Summary: Source folder are not read from POM Key: FORGE-624 URL: https://issues.jboss.org/browse/FORGE-624 Project: Forge Issue Type: Bug Components: Maven Integration Reporter: Jérémie Lagarde The name of the source directory is hardcoded into the MavenJavaSourceFacet class. It would be interesting to read it directly in the pom file. public DirectoryResource getSourceFolder() { return projectRoot.getChildDirectory("src" + File.separator + "main" + File.separator + "java"); } @Override public DirectoryResource getTestSourceFolder() { DirectoryResource projectRoot = project.getProjectRoot(); return projectRoot.getChildDirectory("src" + File.separator + "test" + File.separator + "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

13 years, 8 months

2
4
0 / 0

[JBoss JIRA] (FORGE-628) CommandInterceptor isn't really intercepting

by George Gastaldi (JIRA)

George Gastaldi created FORGE-628: ------------------------------------- Summary: CommandInterceptor isn't really intercepting Key: FORGE-628 URL: https://issues.jboss.org/browse/FORGE-628 Project: Forge Issue Type: Story Reporter: George Gastaldi The design of the org.jboss.forge.shell.spi.CommandInterceptor class seems misleading. Actually it's not possible to intercept a command execution. It only transforms the input before executing. Maybe it should be called CommandTransformer. -- 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

13 years, 8 months

2
5
0 / 0

[JBoss JIRA] (FORGE-619) bad support of field with the following naming pattern aFIELD

by Richard Kennard (JIRA)

[ https://issues.jboss.org/browse/FORGE-619?page=com.atlassian.jira.plugin.... ] Richard Kennard commented on FORGE-619: --------------------------------------- Link is attached to this JIRA as 'Forum Reference': https://community.jboss.org/message/751887 > bad support of field with the following naming pattern aFIELD > ------------------------------------------------------------- > > Key: FORGE-619 > URL: https://issues.jboss.org/browse/FORGE-619 > Project: Forge > Issue Type: Bug > Reporter: Anthony Patricio > Assignee: Richard Kennard > Fix For: 1.0.6.Final > > > Step to reproduce the issue, create an entity from forge with a field named aFIELD > Check the get/set generated method, > As per the javabean naming convention, we should have getaFIELD,setaFIELD but we have getAFIELD setAFIELD. > When generated by eclipse then scaffolding, problem can appear, more important if the id is following the same naming pattern. > Richard fixed almost everything related to meta widget. > However the ForgePropertyStyle still needs some polishing. > Check the forum reference. > Cheers -- 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

13 years, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-605) Add a built-in shell command to copy files (cp)

by Dan Allen (JIRA)

Dan Allen created FORGE-605: ------------------------------- Summary: Add a built-in shell command to copy files (cp) Key: FORGE-605 URL: https://issues.jboss.org/browse/FORGE-605 Project: Forge Issue Type: Feature Request Components: Builtin Plugins Affects Versions: 1.0.5.Final Reporter: Dan Allen Create a built-in plugin that provides the cp command to copy a file from one location to another. The mv command can be used as a reference. -- 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

13 years, 8 months

3
2
0 / 0

[JBoss JIRA] (FORGE-619) bad support of field with the following naming pattern aFIELD

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-619?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III commented on FORGE-619: ------------------------------------------ I don't see a forum topic with that name. Do you have a link? Thanks, sorry. > bad support of field with the following naming pattern aFIELD > ------------------------------------------------------------- > > Key: FORGE-619 > URL: https://issues.jboss.org/browse/FORGE-619 > Project: Forge > Issue Type: Bug > Reporter: Anthony Patricio > Assignee: Richard Kennard > Fix For: 1.0.6.Final > > > Step to reproduce the issue, create an entity from forge with a field named aFIELD > Check the get/set generated method, > As per the javabean naming convention, we should have getaFIELD,setaFIELD but we have getAFIELD setAFIELD. > When generated by eclipse then scaffolding, problem can appear, more important if the id is following the same naming pattern. > Richard fixed almost everything related to meta widget. > However the ForgePropertyStyle still needs some polishing. > Check the forum reference. > Cheers -- 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

13 years, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-97) Invoking commands using minus sign seems to break "run" plugin

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-97?page=com.atlassian.jira.plugin.s... ] Lincoln Baxter III commented on FORGE-97: ----------------------------------------- Great fix!!! > Invoking commands using minus sign seems to break "run" plugin > -------------------------------------------------------------- > > Key: FORGE-97 > URL: https://issues.jboss.org/browse/FORGE-97 > Project: Forge > Issue Type: Bug > Components: Shell > Affects Versions: 1.0.0.Alpha4 > Reporter: Lincoln Baxter III > Assignee: George Gastaldi > Fix For: 1.0.6.Final > > > {code} > [no project] JAX $ > [no project] JAX $ run forge-conftrack-demo.fsh > ***ERROR*** Exception encountered: [Error: illegal function name or use of reserved word] > [Near : {... -demo_fsh_1064826090() {currentStep = 1;v = SHELL. ....}] > ^ > [Line: 1, Column: 39] (type "set VERBOSE true" to enable stack traces) > [no project] JAX $ run demo.fsh > ? Start at which step? > {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

13 years, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-619) bad support of field with the following naming pattern aFIELD

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-619?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III reopened FORGE-619: -------------------------------------- > bad support of field with the following naming pattern aFIELD > ------------------------------------------------------------- > > Key: FORGE-619 > URL: https://issues.jboss.org/browse/FORGE-619 > Project: Forge > Issue Type: Bug > Reporter: Anthony Patricio > Assignee: Richard Kennard > Fix For: 1.0.6.Final > > > Step to reproduce the issue, create an entity from forge with a field named aFIELD > Check the get/set generated method, > As per the javabean naming convention, we should have getaFIELD,setaFIELD but we have getAFIELD setAFIELD. > When generated by eclipse then scaffolding, problem can appear, more important if the id is following the same naming pattern. > Richard fixed almost everything related to meta widget. > However the ForgePropertyStyle still needs some polishing. > Check the forum reference. > Cheers -- 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

13 years, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-619) bad support of field with the following naming pattern aFIELD

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-619?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III commented on FORGE-619: ------------------------------------------ Ok. I'll check it out. > bad support of field with the following naming pattern aFIELD > ------------------------------------------------------------- > > Key: FORGE-619 > URL: https://issues.jboss.org/browse/FORGE-619 > Project: Forge > Issue Type: Bug > Reporter: Anthony Patricio > Assignee: Richard Kennard > Fix For: 1.0.6.Final > > > Step to reproduce the issue, create an entity from forge with a field named aFIELD > Check the get/set generated method, > As per the javabean naming convention, we should have getaFIELD,setaFIELD but we have getAFIELD setAFIELD. > When generated by eclipse then scaffolding, problem can appear, more important if the id is following the same naming pattern. > Richard fixed almost everything related to meta widget. > However the ForgePropertyStyle still needs some polishing. > Check the forum reference. > Cheers -- 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

13 years, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-619) bad support of field with the following naming pattern aFIELD

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-619?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III updated FORGE-619: ------------------------------------- Status: Closed (was: Pull Request Sent) Fix Version/s: 1.0.6.Final Resolution: Done > bad support of field with the following naming pattern aFIELD > ------------------------------------------------------------- > > Key: FORGE-619 > URL: https://issues.jboss.org/browse/FORGE-619 > Project: Forge > Issue Type: Bug > Reporter: Anthony Patricio > Assignee: Richard Kennard > Fix For: 1.0.6.Final > > > Step to reproduce the issue, create an entity from forge with a field named aFIELD > Check the get/set generated method, > As per the javabean naming convention, we should have getaFIELD,setaFIELD but we have getAFIELD setAFIELD. > When generated by eclipse then scaffolding, problem can appear, more important if the id is following the same naming pattern. > Richard fixed almost everything related to meta widget. > However the ForgePropertyStyle still needs some polishing. > Check the forum reference. > Cheers -- 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

13 years, 8 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues August 2012