Skip to content

plugin is too verbose #155

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

Open
benkeil opened this issue Aug 15, 2024 · 2 comments
Open

plugin is too verbose #155

benkeil opened this issue Aug 15, 2024 · 2 comments
Assignees
Labels
enhancement New feature or request

Comments

@benkeil
Copy link

benkeil commented Aug 15, 2024

> Configure project :
matching ref: BRANCH - feat/DV-8832/productsup-export

ref configuration: BRANCH - pattern: .+
  version: ${ref}

project version: feat-DV-8832-productsup-export
project version: feat-DV-8832-productsup-export
project version: feat-DV-8832-productsup-export
project version: feat-DV-8832-productsup-export
project version: feat-DV-8832-productsup-export
project version: feat-DV-8832-productsup-export
project version: feat-DV-8832-productsup-export
project version: feat-DV-8832-productsup-export
project version: feat-DV-8832-productsup-export
project version: feat-DV-8832-productsup-export
project version: feat-DV-8832-productsup-export

We have multiple subproject and when we build, the plugin echos the version x times for each submodule (where x is the amount of submodules + the root project)

@qoomon qoomon self-assigned this Aug 15, 2024
@qoomon qoomon added the enhancement New feature or request label Aug 15, 2024
@qoomon
Copy link
Owner

qoomon commented Aug 18, 2024

Fixed in version 6.4.4

@qoomon qoomon closed this as completed Aug 18, 2024
@lukaseckert
Copy link

Hi @qoomon
I'm also currently testing the plugin in multi-module project, it works nice so far but I have a similar verbose logging problem even with 6.4.4. On every build the plugin prints 88 lines 😬
The plugin is configured only on the root project. All child projects inherit the same version and properties.

This is the setup: The gradle project has a special version for feature branches. But it also has a library dependency that has a different version in that case. I solved this by setting a property someOtherDependencyVersion:

val devBranchVersion = "99.0.0-SNAPSHOT"
gitVersioning.apply {
    refs {
        // [...]
        branch("feature/(?<featureBranchName>.+)") {
            version = "99.0.0-\${ref.featureBranchName}-SNAPSHOT"
            properties = mapOf("someOtherDependencyVersion" to devBranchVersion)
        }
        // [...]
}

This will result in 88 lines of

......
  someOtherDependencyVersion: 99.0.0-SNAPSHOT
properties:
  someOtherDependencyVersion: 99.0.0-SNAPSHOT
properties:
  someOtherDependencyVersion: 99.0.0-SNAPSHOT
properties:
  someOtherDependencyVersion: 99.0.0-SNAPSHOT
properties:
  someOtherDependencyVersion: 99.0.0-SNAPSHOT
properties:
  someOtherDependencyVersion: 99.0.0-SNAPSHOT
properties:
  someOtherDependencyVersion: 99.0.0-SNAPSHOT
properties:
  someOtherDependencyVersion: 99.0.0-SNAPSHOT
properties:
  someOtherDependencyVersion: 99.0.0-SNAPSHOT
properties:
.......

@qoomon qoomon reopened this Apr 16, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants