-
Notifications
You must be signed in to change notification settings - Fork 386
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How to handle the Jetty inclusion #621
Comments
The previewer not working is a real show-stopper. |
I am working on including jetty. The effort is combined with #640 |
To avoid confusion: The issue I am seeing is that when unzipping the generated birt-report-designer-all-in-one-4.9.0-2021*-win32.win32.x86_64.zip, calling eclipse.exe there, switching to the Report Design perspective, open any report and and then selecting the menu entry Run -> View Report -> As PDF (or As HTML) this results in
So it seems like Jetty is included somehow, but obviously BIRT and Jetty don't like each other. Is this the issue you describe here? |
Yes. |
Did you read https://www.optimaw.ch/change-to-jdk11-lts/ ? |
I wish I had seen this sooner. I basically went through the same research. Please note that the current HEAD is now compiling with JDK11. |
you can get the compiled jetty-plugin here; https://www.optimaw.ch/nexus/#browse/browse:birt-reloaded, if needed. |
Fixed and verified. |
Jetty is no longer in the release train. This has the following drawbacks:
This was causing the viewer to break when installing 4.9 (from Mar 17 2021) into 4.19.
The BIRT feature included the
o.e.jetty.osgi.boot
bundle which clashed with newer jetty versions. This inclusion was removed with commit 161d153To install the viewer correctly the jetty 9.x update site must be added to the available update sites.
We need to find a fix for it.
The text was updated successfully, but these errors were encountered: