[#BIRT-44] Allow BIRT Module to be deployed as two separate modules - OpenMRS JIRA

Details

Type: New Feature
Status: Needs Assessment
Priority: Should
Resolution: Unresolved
Affects Version/s: None
Fix Version/s: None
Component/s: None

Keywords:

Description:

Hide

The BIRT Report Module is rather large, weighing in at around 10MB. The majority of that comes in the form of JARs required by the BIRT Report Engine. These JARs should be deployed as a separate module (i.e. birt-engine-2_2_0.omod) so that the BIRT integration code can be deployed more easily as another module (birt-report-2_2_0.omod). This is important for implementation in remote locations like Rwanda and Malawi.

This will require changes to the BIRT Report Module build.xml to create multiple omods from the same code base.

In addition, this may also require a change to the module code to allow modules to specify which module version they depend on. Right now, I believe, you can only specify which module dependency, not fine-grained module version dependencies.

Show
The BIRT Report Module is rather large, weighing in at around 10MB. The majority of that comes in the form of JARs required by the BIRT Report Engine. These JARs should be deployed as a separate module (i.e. birt-engine-2_2_0.omod) so that the BIRT integration code can be deployed more easily as another module (birt-report-2_2_0.omod). This is important for implementation in remote locations like Rwanda and Malawi. This will require changes to the BIRT Report Module build.xml to create multiple omods from the same code base. In addition, this may also require a change to the module code to allow modules to specify which module version they depend on. Right now, I believe, you can only specify which module dependency, not fine-grained module version dependencies.

Activity

Ascending order - Click to sort in descending order

Hide

Permalink

Justin Miranda added a comment - 2010-05-03 16:26:09 EDT

Initial commit rev:13211 - Created a separate branch for a module that only contains the BIRT Report Engine and Design Engine APIs. All reporting functionality that uses the BIRT APIs will continue to exist in the module trunk/branches. The trunk/branches will reference the API module rather than the libraries directly. The branches which use the naming convention birtmodule-api-x.y.z will contain the matching BIRT APIs. A version of the BIRT module should be compatible and backwards compatible with multiple versions of the BIRT API module. This should make upgrading easier.

Show

Justin Miranda added a comment - 2010-05-03 16:26:09 EDT Initial commit rev:13211 - Created a separate branch for a module that only contains the BIRT Report Engine and Design Engine APIs. All reporting functionality that uses the BIRT APIs will continue to exist in the module trunk/branches. The trunk/branches will reference the API module rather than the libraries directly. The branches which use the naming convention birtmodule-api-x.y.z will contain the matching BIRT APIs. A version of the BIRT module should be compatible and backwards compatible with multiple versions of the BIRT API module. This should make upgrading easier.

BIRT Report Module

Allow BIRT Module to be deployed as two separate modules

Details

Activity

People

Dates