Hi ! For my part I think I am done. Please have a look and check my English. It’s not my mother tongue … But more important check if the content is correct. I am not in all details and therefore I’d be happy if someone could check if the technical info is correct. I designed a gallery with the info I have. Please send me some examples. This would help to make that page more attractive and if you want to be mentioned on the about page, please feel free to send me what I shall integrate on that page. So far so good. @Wayne Is there a possibility to test the website under github Eclipse before it goes live? Best Christophe Von: birt-dev [mailto:birt-dev-bounces@xxxxxxxxxxx] Im Auftrag von Scott Rosenbaum
Gesendet: Mittwoch, 24. März 2021 15:31
An: For developers on the BIRT project
Betreff: Re: [birt-dev] Unit tests Alex, I can't point you to any documentation, but I can give you a bit of history from my fuzzy memories. First off, the goal of the runtime was to have a way to distribute BIRT free from the UI. The project wanted people to be able to include BIRT in their applications, but we did not want them to have to include all the UI components. So the Runtime is just those components required to Design (design engine API), Run, and Render reports with out any of the UI components present. When this was first created, it was tightly bundled with the whole eclipse platform, and required the engine to first start up the platform in order for the Report Engine to work. Once the project got going, there was a lot of demand from our users to create something that was not dependent on the Platform. "We just want to drop the jars in the lib directory and run reports" was a common request. So we modified the runtime to not be dependent on the platform, which is now the modern runtime. But what about users that have implemented BIRT using the 'old' way of doing things with all the platform code, plugins directory, etc. We didn't want to force them to change their code, or we wanted to let them just drop in their plugins. We also had customers that were deploying their reports within an RCP client. So that is what led to the Runtime-OSGI. It is simply a backwards compatible version of the Runtime. Do we need to keep it? I don't know, my guess is no, but I would leave that up to the community. Hi Steve,
I was able to workaround this particular failure by adding more bundles to birt-runtime-osgi, and then more and more.
And then I improved class loader creation a bit to consider more than one folder ... but then finally I was blocked by classes from Tidy.jar that archived inside org.eclipse.birt.report.engine bundle.
Perhaps someone can point me to a document that explains what is the specific goal of "birt-runtime-osgi" and why BIRT needs wrapper layer around Eclipse Platform
Regards,
AF 24.03.2021 16:29, Steve Schafer пишет: When using mvn package without -DskipTests it gets class-not-found errors. Is this the correct way to run the unit tests?
-- _______________________________________________ birt-dev mailing list birt-dev@xxxxxxxxxxx To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/birt-dev
_______________________________________________
birt-dev mailing list
birt-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/birt-dev
-- |
