[forge-issues] [JBoss JIRA] (FORGE-425) Provide a way to override plugin resources without coding

Richard Kennard (JIRA) jira-events at lists.jboss.org
Thu Apr 19 19:13:18 EDT 2012


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

Richard Kennard commented on FORGE-425:
---------------------------------------

Hi guys. Just noticed FORGE-216. I'm not clear how that ties into this? It appears to be a weaker form of this request, but I think it'd be nice to have a more general purpose solution?
                
> Provide a way to override plugin resources without coding
> ---------------------------------------------------------
>
>                 Key: FORGE-425
>                 URL: https://issues.jboss.org/browse/FORGE-425
>             Project: Forge
>          Issue Type: Feature Request
>            Reporter: Richard Kennard
>
> At present, Forge makes it easy for users to add their own plugins by writing some code.
> However this is onerous for use cases where users just want to tweak some static resource or template. For scaffolding specifically, but for plugins generally, it would be good to have a mechanism to allow users to easily 'drop in' replacement files.
> From discussions on the mailing list, the consensus seems to be:
> 1. Plugins should keep their resources in as flat a structure as possible. For example at the moment scaffolding uses "resources/org/jboss/forge/scaffold/faces/scaffold/BackingBean.jv" but we should change this to, say, "resources/scaffold/BackingBean.jv"
> 2. Forge should provide a folder, say, /forge-distribution/resources where users can drop replacement files
> There is some disagreement over how this is to be implemented. The concerns are:
> 1. Richard would prefer that plugins did not have to explicitly worry about this 'replacement mechanism'. Lots of plugins already call .getResource, so it'd be good if this just magically checked /forge-distribution/resources for us.
> 2. Max does not want this 'replacement mechanism' to work by putting /forge-distribution/resources on the classpath (Max can explain why :)

--
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

        


More information about the forge-issues mailing list