You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@shindig.apache.org by "Kevin Brown (JIRA)" <ji...@apache.org> on 2008/05/16 13:11:55 UTC
[jira] Closed: (SHINDIG-269) package all features in a single jar,
load from classpath
[ https://issues.apache.org/jira/browse/SHINDIG-269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kevin Brown closed SHINDIG-269.
-------------------------------
Resolution: Fixed
Applied patch as is, but removed <includes> so that all files are always pulled in.
> 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.