markobean commented on pull request #5307: URL: https://github.com/apache/nifi/pull/5307#issuecomment-906481048
You're correct that -DexcludeNiFiRegistry will not work on a clean machine/clean local maven repo - not if the version you are building is not available in your specified maven repositories. So, an initial build of nifi-registry will have to be performed (or deps available in a remote maven repo for the particular version you are building.) As for excluding NiFi from the other builds, e.g. NiFi Registry, I had originally considered that. However, I did not believe it was necessary. If you want to build NiFi Registry, for example, you simply run the build from ~/nifi/nifi-registry rather than from the project root, ~/nifi/. (Alternatively, run the build with `-f` flag from maven specifying the ~/nifi/nifi-registry/pom.xml.) I just tried that, and there are in fact dependencies required by nifi-registry. `Could not find artifact org.apache.nifi:nifi-sensitive-property-provider:jar:1.15.0-SNAPSHOT ` So, it appears that this is problematic in both cases (building NiFi without NiFi Registry, or building NiFi Registry without NiFi). However, the use case here is for repeated development builds. I think it would still be a useful feature for a developer and/or CI/CD after performing a full build for a given version. This allows a similar strategy as building a single NAR bundle without requiring a re-build of the entire project. Still open to suggestions if you find the existing behavior too limiting. -- 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]
