BIRT Eclipse Installer error

[SteveSchafer-Innovent]

BIRT Eclipse Installer error

[merks]

Is the git repo pulled to the current state? It seems to me that project is deleted and that batik 1.17 has been used for quite some time now.

[SteveSchafer-Innovent]

It appears to be using my fork. I didn't expect that because I copied the link from the main BIRT page. Once I told GitHub to sync my fork that problem went away. Now I have 185 errors in eclipse but that will be a separate issue if I can't figure it out.

[merks]

FYI, I tested this morning:

Note that here I have checkmarked Show all variables. I clone with the original URI, not my fork, and I create the clone in a location relative to the installation so if I create a new installation, I clone a new clone. (The state of this checkmark is remembered for the next time so uncheck it once you are done inspecting all the variables that were previous recorded after changing any that you might want to change differently.)

The process completes like this:

The two maven errors are annoying, but I just delete them. I'm not sure why or if it's necessary to have maven builders at all. Certainly there is no need to generate Javadoc in the IDE...

This documentation describes the workflow most folks use when working with fork:

https://github.com/orgs/eclipse-simrel/discussions/3

With this approach you never need to be concerned with syncing your fork because you never clone the fork and never use the fork's master branch...