January 2013 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-737) Addons are not loaded after their dependencies

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-737?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III closed FORGE-737. ------------------------------------ Resolution: Done Done. > Addons are not loaded after their dependencies > ---------------------------------------------- > > Key: FORGE-737 > URL: https://issues.jboss.org/browse/FORGE-737 > Project: Forge > Issue Type: Bug > Affects Versions: 2.0.0.Alpha1 > Reporter: George Gastaldi > Assignee: Lincoln Baxter III > Priority: Critical > Fix For: 2.0.0.Alpha1 > > > Addon A depends on Addon B. > Order of loading should be > Addon B -> Addon A > The current impl ignores dependencies between addons while loading. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (FORGE-719) Design an user interface API for addons

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-719?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III reassigned FORGE-719: ---------------------------------------- Assignee: Lincoln Baxter III > Design an user interface API for addons > --------------------------------------- > > Key: FORGE-719 > URL: https://issues.jboss.org/browse/FORGE-719 > Project: Forge > Issue Type: Story > Components: Brainstorming > Reporter: George Gastaldi > Assignee: Lincoln Baxter III > Fix For: 2.0.0.Alpha1 > > > Requirements: > - It must be usable in a Shell UI > - It should be usable in a Visual UI (SWT, Swing) > - It must be typesafe, therefore allowing the use of complex types. > Let's use this JIRA to brainstorm about it. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (FORGE-705) Migrate Resources API to Forge 2.0 AddOn

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-705?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III closed FORGE-705. ------------------------------------ Resolution: Done Done > Migrate Resources API to Forge 2.0 AddOn > ---------------------------------------- > > Key: FORGE-705 > URL: https://issues.jboss.org/browse/FORGE-705 > Project: Forge > Issue Type: Feature Request > Components: Resources API > Reporter: Ken Finnigan > Assignee: Ken Finnigan > Fix For: 2.0.0.Alpha1 > > -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (FORGE-738) Support Global Producers

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-738?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III closed FORGE-738. ------------------------------------ Resolution: Out of Date This has been resolved via the new @Exported service registry annotation. > Support Global Producers > ------------------------ > > Key: FORGE-738 > URL: https://issues.jboss.org/browse/FORGE-738 > Project: Forge > Issue Type: Enhancement > Affects Versions: 2.0.0.Alpha1 > Reporter: George Gastaldi > Priority: Blocker > Fix For: 2.0.0.Alpha1 > > > The UI API has a UIInputProducer, which produces UIInput objects based on the injection point (Parameterized name used, attribute name, etc). > However, when developing an addon which @Inject UIInput<String> firstname for example, the following error is thrown: > {code} > Caused by: org.jboss.weld.exceptions.DeploymentException: WELD-001408 Unsatisfied dependencies for type [UIInput<String>] with qualifiers [@Default] at injection point [[UnbackedAnnotatedField] @Inject private org.jboss.forge.ui.MyFirstWizard.firstName] > {code} > This is due the fact that you can't inject between containers unless it's @Remote. Forge 2 should support registration of a global producer, which just adds that producer to all addons on which it is depended -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (FORGE-759) Move the examples projects to the addon-container-test module

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-759?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III reassigned FORGE-759: ---------------------------------------- Assignee: Lincoln Baxter III > Move the examples projects to the addon-container-test module > ------------------------------------------------------------- > > Key: FORGE-759 > URL: https://issues.jboss.org/browse/FORGE-759 > Project: Forge > Issue Type: Task > Components: Test Harness > Affects Versions: 2.0.0.Alpha1 > Reporter: George Gastaldi > Assignee: Lincoln Baxter III > Priority: Minor > Fix For: 2.0.0.Final > > > The example projects should be placed inside the addon-container-tests module. Probably not as part of the build, but deployed as part of the test execution. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (FORGE-759) Move the examples projects to the addon-container-test module

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-759?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III closed FORGE-759. ------------------------------------ Fix Version/s: 2.0.0.Alpha1 (was: 2.0.0.Final) Resolution: Partially Completed > Move the examples projects to the addon-container-test module > ------------------------------------------------------------- > > Key: FORGE-759 > URL: https://issues.jboss.org/browse/FORGE-759 > Project: Forge > Issue Type: Task > Components: Test Harness > Affects Versions: 2.0.0.Alpha1 > Reporter: George Gastaldi > Assignee: Lincoln Baxter III > Priority: Minor > Fix For: 2.0.0.Alpha1 > > > The example projects should be placed inside the addon-container-tests module. Probably not as part of the build, but deployed as part of the test execution. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (FORGE-564) Allow multiple @Alias for a plugin

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-564?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III closed FORGE-564. ------------------------------------ Resolution: Won't Fix Not going to fix this. There is not enough demand to support it. Either extend the Plugin/Command or don't have multiple names. Workaround exists. > Allow multiple @Alias for a plugin > ---------------------------------- > > Key: FORGE-564 > URL: https://issues.jboss.org/browse/FORGE-564 > Project: Forge > Issue Type: Enhancement > Reporter: George Gastaldi > Labels: HackNight > Fix For: 1.2.1.Final > > > A plugin could have multiple alias. For example, the Help plugin could be invoked by "help" or "?". > This issue has two possible solutions : > # Changing the @Alias value() method to return a String[] or > # As Dan Allen suggested, introduce an @Aliases annotation that accepts a collection of @Alias annotations. this reads nicer and leaves the door open for per-alias customizations if we should need them. > The second approach looks nicer. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (FORGE-308) Need a way of supplying JARs to Plugins (e.g. Hibernate Tools)

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-308?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III closed FORGE-308. ------------------------------------ Resolution: Won't Fix Not fixing this until a more clear need is specified. > Need a way of supplying JARs to Plugins (e.g. Hibernate Tools) > --------------------------------------------------------------- > > Key: FORGE-308 > URL: https://issues.jboss.org/browse/FORGE-308 > Project: Forge > Issue Type: Feature Request > Components: Plugin API, Usability > Affects Versions: 1.0.0.Beta2 > Reporter: Lincoln Baxter III > Assignee: Koen Aers > Fix For: 2.0.0.Alpha1 > > > You could (in theory) add a JAR to the plugin module where it is installed: > .forge/plugins/org/jboss/hibernate/forge/hibernate-tools-plugin/dependencies/1.0.0-SNAPSHOT-*** > and also add that jar as a resource in the module.xml file > .forge/plugins/org/jboss/hibernate/forge/hibernate-tools-plugin/dependencies/1.0.0-SNAPSHOT-***/modules.xml > That should do it, but it's not easy. This needs to be streamlined -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (FORGE-226) Support for Facets construct on Resources

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-226?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III reassigned FORGE-226: ---------------------------------------- Assignee: Lincoln Baxter III > Support for Facets construct on Resources > ----------------------------------------- > > Key: FORGE-226 > URL: https://issues.jboss.org/browse/FORGE-226 > Project: Forge > Issue Type: Feature Request > Reporter: Aslak Knutsen > Assignee: Lincoln Baxter III > Fix For: 2.0.0.Alpha1 > > > It would be handy to have Facets support for Resources so logic on recognizing/handling common resource related operations in one place. > e.g. > {code} > JavaSourceResource.getFacet(EJBFacet.class) > .isBeanType(Type.MESSAGE_DRIVEN_BEAN) > JavaSourceResource.getFacet(ArquillianFacet.class) > .addToDeployment(Class) > .getDeployments() > {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, 10 months

1
0
0 / 0

[JBoss JIRA] (FORGE-226) Support for Facets construct on Resources

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-226?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III closed FORGE-226. ------------------------------------ Resolution: Done > Support for Facets construct on Resources > ----------------------------------------- > > Key: FORGE-226 > URL: https://issues.jboss.org/browse/FORGE-226 > Project: Forge > Issue Type: Feature Request > Reporter: Aslak Knutsen > Assignee: Lincoln Baxter III > Fix For: 2.0.0.Alpha1 > > > It would be handy to have Facets support for Resources so logic on recognizing/handling common resource related operations in one place. > e.g. > {code} > JavaSourceResource.getFacet(EJBFacet.class) > .isBeanType(Type.MESSAGE_DRIVEN_BEAN) > JavaSourceResource.getFacet(ArquillianFacet.class) > .addToDeployment(Class) > .getDeployments() > {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, 10 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues January 2013