Skip to content

Conversation

@hgschmie
Copy link
Contributor

This matches the attach parameter from the source plugin

Setting this parameter to false will skip attaching the generated jar artifact to the build. It will not be picked up by the install and deploy goals.

Omitting or setting this parameter to true will attach the jar to the build. This is the default behavior.

The use case for this is generating test jars as part of a build to be used in integration tests while they should not actually be deployed to a repository.

Following this checklist to help us incorporate your
contribution quickly and easily:

  • Your pull request should address just one issue, without pulling in other changes.
  • Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
  • Each commit in the pull request should have a meaningful subject line and body.
    Note that commits might be squashed by a maintainer on merge.
  • Write unit tests that match behavioral changes, where the tests fail if the changes to the runtime are not applied.
    This may not always be possible but is a best-practice.
  • Run mvn verify to make sure basic checks pass.
    A more thorough check will be performed on your pull request automatically.
  • You have run the integration tests successfully (mvn -Prun-its verify).

If your pull request is about ~20 lines of code you don't need to sign an
Individual Contributor License Agreement if you are unsure
please ask on the developers list.

To make clear that you license your contribution under
the Apache License Version 2.0, January 2004
you have to acknowledge this by using the following check-box.

@hgschmie hgschmie added enhancement New feature or request java Pull requests that update Java code labels Oct 15, 2025
This matches the `attach` parameter from the source plugin

Setting this parameter to `false` will skip attaching the generated jar
artifact to the build. It will not be picked up by the install and
deploy goals.

Omitting or setting this parameter to `true` will attach the jar to the
build. This is the default behavior.

The use case for this is generating test jars as part of a build to be
used in integration tests while they should not actually be deployed to
a repository.
@hgschmie hgschmie force-pushed the skip-jar-attach-4.x branch from a4a7d57 to 8c4dead Compare October 27, 2025 20:43
@hgschmie hgschmie merged commit d751f10 into apache:master Oct 28, 2025
11 of 16 checks passed
@github-actions github-actions bot added this to the 4.0.0-beta-2 milestone Oct 28, 2025
@hgschmie hgschmie deleted the skip-jar-attach-4.x branch October 28, 2025 01:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request java Pull requests that update Java code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant