September 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 George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-220?page=com.atlassian.jira.plugin.... ] George Gastaldi edited comment on FORGE-220 at 9/25/12 9:29 PM: ---------------------------------------------------------------- This could be a nice solution as well: http://jnotify.sourceforge.net/, however due to native system calls it may not be desirable at all. But it's nice to mention it in this issue :) was (Author: gastaldi): This could be a nice solution as well: http://jnotify.sourceforge.net/ > 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 For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

1
0
0 / 0

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

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-220?page=com.atlassian.jira.plugin.... ] George Gastaldi commented on FORGE-220: --------------------------------------- This could be a nice solution as well: http://jnotify.sourceforge.net/ > 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 For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-682) ShellPrompt has fixed set of PromptTypes, should be extensible

by Andre Dietisheim (JIRA)

Andre Dietisheim created FORGE-682: -------------------------------------- Summary: ShellPrompt has fixed set of PromptTypes, should be extensible Key: FORGE-682 URL: https://issues.jboss.org/browse/FORGE-682 Project: Forge Issue Type: Enhancement Affects Versions: 1.0.5.Final Reporter: Andre Dietisheim If a plugin wants to prompt the user to supply some settings it'll use: {code:title=ShellPrompt} String promptCommon(String message, PromptType type); {code} PromptType is what the prompt would use to validate the user input against. Unfortunately PromptType is an enum so there's no way for a plugin to provide it's own prompt type. -- 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, 7 months

2
3
0 / 0

[JBoss JIRA] (FORGE-681) forge.xml should not be created in non-plugin projects

by George Gastaldi (JIRA)

George Gastaldi created FORGE-681: ------------------------------------- Summary: forge.xml should not be created in non-plugin projects Key: FORGE-681 URL: https://issues.jboss.org/browse/FORGE-681 Project: Forge Issue Type: Feature Request Components: Usability Affects Versions: 1.1.0.Final Reporter: George Gastaldi Assignee: George Gastaldi Priority: Minor Fix For: 1.1.1.Final The forge.xml file is useless on projects which are not Forge plugins. It should not be created by default -- 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, 7 months

1
1
0 / 0

[JBoss JIRA] (FORGE-570) When using the field command, member variables should be created in the variable section

by Jim Tyrrell (JIRA)

Jim Tyrrell created FORGE-570: --------------------------------- Summary: When using the field command, member variables should be created in the variable section Key: FORGE-570 URL: https://issues.jboss.org/browse/FORGE-570 Project: Forge Issue Type: Feature Request Reporter: Jim Tyrrell When adding a new member variable via a command like: field boolean --named major That field should be added nearby below the other variables in the class. This is right out of Java style guides from 1995/6. Make for a file that is really hard to look at for us poor humans. Also hurts our ability to demo this well in the field. -- 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, 7 months

3
5
0 / 0

[JBoss JIRA] (FORGE-586) Connecting to remote repository [https://raw.github.com/forge/plugin-repository/master/repository.yaml]... ***ERROR*** [forge install-plugin] peer not authenticated

by Stefan Frank (JIRA)

Stefan Frank created FORGE-586: ---------------------------------- Summary: Connecting to remote repository [https://raw.github.com/forge/plugin-repository/master/repository.yaml]... ***ERROR*** [forge install-plugin] peer not authenticated Key: FORGE-586 URL: https://issues.jboss.org/browse/FORGE-586 Project: Forge Issue Type: Bug Components: Plugin Repository Affects Versions: 1.0.5.Final Environment: mac osx, forge 1.0.5.FINAL Reporter: Stefan Frank Whenever I'm trying to list or install a plugin, I'm getting an peer not authenticated: JBoss Forge, version [ 1.0.5.Final ] - JBoss, by Red Hat, Inc. [ http://jboss.org/forge ] [example] example $ forge list-plugins Wrote /Users/sfrank/.forge/plugins [example] example $ forge install-plugin jboss-as-7 Connecting to remote repository [https://raw.github.com/forge/plugin-repository/master/repository.yaml]... ***ERROR*** [forge install-plugin] peer not authenticated -- 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, 7 months

3
8
0 / 0

[JBoss JIRA] (FORGE-192) Make Forge console i18n and L10n compatible

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-192?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-192: ---------------------------------- Component/s: Brainstorming > Make Forge console i18n and L10n compatible > ------------------------------------------- > > Key: FORGE-192 > URL: https://issues.jboss.org/browse/FORGE-192 > Project: Forge > Issue Type: Feature Request > Components: Brainstorming, Shell > Affects Versions: 1.0.6.Final > Reporter: George Gastaldi > Fix For: 2.0.0.Alpha1 > > > Forge should allow different languages to be used, so that the help messages and commands could be typed on the native speaker developer language. > Example: When a Brazilian Portuguese developer is creating a new project, he would type: "novo-projeto" instead of "new-project". -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-275) delete associated methods when deleting a field

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-275?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-275: ---------------------------------- Fix Version/s: 1.1.1.Final (was: 1.1.0.Final) > delete associated methods when deleting a field > ----------------------------------------------- > > Key: FORGE-275 > URL: https://issues.jboss.org/browse/FORGE-275 > Project: Forge > Issue Type: Feature Request > Components: Brainstorming, Builtin Plugins > Affects Versions: 1.0.0.Alpha2, 1.0.0.Alpha3 > Reporter: Rodney Russ > Assignee: Ricardo Martinelli Oliveira > Priority: Minor > Labels: Starter > Fix For: 1.1.1.Final > > Attachments: Forge-275.patch > > > When removing a field, it would make sense to remove the associated methods. For example: > cd Person.java > rm firstName > *delete associated methods setFirstName() and getFirstName() (Y/n)? -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-275) delete associated methods when deleting a field

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-275?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-275: ---------------------------------- Status: Pull Request Sent (was: Reopened) Git Pull Request: https://github.com/forge/core/pull/219 (was: https://github.com/forge/core/pull/219) > delete associated methods when deleting a field > ----------------------------------------------- > > Key: FORGE-275 > URL: https://issues.jboss.org/browse/FORGE-275 > Project: Forge > Issue Type: Feature Request > Components: Brainstorming, Builtin Plugins > Affects Versions: 1.0.0.Alpha2, 1.0.0.Alpha3 > Reporter: Rodney Russ > Assignee: Ricardo Martinelli Oliveira > Priority: Minor > Labels: Starter > Fix For: 1.1.0.Final > > Attachments: Forge-275.patch > > > When removing a field, it would make sense to remove the associated methods. For example: > cd Person.java > rm firstName > *delete associated methods setFirstName() and getFirstName() (Y/n)? -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-275) delete associated methods when deleting a field

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-275?page=com.atlassian.jira.plugin.... ] George Gastaldi reopened FORGE-275: ----------------------------------- > delete associated methods when deleting a field > ----------------------------------------------- > > Key: FORGE-275 > URL: https://issues.jboss.org/browse/FORGE-275 > Project: Forge > Issue Type: Feature Request > Components: Brainstorming, Builtin Plugins > Affects Versions: 1.0.0.Alpha2, 1.0.0.Alpha3 > Reporter: Rodney Russ > Assignee: Ricardo Martinelli Oliveira > Priority: Minor > Labels: Starter > Fix For: 1.1.0.Final > > Attachments: Forge-275.patch > > > When removing a field, it would make sense to remove the associated methods. For example: > cd Person.java > rm firstName > *delete associated methods setFirstName() and getFirstName() (Y/n)? -- 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, 7 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues September 2012