Community
Participate
Working Groups
Build Identifier: When deploying a BIRT application, the BIRT OSGi engine is placed within the application. It would be good if we could set BIRT so that the engine is somewhere in the file system. This would decrease BIRT applications for about 30 MB. I will create a patch. Reproducible: Always
Attached is a patch. The user can create a platform folder somewhere in the workspace and add it to the application as follows: - create a context parameter like the following: <context-param> <description>The platform home directory. Default to WEB-INF/platform</description> <param-name>BIRT_PLATFORM_HOME</param-name> <param-value>C:/platform</param-value> </context-param> - start the server using -DBIRT_PLATFORM_HOME=c:\platform The attached image shows the UI in which the user can do the following: - enter a platform home (BIRT facet delegate will automatically create a context parameter) - copy platform resources to the entered directory (the Create Platform button) - can decide whether to copy the platform to WEB-INF/platform of the application (the Copy Platform checkbox) If the user doesn't change anything, the BIRT facet will behave as before. coreapi.jar in the WEB-INF/lib directory needs to be replaced with the attached coreapi.jar when testing the patch (or a new birt.zip needs to be created within the Birt WTP integration plugin).
Created attachment 191584 [details] a patch
Created attachment 191585 [details] BIRT facet page
Created attachment 191586 [details] coreapi.jar
