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

[Ken Finnigan (JIRA)]

    [ https://issues.jboss.org/browse/FORGE-705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12735912#comment-12735912 ] 

Ken Finnigan commented on FORGE-705:
------------------------------------

(03:31:20 PM) lincolnthree: kenfinnigan: https://github.com/forge/core/tree/2.0/plugin-container-api/src/main/java/org/jboss/forge/container
(03:31:47 PM) lincolnthree: You'll want to probably figure out how people are going to interact with the Resource API
(03:32:06 PM) lincolnthree: In Forge 1.x, you had to @Inject the ResourceFactory
(03:32:13 PM) lincolnthree: That may still be the case in Forge 2.0
(03:32:18 PM) gastaldi: yeah
(03:32:20 PM) lincolnthree: But just something to consider.
(03:32:27 PM) lincolnthree: Something will need to set up the ResourceFactory
(03:32:47 PM) lincolnthree: And if you need to do that, you'll probably want to @Observes Startup event.
(03:33:02 PM) gastaldi: kenfinnigan: see the Aesh Addon example
(03:33:11 PM) gastaldi: there are some stuff in there to help
(03:33:41 PM) gastaldi: like the @Observes Startup event for instance
(03:34:22 PM) kenfinnigan: so would resources api be in forge-resource-addon module under core?
(03:34:46 PM) kenfinnigan: ie. create that module, or should the code live somewhere else?
(03:34:56 PM) lincolnthree: yeah, create that module
(03:35:01 PM) lincolnthree: for now we can put it all in the same repo
(03:35:06 PM) lincolnthree: but it should eventually be split up
                
> 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