June 2013 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-688) Addition of the JavaEE 6 BOM should be encapsulated in a specific Facet

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-688?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-688: ---------------------------------- Fix Version/s: 2.x Future (was: 2.0.0.Alpha5) > Addition of the JavaEE 6 BOM should be encapsulated in a specific Facet > ----------------------------------------------------------------------- > > Key: FORGE-688 > URL: https://issues.jboss.org/browse/FORGE-688 > Project: Forge > Issue Type: Enhancement > Components: Plugin API > Affects Versions: 1.1.0.Final > Reporter: George Gastaldi > Priority: Minor > Fix For: 2.x Future > > > It would be nice if we have a JavaEE6Facet, which installs the jboss bom. > Even though the BaseJavaEEFacet abstract class already does that, this behavior would not be possible if a custom Facet is created extending a specific subclass of BaseFacet and requiring the JavaEE6. > The more elegant solution would be to add: > {code:java} > @RequiresFacet(JavaEE6Facet.class) > {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, 3 months

1
0
0 / 0

[JBoss JIRA] (FORGE-775) Create a CDI metadata cache that allows lazy, on-demand loading of addons

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.x Future (was: 2.0.0.Alpha5) > Create a CDI metadata cache that allows lazy, on-demand loading of addons > ------------------------------------------------------------------------- > > Key: FORGE-775 > URL: https://issues.jboss.org/browse/FORGE-775 > Project: Forge > Issue Type: Feature Request > Components: Container, Plugin API > Reporter: Lincoln Baxter III > Fix For: 2.x Future > > > 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, 3 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.x Future (was: 2.0.0.Alpha5) > 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: Feature Request > Components: Event Bus, UI - Eclipse, UI - Shell > Reporter: Lincoln Baxter III > Assignee: Koen Aers > Fix For: 2.x Future > > > 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, 3 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.x Future (was: 2.0.0.Alpha5) > 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: Feature Request > Components: Container > Affects Versions: 2.0.0.Alpha1 > Reporter: Lincoln Baxter III > Assignee: Lincoln Baxter III > Fix For: 2.x Future > > > 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, 3 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.x Future (was: 2.0.0.Alpha5) > 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: Feature Request > Components: Parsers / File Manipulation > Reporter: Lincoln Baxter III > Fix For: 2.x Future > > > 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, 3 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.x Future (was: 2.0.0.Alpha5) > 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.x Future > > > 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, 3 months

1
0
0 / 0

[JBoss JIRA] (FORGE-783) Create a UICommand resolution strategy

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-783?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-783: ---------------------------------- Fix Version/s: 2.x Future (was: 2.0.0.Alpha5) > Create a UICommand resolution strategy > -------------------------------------- > > Key: FORGE-783 > URL: https://issues.jboss.org/browse/FORGE-783 > Project: Forge > Issue Type: Task > Components: Plugin API, Plugin Repository, UI - Eclipse, UI - Shell > Reporter: Koen Aers > Fix For: 2.x Future > > > We will need a UICommand resolution strategy for when there are conflicts between UICommand names/etc (possible solutions are to use addon's maven coordinates, the description, 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

11 years, 3 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.x Future (was: 2.0.0.Alpha5) > 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.x Future > > > {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, 3 months

1
0
0 / 0

[JBoss JIRA] (FORGE-841) Add Forge as a container in the Servers tab

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-841?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-841: ---------------------------------- Fix Version/s: 2.x Future (was: 2.0.0.Alpha5) > Add Forge as a container in the Servers tab > ------------------------------------------- > > Key: FORGE-841 > URL: https://issues.jboss.org/browse/FORGE-841 > Project: Forge > Issue Type: Feature Request > Components: UI - Eclipse > Affects Versions: 2.0.0.Alpha1 > Reporter: George Gastaldi > Assignee: Koen Aers > Fix For: 2.x Future > > > Installing of addons could be made as dragging-drop a forge addon project in this server. Startup and Shutdown are also easily managed this way. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (FORGE-861) Forge 2 does not start upon installation into Eclipse. Must restart eclipse.

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-861?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-861: ---------------------------------- Fix Version/s: 2.x Future (was: 2.0.0.Alpha5) > Forge 2 does not start upon installation into Eclipse. Must restart eclipse. > ---------------------------------------------------------------------------- > > Key: FORGE-861 > URL: https://issues.jboss.org/browse/FORGE-861 > Project: Forge > Issue Type: Bug > Components: UI - Eclipse > Affects Versions: 2.0.0.Alpha2 > Reporter: Lincoln Baxter III > Fix For: 2.x Future > > > Technically this issue is in the JBDS side, but since it is related to Forge 2 only, I put the issue here for now. -- 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, 3 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues June 2013