This post has NOT been accepted by the mailing list yet.
Thanks for your answer.
We checked several plugins last week, regarding structure and dependencies.
In my opinion, having in mind current plugin structure there is missing part, which is pretty important. Most of the plugins have some presentation on the site, some content on the page. At the moment that presentation part of the plugin which will be used in the site project, is missing. Plugin I am working on at the moment, has:
-cms part (frontend-namespace.xml and hippoecm-extension.xml, wicket specific classes, etc)
-site part (some utility classes, which will be used in BaseHstComponent and jsp tag which will render plugin specific content on the page).
Therefore, appropriate structure for the plugin in my case will be:
The rest should be easy:
1. Add referenced dependencies into CMS and Site projects, regarding plugin (Cms project will have dependency to myplugin-cms.jar, similar goes for site)
2. Some minor adjustments in the code must be done like: include JSP tag on the page, use this utility classes provided to grab plugin specific data,... (Some readme.txt to describe details should be fine.)
In our case this works perfectly. We are discussing to make maven archetype, having in mind structure and dependencies defined above.
This is the idea. Is this good approach? What is your opinion?