Ticket #276 (closed Enhancement: fixed)
Pick up JavaScript plugin files automatically
Reported by: | jri | Owned by: | jri |
---|---|---|---|
Priority: | Major | Milestone: | Release 4.1 |
Component: | DeepaMehta Standard Distribution | Version: | 4.0.11 |
Keywords: | Cc: | dgf | |
Complexity: | 5 | Area: | Application Framework / API |
Module: | deepamehta-webclient |
Description
The "clientSidePluginFile" configuration property should be abolished.
"Convention Over Configuration" rules.
Change History
comment:3 Changed 12 years ago by Jörg Richter
Webclient: auto pick up plugin classes (#276).
The "clientSidePluginFile" plugin config property is obsolete.
Wording in API: "Plugin ID" is now called "Plugin URI".
IMPORTANT: plugin developers must rename the plugin's main file to "plugin.js"
Name and location is fixed:
/web/script/plugin.js
Hint: if you use Maven resource filtering for your plugin main file don't forget to adapt the POM.
See ticket 276.
comment:4 in reply to: ↑ 2 Changed 12 years ago by jri
Replying to dgf:
which convention you have in mind?
Fixed file name and location.
Just like e.g. CKEditor's plugins.
comment:5 Changed 12 years ago by jri
- Status changed from accepted to closed
- Resolution set to fixed
comment:6 Changed 12 years ago by Jörg Richter
Webclient: auto pick up plugin classes (#276).
The "clientSidePluginFile" plugin config property is obsolete.
Wording in API: "Plugin ID" is now called "Plugin URI".
IMPORTANT: plugin developers must rename the plugin's main file to "plugin.js"
Name and location is fixed:
/web/script/plugin.js
Hint: if you use Maven resource filtering for your plugin main file don't forget to adapt the POM.
See ticket 276.
comment:7 Changed 12 years ago by Jörg Richter
Webclient: auto pick up plugin classes (#276).
The "clientSidePluginFile" plugin config property is obsolete.
Wording in API: "Plugin ID" is now called "Plugin URI".
IMPORTANT: plugin developers must rename the plugin's main file to "plugin.js"
Name and location is fixed:
/web/script/plugin.js
Hint: if you use Maven resource filtering for your plugin main file don't forget to adapt the POM.
See ticket 276.