The information in the plugins.xml file would be better kept in the plugin directory and added to the plugins.xml file when deployed. This would reduce the amount of duplication in the plugins config files.
All the necessary values are now in the plugin build.xml file.
This change will require that the plugins.xml file be retrieved from the build directory rather than the plugins directory when building the plugin documentation pages. We will therefore need a fall back to retrieve this file from the network if it is not currently available - this can be done with the locationmap
Description
The information in the plugins.xml file would be better kept in the plugin directory and added to the plugins.xml file when deployed. This would reduce the amount of duplication in the plugins config files.
All the necessary values are now in the plugin build.xml file.
This change will require that the plugins.xml file be retrieved from the build directory rather than the plugins directory when building the plugin documentation pages. We will therefore need a fall back to retrieve this file from the network if it is not currently available - this can be done with the locationmap
deploy versioned plugins (partial solution for FOR-528), also took the opportunity to add some properties to the plugin build file that will be needed for (FOR-533)
Use original specific match to process only the "Plugins Index" and not also normal xdocs.
Fix the break caused by r521010 for URIs like pluginDocs/index.html and pluginDocs/plugins_0_80/usingPlugins.html
Part of FOR-533.
Improvement
Open
Minor
Auto Generate plugins.xml entry
