Skip to content
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

Quiet option for regex-property goal. #152

Open
garretwilson opened this issue Oct 24, 2022 · 2 comments
Open

Quiet option for regex-property goal. #152

garretwilson opened this issue Oct 24, 2022 · 2 comments

Comments

@garretwilson
Copy link

Could we get a <quiet> option for the regex-property goal? (Or better yet, don't provide output at all?)

For example I have something like this to drop any -SNAPSHOT to find out what the release version will be:

<plugin>
  <groupId>org.codehaus.mojo</groupId>
  <artifactId>build-helper-maven-plugin</artifactId>
  <executions>
    <execution>
      <id>set-project-release-version</id>
      <goals>
        <goal>regex-property</goal>
      </goals>
      <configuration>
        <name>project.releaseVersion</name>
        <value>${project.version}</value>
        <regex>-.*</regex>
        <failIfNoMatch>false</failIfNoMatch>
      </configuration>
    </execution>
  </executions>
</plugin>

If the project version is already the release, version, great! There's nothing to do. But build-helper-maven-plugin feels it just needs to tell me about it. "Hey, developer; you might be interested in knowing that your regular expression didn't match!" (I'm quoting from memory, so it might not be exact. 😅)

The message isn't an error. It's not even a warning. It's just clutter. (And the last thing I need in my build output is more clutter.) And I already told it <failIfNoMatch>false</failIfNoMatch>. We need a <beQuietAndKeepToYourselfIfNoMatch> option. 😁

Thanks!

@github-actions github-actions bot added the Stale label Oct 25, 2023
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Nov 1, 2023
@garretwilson
Copy link
Author

Did a human decide this was not planned, or did a bot close this because no one looked at it to make a decision?

Would the team be open to a pull request?

@slachiewicz slachiewicz removed the Stale label Nov 1, 2023
@slachiewicz slachiewicz reopened this Nov 1, 2023
@slawekjaranowski
Copy link
Member

Did a human decide this was not planned, or did a bot close this because no one looked at it to make a decision?

Would the team be open to a pull request?

We always open for a pull request 😄

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants