[
https://issues.apache.org/jira/browse/SHINDIG-269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12597297#action_12597297
]
Kevin Brown commented on SHINDIG-269:
-------------------------------------
"features" is intentionally a separate directory, and not everything in there
is going to be javascript. The main piece of data in the features directory is
XML. The javascript files themselves could be placed into javascript/, but that
makes globbing files more difficult.
trunk/javascript is entirely for sample files and the like.
> 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.
