Type: Feature Request
Resolution: Out of Date
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