mattcasters opened a new pull request, #8388: URL: https://github.com/apache/hop/pull/8388
Fixes #8387 Incremental GitHub PR builds fail while resolving `hop-ui-rcp`: ```text Could not find artifact org.eclipse:org.eclipse.tm4e.core:jar:2.20.0-SNAPSHOT ``` That coordinate is Hop's unpublished `lib-p2/tm4e` wrapper (Eclipse TM4E 0.17.2 installed under the Hop version). It is never deployed (`maven.deploy.skip`, excluded from the snapshot wagon). Full `main` builds still work because GIB is disabled there. After #8356, PR jobs enable gitflow-incremental-builder. With default `buildUpstreamMode=changed`, GIB rebuilds upstreams of *directly changed* modules only. A `hop-ui` change therefore selects `hop-ui-rcp` as downstream and drops `org.eclipse.tm4e.core`, so Maven looks for the SNAPSHOT in repositories and fails. This keeps the two unpublished P2 wrappers in every incremental reactor: ```xml <gib.forceBuildModules>org.eclipse.tm4e.core,org.eclipse.swtbot.swt.finder</gib.forceBuildModules> ``` SWTBot has the same unpublished wrapper shape and would hit the same hole on a different change set. Verified locally by simulating a `hop-ui`-only change with GIB enabled: the reactor now includes Eclipse TM4E Core Wrapper and `hop-ui-rcp` resolves. ------------------------ - [x] Run `mvn clean install apache-rat:check` to make sure basic checks pass. A more thorough check will be performed on your pull request automatically. - [x] If you have a group of commits related to the same change, please squash your commits into one and force push your branch using `git rebase -i`. - [x] Mention the appropriate issue in your description (for example: `addresses #123`), if applicable. - [x] I hereby declare this contribution to be licensed under the [Apache License Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0) - [ ] In any other case, please file an [Apache Individual Contributor License Agreement](https://www.apache.org/licenses/icla.pdf). -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
