[
https://issues.apache.org/jira/browse/SHINDIG-269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12597578#action_12597578
]
Kevin Brown commented on SHINDIG-269:
-------------------------------------
The features.txt file is very awkward, but nobody seemed to have a good
alternative solution other than loading from disk. For my own deployments, I
always use the disk-based loading to avoid dealing with the text file.
If you know a better way to recursively load the xml files, that would be very
helpful. Various wildcard matching on resource loaders didn't seem to work.
> package all features in a single jar, load from classpath
> ---------------------------------------------------------
>
> Key: SHINDIG-269
> URL: https://issues.apache.org/jira/browse/SHINDIG-269
> Project: Shindig
> Issue Type: Improvement
> Components: Features (Javascript), Gadget Rendering Server (Java)
> Reporter: Henning Schmiedehausen
> Attachments: javascript-jar.patch
>
>
> The attached patch creates a Maven project for the features directory. This
> allows automatic packaging up of the features into a single jar, which then
> can be placed on the classpath for the gadget server and the demo container.
> This removes the need for the various javascript related plugins from the
> gadget rendering server and also a number of the cross-project linking and
> copying. The features directory itself is not modified, so the PHP version
> should still run fine.
> In the long run, it might be good to move the features out of the root
> directory and into e.g. src/javascript to allow better control of the jar
> creation.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
