August 2012 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-169) Persistence plugin should optionally add maven configuration for a meta-model generator

by Ken Finnigan (JIRA)

[ https://issues.jboss.org/browse/FORGE-169?page=com.atlassian.jira.plugin.... ] Ken Finnigan commented on FORGE-169: ------------------------------------ I made a start, but that was quite a while ago now. Haven't had an opportunity to get back into it yet, though it is on my list ;-) > Persistence plugin should optionally add maven configuration for a meta-model generator > --------------------------------------------------------------------------------------- > > Key: FORGE-169 > URL: https://issues.jboss.org/browse/FORGE-169 > Project: Forge > Issue Type: Enhancement > Components: Java EE APIs > Affects Versions: 1.0.6.Final > Reporter: Paul Bakker > Assignee: Ken Finnigan > Fix For: 1.0.7.Final > > > If JPA 2.0 is used, and the provider supports a meta-model generator it should be added to the pom file. -- 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-184) Add 'plugins register-plugin', 'update-registration' style commands for updating the central plugin repository index

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-184?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III updated FORGE-184: ------------------------------------- Fix Version/s: 2.0.0.Alpha1 (was: Future) Component/s: Plugin Repository > Add 'plugins register-plugin', 'update-registration' style commands for updating the central plugin repository index > -------------------------------------------------------------------------------------------------------------------- > > Key: FORGE-184 > URL: https://issues.jboss.org/browse/FORGE-184 > Project: Forge > Issue Type: Feature Request > Components: Brainstorming, Builtin Plugins, Plugin Repository > Affects Versions: 1.0.0.Alpha4 > Reporter: Lincoln Baxter III > Fix For: 2.0.0.Alpha1 > > > Forge should provide commands to simplify the process of registering a plugin with the central repository. > The command should verify all metadata by attempting to build/install the plugin before allowing an update request to be sent. -- 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-179) The 'open' and 'edit' commands should be configurable

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-179?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III updated FORGE-179: ------------------------------------- Labels: Starter (was: ) Fix Version/s: 1.0.7.Final > The 'open' and 'edit' commands should be configurable > ----------------------------------------------------- > > Key: FORGE-179 > URL: https://issues.jboss.org/browse/FORGE-179 > Project: Forge > Issue Type: Enhancement > Components: Builtin Plugins > Affects Versions: 1.0.0.Alpha3 > Reporter: Lincoln Baxter III > Assignee: Koen Aers > Labels: Starter > Fix For: 1.0.7.Final > > > 'open' and 'edit' currently use the default system application, but if hooks were provided into this system, they could instead be used to open files using a user-specified application, or even trigger editors to open in JBoss Tools. > Koen, I am asigning this to you because I want your feedback here. If running forge in eclipse, these commands should probably be a no-op, and your eclipse system will simply intercept the output and open/edit the desired file, yes? -- 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-177) Improve error handling in setBody method of MethodImpl

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-177?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III updated FORGE-177: ------------------------------------- Summary: Improve error handling in setBody method of MethodImpl (was: Error handling in setBody method of MethodImpl) Fix Version/s: 1.0.7.Final Affects Version/s: 1.0.6.Final > Improve error handling in setBody method of MethodImpl > ------------------------------------------------------ > > Key: FORGE-177 > URL: https://issues.jboss.org/browse/FORGE-177 > Project: Forge > Issue Type: Enhancement > Components: Parsers / File Manipulation > Affects Versions: 1.0.6.Final > Reporter: Paul Bakker > Priority: Minor > Fix For: 1.0.7.Final > > > When this method is called with a String, but the String doesn't parse correctly, the method fails silently. Instead of a ParseException or something like that it just returns an empty body. -- 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-266) Forge Plugins should be decoupled from the Shell Interface, run standalone in JBoss Tools

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-266?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-266: ---------------------------------- Fix Version/s: 2.0.0.Alpha1 > Forge Plugins should be decoupled from the Shell Interface, run standalone in JBoss Tools > ----------------------------------------------------------------------------------------- > > Key: FORGE-266 > URL: https://issues.jboss.org/browse/FORGE-266 > Project: Forge > Issue Type: Feature Request > Components: Brainstorming, JBoss Tools Integration > Reporter: Lincoln Baxter III > Fix For: 2.0.0.Alpha1 > > > (01:41:28 PM) Lincoln: I'd like to start Forge in JBoss Tools, but instead of using the Shell, use the PluginMetadata to build a GUI to run Plugins from the IDE itself. > (01:41:34 PM) Lincoln: Using windows and input fields, etc. > (01:41:45 PM) Koen Aers: hm > (01:42:07 PM) Lincoln: So workflow like this: > (01:42:46 PM) Lincoln: <CTRL-4> JBT pops up a window like <CTRL-3> where you can type and it will search through the list of commands that are available > (01:42:48 PM) Lincoln: you can pick one > (01:42:51 PM) Lincoln: when you do > (01:43:06 PM) Lincoln: JBT generates a UI for that command, with a list of required and optional fields, based on teh plugin metadata -- 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-169) Persistence plugin should optionally add maven configuration for a meta-model generator

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-169?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III updated FORGE-169: ------------------------------------- Fix Version/s: 1.0.7.Final Affects Version/s: 1.0.6.Final Component/s: Java EE APIs Hey Ken, did you ever start on this one? > Persistence plugin should optionally add maven configuration for a meta-model generator > --------------------------------------------------------------------------------------- > > Key: FORGE-169 > URL: https://issues.jboss.org/browse/FORGE-169 > Project: Forge > Issue Type: Enhancement > Components: Java EE APIs > Affects Versions: 1.0.6.Final > Reporter: Paul Bakker > Assignee: Ken Finnigan > Fix For: 1.0.7.Final > > > If JPA 2.0 is used, and the provider supports a meta-model generator it should be added to the pom file. -- 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-253) Forge should provide development profiles API for datasources and other configs

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-253?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-253: ---------------------------------- Fix Version/s: 2.0.0.Alpha1 > Forge should provide development profiles API for datasources and other configs > ------------------------------------------------------------------------------- > > Key: FORGE-253 > URL: https://issues.jboss.org/browse/FORGE-253 > Project: Forge > Issue Type: Feature Request > Components: Plugin API > Affects Versions: 1.0.0.Alpha3 > Reporter: Lincoln Baxter III > Fix For: 2.0.0.Alpha1 > > > lincolnthree > It gives you what is in persistence.xml > 11:22 > maxandersen > it wasn't there a jbossworld > 11:22 > lincolnthree > that's been there from the beginning > 11:22 > maxandersen > yes - persistence.xml says datasources > nothing about the actual connection info > 11:23 > lincolnthree > oh right > well > connection info is stored on the server > forge doesn't know that > unless it's in the persistence.xml > 11:23 > maxandersen > lincolnthree: exaactly - but it has to know that eventually. > 11:23 > lincolnthree > as properties > 11:23 > maxandersen > lincolnthree: it wont be > lincolnthree: this is why tools like rails, hibernate tools and others have notion of "profiles" or simply just property overrides for use at design time and for use at runtime -- 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-445) GZip compression configuration plugin

by Dan Allen (JIRA)

Dan Allen created FORGE-445: ------------------------------- Summary: GZip compression configuration plugin Key: FORGE-445 URL: https://issues.jboss.org/browse/FORGE-445 Project: Forge Issue Type: Feature Request Components: Brainstorming Reporter: Dan Allen GZip compression is the perfect case of a monkey's job (aka forge plugin). In some cases, it needs to be added to web.xml as a filter. In other cases, it needs to modify the application server configuration. It would be cool to have a GZip compression plugin that would apply the configuration in the appropriate way based on input from the user. For example: setup gzip --scope application --provider XXXX setup gzip --scope container --container JBOSS_AS_7 If the application vs container paths are different, it may warrant two separate commands, such as gzip-filter and gzip-server-config -- 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
1
0 / 0

[JBoss JIRA] (FORGE-440) A pom.xml which contains comments looses all of them after Forge operates on it.

by Pete Muir (JIRA)

Pete Muir created FORGE-440: ------------------------------- Summary: A pom.xml which contains comments looses all of them after Forge operates on it. Key: FORGE-440 URL: https://issues.jboss.org/browse/FORGE-440 Project: Forge Issue Type: Bug Environment: HEAD Reporter: Pete Muir Priority: Critical Also looses formatting, but this is less of an issue. -- 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

4
4
0 / 0

[JBoss JIRA] (FORGE-529) "Configure HTTP Proxy" documentation is incomplete

by Gernot P (JIRA)

Gernot P created FORGE-529: ------------------------------ Summary: "Configure HTTP Proxy" documentation is incomplete Key: FORGE-529 URL: https://issues.jboss.org/browse/FORGE-529 Project: Forge Issue Type: Bug Affects Versions: 1.0.2.Final Reporter: Gernot P "Configure HTTP Proxy" documentation (https://docs.jboss.org/author/display/FORGE/Configure+HTTP+Proxy) says: "Open the user configuration in ~/.forge/config.xml" but there's no config.xml (I use Forge 1.0.2Final). I also have not found any doc about config.xml. Is there any xsd out there? What's the root element? -- 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
1
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues August 2012