April 2013 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-734) AnnotationTarget should be renamed to AnnotationCapable

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-734?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-734: ---------------------------------- Fix Version/s: 2.0.0.Alpha3 (was: 2.0.0.Alpha2) > AnnotationTarget should be renamed to AnnotationCapable > ------------------------------------------------------- > > Key: FORGE-734 > URL: https://issues.jboss.org/browse/FORGE-734 > Project: Forge > Issue Type: Enhancement > Components: Parsers / File Manipulation > Affects Versions: 1.1.3.Final > Reporter: George Gastaldi > Priority: Minor > Fix For: 2.0.0.Alpha3 > > > In order to keep the API consistent, I propose that the interface > {code}org.jboss.forge.parser.java.AnnotationTarget{code} > should be renamed to > {code}org.jboss.forge.parser.java.AnnotationCapable{code} -- 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

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-689) Shell should report "People who used this command also used the following commands: X Y Z"

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-689?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-689: ---------------------------------- Fix Version/s: 2.0.0.Alpha3 (was: 2.0.0.Alpha2) > Shell should report "People who used this command also used the following commands: X Y Z" > ------------------------------------------------------------------------------------------ > > Key: FORGE-689 > URL: https://issues.jboss.org/browse/FORGE-689 > Project: Forge > Issue Type: Feature Request > Components: UI - Shell > Affects Versions: 1.1.0.Final > Reporter: Lincoln Baxter III > Fix For: 2.0.0.Alpha3 > > > This should probably not be tied to the shell, but use analytics tracking data to report on which commands generally follow which and expose an API that can be used to implement this feature in the shell, IDE, or any UI. -- 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

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-776) Show what you would have typed in the Terminal as you execute other UI impls/Wizards

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-776?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-776: ---------------------------------- Fix Version/s: 2.0.0.Alpha3 (was: 2.0.0.Alpha2) > Show what you would have typed in the Terminal as you execute other UI impls/Wizards > ------------------------------------------------------------------------------------ > > Key: FORGE-776 > URL: https://issues.jboss.org/browse/FORGE-776 > Project: Forge > Issue Type: Story > Components: Event Bus, UI - Eclipse, UI - Shell > Reporter: Lincoln Baxter III > Assignee: Koen Aers > Fix For: 2.0.0.Alpha3 > > > Effectively, "Link with Shell/Terminal" -- 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

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-779) Class parameters are not correctly loaded for the consuming addon's classloader

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-779?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-779: ---------------------------------- Fix Version/s: 2.0.0.Alpha3 (was: 2.0.0.Alpha2) > Class parameters are not correctly loaded for the consuming addon's classloader > ------------------------------------------------------------------------------- > > Key: FORGE-779 > URL: https://issues.jboss.org/browse/FORGE-779 > Project: Forge > Issue Type: Bug > Reporter: George Gastaldi > Assignee: Lincoln Baxter III > Priority: Critical > Fix For: 2.0.0.Alpha3 > > > Having the following scenario: > Eclipse plugin -> calls ConverterFactory -> passes Resource.class as a parameter > {code:java} > ConverterFactory.getConverter(File.class, Resource.class) > {code} > in ResourceConverterGenerator (resources addon): > {code:java} > @Override > public boolean handles(Class<?> source, Class<?> target) > { > return Resource.class.isAssignableFrom(target); > } > {code} > Returns false, because the classloader that loaded the Resource class is the Eclipse classloader, not the Resource addon classloader AND Resource.class is not visible in the convert addon. -- 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

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-795) Create an Implementation of Forge Java Parser using Javassist CtClass or Apache BCEL

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-795?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-795: ---------------------------------- Fix Version/s: 2.0.0.Alpha3 (was: 2.0.0.Alpha2) > Create an Implementation of Forge Java Parser using Javassist CtClass or Apache BCEL > ------------------------------------------------------------------------------------ > > Key: FORGE-795 > URL: https://issues.jboss.org/browse/FORGE-795 > Project: Forge > Issue Type: Story > Components: Parsers / File Manipulation > Reporter: Lincoln Baxter III > Fix For: 2.0.0.Alpha3 > > > http://www.csg.is.titech.ac.jp/~chiba/javassist/html/javassist/CtClass.html > http://commons.apache.org/bcel/ -- 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

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-771) Result.success(message) should be displayed as a "Growl" notification after UICommand invocation in Eclipse.

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-771?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-771: ---------------------------------- Fix Version/s: 2.0.0.Alpha3 (was: 2.0.0.Alpha2) > Result.success(message) should be displayed as a "Growl" notification after UICommand invocation in Eclipse. > ------------------------------------------------------------------------------------------------------------ > > Key: FORGE-771 > URL: https://issues.jboss.org/browse/FORGE-771 > Project: Forge > Issue Type: Enhancement > Components: UI - Eclipse > Affects Versions: 2.0.0.Alpha1 > Reporter: Lincoln Baxter III > Assignee: Koen Aers > Fix For: 2.0.0.Alpha3 > > -- 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

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-801) Support for Transactional Resources

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-801?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-801: ---------------------------------- Fix Version/s: 2.0.0.Alpha3 (was: 2.0.0.Alpha2) > Support for Transactional Resources > ------------------------------------ > > Key: FORGE-801 > URL: https://issues.jboss.org/browse/FORGE-801 > Project: Forge > Issue Type: Feature Request > Components: Resources API > Affects Versions: 1.2.1.Final > Reporter: George Gastaldi > Assignee: George Gastaldi > Priority: Critical > Fix For: 2.0.0.Alpha3 > > Attachments: IMG_20130225_215814.jpg, UserGuide_TXFileInJava_v1.0.pdf > > > FileResources should be transactional, that is, allow modification of resources for displaying purposes and allow commit or rollback of changes. > The implementation could copy the modified file to a temporary folder and when commit is invoked, copy back the contents to the original folder. > It may be necessary to provide a pointer back to the original file (Properties file next to changed file maybe?). -- 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

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-802) Support multiple select/pick-up/cd Resources

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-802?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-802: ---------------------------------- Fix Version/s: 2.0.0.Alpha3 (was: 2.0.0.Alpha2) > Support multiple select/pick-up/cd Resources > -------------------------------------------- > > Key: FORGE-802 > URL: https://issues.jboss.org/browse/FORGE-802 > Project: Forge > Issue Type: Feature Request > Components: UI - Shell > Reporter: Lincoln Baxter III > Fix For: 2.0.0.Alpha3 > > > {code}/home/lincoln/projects/forge/*.java/get* [2432 selected] ${code} > (04:17:31 PM) lincolnthree1: i was thinking it would be nice if the cd or "select" or "pick up" command accepted wildcards/filters of some sort > (04:17:44 PM) lincolnthree1: obviously *.java works, but only in the current directory/resource > (04:17:46 PM) lincolnthree1: so > (04:17:54 PM) lincolnthree1: 'cd *.java' would select all the > (04:18:00 PM) lincolnthree1: java files in the current dir > (04:18:07 PM) lincolnthree1: but it would be really nice if you could do something like: > (04:18:20 PM) lincolnthree1: select **/*.java > (04:18:27 PM) lincolnthree1: or select *.java -r > (04:18:32 PM) lincolnthree1: select -r *.java > (04:18:40 PM) lincolnthree1: and recursively select resources > (04:18:50 PM) lincolnthree1: from . onward > (04:20:39 PM) stalep: sure that should work. but what do you mean by "select". selected for what? > (04:21:11 PM) lincolnthree1: UIContext.getInitialSelection() > (04:21:18 PM) lincolnthree1: multi-cd > (04:22:00 PM) stalep: im my head cd is change directory, so sorry for being a bit slow with the context switching :) > (04:22:21 PM) lincolnthree1: think of this as an advanced for of CD > (04:22:28 PM) lincolnthree1: imagine this: > (04:22:31 PM) lincolnthree1: cd *.java > (04:22:34 PM) gegastaldi: pick-up might be more like it > (04:22:38 PM) lincolnthree1: [12 java files in context] > (04:22:43 PM) mmatloka: gegastaldi: are you ready?:P > (04:22:50 PM) lincolnthree1: ls . > (04:22:54 PM) gercan [~gorkem(a)217.131.48.21] entered the room. > (04:23:03 PM) lincolnthree1: now prints out all the fields/methods of the 12 java files > (04:23:11 PM) gegastaldi: mmatloka: for what ? Pull requests ? :) > (04:23:13 PM) lincolnthree1: rm . would delete all 12 java files > (04:23:18 PM) stalep: ok > (04:23:26 PM) mmatloka: gegastaldi: for learning :D > (04:23:27 PM) jamezp_afk is now known as jamezp > (04:23:32 PM) lincolnthree1: so it's like "cd++" > (04:23:41 PM) lincolnthree1: taking 'cd' to the next level > (04:24:23 PM) stalep: so its not a cd, but more of a select as you mentioned earlier > (04:24:39 PM) gegastaldi: cr > (04:24:41 PM) lincolnthree1: basically > (04:24:44 PM) gegastaldi: Select resource > (04:24:45 PM) stalep: co cd *.java will select all methods on all java files? > (04:24:51 PM) lincolnthree1: well > (04:24:58 PM) lincolnthree1: cd *.java would select all java files in the current dir > (04:25:02 PM) lincolnthree1: once you've done that > (04:25:07 PM) lincolnthree1: you could then cd get* > (04:25:15 PM) lincolnthree1: which would select all getters in all java files in the current directory > (04:25:48 PM) lincolnthree1: so 'cd *.java/get*' would be the equivalent single command > (04:25:57 PM) stalep: ok > (04:26:07 PM) Cojan [~cvanball@2001:980:92c0:1:2677:3ff:fe7d:2620] entered the room. > (04:26:20 PM) gegastaldi: Oh, cd as in Change Destination, not Change Directory :) > (04:26:35 PM) lincolnthree1: then issuing an 'rm' would delete all those selected getters and drop you back to a selection of just the *.java files > (04:27:04 PM) lincolnthree1: similarly, I guess you could do: > (04:27:08 PM) lincolnthree1: rm *.java/get* > (04:27:27 PM) lincolnthree1: and just imagine if autocomplete worked here > (04:27:34 PM) lincolnthree1: serious shell power > (04:28:26 PM) gegastaldi: There should be a way to display the selected resources in the command prompt also > (04:28:37 PM) lincolnthree1: right > (04:28:43 PM) lincolnthree1: so the prompt would probably say something like: > (04:29:22 PM) lincolnthree1: /home/lincoln/projects/forge/[*.java/get*] 12 selected $ > (04:29:33 PM) lincolnthree1: actually it would probably be something like: > (04:29:42 PM) lincolnthree1: /home/lincoln/projects/forge/[*.java/get*] 2432 selected $ > (04:29:45 PM) lincolnthree1: lol > (04:29:50 PM) gegastaldi: Lol > (04:30:07 PM) gegastaldi: I like the idea > (04:30:25 PM) gegastaldi: But > (04:30:27 PM) lincolnthree1: or maybe > (04:30:36 PM) lincolnthree1: /home/lincoln/projects/forge/*.java/get* [2432 selected] $ -- 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

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-770) Ability to restrict ServiceRegistry and AddonRegistry services by addon dependency version

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-770?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-770: ---------------------------------- Fix Version/s: 2.0.0.Alpha3 (was: 2.0.0.Alpha2) > Ability to restrict ServiceRegistry and AddonRegistry services by addon dependency version > ------------------------------------------------------------------------------------------- > > Key: FORGE-770 > URL: https://issues.jboss.org/browse/FORGE-770 > Project: Forge > Issue Type: Story > Components: Container > Affects Versions: 2.0.0.Alpha1 > Reporter: Lincoln Baxter III > Assignee: Lincoln Baxter III > Fix For: 2.0.0.Alpha3 > > > Like in OSGi (shudder,) when looking up services from the ServiceRegistry, it should be possible to require that services retrieved from the ServiceRegistry be locked to a specific addon API version (via addon-dependency/classloader mapping.) > {code} > (A) -> (B, v1) > -> Service 1 > (B, v2) > -> Service 1v2 > -> Service 2v1 > {code} > A should receive only the instance of Service 1 from (B, v1) -- 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

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-775) Create a UICommandCache which uses generated Class files to lazy-load addons on demand

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-775?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-775: ---------------------------------- Fix Version/s: 2.0.0.Alpha3 (was: 2.0.0.Alpha2) > Create a UICommandCache which uses generated Class files to lazy-load addons on demand > -------------------------------------------------------------------------------------- > > Key: FORGE-775 > URL: https://issues.jboss.org/browse/FORGE-775 > Project: Forge > Issue Type: Story > Components: Container, Plugin API > Reporter: Lincoln Baxter III > Fix For: 2.0.0.Alpha3 > > > There must be an option to eagerly load an addon. > addon.xml > {code}<start-with-container>true</start-with-container>{code} > Also need to proxy appropriate command constraint metadata (UICommand.handles(...) needs to be redesigned to be more static? -- 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

11 years, 8 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues April 2013