flugtiger / birt Goto Github PK

The tests of the engine-Module should be fixed (module 'org.eclipse.birt.report.engine.tests'). Thereafter they should be added to the travis build (add a new MODULE to .travis.yaml).

Acceptance Criteria

• Tests of the org.eclipse.birt.report.engine.tests -Module all pass
• Travis runs this modules tests automatically on each push

The target platform definition should be done using a PDE target definition file. This file can be imported into Eclipse to make it automatically resolve any dependencies not bundled within BIRT.
To not be required to maintain separate target definitions for Eclipse and the maven (tycho) build, tycho should use the same target definition file as Eclipse.

When the oomph setup tries to import all the BIRT projects into Eclipse, some projects are skipped due to duplicated project names.

Acceptance Criteria

• When oomph imports the BIRT projects into Eclipse, no projects are skipped anymore

Question here.

First of all, thank you for this repo. It's good to see that there is still a BIRT community alive.
I tried to follow your steps setup up the Eclipse IDE. However, a few (~100) build errors remain:
dom4j imports cannot be resolved.

Is there something I missed?
Thanks!

When importing the report viewer maven project into eclipse, m2e crashes. This is because the project builds two separate artifacts (web.jar and plugin.jar) which is not really support in maven.

Lower Java version have hit their end-of-support. Therefore it should be save to update the minimum required execution environment to Java 8 for all BIRT plugins (the platform already requires java 8).

due to https://support.sonatype.com/hc/en-us/articles/360041287334 the task fails with

ERROR: org.eclipse.equinox.p2.transport.ecf code=1002 HTTP Server 'Not Implemented': http://repo1.maven.org/maven2/.m2e/connectors/m2eclipse-tycho/0.8.1/N/LATEST/content.xml
ERROR: org.eclipse.ecf.identity code=0 HttpComponents connection error response code 501.
at org.eclipse.ecf.provider.filetransfer.httpclient4.HttpClientFileSystemBrowser.runRequest(HttpClientFileSystemBrowser.java:293)
at org.eclipse.ecf.provider.filetransfer.browse.AbstractFileSystemBrowser$DirectoryJob.run(AbstractFileSystemBrowser.java:69)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63)

Please adjust the Url to
https://repo1.maven.org/maven2/.m2e/connectors/m2eclipse-tycho/0.8.1/N/LATEST/content.xml

Hello Alexander

do you happen to know how to do a rcp designer build for Linux?

birt-rcp-report-designer-4.8.0-20180626-linux.gtk.x86_64.zip
found on http://mirrors.ibiblio.org/eclipse/birt/downloads/drops/R-R1-4.8.0-201806261756?

ps: i made some changes based on your fork: upgrade to apache batik 1.13, apache poi 4.1.1, replaced iText 2.1.7 with OpenPdf 1.3.24.
Great work you did, congrats!

Thank you
Andrej

When these tests are run, there is deadlock occurring sporadically:

org.eclipse.birt.core.archive.FileArchiveTest.testMutipleThreadReadWrite()
org.eclipse.birt.core.archive.FolderArchiveTest.testMutipleThreadReadWrite()

All the warnings issued by Eclipse that affect the plugins metadata files (plugin.xml, MANIFEST.MF, build.properties) should be fixed.
This helps to improve the overall code quality and keeps developers focused.

To make it easier for new contributors, there should be a short howto on github that describes the build process of BIRT.

We want Travis to test all BIRT modules. To speed up the build process, the different modules of BIRT shall be tested in parallel by using the 'matrix build' feature of Travis.

By leveraging Eclipse Oomph (https://projects.eclipse.org/projects/tools.oomph) the cumbersome process of setting up an IDE for Eclipse BIRT can be vastly simplified and shortened.

Travis should run the tests in org.eclipse.birt.report.model.tests and they should all pass

Hi!

Would it be easy to update POI to 3.17 - what would the steps be that are required?

Thanks
Thomas