[ 
http://mifosforge.jira.com/browse/MIFOS-4429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=64968#comment-64968
 ] 

Michael Vorburger commented on MIFOS-4429:
------------------------------------------

Ha! - I did it again, we're (about to) squash this one as well. "Here is what 
happened", as Mr. Monk would say:

BIRT is really... finiky... about the exact Rhino (JavaScript interpreter) 
js.jar it needs / likes.  Note for example the 
http://wiki.eclipse.org/BIRT/FAQ/Deployment#Q:_How_do_I_install_BIRT_in_JBoss.3F
 as well as "Q: How do I install BIRT in WebLogic 10.0" just underneath.  Also 
e.g. 
http://www.eclipse.org/forums/index.php?t=tree&goto=368429&S=4255026e208db32e9d8bb125a45cce6c,
 and on http://jira.pentaho.com/browse/BISERVER-2711 other folks who have 
trouble with the rhino/js JAR with BIRT.

The Rhino originally used in Mifos when I started all this is 756883 bytes 
large js.jar, see e.g. (currently still) on 
http://mifos.git.sourceforge.net/git/gitweb.cgi?p=mifos/head;a=tree;f=application/reporting/BirtWebViewer-2_5_0/WEB-INF/lib;h=79bd2c49a36328a96a01d28ef88e75d13abc4f42;hb=HEAD

On Hot Workspace 2.0, I had used a <version>1.6R7</version> of rhino:js in 
http://mifos.git.sourceforge.net/git/gitweb.cgi?p=mifos/head;a=blob;f=reporting-libs/pom.xml;h=f75f1c6d4b627ebf04d280c5fde7b959cc503768;hb=refs/heads/hudsonBuild-hotWorkspace
 - that was a somewhat arbitrary choice I made 1 month ago (to the day!), 
thinking that one was "close enough", because there doesn't seem to be a 756883 
bytes js.jar on http://repo1.maven.org/maven2/rhino/js/ as far as I can see 
(but I'd love others to double-check), so I'm not sure where the BIRT folks 
took theirs from...

Interestingly, in mifos-webapp (application) pom.xml around line 250-ish there 
is a the following comment: "This dependency overrides the earlier version of 
Rhino included by spring modules (?). The earlier version of Rhino is 
incompatible with BIRT. - [email protected]", forcing a rhino:js 
<version>1.7R2</version>.  But unless I'm dumb and tired, that doesn't work 
either (the pages above say "known issue with Rhino 1.7", although it's unclear 
which exact BIRT version that refers to). Before my Hot / Workspace 2.0 such a 
dependency was simply overridden during build by the js.jar from (formerly) 
application/reporting/BirtWebViewer-2_5_0/WEB-INF/lib... so... what was that 
for?!

Safest may be to use the exact same js.jar as before, with a org.mifos.birtlibs 
groupId like I did for the other BIRT JARs that are not available on Maven 
central.  I don't particularly like this, because if any other library drags 
along a different Rhino through a transitive dependency, the circus will start 
again.

I have manually tested all this blurb by forcing e.g. an 
<exclusions><exclusion><groupId>rhino</groupId><artifactId>js</artifactId></exclusion>
 </exclusions> in the mifos-webapp <dependency> of mifos-server-workspace's 
pom.xml, and adding the "original" js.jar simply on the Java Build Path as an 
External JAR, and got reports working in the workspace, with all projects open 
(WAR not yet tested).

No code changed / commit yet, would love feedback from others.  What's best 
here?

> New module 'reporting' (BIRT)
> -----------------------------
>
>                 Key: MIFOS-4429
>                 URL: http://mifosforge.jira.com/browse/MIFOS-4429
>             Project: mifos
>          Issue Type: Dev Task
>            Reporter: Michael Vorburger
>            Assignee: Michael Vorburger
>            Priority: Critical
>             Fix For: Release G
>
>
> What is all the stuff in application/reporting, BIRT?
> How is it used? Does the build make use of it (status unclear, to me) ?
> It won't work in my proposed "new workspace" (without some effort, may be 
> possible; haven't investigated).
> Remove?
> Hm.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

------------------------------------------------------------------------------
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
_______________________________________________
Mifos-issues mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mifos-issues

Reply via email to