remove profile that disables doclint#3225
Conversation
|
Why does activating another profile disable this one? |
|
for example, <?xml version="1.0" encoding="UTF-8"?>
<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
<modelVersion>4.0.0</modelVersion>
<groupId>com.mycompany.app</groupId>
<artifactId>my-app</artifactId>
<version>1</version>
<profiles>
<profile>
<id>moo</id>
<activation>
<jdk>[1.8,)</jdk>
</activation>
<build>
<plugins>
<plugin>
<groupId>com.github.ekryd.echo-maven-plugin</groupId>
<artifactId>echo-maven-plugin</artifactId>
<version>1.2.0</version>
<executions>
<execution>
<phase>compile</phase>
<goals>
<goal>echo</goal>
</goals>
<configuration>
<message>hi!</message>
</configuration>
</execution>
</executions>
</plugin>
</plugins>
</build>
</profile>
<profile>
<id>baa</id>
</profile>
</profiles>
</project> |
|
@igorbernstein2 I think you are right. Multiple profiles can be activated at same time. We had this issue - in circle CI docker image, mvn javadoc:jar won't throw errors (only warnings). But those errrors will be thrown during release process. I thought it had something to do with profiles because release uses "release" profile. I took a second look and this issue doesn't seem to be related to profiles. Nevertheless, I still would like to remove this profile unless there's a reason to keep it. |
|
No worries. I'll just move it to my ~/.m2/settings.xml |
|
Greetings folks! This issue is getting a little moldy. Should we drive this one forward, or close it out? |
|
My original attempt to disable javadoc lint got lost when the directory structure changed. I'm planning on re-introducing the change after reporting change gets unreverted: To clarify my intent: I would like to disable all java8 doclint warnings about missing parameter docs. This is similar to what gax does: However in maven this is bit uglier because I have use a profile to conditionally target java8 only |
|
We can do this by updating to maven-javadoc-plugin 3.0+ and set the doclint configuration option. Adding a work item to #3757 |
…ryconnection-v1 to v2.43.0 (#3225)
This PR contains the following updates: | Package | Change | Age | Adoption | Passing | Confidence | |---|---|---|---|---|---| | [com.google.cloud.opentelemetry:detector-resources-support](https://redirect.github.com/GoogleCloudPlatform/opentelemetry-operations-java) | `0.31.0` -> `0.32.0` | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | | [com.google.cloud.opentelemetry:shared-resourcemapping](https://redirect.github.com/GoogleCloudPlatform/opentelemetry-operations-java) | `0.31.0` -> `0.32.0` | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | | [com.google.cloud.opentelemetry:exporter-metrics](https://redirect.github.com/GoogleCloudPlatform/opentelemetry-operations-java) | `0.31.0` -> `0.32.0` | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | --- > [!WARNING] > Some dependencies could not be looked up. Check the Dependency Dashboard for more information. --- ### Release Notes <details> <summary>GoogleCloudPlatform/opentelemetry-operations-java (com.google.cloud.opentelemetry:detector-resources-support)</summary> ### [`v0.32.0`](https://redirect.github.com/GoogleCloudPlatform/opentelemetry-operations-java/releases/tag/v0.32.0) [Compare Source](https://redirect.github.com/GoogleCloudPlatform/opentelemetry-operations-java/compare/v0.31.0...v0.32.0) ##### Release Highlights - Enables detection of Cloud Run Jobs environment in GCP resource detector. ##### What's Changed - Delete unused logback xml from instrumentation quickstart by [@​aabmass](https://redirect.github.com/aabmass) in [https://github.com/GoogleCloudPlatform/opentelemetry-operations-java/pull/333](https://redirect.github.com/GoogleCloudPlatform/opentelemetry-operations-java/pull/333) - Upgrade to latest nebula-release plugin to fix build by [@​aabmass](https://redirect.github.com/aabmass) in [https://github.com/GoogleCloudPlatform/opentelemetry-operations-java/pull/362](https://redirect.github.com/GoogleCloudPlatform/opentelemetry-operations-java/pull/362) - Migrate e2e tests Container Registry usage to Artifact Registry by [@​aabmass](https://redirect.github.com/aabmass) in [https://github.com/GoogleCloudPlatform/opentelemetry-operations-java/pull/360](https://redirect.github.com/GoogleCloudPlatform/opentelemetry-operations-java/pull/360) - Update the collector image used in instrumentation quickstart by [@​aabmass](https://redirect.github.com/aabmass) in [https://github.com/GoogleCloudPlatform/opentelemetry-operations-java/pull/364](https://redirect.github.com/GoogleCloudPlatform/opentelemetry-operations-java/pull/364) - Rename spring example by [@​psx95](https://redirect.github.com/psx95) in [https://github.com/GoogleCloudPlatform/opentelemetry-operations-java/pull/367](https://redirect.github.com/GoogleCloudPlatform/opentelemetry-operations-java/pull/367) - Add manually instrumented spring sample by [@​psx95](https://redirect.github.com/psx95) in [https://github.com/GoogleCloudPlatform/opentelemetry-operations-java/pull/368](https://redirect.github.com/GoogleCloudPlatform/opentelemetry-operations-java/pull/368) - Update metrics example by [@​psx95](https://redirect.github.com/psx95) in [https://github.com/GoogleCloudPlatform/opentelemetry-operations-java/pull/370](https://redirect.github.com/GoogleCloudPlatform/opentelemetry-operations-java/pull/370) - Fix the sample code shown in README by [@​psx95](https://redirect.github.com/psx95) in [https://github.com/GoogleCloudPlatform/opentelemetry-operations-java/pull/373](https://redirect.github.com/GoogleCloudPlatform/opentelemetry-operations-java/pull/373) - Support cloud run jobs in resource detection by [@​psx95](https://redirect.github.com/psx95) in [https://github.com/GoogleCloudPlatform/opentelemetry-operations-java/pull/371](https://redirect.github.com/GoogleCloudPlatform/opentelemetry-operations-java/pull/371) - Remove obsolete TODO comment by [@​psx95](https://redirect.github.com/psx95) in [https://github.com/GoogleCloudPlatform/opentelemetry-operations-java/pull/374](https://redirect.github.com/GoogleCloudPlatform/opentelemetry-operations-java/pull/374) **Full Changelog**: GoogleCloudPlatform/opentelemetry-operations-java@v0.31.0...v0.32.0 </details> --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about these updates again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR was generated by [Mend Renovate](https://mend.io/renovate/). View the [repository job log](https://developer.mend.io/github/googleapis/sdk-platform-java). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzOC44MC4wIiwidXBkYXRlZEluVmVyIjoiMzguODAuMCIsInRhcmdldEJyYW5jaCI6Im1haW4iLCJsYWJlbHMiOltdfQ==-->
🤖 I have created a release *beep* *boop* --- <details><summary>2.46.1</summary> ## [2.46.1](googleapis/sdk-platform-java@v2.46.0...v2.46.1) (2024-09-25) ### Dependencies * update dependency black to v24.8.0 ([#3234](googleapis/sdk-platform-java#3234)) ([e773ec3](googleapis/sdk-platform-java@e773ec3)) * update dependency lxml to v5.3.0 ([#3237](googleapis/sdk-platform-java#3237)) ([ac6e622](googleapis/sdk-platform-java@ac6e622)) * update dependency net.bytebuddy:byte-buddy to v1.15.2 ([#3235](googleapis/sdk-platform-java#3235)) ([1e72ff0](googleapis/sdk-platform-java@1e72ff0)) * update dependency pyyaml to v6.0.2 ([#3231](googleapis/sdk-platform-java#3231)) ([200f332](googleapis/sdk-platform-java@200f332)) * update dependency watchdog to v4.0.2 ([#3232](googleapis/sdk-platform-java#3232)) ([60b7721](googleapis/sdk-platform-java@60b7721)) * update google api dependencies ([#3224](googleapis/sdk-platform-java#3224)) ([0de08b2](googleapis/sdk-platform-java@0de08b2)) * update google.cloud.opentelemetry.version to v0.32.0 ([#3225](googleapis/sdk-platform-java#3225)) ([861f188](googleapis/sdk-platform-java@861f188)) * update grpc dependencies to v1.68.0 ([#3220](googleapis/sdk-platform-java#3220)) ([618288c](googleapis/sdk-platform-java@618288c)) * update junit5 monorepo to v5.11.1 ([#3236](googleapis/sdk-platform-java#3236)) ([1550ceb](googleapis/sdk-platform-java@1550ceb)) </details> --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). Co-authored-by: release-please[bot] <55107282+release-please[bot]@users.noreply.github.com>
## Description feat: *breaking behavior* rewrite Storage.blobAppendableUpload to be non-blocking and have improved throughput (#3231) Rewrite internals of BlobAppendableUpload to provide non-blocking write calls, and it take advantage of grpc async message handling. When `AppendableUploadWriteableByteChannel#write(ByteBuffer)` is called, an attempt will be made to enqueue the bytes in the outbound queue to GCS. If there is only enough room to partially consume the bytes provided in the `ByteBuffer` the write call will return early specifying the number of bytes actually consumed. As acknowledgements come in from gcs, enqueued messages will be evicted freeing space in the outbound queue. Thereby allowing more bytes to be consumed and enqueued. Given appendable objects are still in private preview I can't quote any metrics here, however preliminary benchmarking of several million objects across a range of sizes show across the board throughput improvments. Because the channel's write call is now non-blocking, if you want to block your application until the full buffer is consumed some new helper methods have been added in StorageChannelUtils to provide blocking behavior. A new method `MinFlushSizeFlushPolicy#withMaxPendingBytes(long)` has been added to allow limiting the number of pending outbound bytes. The default values is 16MiB, but can be configured lower if necessary. ## Release Notes BEGIN_COMMIT_OVERRIDE BEGIN_NESTED_COMMIT feat: *breaking behavior* rewrite Storage.blobAppendableUpload to be non-blocking and have improved throughput (#3231) END_NESTED_COMMIT BEGIN_NESTED_COMMIT feat: add StorageChannelUtils to provide helper methods to perform blocking read/write to/from non-blocking channels (#3231) END_NESTED_COMMIT BEGIN_NESTED_COMMIT feat: add MinFlushSizeFlushPolicy#withMaxPendingBytes(long) (#3231) END_NESTED_COMMIT BEGIN_NESTED_COMMIT fix: update BlobAppendableUploadConfig and FlushPolicy.MinFlushSizeFlushPolicy to default to 4MiB minFlushSize and 16MiB maxPendingBytes (#3249) END_NESTED_COMMIT BEGIN_NESTED_COMMIT fix: make FlushPolicy${Min,Max}FlushSizeFlushPolicy constructors private (#3217) END_NESTED_COMMIT END_COMMIMT_OVERRIDE ## Sub PRs This PR is made of up the following PRs, in sequence 1. #3217 2. #3218 3. #3219 4. #3220 5. #3221 6. #3222 7. #3223 8. #3224 9. #3225 10. #3226 11. #3227 12. #3228 13. #3229 14. #3230 15. #3235 16. #3236 17. #3241 18. #3242 19. #3246 20. #3248 21. #3249 22. #3252
Remove this piece of magic code that automatically activates the profile and disables javadoc lint check. Any javadoc errors will still bite us during releasing where a different profile is activated.