Re: MiNiFi C2 Module Removal

[David Handermann]

Thanks for the confirmation, Arpad.

Pending the approval of the pull request, I will update the Migration
Guide and NiFi 2.0 Deprecated Components and Features pages.

Regards,
David Handermann


On Mon, Jan 22, 2024 at 4:53 PM Arpad Boda  wrote:
>
> Thanks, David,
>
> At the moment I don't see anyone maintaining it, so some docs should be
> updated to make it clear that it's not part of the 2.0 line anymore,
> otherwise I don't see any better solution.
>
> Regards,
> Arpad
>
> On Mon, Jan 22, 2024 at 11:35 PM David Handermann <
> exceptionfact...@apache.org> wrote:
>
> > Arpad,
> >
> > Thanks for the reply.
> >
> > I submitted a pull request [1] which deletes the modules from the main
> > branch. As described in the Jira issues, the purpose is to eliminate
> > maintenance of the C2 server components as they stand.
> >
> > [1] https://github.com/apache/nifi/pull/8291
> >
> > Regards,
> > David Handermann
> >
> > On Mon, Jan 22, 2024 at 4:33 PM Arpad Boda 
> > wrote:
> > >
> > > David,
> > >
> > > Thanks for bringing up this topic!
> > > How do you mean removing it? Moving it into a different repo?
> > >
> > > Thanks,
> > > Arpad
> > >
> > > On Mon, Jan 22, 2024 at 11:29 PM David Handermann <
> > > exceptionfact...@apache.org> wrote:
> > >
> > > > Team,
> > > >
> > > > In the process of reviewing the repository for NiFi 2.0.0 release
> > > > planning, it looks the minifi-c2 bundle of modules should be
> > > > considered for removal from the repository.
> > > >
> > > > NIFI-9428 [1] describes the general effort around MiNiFi command and
> > > > control, including a task to create a C2 server reference
> > > > implementation. Based on the passage of time and the lack of changes,
> > > > removing the MiNiFi C2 server modules from the repository seems to be
> > > > the best approach as part of NiFi 2.0.0 release efforts. Even if a new
> > > > reference implementation were to be created, it would be better to
> > > > start with a clean slate, as outlined in the reference Jira issue.
> > > >
> > > > I have captured the proposal in NIFI-12657 [2] and I will be
> > > > submitting a pull request to implement the removal.
> > > >
> > > > Regards,
> > > > David Handermann
> > > >
> > > > [1] https://issues.apache.org/jira/browse/NIFI-9428
> > > > [2] https://issues.apache.org/jira/browse/NIFI-12657
> > > >
> >

Re: MiNiFi C2 Module Removal

[Arpad Boda]

Thanks, David,

At the moment I don't see anyone maintaining it, so some docs should be
updated to make it clear that it's not part of the 2.0 line anymore,
otherwise I don't see any better solution.

Regards,
Arpad

On Mon, Jan 22, 2024 at 11:35 PM David Handermann <
exceptionfact...@apache.org> wrote:

> Arpad,
>
> Thanks for the reply.
>
> I submitted a pull request [1] which deletes the modules from the main
> branch. As described in the Jira issues, the purpose is to eliminate
> maintenance of the C2 server components as they stand.
>
> [1] https://github.com/apache/nifi/pull/8291
>
> Regards,
> David Handermann
>
> On Mon, Jan 22, 2024 at 4:33 PM Arpad Boda 
> wrote:
> >
> > David,
> >
> > Thanks for bringing up this topic!
> > How do you mean removing it? Moving it into a different repo?
> >
> > Thanks,
> > Arpad
> >
> > On Mon, Jan 22, 2024 at 11:29 PM David Handermann <
> > exceptionfact...@apache.org> wrote:
> >
> > > Team,
> > >
> > > In the process of reviewing the repository for NiFi 2.0.0 release
> > > planning, it looks the minifi-c2 bundle of modules should be
> > > considered for removal from the repository.
> > >
> > > NIFI-9428 [1] describes the general effort around MiNiFi command and
> > > control, including a task to create a C2 server reference
> > > implementation. Based on the passage of time and the lack of changes,
> > > removing the MiNiFi C2 server modules from the repository seems to be
> > > the best approach as part of NiFi 2.0.0 release efforts. Even if a new
> > > reference implementation were to be created, it would be better to
> > > start with a clean slate, as outlined in the reference Jira issue.
> > >
> > > I have captured the proposal in NIFI-12657 [2] and I will be
> > > submitting a pull request to implement the removal.
> > >
> > > Regards,
> > > David Handermann
> > >
> > > [1] https://issues.apache.org/jira/browse/NIFI-9428
> > > [2] https://issues.apache.org/jira/browse/NIFI-12657
> > >
>

Re: MiNiFi C2 Module Removal

[David Handermann]

Arpad,

Thanks for the reply.

I submitted a pull request [1] which deletes the modules from the main
branch. As described in the Jira issues, the purpose is to eliminate
maintenance of the C2 server components as they stand.

[1] https://github.com/apache/nifi/pull/8291

Regards,
David Handermann

On Mon, Jan 22, 2024 at 4:33 PM Arpad Boda  wrote:
>
> David,
>
> Thanks for bringing up this topic!
> How do you mean removing it? Moving it into a different repo?
>
> Thanks,
> Arpad
>
> On Mon, Jan 22, 2024 at 11:29 PM David Handermann <
> exceptionfact...@apache.org> wrote:
>
> > Team,
> >
> > In the process of reviewing the repository for NiFi 2.0.0 release
> > planning, it looks the minifi-c2 bundle of modules should be
> > considered for removal from the repository.
> >
> > NIFI-9428 [1] describes the general effort around MiNiFi command and
> > control, including a task to create a C2 server reference
> > implementation. Based on the passage of time and the lack of changes,
> > removing the MiNiFi C2 server modules from the repository seems to be
> > the best approach as part of NiFi 2.0.0 release efforts. Even if a new
> > reference implementation were to be created, it would be better to
> > start with a clean slate, as outlined in the reference Jira issue.
> >
> > I have captured the proposal in NIFI-12657 [2] and I will be
> > submitting a pull request to implement the removal.
> >
> > Regards,
> > David Handermann
> >
> > [1] https://issues.apache.org/jira/browse/NIFI-9428
> > [2] https://issues.apache.org/jira/browse/NIFI-12657
> >

Re: MiNiFi C2 Module Removal

[Arpad Boda]

David,

Thanks for bringing up this topic!
How do you mean removing it? Moving it into a different repo?

Thanks,
Arpad

On Mon, Jan 22, 2024 at 11:29 PM David Handermann <
exceptionfact...@apache.org> wrote:

> Team,
>
> In the process of reviewing the repository for NiFi 2.0.0 release
> planning, it looks the minifi-c2 bundle of modules should be
> considered for removal from the repository.
>
> NIFI-9428 [1] describes the general effort around MiNiFi command and
> control, including a task to create a C2 server reference
> implementation. Based on the passage of time and the lack of changes,
> removing the MiNiFi C2 server modules from the repository seems to be
> the best approach as part of NiFi 2.0.0 release efforts. Even if a new
> reference implementation were to be created, it would be better to
> start with a clean slate, as outlined in the reference Jira issue.
>
> I have captured the proposal in NIFI-12657 [2] and I will be
> submitting a pull request to implement the removal.
>
> Regards,
> David Handermann
>
> [1] https://issues.apache.org/jira/browse/NIFI-9428
> [2] https://issues.apache.org/jira/browse/NIFI-12657
>

MiNiFi C2 Module Removal

[David Handermann]

Team,

In the process of reviewing the repository for NiFi 2.0.0 release
planning, it looks the minifi-c2 bundle of modules should be
considered for removal from the repository.

NIFI-9428 [1] describes the general effort around MiNiFi command and
control, including a task to create a C2 server reference
implementation. Based on the passage of time and the lack of changes,
removing the MiNiFi C2 server modules from the repository seems to be
the best approach as part of NiFi 2.0.0 release efforts. Even if a new
reference implementation were to be created, it would be better to
start with a clean slate, as outlined in the reference Jira issue.

I have captured the proposal in NIFI-12657 [2] and I will be
submitting a pull request to implement the removal.

Regards,
David Handermann

[1] https://issues.apache.org/jira/browse/NIFI-9428
[2] https://issues.apache.org/jira/browse/NIFI-12657

Re: [CANCEL][VOTE] Release Apache NiFi 2.0.0-M2 (RC1)

[David Handermann]

Chris,

Regarding the new UI profile, it should not be included in the
include-all because it is currently still in progress. However, from a
source management perspective, all of the Maven modules should reflect
the release version, so I plan to cover that in the next release
candidate build.

Regards,
David Handermann

On Mon, Jan 22, 2024 at 10:05 AM Chris Sampson
 wrote:
>
> Maven might have got itself confused. Could you try clearing out your
> .m2/repository (at least if anything in the org/apache/nifi directories)?
>
> Note that if you delete the whole local repo, then the build will need to
> re-download all 3rd party libraries too, so things will take longer.
>
> On the new UI front, should it be covered by the include-all profile in the
> nifi-assembly (I don't think it is currently, but that's maybe intentional
> and in the cards to change later one it's more stable)?
>
> On Mon, 22 Jan 2024, 15:58 Dan S,  wrote:
>
> > ./mvnw -T 1C clean install -Pcontrib-check
> >
> > On Mon, Jan 22, 2024 at 10:55 AM David Handermann <
> > exceptionfact...@apache.org> wrote:
> >
> > > Dan,
> > >
> > > Thanks for noting this build behavior.
> > >
> > > The release candidate process does not publish artifacts to the Maven
> > > Central repository. The RC build only publishes artifacts to the
> > > Apache Nexus staging repository. When running the standard full
> > > rebuild as described in the release verification steps, it should not
> > > try to retrieve release versions at all. Can you provide the command
> > > you used for the initial build?
> > >
> > > Regards,
> > > David Handermann
> > >
> > > On Mon, Jan 22, 2024 at 9:52 AM Dan S  wrote:
> > > >
> > > > Sorry typo in my previous email
> > > >  would like to bring to your attention that I had a problem building as
> > > > certain dependencies did seem to be present in Maven repos.
> > > >  would like to bring to your attention that I had a problem building as
> > > > certain dependencies did not seem to be present in Maven repos.
> > > >
> > > > On Mon, Jan 22, 2024 at 10:36 AM Dan S  wrote:
> > > >
> > > > > David,
> > > > >  Despite cancelling RC1 I would like to bring to your attention that
> > I
> > > had
> > > > > a problem building as certain dependencies did seem to be present in
> > > Maven
> > > > > repos.
> > > > > I initially got
> > > > >
> > > > >> Could not resolve dependencies for project
> > > > >> org.apache.nifi:nifi-stateless-nar:nar:2.0.0-M2: The following
> > > artifacts
> > > > >> could not be resolved:
> > > org.apache.nifi:nifi-stateless-engine:jar:2.0.0-M2
> > > > >> (absent): Could not find artifact
> > > > >> org.apache.nifi:nifi-stateless-engine:jar:2.0.0-M2 in central (
> > > > >> https://repo.maven.apache.org/maven2)
> > > > >
> > > > >
> > > > > I tried resuming and I had to manually resume with the following as
> > it
> > > > > errored each time.
> > > > >
> > > > >> ./mvnw -T 1C clean install -Pcontrib-check -rf :nifi-stateless-nar
> > > > >> ./mvnw -T 1C clean install -Pcontrib-check -rf :nifi-salesforce-nar
> > > > >> ./mvnw -T 1C clean install -Pcontrib-check -rf :nifi-zendesk-nar
> > > > >> ./mvnw -T 1C clean install -Pcontrib-check -rf :nifi-airtable-nar
> > > > >> ./mvnw -T 1C clean install -Pcontrib-check -rf
> > > :nifi-box-services-api-nar
> > > > >> ./mvnw -T 1C clean install -Pcontrib-check -rf :nifi-cipher-nar
> > > > >
> > > > >
> > > > > At the last command I got an error with
> > > > >
> > > > >> [ERROR] Failed to execute goal on project nifi-cipher-nar: Could not
> > > > >> resolve dependencies for project
> > > > >> org.apache.nifi:nifi-cipher-nar:nar:2.0.0-M2: The following
> > artifacts
> > > could
> > > > >> not be resolved: org.apache.nifi:nifi-cipher-processors:jar:2.0.0-M2
> > > > >> (absent), org.apache.nifi:nifi-standard-shared-nar:nar:2.0.0-M2
> > > (absent):
> > > > >> org.apache.nifi:nifi-cipher-processors:jar:2.0.0-M2 was not found in
> > > > >> https://repo.maven.apache.org/maven2 during a previous attempt.
> > This
> > > > >> failure was cached in the local repository and resolution is not
> > > > >> reattempted until the update interval of central has elapsed or
> > > updates are
> > > > >> forced -> [Help 1]
> > > > >> [ERROR] Failed to execute goal on project nifi-apicurio-nar: Could
> > not
> > > > >> resolve dependencies for project
> > > > >> org.apache.nifi:nifi-apicurio-nar:nar:2.0.0-M2: The following
> > > artifacts
> > > > >> could not be resolved:
> > > > >> org.apache.nifi:nifi-apicurio-schema-registry-service:jar:2.0.0-M2
> > > > >> (absent), org.apache.nifi:nifi-standard-shared-nar:nar:2.0.0-M2
> > > (absent):
> > > > >> Could not find artifact
> > > > >> org.apache.nifi:nifi-apicurio-schema-registry-service:jar:2.0.0-M2
> > in
> > > > >> central (https://repo.maven.apache.org/maven2) -> [Help 1]
> > > > >> [ERROR] Failed to execute goal on project nifi-py4j-nar: Could not
> > > > >> resolve dependencies for project
> > > > >> org.apache.nifi:nifi-py4j-nar:nar:2.0.0-M2: The 

Re: [CANCEL][VOTE] Release Apache NiFi 2.0.0-M2 (RC1)

[David Handermann]

Gabor,

Thanks for highlighting this issue, it sounds like the default
configuration expectation changed with the upgrade to Spring 6.

This should probably be carried over to a new thread, but based on an
initial review of the history, the MiNiFi C2 Server has had minimal
maintenance in the last two years, so it may be worth considering
removal from the main branch as part of NiFi 2.0.

Regards,
David Handermann

On Mon, Jan 22, 2024 at 1:02 PM Gábor Gyimesi  wrote:
>
> Hi,
>
> I've also found an issue with RC earlier today, that the Minifi C2 server
> is not working anymore with Minifi C++.
>
> It seems that the Jetty server upgrade which was part of NIFI-11703 (
> https://github.com/apache/nifi/pull/8197) broke the compatibility and now
> we are getting 403 Forbidden response in the heartbeats:
>
> 2024-01-22 15:54:47,262 DEBUG [qtp443721024-38]
> o.s.security.web.csrf.CsrfFilter Invalid CSRF token found for
> http://localhost:10090/c2/config/heartbeat
> 2024-01-22 15:54:47,263 DEBUG [qtp443721024-38]
> o.s.s.web.access.AccessDeniedHandlerImpl Responding with 403 status
> code
>
> Kalman Jantner is working on the issue, maybe this fix should also be
> included in the next RC.
>
> BR,
> Gabor
>
> On Mon, 22 Jan 2024 at 17:08, Dan S  wrote:
>
> > Joe,
> >  I do not have any specific settings.xml.
> >
> > Chris,
> >  Before building I had wiped away my local Maven repo per the optional step
> > in Release Candidate Verification
> > <
> > https://cwiki.apache.org/confluence/display/NIFI/Release+Candidate+Verification
> > >
> >
> > On Mon, Jan 22, 2024 at 11:05 AM Chris Sampson
> >  wrote:
> >
> > > Maven might have got itself confused. Could you try clearing out your
> > > .m2/repository (at least if anything in the org/apache/nifi directories)?
> > >
> > > Note that if you delete the whole local repo, then the build will need to
> > > re-download all 3rd party libraries too, so things will take longer.
> > >
> > > On the new UI front, should it be covered by the include-all profile in
> > the
> > > nifi-assembly (I don't think it is currently, but that's maybe
> > intentional
> > > and in the cards to change later one it's more stable)?
> > >
> > > On Mon, 22 Jan 2024, 15:58 Dan S,  wrote:
> > >
> > > > ./mvnw -T 1C clean install -Pcontrib-check
> > > >
> > > > On Mon, Jan 22, 2024 at 10:55 AM David Handermann <
> > > > exceptionfact...@apache.org> wrote:
> > > >
> > > > > Dan,
> > > > >
> > > > > Thanks for noting this build behavior.
> > > > >
> > > > > The release candidate process does not publish artifacts to the Maven
> > > > > Central repository. The RC build only publishes artifacts to the
> > > > > Apache Nexus staging repository. When running the standard full
> > > > > rebuild as described in the release verification steps, it should not
> > > > > try to retrieve release versions at all. Can you provide the command
> > > > > you used for the initial build?
> > > > >
> > > > > Regards,
> > > > > David Handermann
> > > > >
> > > > > On Mon, Jan 22, 2024 at 9:52 AM Dan S  wrote:
> > > > > >
> > > > > > Sorry typo in my previous email
> > > > > >  would like to bring to your attention that I had a problem
> > building
> > > as
> > > > > > certain dependencies did seem to be present in Maven repos.
> > > > > >  would like to bring to your attention that I had a problem
> > building
> > > as
> > > > > > certain dependencies did not seem to be present in Maven repos.
> > > > > >
> > > > > > On Mon, Jan 22, 2024 at 10:36 AM Dan S  wrote:
> > > > > >
> > > > > > > David,
> > > > > > >  Despite cancelling RC1 I would like to bring to your attention
> > > that
> > > > I
> > > > > had
> > > > > > > a problem building as certain dependencies did seem to be present
> > > in
> > > > > Maven
> > > > > > > repos.
> > > > > > > I initially got
> > > > > > >
> > > > > > >> Could not resolve dependencies for project
> > > > > > >> org.apache.nifi:nifi-stateless-nar:nar:2.0.0-M2: The following
> > > > > artifacts
> > > > > > >> could not be resolved:
> > > > > org.apache.nifi:nifi-stateless-engine:jar:2.0.0-M2
> > > > > > >> (absent): Could not find artifact
> > > > > > >> org.apache.nifi:nifi-stateless-engine:jar:2.0.0-M2 in central (
> > > > > > >> https://repo.maven.apache.org/maven2)
> > > > > > >
> > > > > > >
> > > > > > > I tried resuming and I had to manually resume with the following
> > as
> > > > it
> > > > > > > errored each time.
> > > > > > >
> > > > > > >> ./mvnw -T 1C clean install -Pcontrib-check -rf
> > :nifi-stateless-nar
> > > > > > >> ./mvnw -T 1C clean install -Pcontrib-check -rf
> > > :nifi-salesforce-nar
> > > > > > >> ./mvnw -T 1C clean install -Pcontrib-check -rf :nifi-zendesk-nar
> > > > > > >> ./mvnw -T 1C clean install -Pcontrib-check -rf
> > :nifi-airtable-nar
> > > > > > >> ./mvnw -T 1C clean install -Pcontrib-check -rf
> > > > > :nifi-box-services-api-nar
> > > > > > >> ./mvnw -T 1C clean install -Pcontrib-check -rf :nifi-cipher-nar
> > > > > > >
> > > > > > >
> > > > > > > At the 

Re: [CANCEL][VOTE] Release Apache NiFi 2.0.0-M2 (RC1)

[Dan S]

I was able to eventually build per my colleague's suggestion to run the
Maven build in a single thread without -T 1C.


On Mon, Jan 22, 2024 at 2:02 PM Gábor Gyimesi  wrote:

> Hi,
>
> I've also found an issue with RC earlier today, that the Minifi C2 server
> is not working anymore with Minifi C++.
>
> It seems that the Jetty server upgrade which was part of NIFI-11703 (
> https://github.com/apache/nifi/pull/8197) broke the compatibility and now
> we are getting 403 Forbidden response in the heartbeats:
>
> 2024-01-22 15:54:47,262 DEBUG [qtp443721024-38]
> o.s.security.web.csrf.CsrfFilter Invalid CSRF token found for
> http://localhost:10090/c2/config/heartbeat
> 2024-01-22 15:54:47,263 DEBUG [qtp443721024-38]
> o.s.s.web.access.AccessDeniedHandlerImpl Responding with 403 status
> code
>
> Kalman Jantner is working on the issue, maybe this fix should also be
> included in the next RC.
>
> BR,
> Gabor
>
> On Mon, 22 Jan 2024 at 17:08, Dan S  wrote:
>
> > Joe,
> >  I do not have any specific settings.xml.
> >
> > Chris,
> >  Before building I had wiped away my local Maven repo per the optional
> step
> > in Release Candidate Verification
> > <
> >
> https://cwiki.apache.org/confluence/display/NIFI/Release+Candidate+Verification
> > >
> >
> > On Mon, Jan 22, 2024 at 11:05 AM Chris Sampson
> >  wrote:
> >
> > > Maven might have got itself confused. Could you try clearing out your
> > > .m2/repository (at least if anything in the org/apache/nifi
> directories)?
> > >
> > > Note that if you delete the whole local repo, then the build will need
> to
> > > re-download all 3rd party libraries too, so things will take longer.
> > >
> > > On the new UI front, should it be covered by the include-all profile in
> > the
> > > nifi-assembly (I don't think it is currently, but that's maybe
> > intentional
> > > and in the cards to change later one it's more stable)?
> > >
> > > On Mon, 22 Jan 2024, 15:58 Dan S,  wrote:
> > >
> > > > ./mvnw -T 1C clean install -Pcontrib-check
> > > >
> > > > On Mon, Jan 22, 2024 at 10:55 AM David Handermann <
> > > > exceptionfact...@apache.org> wrote:
> > > >
> > > > > Dan,
> > > > >
> > > > > Thanks for noting this build behavior.
> > > > >
> > > > > The release candidate process does not publish artifacts to the
> Maven
> > > > > Central repository. The RC build only publishes artifacts to the
> > > > > Apache Nexus staging repository. When running the standard full
> > > > > rebuild as described in the release verification steps, it should
> not
> > > > > try to retrieve release versions at all. Can you provide the
> command
> > > > > you used for the initial build?
> > > > >
> > > > > Regards,
> > > > > David Handermann
> > > > >
> > > > > On Mon, Jan 22, 2024 at 9:52 AM Dan S  wrote:
> > > > > >
> > > > > > Sorry typo in my previous email
> > > > > >  would like to bring to your attention that I had a problem
> > building
> > > as
> > > > > > certain dependencies did seem to be present in Maven repos.
> > > > > >  would like to bring to your attention that I had a problem
> > building
> > > as
> > > > > > certain dependencies did not seem to be present in Maven repos.
> > > > > >
> > > > > > On Mon, Jan 22, 2024 at 10:36 AM Dan S 
> wrote:
> > > > > >
> > > > > > > David,
> > > > > > >  Despite cancelling RC1 I would like to bring to your attention
> > > that
> > > > I
> > > > > had
> > > > > > > a problem building as certain dependencies did seem to be
> present
> > > in
> > > > > Maven
> > > > > > > repos.
> > > > > > > I initially got
> > > > > > >
> > > > > > >> Could not resolve dependencies for project
> > > > > > >> org.apache.nifi:nifi-stateless-nar:nar:2.0.0-M2: The following
> > > > > artifacts
> > > > > > >> could not be resolved:
> > > > > org.apache.nifi:nifi-stateless-engine:jar:2.0.0-M2
> > > > > > >> (absent): Could not find artifact
> > > > > > >> org.apache.nifi:nifi-stateless-engine:jar:2.0.0-M2 in central
> (
> > > > > > >> https://repo.maven.apache.org/maven2)
> > > > > > >
> > > > > > >
> > > > > > > I tried resuming and I had to manually resume with the
> following
> > as
> > > > it
> > > > > > > errored each time.
> > > > > > >
> > > > > > >> ./mvnw -T 1C clean install -Pcontrib-check -rf
> > :nifi-stateless-nar
> > > > > > >> ./mvnw -T 1C clean install -Pcontrib-check -rf
> > > :nifi-salesforce-nar
> > > > > > >> ./mvnw -T 1C clean install -Pcontrib-check -rf
> :nifi-zendesk-nar
> > > > > > >> ./mvnw -T 1C clean install -Pcontrib-check -rf
> > :nifi-airtable-nar
> > > > > > >> ./mvnw -T 1C clean install -Pcontrib-check -rf
> > > > > :nifi-box-services-api-nar
> > > > > > >> ./mvnw -T 1C clean install -Pcontrib-check -rf
> :nifi-cipher-nar
> > > > > > >
> > > > > > >
> > > > > > > At the last command I got an error with
> > > > > > >
> > > > > > >> [ERROR] Failed to execute goal on project nifi-cipher-nar:
> Could
> > > not
> > > > > > >> resolve dependencies for project
> > > > > > >> org.apache.nifi:nifi-cipher-nar:nar:2.0.0-M2: The following
> > > > 

Re: [CANCEL][VOTE] Release Apache NiFi 2.0.0-M2 (RC1)

[Gábor Gyimesi]

Hi,

I've also found an issue with RC earlier today, that the Minifi C2 server
is not working anymore with Minifi C++.

It seems that the Jetty server upgrade which was part of NIFI-11703 (
https://github.com/apache/nifi/pull/8197) broke the compatibility and now
we are getting 403 Forbidden response in the heartbeats:

2024-01-22 15:54:47,262 DEBUG [qtp443721024-38]
o.s.security.web.csrf.CsrfFilter Invalid CSRF token found for
http://localhost:10090/c2/config/heartbeat
2024-01-22 15:54:47,263 DEBUG [qtp443721024-38]
o.s.s.web.access.AccessDeniedHandlerImpl Responding with 403 status
code

Kalman Jantner is working on the issue, maybe this fix should also be
included in the next RC.

BR,
Gabor

On Mon, 22 Jan 2024 at 17:08, Dan S  wrote:

> Joe,
>  I do not have any specific settings.xml.
>
> Chris,
>  Before building I had wiped away my local Maven repo per the optional step
> in Release Candidate Verification
> <
> https://cwiki.apache.org/confluence/display/NIFI/Release+Candidate+Verification
> >
>
> On Mon, Jan 22, 2024 at 11:05 AM Chris Sampson
>  wrote:
>
> > Maven might have got itself confused. Could you try clearing out your
> > .m2/repository (at least if anything in the org/apache/nifi directories)?
> >
> > Note that if you delete the whole local repo, then the build will need to
> > re-download all 3rd party libraries too, so things will take longer.
> >
> > On the new UI front, should it be covered by the include-all profile in
> the
> > nifi-assembly (I don't think it is currently, but that's maybe
> intentional
> > and in the cards to change later one it's more stable)?
> >
> > On Mon, 22 Jan 2024, 15:58 Dan S,  wrote:
> >
> > > ./mvnw -T 1C clean install -Pcontrib-check
> > >
> > > On Mon, Jan 22, 2024 at 10:55 AM David Handermann <
> > > exceptionfact...@apache.org> wrote:
> > >
> > > > Dan,
> > > >
> > > > Thanks for noting this build behavior.
> > > >
> > > > The release candidate process does not publish artifacts to the Maven
> > > > Central repository. The RC build only publishes artifacts to the
> > > > Apache Nexus staging repository. When running the standard full
> > > > rebuild as described in the release verification steps, it should not
> > > > try to retrieve release versions at all. Can you provide the command
> > > > you used for the initial build?
> > > >
> > > > Regards,
> > > > David Handermann
> > > >
> > > > On Mon, Jan 22, 2024 at 9:52 AM Dan S  wrote:
> > > > >
> > > > > Sorry typo in my previous email
> > > > >  would like to bring to your attention that I had a problem
> building
> > as
> > > > > certain dependencies did seem to be present in Maven repos.
> > > > >  would like to bring to your attention that I had a problem
> building
> > as
> > > > > certain dependencies did not seem to be present in Maven repos.
> > > > >
> > > > > On Mon, Jan 22, 2024 at 10:36 AM Dan S  wrote:
> > > > >
> > > > > > David,
> > > > > >  Despite cancelling RC1 I would like to bring to your attention
> > that
> > > I
> > > > had
> > > > > > a problem building as certain dependencies did seem to be present
> > in
> > > > Maven
> > > > > > repos.
> > > > > > I initially got
> > > > > >
> > > > > >> Could not resolve dependencies for project
> > > > > >> org.apache.nifi:nifi-stateless-nar:nar:2.0.0-M2: The following
> > > > artifacts
> > > > > >> could not be resolved:
> > > > org.apache.nifi:nifi-stateless-engine:jar:2.0.0-M2
> > > > > >> (absent): Could not find artifact
> > > > > >> org.apache.nifi:nifi-stateless-engine:jar:2.0.0-M2 in central (
> > > > > >> https://repo.maven.apache.org/maven2)
> > > > > >
> > > > > >
> > > > > > I tried resuming and I had to manually resume with the following
> as
> > > it
> > > > > > errored each time.
> > > > > >
> > > > > >> ./mvnw -T 1C clean install -Pcontrib-check -rf
> :nifi-stateless-nar
> > > > > >> ./mvnw -T 1C clean install -Pcontrib-check -rf
> > :nifi-salesforce-nar
> > > > > >> ./mvnw -T 1C clean install -Pcontrib-check -rf :nifi-zendesk-nar
> > > > > >> ./mvnw -T 1C clean install -Pcontrib-check -rf
> :nifi-airtable-nar
> > > > > >> ./mvnw -T 1C clean install -Pcontrib-check -rf
> > > > :nifi-box-services-api-nar
> > > > > >> ./mvnw -T 1C clean install -Pcontrib-check -rf :nifi-cipher-nar
> > > > > >
> > > > > >
> > > > > > At the last command I got an error with
> > > > > >
> > > > > >> [ERROR] Failed to execute goal on project nifi-cipher-nar: Could
> > not
> > > > > >> resolve dependencies for project
> > > > > >> org.apache.nifi:nifi-cipher-nar:nar:2.0.0-M2: The following
> > > artifacts
> > > > could
> > > > > >> not be resolved:
> > org.apache.nifi:nifi-cipher-processors:jar:2.0.0-M2
> > > > > >> (absent), org.apache.nifi:nifi-standard-shared-nar:nar:2.0.0-M2
> > > > (absent):
> > > > > >> org.apache.nifi:nifi-cipher-processors:jar:2.0.0-M2 was not
> found
> > in
> > > > > >> https://repo.maven.apache.org/maven2 during a previous attempt.
> > > This
> > > > > >> failure was cached in the local repository and resolution is not

Re: [CANCEL][VOTE] Release Apache NiFi 2.0.0-M2 (RC1)

[Dan S]

Joe,
 I do not have any specific settings.xml.

Chris,
 Before building I had wiped away my local Maven repo per the optional step
in Release Candidate Verification


On Mon, Jan 22, 2024 at 11:05 AM Chris Sampson
 wrote:

> Maven might have got itself confused. Could you try clearing out your
> .m2/repository (at least if anything in the org/apache/nifi directories)?
>
> Note that if you delete the whole local repo, then the build will need to
> re-download all 3rd party libraries too, so things will take longer.
>
> On the new UI front, should it be covered by the include-all profile in the
> nifi-assembly (I don't think it is currently, but that's maybe intentional
> and in the cards to change later one it's more stable)?
>
> On Mon, 22 Jan 2024, 15:58 Dan S,  wrote:
>
> > ./mvnw -T 1C clean install -Pcontrib-check
> >
> > On Mon, Jan 22, 2024 at 10:55 AM David Handermann <
> > exceptionfact...@apache.org> wrote:
> >
> > > Dan,
> > >
> > > Thanks for noting this build behavior.
> > >
> > > The release candidate process does not publish artifacts to the Maven
> > > Central repository. The RC build only publishes artifacts to the
> > > Apache Nexus staging repository. When running the standard full
> > > rebuild as described in the release verification steps, it should not
> > > try to retrieve release versions at all. Can you provide the command
> > > you used for the initial build?
> > >
> > > Regards,
> > > David Handermann
> > >
> > > On Mon, Jan 22, 2024 at 9:52 AM Dan S  wrote:
> > > >
> > > > Sorry typo in my previous email
> > > >  would like to bring to your attention that I had a problem building
> as
> > > > certain dependencies did seem to be present in Maven repos.
> > > >  would like to bring to your attention that I had a problem building
> as
> > > > certain dependencies did not seem to be present in Maven repos.
> > > >
> > > > On Mon, Jan 22, 2024 at 10:36 AM Dan S  wrote:
> > > >
> > > > > David,
> > > > >  Despite cancelling RC1 I would like to bring to your attention
> that
> > I
> > > had
> > > > > a problem building as certain dependencies did seem to be present
> in
> > > Maven
> > > > > repos.
> > > > > I initially got
> > > > >
> > > > >> Could not resolve dependencies for project
> > > > >> org.apache.nifi:nifi-stateless-nar:nar:2.0.0-M2: The following
> > > artifacts
> > > > >> could not be resolved:
> > > org.apache.nifi:nifi-stateless-engine:jar:2.0.0-M2
> > > > >> (absent): Could not find artifact
> > > > >> org.apache.nifi:nifi-stateless-engine:jar:2.0.0-M2 in central (
> > > > >> https://repo.maven.apache.org/maven2)
> > > > >
> > > > >
> > > > > I tried resuming and I had to manually resume with the following as
> > it
> > > > > errored each time.
> > > > >
> > > > >> ./mvnw -T 1C clean install -Pcontrib-check -rf :nifi-stateless-nar
> > > > >> ./mvnw -T 1C clean install -Pcontrib-check -rf
> :nifi-salesforce-nar
> > > > >> ./mvnw -T 1C clean install -Pcontrib-check -rf :nifi-zendesk-nar
> > > > >> ./mvnw -T 1C clean install -Pcontrib-check -rf :nifi-airtable-nar
> > > > >> ./mvnw -T 1C clean install -Pcontrib-check -rf
> > > :nifi-box-services-api-nar
> > > > >> ./mvnw -T 1C clean install -Pcontrib-check -rf :nifi-cipher-nar
> > > > >
> > > > >
> > > > > At the last command I got an error with
> > > > >
> > > > >> [ERROR] Failed to execute goal on project nifi-cipher-nar: Could
> not
> > > > >> resolve dependencies for project
> > > > >> org.apache.nifi:nifi-cipher-nar:nar:2.0.0-M2: The following
> > artifacts
> > > could
> > > > >> not be resolved:
> org.apache.nifi:nifi-cipher-processors:jar:2.0.0-M2
> > > > >> (absent), org.apache.nifi:nifi-standard-shared-nar:nar:2.0.0-M2
> > > (absent):
> > > > >> org.apache.nifi:nifi-cipher-processors:jar:2.0.0-M2 was not found
> in
> > > > >> https://repo.maven.apache.org/maven2 during a previous attempt.
> > This
> > > > >> failure was cached in the local repository and resolution is not
> > > > >> reattempted until the update interval of central has elapsed or
> > > updates are
> > > > >> forced -> [Help 1]
> > > > >> [ERROR] Failed to execute goal on project nifi-apicurio-nar: Could
> > not
> > > > >> resolve dependencies for project
> > > > >> org.apache.nifi:nifi-apicurio-nar:nar:2.0.0-M2: The following
> > > artifacts
> > > > >> could not be resolved:
> > > > >> org.apache.nifi:nifi-apicurio-schema-registry-service:jar:2.0.0-M2
> > > > >> (absent), org.apache.nifi:nifi-standard-shared-nar:nar:2.0.0-M2
> > > (absent):
> > > > >> Could not find artifact
> > > > >> org.apache.nifi:nifi-apicurio-schema-registry-service:jar:2.0.0-M2
> > in
> > > > >> central (https://repo.maven.apache.org/maven2) -> [Help 1]
> > > > >> [ERROR] Failed to execute goal on project nifi-py4j-nar: Could not
> > > > >> resolve dependencies for project
> > > > >> org.apache.nifi:nifi-py4j-nar:nar:2.0.0-M2: The following
> artifacts
> > > could
> > > > >> not be resolved: 

Re: [CANCEL][VOTE] Release Apache NiFi 2.0.0-M2 (RC1)

[Chris Sampson]

Maven might have got itself confused. Could you try clearing out your
.m2/repository (at least if anything in the org/apache/nifi directories)?

Note that if you delete the whole local repo, then the build will need to
re-download all 3rd party libraries too, so things will take longer.

On the new UI front, should it be covered by the include-all profile in the
nifi-assembly (I don't think it is currently, but that's maybe intentional
and in the cards to change later one it's more stable)?

On Mon, 22 Jan 2024, 15:58 Dan S,  wrote:

> ./mvnw -T 1C clean install -Pcontrib-check
>
> On Mon, Jan 22, 2024 at 10:55 AM David Handermann <
> exceptionfact...@apache.org> wrote:
>
> > Dan,
> >
> > Thanks for noting this build behavior.
> >
> > The release candidate process does not publish artifacts to the Maven
> > Central repository. The RC build only publishes artifacts to the
> > Apache Nexus staging repository. When running the standard full
> > rebuild as described in the release verification steps, it should not
> > try to retrieve release versions at all. Can you provide the command
> > you used for the initial build?
> >
> > Regards,
> > David Handermann
> >
> > On Mon, Jan 22, 2024 at 9:52 AM Dan S  wrote:
> > >
> > > Sorry typo in my previous email
> > >  would like to bring to your attention that I had a problem building as
> > > certain dependencies did seem to be present in Maven repos.
> > >  would like to bring to your attention that I had a problem building as
> > > certain dependencies did not seem to be present in Maven repos.
> > >
> > > On Mon, Jan 22, 2024 at 10:36 AM Dan S  wrote:
> > >
> > > > David,
> > > >  Despite cancelling RC1 I would like to bring to your attention that
> I
> > had
> > > > a problem building as certain dependencies did seem to be present in
> > Maven
> > > > repos.
> > > > I initially got
> > > >
> > > >> Could not resolve dependencies for project
> > > >> org.apache.nifi:nifi-stateless-nar:nar:2.0.0-M2: The following
> > artifacts
> > > >> could not be resolved:
> > org.apache.nifi:nifi-stateless-engine:jar:2.0.0-M2
> > > >> (absent): Could not find artifact
> > > >> org.apache.nifi:nifi-stateless-engine:jar:2.0.0-M2 in central (
> > > >> https://repo.maven.apache.org/maven2)
> > > >
> > > >
> > > > I tried resuming and I had to manually resume with the following as
> it
> > > > errored each time.
> > > >
> > > >> ./mvnw -T 1C clean install -Pcontrib-check -rf :nifi-stateless-nar
> > > >> ./mvnw -T 1C clean install -Pcontrib-check -rf :nifi-salesforce-nar
> > > >> ./mvnw -T 1C clean install -Pcontrib-check -rf :nifi-zendesk-nar
> > > >> ./mvnw -T 1C clean install -Pcontrib-check -rf :nifi-airtable-nar
> > > >> ./mvnw -T 1C clean install -Pcontrib-check -rf
> > :nifi-box-services-api-nar
> > > >> ./mvnw -T 1C clean install -Pcontrib-check -rf :nifi-cipher-nar
> > > >
> > > >
> > > > At the last command I got an error with
> > > >
> > > >> [ERROR] Failed to execute goal on project nifi-cipher-nar: Could not
> > > >> resolve dependencies for project
> > > >> org.apache.nifi:nifi-cipher-nar:nar:2.0.0-M2: The following
> artifacts
> > could
> > > >> not be resolved: org.apache.nifi:nifi-cipher-processors:jar:2.0.0-M2
> > > >> (absent), org.apache.nifi:nifi-standard-shared-nar:nar:2.0.0-M2
> > (absent):
> > > >> org.apache.nifi:nifi-cipher-processors:jar:2.0.0-M2 was not found in
> > > >> https://repo.maven.apache.org/maven2 during a previous attempt.
> This
> > > >> failure was cached in the local repository and resolution is not
> > > >> reattempted until the update interval of central has elapsed or
> > updates are
> > > >> forced -> [Help 1]
> > > >> [ERROR] Failed to execute goal on project nifi-apicurio-nar: Could
> not
> > > >> resolve dependencies for project
> > > >> org.apache.nifi:nifi-apicurio-nar:nar:2.0.0-M2: The following
> > artifacts
> > > >> could not be resolved:
> > > >> org.apache.nifi:nifi-apicurio-schema-registry-service:jar:2.0.0-M2
> > > >> (absent), org.apache.nifi:nifi-standard-shared-nar:nar:2.0.0-M2
> > (absent):
> > > >> Could not find artifact
> > > >> org.apache.nifi:nifi-apicurio-schema-registry-service:jar:2.0.0-M2
> in
> > > >> central (https://repo.maven.apache.org/maven2) -> [Help 1]
> > > >> [ERROR] Failed to execute goal on project nifi-py4j-nar: Could not
> > > >> resolve dependencies for project
> > > >> org.apache.nifi:nifi-py4j-nar:nar:2.0.0-M2: The following artifacts
> > could
> > > >> not be resolved: org.apache.nifi:nifi-py4j-bridge:jar:2.0.0-M2
> > (absent),
> > > >> org.apache.nifi:nifi-standard-shared-nar:nar:2.0.0-M2 (absent):
> Could
> > not
> > > >> find artifact org.apache.nifi:nifi-py4j-bridge:jar:2.0.0-M2 in
> > central (
> > > >> https://repo.maven.apache.org/maven2) -> [Help 1]
> > > >> [ERROR] Failed to execute goal on project nifi-opentelemetry-nar:
> > Could
> > > >> not resolve dependencies for project
> > > >> org.apache.nifi:nifi-opentelemetry-nar:nar:2.0.0-M2: The following
> > > >> artifacts could not be 

Re: [CANCEL][VOTE] Release Apache NiFi 2.0.0-M2 (RC1)

[Joe Witt]

Dan,

What about your maven settings.xml perhaps?  Anything interesting there?

Thanks

On Mon, Jan 22, 2024 at 8:57 AM Dan S  wrote:

> ./mvnw -T 1C clean install -Pcontrib-check
>
> On Mon, Jan 22, 2024 at 10:55 AM David Handermann <
> exceptionfact...@apache.org> wrote:
>
> > Dan,
> >
> > Thanks for noting this build behavior.
> >
> > The release candidate process does not publish artifacts to the Maven
> > Central repository. The RC build only publishes artifacts to the
> > Apache Nexus staging repository. When running the standard full
> > rebuild as described in the release verification steps, it should not
> > try to retrieve release versions at all. Can you provide the command
> > you used for the initial build?
> >
> > Regards,
> > David Handermann
> >
> > On Mon, Jan 22, 2024 at 9:52 AM Dan S  wrote:
> > >
> > > Sorry typo in my previous email
> > >  would like to bring to your attention that I had a problem building as
> > > certain dependencies did seem to be present in Maven repos.
> > >  would like to bring to your attention that I had a problem building as
> > > certain dependencies did not seem to be present in Maven repos.
> > >
> > > On Mon, Jan 22, 2024 at 10:36 AM Dan S  wrote:
> > >
> > > > David,
> > > >  Despite cancelling RC1 I would like to bring to your attention that
> I
> > had
> > > > a problem building as certain dependencies did seem to be present in
> > Maven
> > > > repos.
> > > > I initially got
> > > >
> > > >> Could not resolve dependencies for project
> > > >> org.apache.nifi:nifi-stateless-nar:nar:2.0.0-M2: The following
> > artifacts
> > > >> could not be resolved:
> > org.apache.nifi:nifi-stateless-engine:jar:2.0.0-M2
> > > >> (absent): Could not find artifact
> > > >> org.apache.nifi:nifi-stateless-engine:jar:2.0.0-M2 in central (
> > > >> https://repo.maven.apache.org/maven2)
> > > >
> > > >
> > > > I tried resuming and I had to manually resume with the following as
> it
> > > > errored each time.
> > > >
> > > >> ./mvnw -T 1C clean install -Pcontrib-check -rf :nifi-stateless-nar
> > > >> ./mvnw -T 1C clean install -Pcontrib-check -rf :nifi-salesforce-nar
> > > >> ./mvnw -T 1C clean install -Pcontrib-check -rf :nifi-zendesk-nar
> > > >> ./mvnw -T 1C clean install -Pcontrib-check -rf :nifi-airtable-nar
> > > >> ./mvnw -T 1C clean install -Pcontrib-check -rf
> > :nifi-box-services-api-nar
> > > >> ./mvnw -T 1C clean install -Pcontrib-check -rf :nifi-cipher-nar
> > > >
> > > >
> > > > At the last command I got an error with
> > > >
> > > >> [ERROR] Failed to execute goal on project nifi-cipher-nar: Could not
> > > >> resolve dependencies for project
> > > >> org.apache.nifi:nifi-cipher-nar:nar:2.0.0-M2: The following
> artifacts
> > could
> > > >> not be resolved: org.apache.nifi:nifi-cipher-processors:jar:2.0.0-M2
> > > >> (absent), org.apache.nifi:nifi-standard-shared-nar:nar:2.0.0-M2
> > (absent):
> > > >> org.apache.nifi:nifi-cipher-processors:jar:2.0.0-M2 was not found in
> > > >> https://repo.maven.apache.org/maven2 during a previous attempt.
> This
> > > >> failure was cached in the local repository and resolution is not
> > > >> reattempted until the update interval of central has elapsed or
> > updates are
> > > >> forced -> [Help 1]
> > > >> [ERROR] Failed to execute goal on project nifi-apicurio-nar: Could
> not
> > > >> resolve dependencies for project
> > > >> org.apache.nifi:nifi-apicurio-nar:nar:2.0.0-M2: The following
> > artifacts
> > > >> could not be resolved:
> > > >> org.apache.nifi:nifi-apicurio-schema-registry-service:jar:2.0.0-M2
> > > >> (absent), org.apache.nifi:nifi-standard-shared-nar:nar:2.0.0-M2
> > (absent):
> > > >> Could not find artifact
> > > >> org.apache.nifi:nifi-apicurio-schema-registry-service:jar:2.0.0-M2
> in
> > > >> central (https://repo.maven.apache.org/maven2) -> [Help 1]
> > > >> [ERROR] Failed to execute goal on project nifi-py4j-nar: Could not
> > > >> resolve dependencies for project
> > > >> org.apache.nifi:nifi-py4j-nar:nar:2.0.0-M2: The following artifacts
> > could
> > > >> not be resolved: org.apache.nifi:nifi-py4j-bridge:jar:2.0.0-M2
> > (absent),
> > > >> org.apache.nifi:nifi-standard-shared-nar:nar:2.0.0-M2 (absent):
> Could
> > not
> > > >> find artifact org.apache.nifi:nifi-py4j-bridge:jar:2.0.0-M2 in
> > central (
> > > >> https://repo.maven.apache.org/maven2) -> [Help 1]
> > > >> [ERROR] Failed to execute goal on project nifi-opentelemetry-nar:
> > Could
> > > >> not resolve dependencies for project
> > > >> org.apache.nifi:nifi-opentelemetry-nar:nar:2.0.0-M2: The following
> > > >> artifacts could not be resolved:
> > > >> org.apache.nifi:nifi-opentelemetry-processors:jar:2.0.0-M2 (absent),
> > > >> org.apache.nifi:nifi-standard-shared-nar:nar:2.0.0-M2 (absent):
> Could
> > not
> > > >> find artifact
> > org.apache.nifi:nifi-opentelemetry-processors:jar:2.0.0-M2 in
> > > >> central (https://repo.maven.apache.org/maven2) -> [Help 1]
> > > >> [ERROR] Failed to execute goal on project nifi-jolt-nar: Could 

Re: [CANCEL][VOTE] Release Apache NiFi 2.0.0-M2 (RC1)

[Dan S]

./mvnw -T 1C clean install -Pcontrib-check

On Mon, Jan 22, 2024 at 10:55 AM David Handermann <
exceptionfact...@apache.org> wrote:

> Dan,
>
> Thanks for noting this build behavior.
>
> The release candidate process does not publish artifacts to the Maven
> Central repository. The RC build only publishes artifacts to the
> Apache Nexus staging repository. When running the standard full
> rebuild as described in the release verification steps, it should not
> try to retrieve release versions at all. Can you provide the command
> you used for the initial build?
>
> Regards,
> David Handermann
>
> On Mon, Jan 22, 2024 at 9:52 AM Dan S  wrote:
> >
> > Sorry typo in my previous email
> >  would like to bring to your attention that I had a problem building as
> > certain dependencies did seem to be present in Maven repos.
> >  would like to bring to your attention that I had a problem building as
> > certain dependencies did not seem to be present in Maven repos.
> >
> > On Mon, Jan 22, 2024 at 10:36 AM Dan S  wrote:
> >
> > > David,
> > >  Despite cancelling RC1 I would like to bring to your attention that I
> had
> > > a problem building as certain dependencies did seem to be present in
> Maven
> > > repos.
> > > I initially got
> > >
> > >> Could not resolve dependencies for project
> > >> org.apache.nifi:nifi-stateless-nar:nar:2.0.0-M2: The following
> artifacts
> > >> could not be resolved:
> org.apache.nifi:nifi-stateless-engine:jar:2.0.0-M2
> > >> (absent): Could not find artifact
> > >> org.apache.nifi:nifi-stateless-engine:jar:2.0.0-M2 in central (
> > >> https://repo.maven.apache.org/maven2)
> > >
> > >
> > > I tried resuming and I had to manually resume with the following as it
> > > errored each time.
> > >
> > >> ./mvnw -T 1C clean install -Pcontrib-check -rf :nifi-stateless-nar
> > >> ./mvnw -T 1C clean install -Pcontrib-check -rf :nifi-salesforce-nar
> > >> ./mvnw -T 1C clean install -Pcontrib-check -rf :nifi-zendesk-nar
> > >> ./mvnw -T 1C clean install -Pcontrib-check -rf :nifi-airtable-nar
> > >> ./mvnw -T 1C clean install -Pcontrib-check -rf
> :nifi-box-services-api-nar
> > >> ./mvnw -T 1C clean install -Pcontrib-check -rf :nifi-cipher-nar
> > >
> > >
> > > At the last command I got an error with
> > >
> > >> [ERROR] Failed to execute goal on project nifi-cipher-nar: Could not
> > >> resolve dependencies for project
> > >> org.apache.nifi:nifi-cipher-nar:nar:2.0.0-M2: The following artifacts
> could
> > >> not be resolved: org.apache.nifi:nifi-cipher-processors:jar:2.0.0-M2
> > >> (absent), org.apache.nifi:nifi-standard-shared-nar:nar:2.0.0-M2
> (absent):
> > >> org.apache.nifi:nifi-cipher-processors:jar:2.0.0-M2 was not found in
> > >> https://repo.maven.apache.org/maven2 during a previous attempt. This
> > >> failure was cached in the local repository and resolution is not
> > >> reattempted until the update interval of central has elapsed or
> updates are
> > >> forced -> [Help 1]
> > >> [ERROR] Failed to execute goal on project nifi-apicurio-nar: Could not
> > >> resolve dependencies for project
> > >> org.apache.nifi:nifi-apicurio-nar:nar:2.0.0-M2: The following
> artifacts
> > >> could not be resolved:
> > >> org.apache.nifi:nifi-apicurio-schema-registry-service:jar:2.0.0-M2
> > >> (absent), org.apache.nifi:nifi-standard-shared-nar:nar:2.0.0-M2
> (absent):
> > >> Could not find artifact
> > >> org.apache.nifi:nifi-apicurio-schema-registry-service:jar:2.0.0-M2 in
> > >> central (https://repo.maven.apache.org/maven2) -> [Help 1]
> > >> [ERROR] Failed to execute goal on project nifi-py4j-nar: Could not
> > >> resolve dependencies for project
> > >> org.apache.nifi:nifi-py4j-nar:nar:2.0.0-M2: The following artifacts
> could
> > >> not be resolved: org.apache.nifi:nifi-py4j-bridge:jar:2.0.0-M2
> (absent),
> > >> org.apache.nifi:nifi-standard-shared-nar:nar:2.0.0-M2 (absent): Could
> not
> > >> find artifact org.apache.nifi:nifi-py4j-bridge:jar:2.0.0-M2 in
> central (
> > >> https://repo.maven.apache.org/maven2) -> [Help 1]
> > >> [ERROR] Failed to execute goal on project nifi-opentelemetry-nar:
> Could
> > >> not resolve dependencies for project
> > >> org.apache.nifi:nifi-opentelemetry-nar:nar:2.0.0-M2: The following
> > >> artifacts could not be resolved:
> > >> org.apache.nifi:nifi-opentelemetry-processors:jar:2.0.0-M2 (absent),
> > >> org.apache.nifi:nifi-standard-shared-nar:nar:2.0.0-M2 (absent): Could
> not
> > >> find artifact
> org.apache.nifi:nifi-opentelemetry-processors:jar:2.0.0-M2 in
> > >> central (https://repo.maven.apache.org/maven2) -> [Help 1]
> > >> [ERROR] Failed to execute goal on project nifi-jolt-nar: Could not
> > >> resolve dependencies for project
> > >> org.apache.nifi:nifi-jolt-nar:nar:2.0.0-M2: The following artifacts
> could
> > >> not be resolved: org.apache.nifi:nifi-standard-shared-nar:nar:2.0.0-M2
> > >> (absent), org.apache.nifi:nifi-jolt-processors:jar:2.0.0-M2 (absent):
> > >> org.apache.nifi:nifi-standard-shared-nar:nar:2.0.0-M2 was not found in
> > >> 

Re: [CANCEL][VOTE] Release Apache NiFi 2.0.0-M2 (RC1)

[David Handermann]

Dan,

Thanks for noting this build behavior.

The release candidate process does not publish artifacts to the Maven
Central repository. The RC build only publishes artifacts to the
Apache Nexus staging repository. When running the standard full
rebuild as described in the release verification steps, it should not
try to retrieve release versions at all. Can you provide the command
you used for the initial build?

Regards,
David Handermann

On Mon, Jan 22, 2024 at 9:52 AM Dan S  wrote:
>
> Sorry typo in my previous email
>  would like to bring to your attention that I had a problem building as
> certain dependencies did seem to be present in Maven repos.
>  would like to bring to your attention that I had a problem building as
> certain dependencies did not seem to be present in Maven repos.
>
> On Mon, Jan 22, 2024 at 10:36 AM Dan S  wrote:
>
> > David,
> >  Despite cancelling RC1 I would like to bring to your attention that I had
> > a problem building as certain dependencies did seem to be present in Maven
> > repos.
> > I initially got
> >
> >> Could not resolve dependencies for project
> >> org.apache.nifi:nifi-stateless-nar:nar:2.0.0-M2: The following artifacts
> >> could not be resolved: org.apache.nifi:nifi-stateless-engine:jar:2.0.0-M2
> >> (absent): Could not find artifact
> >> org.apache.nifi:nifi-stateless-engine:jar:2.0.0-M2 in central (
> >> https://repo.maven.apache.org/maven2)
> >
> >
> > I tried resuming and I had to manually resume with the following as it
> > errored each time.
> >
> >> ./mvnw -T 1C clean install -Pcontrib-check -rf :nifi-stateless-nar
> >> ./mvnw -T 1C clean install -Pcontrib-check -rf :nifi-salesforce-nar
> >> ./mvnw -T 1C clean install -Pcontrib-check -rf :nifi-zendesk-nar
> >> ./mvnw -T 1C clean install -Pcontrib-check -rf :nifi-airtable-nar
> >> ./mvnw -T 1C clean install -Pcontrib-check -rf :nifi-box-services-api-nar
> >> ./mvnw -T 1C clean install -Pcontrib-check -rf :nifi-cipher-nar
> >
> >
> > At the last command I got an error with
> >
> >> [ERROR] Failed to execute goal on project nifi-cipher-nar: Could not
> >> resolve dependencies for project
> >> org.apache.nifi:nifi-cipher-nar:nar:2.0.0-M2: The following artifacts could
> >> not be resolved: org.apache.nifi:nifi-cipher-processors:jar:2.0.0-M2
> >> (absent), org.apache.nifi:nifi-standard-shared-nar:nar:2.0.0-M2 (absent):
> >> org.apache.nifi:nifi-cipher-processors:jar:2.0.0-M2 was not found in
> >> https://repo.maven.apache.org/maven2 during a previous attempt. This
> >> failure was cached in the local repository and resolution is not
> >> reattempted until the update interval of central has elapsed or updates are
> >> forced -> [Help 1]
> >> [ERROR] Failed to execute goal on project nifi-apicurio-nar: Could not
> >> resolve dependencies for project
> >> org.apache.nifi:nifi-apicurio-nar:nar:2.0.0-M2: The following artifacts
> >> could not be resolved:
> >> org.apache.nifi:nifi-apicurio-schema-registry-service:jar:2.0.0-M2
> >> (absent), org.apache.nifi:nifi-standard-shared-nar:nar:2.0.0-M2 (absent):
> >> Could not find artifact
> >> org.apache.nifi:nifi-apicurio-schema-registry-service:jar:2.0.0-M2 in
> >> central (https://repo.maven.apache.org/maven2) -> [Help 1]
> >> [ERROR] Failed to execute goal on project nifi-py4j-nar: Could not
> >> resolve dependencies for project
> >> org.apache.nifi:nifi-py4j-nar:nar:2.0.0-M2: The following artifacts could
> >> not be resolved: org.apache.nifi:nifi-py4j-bridge:jar:2.0.0-M2 (absent),
> >> org.apache.nifi:nifi-standard-shared-nar:nar:2.0.0-M2 (absent): Could not
> >> find artifact org.apache.nifi:nifi-py4j-bridge:jar:2.0.0-M2 in central (
> >> https://repo.maven.apache.org/maven2) -> [Help 1]
> >> [ERROR] Failed to execute goal on project nifi-opentelemetry-nar: Could
> >> not resolve dependencies for project
> >> org.apache.nifi:nifi-opentelemetry-nar:nar:2.0.0-M2: The following
> >> artifacts could not be resolved:
> >> org.apache.nifi:nifi-opentelemetry-processors:jar:2.0.0-M2 (absent),
> >> org.apache.nifi:nifi-standard-shared-nar:nar:2.0.0-M2 (absent): Could not
> >> find artifact org.apache.nifi:nifi-opentelemetry-processors:jar:2.0.0-M2 in
> >> central (https://repo.maven.apache.org/maven2) -> [Help 1]
> >> [ERROR] Failed to execute goal on project nifi-jolt-nar: Could not
> >> resolve dependencies for project
> >> org.apache.nifi:nifi-jolt-nar:nar:2.0.0-M2: The following artifacts could
> >> not be resolved: org.apache.nifi:nifi-standard-shared-nar:nar:2.0.0-M2
> >> (absent), org.apache.nifi:nifi-jolt-processors:jar:2.0.0-M2 (absent):
> >> org.apache.nifi:nifi-standard-shared-nar:nar:2.0.0-M2 was not found in
> >> https://repo.maven.apache.org/maven2 during a previous attempt. This
> >> failure was cached in the local repository and resolution is not
> >> reattempted until the update interval of central has elapsed or updates are
> >> forced -> [Help 1]
> >
> >
> > without an option to resume. Please advise. Thanks!
> >
> >
> >
> > On Mon, Jan 22, 2024 at 

Re: [CANCEL][VOTE] Release Apache NiFi 2.0.0-M2 (RC1)

[Dan S]

Sorry typo in my previous email
 would like to bring to your attention that I had a problem building as
certain dependencies did seem to be present in Maven repos.
 would like to bring to your attention that I had a problem building as
certain dependencies did not seem to be present in Maven repos.

On Mon, Jan 22, 2024 at 10:36 AM Dan S  wrote:

> David,
>  Despite cancelling RC1 I would like to bring to your attention that I had
> a problem building as certain dependencies did seem to be present in Maven
> repos.
> I initially got
>
>> Could not resolve dependencies for project
>> org.apache.nifi:nifi-stateless-nar:nar:2.0.0-M2: The following artifacts
>> could not be resolved: org.apache.nifi:nifi-stateless-engine:jar:2.0.0-M2
>> (absent): Could not find artifact
>> org.apache.nifi:nifi-stateless-engine:jar:2.0.0-M2 in central (
>> https://repo.maven.apache.org/maven2)
>
>
> I tried resuming and I had to manually resume with the following as it
> errored each time.
>
>> ./mvnw -T 1C clean install -Pcontrib-check -rf :nifi-stateless-nar
>> ./mvnw -T 1C clean install -Pcontrib-check -rf :nifi-salesforce-nar
>> ./mvnw -T 1C clean install -Pcontrib-check -rf :nifi-zendesk-nar
>> ./mvnw -T 1C clean install -Pcontrib-check -rf :nifi-airtable-nar
>> ./mvnw -T 1C clean install -Pcontrib-check -rf :nifi-box-services-api-nar
>> ./mvnw -T 1C clean install -Pcontrib-check -rf :nifi-cipher-nar
>
>
> At the last command I got an error with
>
>> [ERROR] Failed to execute goal on project nifi-cipher-nar: Could not
>> resolve dependencies for project
>> org.apache.nifi:nifi-cipher-nar:nar:2.0.0-M2: The following artifacts could
>> not be resolved: org.apache.nifi:nifi-cipher-processors:jar:2.0.0-M2
>> (absent), org.apache.nifi:nifi-standard-shared-nar:nar:2.0.0-M2 (absent):
>> org.apache.nifi:nifi-cipher-processors:jar:2.0.0-M2 was not found in
>> https://repo.maven.apache.org/maven2 during a previous attempt. This
>> failure was cached in the local repository and resolution is not
>> reattempted until the update interval of central has elapsed or updates are
>> forced -> [Help 1]
>> [ERROR] Failed to execute goal on project nifi-apicurio-nar: Could not
>> resolve dependencies for project
>> org.apache.nifi:nifi-apicurio-nar:nar:2.0.0-M2: The following artifacts
>> could not be resolved:
>> org.apache.nifi:nifi-apicurio-schema-registry-service:jar:2.0.0-M2
>> (absent), org.apache.nifi:nifi-standard-shared-nar:nar:2.0.0-M2 (absent):
>> Could not find artifact
>> org.apache.nifi:nifi-apicurio-schema-registry-service:jar:2.0.0-M2 in
>> central (https://repo.maven.apache.org/maven2) -> [Help 1]
>> [ERROR] Failed to execute goal on project nifi-py4j-nar: Could not
>> resolve dependencies for project
>> org.apache.nifi:nifi-py4j-nar:nar:2.0.0-M2: The following artifacts could
>> not be resolved: org.apache.nifi:nifi-py4j-bridge:jar:2.0.0-M2 (absent),
>> org.apache.nifi:nifi-standard-shared-nar:nar:2.0.0-M2 (absent): Could not
>> find artifact org.apache.nifi:nifi-py4j-bridge:jar:2.0.0-M2 in central (
>> https://repo.maven.apache.org/maven2) -> [Help 1]
>> [ERROR] Failed to execute goal on project nifi-opentelemetry-nar: Could
>> not resolve dependencies for project
>> org.apache.nifi:nifi-opentelemetry-nar:nar:2.0.0-M2: The following
>> artifacts could not be resolved:
>> org.apache.nifi:nifi-opentelemetry-processors:jar:2.0.0-M2 (absent),
>> org.apache.nifi:nifi-standard-shared-nar:nar:2.0.0-M2 (absent): Could not
>> find artifact org.apache.nifi:nifi-opentelemetry-processors:jar:2.0.0-M2 in
>> central (https://repo.maven.apache.org/maven2) -> [Help 1]
>> [ERROR] Failed to execute goal on project nifi-jolt-nar: Could not
>> resolve dependencies for project
>> org.apache.nifi:nifi-jolt-nar:nar:2.0.0-M2: The following artifacts could
>> not be resolved: org.apache.nifi:nifi-standard-shared-nar:nar:2.0.0-M2
>> (absent), org.apache.nifi:nifi-jolt-processors:jar:2.0.0-M2 (absent):
>> org.apache.nifi:nifi-standard-shared-nar:nar:2.0.0-M2 was not found in
>> https://repo.maven.apache.org/maven2 during a previous attempt. This
>> failure was cached in the local repository and resolution is not
>> reattempted until the update interval of central has elapsed or updates are
>> forced -> [Help 1]
>
>
> without an option to resume. Please advise. Thanks!
>
>
>
> On Mon, Jan 22, 2024 at 10:25 AM David Handermann <
> exceptionfact...@apache.org> wrote:
>
>> RC1 for 2.0.0-M2 is cancelled.
>>
>> On Mon, Jan 22, 2024 at 9:23 AM David Handermann
>>  wrote:
>> >
>> > Joe,
>> >
>> > Thanks for highlighting the build issue related to the optional
>> > profile for the new UI. In the interest of maintaining consistency in
>> > the source release, I agree this issue is worth resolving.
>> >
>> > A new version of the json-path library was also released over the
>> > weekend, resolving CVE-2023-51074. Although this does not appear to
>> > have a direct impact on NiFi usage, it would be helpful to include as
>> > well.
>> >
>> > I am cancelling RC1 

Re: [CANCEL][VOTE] Release Apache NiFi 2.0.0-M2 (RC1)

[Dan S]

David,
 Despite cancelling RC1 I would like to bring to your attention that I had
a problem building as certain dependencies did seem to be present in Maven
repos.
I initially got

> Could not resolve dependencies for project
> org.apache.nifi:nifi-stateless-nar:nar:2.0.0-M2: The following artifacts
> could not be resolved: org.apache.nifi:nifi-stateless-engine:jar:2.0.0-M2
> (absent): Could not find artifact
> org.apache.nifi:nifi-stateless-engine:jar:2.0.0-M2 in central (
> https://repo.maven.apache.org/maven2)


I tried resuming and I had to manually resume with the following as it
errored each time.

> ./mvnw -T 1C clean install -Pcontrib-check -rf :nifi-stateless-nar
> ./mvnw -T 1C clean install -Pcontrib-check -rf :nifi-salesforce-nar
> ./mvnw -T 1C clean install -Pcontrib-check -rf :nifi-zendesk-nar
> ./mvnw -T 1C clean install -Pcontrib-check -rf :nifi-airtable-nar
> ./mvnw -T 1C clean install -Pcontrib-check -rf :nifi-box-services-api-nar
> ./mvnw -T 1C clean install -Pcontrib-check -rf :nifi-cipher-nar


At the last command I got an error with

> [ERROR] Failed to execute goal on project nifi-cipher-nar: Could not
> resolve dependencies for project
> org.apache.nifi:nifi-cipher-nar:nar:2.0.0-M2: The following artifacts could
> not be resolved: org.apache.nifi:nifi-cipher-processors:jar:2.0.0-M2
> (absent), org.apache.nifi:nifi-standard-shared-nar:nar:2.0.0-M2 (absent):
> org.apache.nifi:nifi-cipher-processors:jar:2.0.0-M2 was not found in
> https://repo.maven.apache.org/maven2 during a previous attempt. This
> failure was cached in the local repository and resolution is not
> reattempted until the update interval of central has elapsed or updates are
> forced -> [Help 1]
> [ERROR] Failed to execute goal on project nifi-apicurio-nar: Could not
> resolve dependencies for project
> org.apache.nifi:nifi-apicurio-nar:nar:2.0.0-M2: The following artifacts
> could not be resolved:
> org.apache.nifi:nifi-apicurio-schema-registry-service:jar:2.0.0-M2
> (absent), org.apache.nifi:nifi-standard-shared-nar:nar:2.0.0-M2 (absent):
> Could not find artifact
> org.apache.nifi:nifi-apicurio-schema-registry-service:jar:2.0.0-M2 in
> central (https://repo.maven.apache.org/maven2) -> [Help 1]
> [ERROR] Failed to execute goal on project nifi-py4j-nar: Could not resolve
> dependencies for project org.apache.nifi:nifi-py4j-nar:nar:2.0.0-M2: The
> following artifacts could not be resolved:
> org.apache.nifi:nifi-py4j-bridge:jar:2.0.0-M2 (absent),
> org.apache.nifi:nifi-standard-shared-nar:nar:2.0.0-M2 (absent): Could not
> find artifact org.apache.nifi:nifi-py4j-bridge:jar:2.0.0-M2 in central (
> https://repo.maven.apache.org/maven2) -> [Help 1]
> [ERROR] Failed to execute goal on project nifi-opentelemetry-nar: Could
> not resolve dependencies for project
> org.apache.nifi:nifi-opentelemetry-nar:nar:2.0.0-M2: The following
> artifacts could not be resolved:
> org.apache.nifi:nifi-opentelemetry-processors:jar:2.0.0-M2 (absent),
> org.apache.nifi:nifi-standard-shared-nar:nar:2.0.0-M2 (absent): Could not
> find artifact org.apache.nifi:nifi-opentelemetry-processors:jar:2.0.0-M2 in
> central (https://repo.maven.apache.org/maven2) -> [Help 1]
> [ERROR] Failed to execute goal on project nifi-jolt-nar: Could not resolve
> dependencies for project org.apache.nifi:nifi-jolt-nar:nar:2.0.0-M2: The
> following artifacts could not be resolved:
> org.apache.nifi:nifi-standard-shared-nar:nar:2.0.0-M2 (absent),
> org.apache.nifi:nifi-jolt-processors:jar:2.0.0-M2 (absent):
> org.apache.nifi:nifi-standard-shared-nar:nar:2.0.0-M2 was not found in
> https://repo.maven.apache.org/maven2 during a previous attempt. This
> failure was cached in the local repository and resolution is not
> reattempted until the update interval of central has elapsed or updates are
> forced -> [Help 1]


without an option to resume. Please advise. Thanks!



On Mon, Jan 22, 2024 at 10:25 AM David Handermann <
exceptionfact...@apache.org> wrote:

> RC1 for 2.0.0-M2 is cancelled.
>
> On Mon, Jan 22, 2024 at 9:23 AM David Handermann
>  wrote:
> >
> > Joe,
> >
> > Thanks for highlighting the build issue related to the optional
> > profile for the new UI. In the interest of maintaining consistency in
> > the source release, I agree this issue is worth resolving.
> >
> > A new version of the json-path library was also released over the
> > weekend, resolving CVE-2023-51074. Although this does not appear to
> > have a direct impact on NiFi usage, it would be helpful to include as
> > well.
> >
> > I am cancelling RC1 and I will follow up with an RC2 build after
> > getting the json-path 2.9.0 upgrade reviewed and merged.
> >
> > Regards,
> > David Handermann
> >
> > On Mon, Jan 22, 2024 at 9:15 AM Joe Witt  wrote:
> > >
> > > -1
> > >
> > > David,
> > >
> > > First of all thanks for continuing to plow through the magic of release
> > > management.
> > >
> > > I noticed the static check failed in github and it was due to a
> snapshot
> > > reference. I then tried a 

Re: [VOTE] Release Apache NiFi 2.0.0-M2 (RC1)

[David Handermann]

Joe,

Thanks for highlighting the build issue related to the optional
profile for the new UI. In the interest of maintaining consistency in
the source release, I agree this issue is worth resolving.

A new version of the json-path library was also released over the
weekend, resolving CVE-2023-51074. Although this does not appear to
have a direct impact on NiFi usage, it would be helpful to include as
well.

I am cancelling RC1 and I will follow up with an RC2 build after
getting the json-path 2.9.0 upgrade reviewed and merged.

Regards,
David Handermann

On Mon, Jan 22, 2024 at 9:15 AM Joe Witt  wrote:
>
> -1
>
> David,
>
> First of all thanks for continuing to plow through the magic of release
> management.
>
> I noticed the static check failed in github and it was due to a snapshot
> reference. I then tried a local build of the RC and it failed for me for
> the same reason.  The difference here is that I was wanting to include the
> new UI so it could also be evaluated in the RC.
>
> I think this is worth resolving and doing and RC2 for but if you disagree
> that is fair as well.
>
> Thanks
>
> On Sat, Jan 20, 2024 at 9:36 AM David Handermann <
> exceptionfact...@apache.org> wrote:
>
> > Team,
> >
> > I am pleased to be calling this vote for the source release of Apache
> > NiFi 2.0.0-M2.
> >
> > Please review the following guide for how to verify a release candidate
> > build:
> >
> >
> > https://cwiki.apache.org/confluence/display/NIFI/Release+Candidate+Verification
> >
> > The source being voted on and the convenience binaries are available
> > on the Apache Distribution Repository:
> >
> > https://dist.apache.org/repos/dist/dev/nifi/nifi-2.0.0-M2
> >
> > The build artifacts are available on the Apache Nexus Repository:
> >
> > https://repository.apache.org/content/repositories/orgapachenifi-1254
> >
> > Git Tag: nifi-2.0.0-M2-RC1
> > Git Commit ID: b462c7051d004be70fba34f2795bd5c682cd1124
> > GitHub Commit Link:
> >
> > https://github.com/apache/nifi/commit/b462c7051d004be70fba34f2795bd5c682cd1124
> >
> > Checksums of nifi-2.0.0-M2-source-release.zip
> >
> > SHA256: c42655212abacef6f901f2a43ad7f43d3172c631652c517d822a36321199d411
> > SHA512:
> > b1a4d6790f85719a46f321f64cfc436da459795f03315a2f578940e266aa98a3d4a6d50d5be83583e7ac7adbf4a10f6050be314acc62a27fd247d082100718f4
> >
> > Release artifacts are signed with the following key:
> >
> > https://people.apache.org/keys/committer/exceptionfactory.asc
> >
> > KEYS file is available on the Apache Distribution Repository:
> >
> > https://dist.apache.org/repos/dist/release/nifi/KEYS
> >
> > Issues resolved for this version: 197
> >
> >
> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12353861
> >
> > Release note highlights can be found on the project wiki:
> >
> >
> > https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version2.0.0-M2
> >
> > The vote will be open for 72 hours.
> >
> > Please download the release candidate and evaluate the necessary items
> > including checking hashes, signatures, build from source, and test.
> > Then please vote:
> >
> > [] +1 Release this package as nifi-2.0.0-M2
> > [] +0 no opinion
> > [] -1 Do not release this package because...
> >

[CANCEL][VOTE] Release Apache NiFi 2.0.0-M2 (RC1)

[David Handermann]

RC1 for 2.0.0-M2 is cancelled.

On Mon, Jan 22, 2024 at 9:23 AM David Handermann
 wrote:
>
> Joe,
>
> Thanks for highlighting the build issue related to the optional
> profile for the new UI. In the interest of maintaining consistency in
> the source release, I agree this issue is worth resolving.
>
> A new version of the json-path library was also released over the
> weekend, resolving CVE-2023-51074. Although this does not appear to
> have a direct impact on NiFi usage, it would be helpful to include as
> well.
>
> I am cancelling RC1 and I will follow up with an RC2 build after
> getting the json-path 2.9.0 upgrade reviewed and merged.
>
> Regards,
> David Handermann
>
> On Mon, Jan 22, 2024 at 9:15 AM Joe Witt  wrote:
> >
> > -1
> >
> > David,
> >
> > First of all thanks for continuing to plow through the magic of release
> > management.
> >
> > I noticed the static check failed in github and it was due to a snapshot
> > reference. I then tried a local build of the RC and it failed for me for
> > the same reason.  The difference here is that I was wanting to include the
> > new UI so it could also be evaluated in the RC.
> >
> > I think this is worth resolving and doing and RC2 for but if you disagree
> > that is fair as well.
> >
> > Thanks
> >
> > On Sat, Jan 20, 2024 at 9:36 AM David Handermann <
> > exceptionfact...@apache.org> wrote:
> >
> > > Team,
> > >
> > > I am pleased to be calling this vote for the source release of Apache
> > > NiFi 2.0.0-M2.
> > >
> > > Please review the following guide for how to verify a release candidate
> > > build:
> > >
> > >
> > > https://cwiki.apache.org/confluence/display/NIFI/Release+Candidate+Verification
> > >
> > > The source being voted on and the convenience binaries are available
> > > on the Apache Distribution Repository:
> > >
> > > https://dist.apache.org/repos/dist/dev/nifi/nifi-2.0.0-M2
> > >
> > > The build artifacts are available on the Apache Nexus Repository:
> > >
> > > https://repository.apache.org/content/repositories/orgapachenifi-1254
> > >
> > > Git Tag: nifi-2.0.0-M2-RC1
> > > Git Commit ID: b462c7051d004be70fba34f2795bd5c682cd1124
> > > GitHub Commit Link:
> > >
> > > https://github.com/apache/nifi/commit/b462c7051d004be70fba34f2795bd5c682cd1124
> > >
> > > Checksums of nifi-2.0.0-M2-source-release.zip
> > >
> > > SHA256: c42655212abacef6f901f2a43ad7f43d3172c631652c517d822a36321199d411
> > > SHA512:
> > > b1a4d6790f85719a46f321f64cfc436da459795f03315a2f578940e266aa98a3d4a6d50d5be83583e7ac7adbf4a10f6050be314acc62a27fd247d082100718f4
> > >
> > > Release artifacts are signed with the following key:
> > >
> > > https://people.apache.org/keys/committer/exceptionfactory.asc
> > >
> > > KEYS file is available on the Apache Distribution Repository:
> > >
> > > https://dist.apache.org/repos/dist/release/nifi/KEYS
> > >
> > > Issues resolved for this version: 197
> > >
> > >
> > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12353861
> > >
> > > Release note highlights can be found on the project wiki:
> > >
> > >
> > > https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version2.0.0-M2
> > >
> > > The vote will be open for 72 hours.
> > >
> > > Please download the release candidate and evaluate the necessary items
> > > including checking hashes, signatures, build from source, and test.
> > > Then please vote:
> > >
> > > [] +1 Release this package as nifi-2.0.0-M2
> > > [] +0 no opinion
> > > [] -1 Do not release this package because...
> > >

Re: [VOTE] Release Apache NiFi 2.0.0-M2 (RC1)

[Joe Witt]

-1

David,

First of all thanks for continuing to plow through the magic of release
management.

I noticed the static check failed in github and it was due to a snapshot
reference. I then tried a local build of the RC and it failed for me for
the same reason.  The difference here is that I was wanting to include the
new UI so it could also be evaluated in the RC.

I think this is worth resolving and doing and RC2 for but if you disagree
that is fair as well.

Thanks

On Sat, Jan 20, 2024 at 9:36 AM David Handermann <
exceptionfact...@apache.org> wrote:

> Team,
>
> I am pleased to be calling this vote for the source release of Apache
> NiFi 2.0.0-M2.
>
> Please review the following guide for how to verify a release candidate
> build:
>
>
> https://cwiki.apache.org/confluence/display/NIFI/Release+Candidate+Verification
>
> The source being voted on and the convenience binaries are available
> on the Apache Distribution Repository:
>
> https://dist.apache.org/repos/dist/dev/nifi/nifi-2.0.0-M2
>
> The build artifacts are available on the Apache Nexus Repository:
>
> https://repository.apache.org/content/repositories/orgapachenifi-1254
>
> Git Tag: nifi-2.0.0-M2-RC1
> Git Commit ID: b462c7051d004be70fba34f2795bd5c682cd1124
> GitHub Commit Link:
>
> https://github.com/apache/nifi/commit/b462c7051d004be70fba34f2795bd5c682cd1124
>
> Checksums of nifi-2.0.0-M2-source-release.zip
>
> SHA256: c42655212abacef6f901f2a43ad7f43d3172c631652c517d822a36321199d411
> SHA512:
> b1a4d6790f85719a46f321f64cfc436da459795f03315a2f578940e266aa98a3d4a6d50d5be83583e7ac7adbf4a10f6050be314acc62a27fd247d082100718f4
>
> Release artifacts are signed with the following key:
>
> https://people.apache.org/keys/committer/exceptionfactory.asc
>
> KEYS file is available on the Apache Distribution Repository:
>
> https://dist.apache.org/repos/dist/release/nifi/KEYS
>
> Issues resolved for this version: 197
>
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12353861
>
> Release note highlights can be found on the project wiki:
>
>
> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version2.0.0-M2
>
> The vote will be open for 72 hours.
>
> Please download the release candidate and evaluate the necessary items
> including checking hashes, signatures, build from source, and test.
> Then please vote:
>
> [] +1 Release this package as nifi-2.0.0-M2
> [] +0 no opinion
> [] -1 Do not release this package because...
>