[
https://issues.jboss.org/browse/FORGE-143?page=com.atlassian.jira.plugin....
]
Jason Porter commented on FORGE-143:
------------------------------------
If it's part of a facet, that will work too. I haven't read the new docs yet, but
Facets need to play a bigger part, maybe putting some of these utilities on the facets
makes more sense. Things like current package, creating Java files, common things each
plugin would need to do. There's no point in having each plugin copy / paste all the
same code to do the same actions.
Create some base classes for plugin development
-----------------------------------------------
Key: FORGE-143
URL:
https://issues.jboss.org/browse/FORGE-143
Project: Forge
Issue Type: Enhancement
Components: Plugin API
Affects Versions: 1.0.0.Alpha4
Reporter: Jason Porter
Priority: Minor
There are some core actions a plugin that creates Java classes must do, such as get the
current package. Actions like this should be on an abstract base class such as
JavaSourceCreationPluginBase (maybe something shorter?) which would also implement Plugin
(so we don't break existing plugins) that will have these methods baked in so each
plugin doesn't end up copying the code from somewhere else. If Java had mixins this
would be a perfect fit, alas, it does not and we're stuck with something else.
The class would probably have to have some abstract getter methods that the subclass
would have to implement to get common things like the project.
--
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