[
https://issues.apache.org/jira/browse/SHINDIG-548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12627120#action_12627120
]
Brian Eaton commented on SHINDIG-548:
-------------------------------------
I think this is what we want:
1) We stop using maven to manage the Caja dependency.
2) .class files go in a jar, .js files stay separate files.
3) We check all of those in to shindig somewhere.
4) We wrestle with maven until it agrees to use them.
Why do it that way?
- it keeps the java and the javascript in the same place, so it's easy to
update both at the same time.
- it lets both the PHP and the Java code depend on the javascript.
> Regression: supporting javascript for caja no longer served
> -----------------------------------------------------------
>
> Key: SHINDIG-548
> URL: https://issues.apache.org/jira/browse/SHINDIG-548
> Project: Shindig
> Issue Type: Bug
> Components: Features (Javascript), Gadget Rendering Server (Java)
> Reporter: Jasvir Nagra
>
> Revision -r '{20080821}' breaks running of cajoled gadgets.
> To reproduce:
> 1. Add "<Require feature="caja"> to SocialHelloWorld.xml
> 2. Run samplecontainer either with or without "use caja"
> 3. Note that firebug reports missing ___ object
> This is a regression of a fix lryan added which invoked cajoling *and*
> serving of supporting javascript listed in caja/feature.xml whenever the
> gadget required feature caja, irrespective of url parameters.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
