You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tooling.apache.org by "dave2wave (via GitHub)" <gi...@apache.org> on 2026/03/22 20:12:05 UTC
[I] Recommend upload api steps (tooling-trusted-releases)
dave2wave opened a new issue, #926:
URL: https://github.com/apache/tooling-trusted-releases/issues/926
@hboutemy is creating a Maven Plugin to upload to atr as part of a maven deploy [maven-atr-plugin](https://github.com/apache/maven-studies/blob/maven-atr-plugin/src/site/markdown/usage.md)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@tooling.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tooling.apache.org
For additional commands, e-mail: dev-help@tooling.apache.org
Re: [I] Review Maven ATR plugin and make recommendations (tooling-trusted-releases)
Posted by "dave2wave (via GitHub)" <gi...@apache.org>.
dave2wave commented on issue #926:
URL: https://github.com/apache/tooling-trusted-releases/issues/926#issuecomment-4423494750
@hboutemy please give me the list of Maven PMC members who should have write access.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@tooling.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tooling.apache.org
For additional commands, e-mail: dev-help@tooling.apache.org
Re: [I] Review Maven ATR plugin and make recommendations (tooling-trusted-releases)
Posted by "hboutemy (via GitHub)" <gi...@apache.org>.
hboutemy commented on issue #926:
URL: https://github.com/apache/tooling-trusted-releases/issues/926#issuecomment-4409560972
> Next when we use org.pache.maven.plugins as groupId users can easy execute: mvn atr:goal
short answer: true, but very theoretical
longer: in the future it will be in a profile in ASF parent, manual use with CLI is necessary for now only during the testing phase = as you did
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@tooling.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tooling.apache.org
For additional commands, e-mail: dev-help@tooling.apache.org
Re: [I] Review Maven ATR plugin and make recommendations (tooling-trusted-releases)
Posted by "dave2wave (via GitHub)" <gi...@apache.org>.
dave2wave commented on issue #926:
URL: https://github.com/apache/tooling-trusted-releases/issues/926#issuecomment-4392092360
I need to discuss how we would handle write permissions on a tooling team version of this repository.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@tooling.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tooling.apache.org
For additional commands, e-mail: dev-help@tooling.apache.org
Re: [I] Review Maven ATR plugin and make recommendations (tooling-trusted-releases)
Posted by "dave2wave (via GitHub)" <gi...@apache.org>.
dave2wave commented on issue #926:
URL: https://github.com/apache/tooling-trusted-releases/issues/926#issuecomment-4112024419
> to be clear: it is asked by Tooling to maintain the plugin inside Maven community, not to maintain it as part of Tooling community
> do you confirm?
Tooling staff won't support the plugin directly, but will help with testing and integration.
You ask about the tooling community which is different question. I suppose I could form an official Tooling Committee which could separately support the plugin. Is there an advantage to that?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@tooling.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tooling.apache.org
For additional commands, e-mail: dev-help@tooling.apache.org
Re: [I] Review Maven ATR plugin and make recommendations (tooling-trusted-releases)
Posted by "asf-tooling (via GitHub)" <gi...@apache.org>.
asf-tooling commented on issue #926:
URL: https://github.com/apache/tooling-trusted-releases/issues/926#issuecomment-4410001615
<!-- gofannon-issue-triage-bot v2 -->
**Automated triage** — analyzed at `main@2da7807a`
**Type:** `discussion` • **Classification:** `no_action` • **Confidence:** `high`
**Application domain(s):** `release_lifecycle`, `authentication_authorization`, `artifact_upload`
### Summary
This issue is an ongoing coordination discussion between ATR maintainers and the Maven ATR plugin developers (@hboutemy, @slawekjaranowski) about how the plugin should use ATR's API. The original issue proposed a 4-step workflow (get JWT, check release exists, create release, upload files). @sbp identified the rate-limiting concern (JWT created per file vs reused). The discussion has since evolved into plugin governance (Maven vs Tooling namespace), repository location, and release process decisions. No concrete changes to the ATR codebase have been requested or identified as necessary — the work is primarily in the external maven-studies repository.
### Where this lives in the code today
#### `atr/post/tokens.py` — `jwt_post` (lines 37-50)
_currently does this_
The JWT issuance endpoint rate-limited to 10/hour, which @sbp flagged as a concern when the plugin was creating a JWT per file upload.
```python
@post.typed
@rate_limiter.rate_limit(10, datetime.timedelta(hours=1))
async def jwt_post(
session: web.Committer, _tokens_jwt: Literal["tokens/jwt"], form: shared.tokens.IssueForm
) -> web.QuartResponse:
"""
URL: /tokens/jwt
"""
async with storage.write(session) as write:
wafc = write.as_foundation_committer()
jwt_token = await wafc.tokens.issue_jwt(form.pat)
response = web.TextResponse(jwt_token)
response.headers["Cache-Control"] = "no-store"
return response
```
#### `atr/jwtoken.py` — `issue` (lines 71-89)
_currently does this_
JWT has a 30-minute TTL (via _ATR_JWT_TTL = 30 * 60), meaning one JWT can be reused across multiple file uploads within that window.
```python
def issue(uid: str, *, ttl: int = _ATR_JWT_TTL, pat_hash: str | None = None) -> str:
# audit_guidance no explicit typ header or token_type claim is added: the aud claim (_ATR_JWT_AUDIENCE)
# already acts as an explicit token type discriminator, and ATR issues only one JWT type verified
# by a single internal verifier — the RFC 9068 typ header is relevant to multi-issuer OAuth2 RS
# deployments, which this is not
now = datetime.datetime.now(tz=datetime.UTC)
payload = {
"sub": uid,
"iss": _ATR_JWT_ISSUER,
"aud": _ATR_JWT_AUDIENCE,
"iat": now,
"nbf": now,
"exp": now + datetime.timedelta(seconds=ttl),
"jti": secrets.token_hex(128 // 8),
}
if pat_hash:
payload["atr_th"] = pat_hash
log.auth_event("jwt_issuance", uid, pat_hash=pat_hash if pat_hash else None)
return jwt.encode(payload, _signing_key(), algorithm=_ALGORITHM)
```
#### `atr/post/upload.py` — `_add_files` (lines 55-70)
_currently does this_
The upload endpoint that the Maven plugin calls to upload files. It supports JSON responses (content negotiation), which is what the Maven plugin uses.
```python
async def _add_files(
session: web.Committer,
add_form: shared.upload.AddFilesForm,
project_key: safe.ProjectKey,
version_key: safe.VersionKey,
*,
wants_json: bool,
) -> tuple[web.QuartResponse, int] | web.WerkzeugResponse:
try:
file_data = add_form.file_data
async with storage.write(session) as write:
wacp = await write.as_project_committee_participant(project_key)
creation_error, number_of_files, was_quarantined = await wacp.release.upload_files(
project_key, version_key, file_data
)
```
#### `atr/storage/writers/release.py` — `CommitteeParticipant.start` (lines 609-616)
_currently does this_
The release creation logic that step 3 of the proposed workflow would invoke. It checks for existing releases (returning 409 if one exists) and validates committee membership.
```python
async def start(self, project_key: safe.ProjectKey, version: safe.VersionKey) -> tuple[sql.Release, sql.Project]: # noqa: C901
"""Creates the initial release draft record and revision directory."""
# Get the project from the project name
project = await self.__data.project(
key=str(project_key), status=sql.ProjectStatus.ACTIVE, _committee=True
).get()
if not project:
raise storage.AccessError(f"Project {project_key} not found", status=404)
```
### Proposed approach
No code changes to this repository are required at this time. The issue is a coordination discussion about the Maven ATR plugin (maintained externally at https://github.com/apache/maven-studies/blob/maven-atr-plugin/). The plugin is actively being developed and tested by @hboutemy and @slawekjaranowski. The remaining open items are governance decisions (repository location, groupId, release process) rather than ATR codebase changes. The rate-limiting concern raised by @sbp has been acknowledged by @hboutemy as a plugin-side fix (reuse JWT rather than creating one per file). The ATR API endpoints needed by the plugin (JWT issuance, release creation, file upload) all exist and function correctly based on the successful tests shown in the discussion.
### Open questions
- Whether any ATR API changes are needed to support the 'check if release exists' step (the issue mentions /release/get which may or may not be an existing API route - the file inventory doesn't include the full API layer)
- Whether the 'POST data for create' changes mentioned in the issue body have already been made or are still pending
- Whether the rate limit of 10 JWT requests/hour is sufficient for the Maven plugin workflow or needs adjustment
- Whether the plugin will live under apache/tooling-atr-maven-plugin or remain in Maven namespace - this is still being debated as of the latest comments
_The agent reviewed this issue and is not proposing patches in this run. Review the existing-code citations and open questions above before deciding next steps._
### Files examined
- `atr/jwtoken.py`
- `atr/storage/writers/tokens.py`
- `atr/post/tokens.py`
- `atr/storage/writers/release.py`
- `atr/post/upload.py`
- `atr/storage/readers/releases.py`
- `atr/storage/writers/revision.py`
- `atr/get/tokens.py`
---
*Draft from a triage agent. A human reviewer should validate before merging any change. The agent did not run tests or verify diffs apply.*
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@tooling.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tooling.apache.org
For additional commands, e-mail: dev-help@tooling.apache.org
Re: [I] Review Maven ATR plugin and make recommendations (tooling-trusted-releases)
Posted by "slawekjaranowski (via GitHub)" <gi...@apache.org>.
slawekjaranowski commented on issue #926:
URL: https://github.com/apache/tooling-trusted-releases/issues/926#issuecomment-4391947833
My testing for: https://release-test.apache.org/vote/maven-apache-parent/38
After `mvn release:prepare release:perform`
```
cd target/checkout
mvn atr:check-composing -Datr.project=maven-apache-parent -Datr.version=38
[INFO] --- atr:1.0.0-beta-1-SNAPSHOT:check-composing (default-cli) @ apache ---
[INFO] Checking project release in ATR: https://release-test.apache.org/projects/maven-apache-parent version 38
[INFO] Version exists in ATR:
Phase: Release Candidate (Draft - Being Composed)
Created: 2026-05-06T19:55:38.131250
Latest Revision: 00001
[INFO] Version is being composed in ATR: maven-apache-parent 38
See https://release-test.apache.org/compose/maven-apache-parent/38 for more information
mvn atr:upload -Datr.project=maven-apache-parent -Datr.version=38 -Datr.files=target/apache-38-source-release.zip,target/apache-38-source-release.zip.asc,target/apache-38-source-release.zip.sha512
[INFO] --- atr:1.0.0-beta-1-SNAPSHOT:upload (default-cli) @ apache ---
[INFO] Uploading 3 files to ATR https://release-test.apache.org/compose/maven-apache-parent/38
[INFO] >>> apache-38-source-release.zip (21 KB) to https://release-test.apache.org/file/maven-apache-parent/38/apache-38-source-release.zip
[INFO] upload successful, revision: unknown
[INFO] >>> apache-38-source-release.zip.asc (902 bytes) to https://release-test.apache.org/file/maven-apache-parent/38/apache-38-source-release.zip.asc
[INFO] upload successful, revision: 00002
[INFO] >>> apache-38-source-release.zip.sha512 (128 bytes) to https://release-test.apache.org/file/maven-apache-parent/38/apache-38-source-release.zip.sha512
[INFO] upload successful, revision: 00004
```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@tooling.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tooling.apache.org
For additional commands, e-mail: dev-help@tooling.apache.org
Re: [I] Review Maven ATR plugin and make recommendations (tooling-trusted-releases)
Posted by "hboutemy (via GitHub)" <gi...@apache.org>.
hboutemy commented on issue #926:
URL: https://github.com/apache/tooling-trusted-releases/issues/926#issuecomment-4424299187
I would also have expected https://github.com/apache/tooling-atr-maven-plugin as proposed in https://github.com/apache/tooling-trusted-releases/issues/926#issuecomment-4265976499
[tooling-maven-release-plugin.git](https://gitbox.apache.org/repos/asf/tooling-maven-release-plugin.git) is so surprising
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@tooling.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tooling.apache.org
For additional commands, e-mail: dev-help@tooling.apache.org
Re: [I] Review Maven ATR plugin and make recommendations (tooling-trusted-releases)
Posted by "hboutemy (via GitHub)" <gi...@apache.org>.
hboutemy commented on issue #926:
URL: https://github.com/apache/tooling-trusted-releases/issues/926#issuecomment-4107061403
to be clear: it is asked by Tooling to maintain the plugin inside Maven community, not to maintain it as part of Tooling community
do you confirm?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@tooling.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tooling.apache.org
For additional commands, e-mail: dev-help@tooling.apache.org
Re: [I] Review Maven ATR plugin and make recommendations (tooling-trusted-releases)
Posted by "slawekjaranowski (via GitHub)" <gi...@apache.org>.
slawekjaranowski commented on issue #926:
URL: https://github.com/apache/tooling-trusted-releases/issues/926#issuecomment-4423917904
@dave2wave thanks, can we change repo and finally plugin name to something like:
repo to: `tooling-pluginName-maven-plugin`
and plugin will be, groupId:artifactId : `org.apache.tooling:pluginName-maven-plugin`
according to: https://maven.apache.org/guides/plugin/guide-java-plugin-development.html#important-notice
I'm not sure if name `release` will be the best for `pluginName`
We also have a release plugin at Maven: `org.apache.maven.plugins:maven-release-plugin`
and we can invoke plugin by short name, which is resolved by
`pluginName-maven-plugin` or `maven-pluginName-plugin`, so we can have a conflict here ...
I see that it is:
Python Client: https://github.com/apache/tooling-releases-client
GitHub Actions: https://github.com/apache/tooling-actions
I'm not sure such name choose to maven plugin - maybe `atr` or `releases-client`, as `pluginName` will be ok ...
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@tooling.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tooling.apache.org
For additional commands, e-mail: dev-help@tooling.apache.org
Re: [I] Review Maven ATR plugin and make recommendations (tooling-trusted-releases)
Posted by "hboutemy (via GitHub)" <gi...@apache.org>.
hboutemy commented on issue #926:
URL: https://github.com/apache/tooling-trusted-releases/issues/926#issuecomment-4412310132
> Maybe better and easier will be maintain it under Maven namespace - we have everything for releasing
easier: sure
better?
it's all about "if you want to go fast, go alone; if you want to go far, go together"
alone, I could have published a release in 5 minutes 1 month ago at io.github.hboutemy and we could have integrated it in version 38 of https://maven.apache.org/pom/asf/#The_apache-release_Profile
Adding the plugin to Maven itself is obvious for the Maven project, it's just one additional plugin to https://maven.apache.org/plugins/ : it will just cost 1/2h of preparation and 72h of vote
but is it really what ASF / Tooling ATR team wants = let ATR integrations out of their hands?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@tooling.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tooling.apache.org
For additional commands, e-mail: dev-help@tooling.apache.org
Re: [I] Review Maven ATR plugin and make recommendations (tooling-trusted-releases)
Posted by "hboutemy (via GitHub)" <gi...@apache.org>.
hboutemy commented on issue #926:
URL: https://github.com/apache/tooling-trusted-releases/issues/926#issuecomment-4273237502
@dave2wave with a move from Maven PMC to Tooling, we would have
`https://release-test.apache.org/compose/tooling-atr-maven-plugin/1.0.0-beta-1-SNAPSHOT`
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@tooling.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tooling.apache.org
For additional commands, e-mail: dev-help@tooling.apache.org
Re: [I] Review Maven ATR plugin and make recommendations (tooling-trusted-releases)
Posted by "slawekjaranowski (via GitHub)" <gi...@apache.org>.
slawekjaranowski commented on issue #926:
URL: https://github.com/apache/tooling-trusted-releases/issues/926#issuecomment-4374069470
@hboutemy @dave2wave what do you think to create a dedicated repository for such plugin?
I have some idea to it and I would like to have a history what is changed, propose PR and so on ...
We also need a start build plugin by CI
I know I can propose PR for sandbox project but with dedicated project will be more clear
We also start a release cycles with some of beta version for easy testing by others.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@tooling.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tooling.apache.org
For additional commands, e-mail: dev-help@tooling.apache.org
Re: [I] Review Maven ATR plugin and make recommendations (tooling-trusted-releases)
Posted by "hboutemy (via GitHub)" <gi...@apache.org>.
hboutemy commented on issue #926:
URL: https://github.com/apache/tooling-trusted-releases/issues/926#issuecomment-4425137500
thank you
current maven-studies code pushed: we can now continue on https://github.com/apache/tooling-atr-maven-plugin
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@tooling.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tooling.apache.org
For additional commands, e-mail: dev-help@tooling.apache.org
Re: [I] Review Maven ATR plugin and make recommendations (tooling-trusted-releases)
Posted by "hboutemy (via GitHub)" <gi...@apache.org>.
hboutemy commented on issue #926:
URL: https://github.com/apache/tooling-trusted-releases/issues/926#issuecomment-4120043831
> Is there an advantage to that?
I see one advantage: Tooling eating its own dog food, and doing some releases the PMC way in multiple technologies (Java with Maven, Java with Gradle, Java with sbt, JavaScript, and each technology that ASF project will do releases)
of course, Tooling will require some contribution, but it's only on non-core aspects, so each time it will require a few experts from diverse tech stack, but I don't expect this will be much
and this can be a great common space for technology practices sharing
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@tooling.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tooling.apache.org
For additional commands, e-mail: dev-help@tooling.apache.org
Re: [I] Review Maven ATR plugin and make recommendations (tooling-trusted-releases)
Posted by "hboutemy (via GitHub)" <gi...@apache.org>.
hboutemy commented on issue #926:
URL: https://github.com/apache/tooling-trusted-releases/issues/926#issuecomment-4265976499
code for now was written with Maven PMC target, with `org.apache.maven.plugins:maven-atr-plugin` coordinates
but moving to ATR, it would move to `org.apache.tooling:atr-maven-plugin` to follow conventions
for the GitHub repository, I'd propose `apache/tooling-atr-maven-plugin`
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@tooling.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tooling.apache.org
For additional commands, e-mail: dev-help@tooling.apache.org
Re: [I] Review Maven ATR plugin and make recommendations (tooling-trusted-releases)
Posted by "dave2wave (via GitHub)" <gi...@apache.org>.
dave2wave closed issue #926: Review Maven ATR plugin and make recommendations
URL: https://github.com/apache/tooling-trusted-releases/issues/926
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@tooling.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tooling.apache.org
For additional commands, e-mail: dev-help@tooling.apache.org
Re: [I] Review Maven ATR plugin and make recommendations (tooling-trusted-releases)
Posted by "hboutemy (via GitHub)" <gi...@apache.org>.
hboutemy commented on issue #926:
URL: https://github.com/apache/tooling-trusted-releases/issues/926#issuecomment-4120079596
> I notice that a JWT is being created for every file that's uploaded
every file? uh, that one is a stupid mistake I'll fix soon, thanks for the feedback
it will be trivial to reuse jwt token for multiple files on one goal invocation = what happens in general
I think it can be reasonably easy to reuse against multiple goal invocations: should happen less, but should be valuable to prepare for that
on reusing jwt between separate mvn invocations:
- would that make sense?
- where would the jwt token be stored between the invocations? how do you do with `atr` command?
- what is the expiration? what to do on expired jwt?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@tooling.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tooling.apache.org
For additional commands, e-mail: dev-help@tooling.apache.org
Re: [I] Review Maven ATR plugin and make recommendations (tooling-trusted-releases)
Posted by "dave2wave (via GitHub)" <gi...@apache.org>.
dave2wave commented on issue #926:
URL: https://github.com/apache/tooling-trusted-releases/issues/926#issuecomment-4248939159
> I'm open to help for testing and future maintain 😄
Having a second Maven/Java expert involved definitely helps me lean towards make it a tooling "release"
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@tooling.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tooling.apache.org
For additional commands, e-mail: dev-help@tooling.apache.org
Re: [I] Review Maven ATR plugin and make recommendations (tooling-trusted-releases)
Posted by "hboutemy (via GitHub)" <gi...@apache.org>.
hboutemy commented on issue #926:
URL: https://github.com/apache/tooling-trusted-releases/issues/926#issuecomment-4273229434
testing `push-to-atr` profile added to the project
=> @slawekjaranowski @cstamas you can test the plugin SNAPSHOT simply by:
1. install the plugin `mvn install`
2. test a publication, even of the SNAPSHOT:
```
❯ mvn -Papache-release,push-to-atr deploy
[INFO] Scanning for projects...
[INFO]
[INFO] -------------< org.apache.maven.plugins:maven-atr-plugin >--------------
[INFO] Building Apache Maven ATR Plugin 1.0.0-beta-1-SNAPSHOT
[INFO] from pom.xml
[INFO] ----------------------------[ maven-plugin ]----------------------------
[INFO]
[INFO] --- enforcer:3.5.0:enforce (enforce-bytecode-version) @ maven-atr-plugin ---
[INFO] Rule 0: org.codehaus.mojo.extraenforcer.dependencies.EnforceBytecodeVersion passed
[INFO]
[INFO] --- enforcer:3.5.0:enforce (enforce-maven-version) @ maven-atr-plugin ---
[INFO] Rule 0: org.apache.maven.enforcer.rules.version.RequireMavenVersion passed
[INFO]
[INFO] --- enforcer:3.5.0:enforce (enforce-java-version) @ maven-atr-plugin ---
[INFO] Rule 0: org.apache.maven.enforcer.rules.version.RequireJavaVersion passed
[INFO]
[INFO] --- enforcer:3.5.0:enforce (ensure-no-container-api) @ maven-atr-plugin ---
[INFO] Rule 0: org.apache.maven.enforcer.rules.dependency.BannedDependencies passed
[INFO]
[INFO] --- atr:1.0.0-beta-1-SNAPSHOT:check-composing (atr-check-composing) @ maven-atr-plugin ---
[INFO] Checking project release in ATR: maven-atr-plugin version 1.0.0-beta-1-SNAPSHOT
[INFO] Version exists in ATR:
Phase: Release Candidate (Draft - Being Composed)
Created: 2026-04-18T08:06:16.254839
Latest Revision: 00001
[INFO] Version is being composed in ATR: maven-atr-plugin 1.0.0-beta-1-SNAPSHOT
See https://release-test.apache.org/compose/maven-atr-plugin/1.0.0-beta-1-SNAPSHOT for more information
...
[INFO] --- deploy:3.1.2:deploy (default-deploy) @ maven-atr-plugin ---
Downloading from apache.snapshots.https: https://repository.apache.org/content/repositories/snapshots/org/apache/maven/plugins/maven-atr-plugin/1.0.0-beta-1-SNAPSHOT/maven-metadata.xml
...
Uploaded to apache.snapshots.https: https://repository.apache.org/content/repositories/snapshots/org/apache/maven/plugins/maven-metadata.xml (9.0 kB at 33 kB/s)
[INFO]
[INFO] --- atr:1.0.0-beta-1-SNAPSHOT:upload (upload-to-atr) @ maven-atr-plugin ---
[INFO] Uploading artifacts to ATR...
[INFO] Composing release https://release-test.apache.org/compose/maven-atr-plugin/1.0.0-beta-1-SNAPSHOT
[INFO] Files: 3
[INFO] Uploading: maven-atr-plugin-1.0.0-beta-1-SNAPSHOT-source-release.zip to https://release-test.apache.org/file/maven-atr-plugin/1.0.0-beta-1-SNAPSHOT/maven-atr-plugin-1.0.0-beta-1-SNAPSHOT-source-release.zip
[INFO] Upload successful. Revision: unknown
[INFO] Uploading: maven-atr-plugin-1.0.0-beta-1-SNAPSHOT-source-release.zip.sha512 to https://release-test.apache.org/file/maven-atr-plugin/1.0.0-beta-1-SNAPSHOT/maven-atr-plugin-1.0.0-beta-1-SNAPSHOT-source-release.zip.sha512
[INFO] Upload successful. Revision: 00002
[INFO] Uploading: maven-atr-plugin-1.0.0-beta-1-SNAPSHOT-source-release.zip.asc to https://release-test.apache.org/file/maven-atr-plugin/1.0.0-beta-1-SNAPSHOT/maven-atr-plugin-1.0.0-beta-1-SNAPSHOT-source-release.zip.asc
[INFO] Upload successful. Revision: 00004
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 16.346 s
[INFO] Finished at: 2026-04-18T10:14:05+02:00
[INFO] ------------------------------------------------------------------------
```
you'll see the early error message if you forgot to configure your server settings in `~/.m2/settings.xml`: https://github.com/apache/maven-studies/blob/maven-atr-plugin/src/site/markdown/usage.md
I created the draft release in ATR and uploaded content: don't hesitate to delete it from ATR and re-create a new one, as ATR does not allow override upload
```
[INFO] --- atr:1.0.0-beta-1-SNAPSHOT:upload (upload-to-atr) @ maven-atr-plugin ---
[INFO] Uploading artifacts to ATR...
[INFO] Composing release https://release-test.apache.org/compose/maven-atr-plugin/1.0.0-beta-1-SNAPSHOT
[INFO] Files: 3
[INFO] Uploading: maven-atr-plugin-1.0.0-beta-1-SNAPSHOT-source-release.zip to https://release-test.apache.org/file/maven-atr-plugin/1.0.0-beta-1-SNAPSHOT/maven-atr-plugin-1.0.0-beta-1-SNAPSHOT-source-release.zip
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 6.814 s
[INFO] Finished at: 2026-04-18T10:23:21+02:00
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-atr-plugin:1.0.0-beta-1-SNAPSHOT:upload (upload-to-atr) on project maven-atr-plugin: Failed to upload file: HTTP 500 - {"error":"Internal server error"}
```
(a few days ago, it was not saying "Internal server error" but was more explicit about rejecting override of content already uploaded)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@tooling.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tooling.apache.org
For additional commands, e-mail: dev-help@tooling.apache.org
Re: [I] Review Maven ATR plugin and make recommendations (tooling-trusted-releases)
Posted by "hboutemy (via GitHub)" <gi...@apache.org>.
hboutemy commented on issue #926:
URL: https://github.com/apache/tooling-trusted-releases/issues/926#issuecomment-4246636452
I added a `atr:chec-composing` goal https://github.com/apache/maven-studies/commit/4b189edcc6c59b87166cef5c9c4f12424bad0725
intent is not to start the release, but check that the release is ready to be composed
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@tooling.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tooling.apache.org
For additional commands, e-mail: dev-help@tooling.apache.org
Re: [I] Review Maven ATR plugin and make recommendations (tooling-trusted-releases)
Posted by "slawekjaranowski (via GitHub)" <gi...@apache.org>.
slawekjaranowski commented on issue #926:
URL: https://github.com/apache/tooling-trusted-releases/issues/926#issuecomment-4395435439
Maybe better and easier will be maintain it under Maven namespace - we have everything for releasing
Next when we use `org.pache.maven.plugins` as groupId users can easy execute: `mvn atr:goal`
in other groupId user need to provide a full path for plugin: `mvn org.apache.xxx:art:goal`
@hboutemy @cstamas - what do you think?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@tooling.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tooling.apache.org
For additional commands, e-mail: dev-help@tooling.apache.org
Re: [I] Review Maven ATR plugin and make recommendations (tooling-trusted-releases)
Posted by "dave2wave (via GitHub)" <gi...@apache.org>.
dave2wave commented on issue #926:
URL: https://github.com/apache/tooling-trusted-releases/issues/926#issuecomment-4423622423
Infra is setting up the Maven PMC as alt owners so you should be good to setup the plugin there. Once it's setup we'll work through the release mechanism...
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@tooling.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tooling.apache.org
For additional commands, e-mail: dev-help@tooling.apache.org
Re: [I] Review Maven ATR plugin and make recommendations (tooling-trusted-releases)
Posted by "sbp (via GitHub)" <gi...@apache.org>.
sbp commented on issue #926:
URL: https://github.com/apache/tooling-trusted-releases/issues/926#issuecomment-4112046520
@hboutemy Thanks for this. I notice that a JWT is being created for every file that's uploaded. JWT creation is rate limited to 10 per hour in ATR, because its JWTs last 30 minutes (if the PAT hasn't been revoked). The limit is likely to be reached if a JWT is not reused.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@tooling.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tooling.apache.org
For additional commands, e-mail: dev-help@tooling.apache.org
Re: [I] Review Maven ATR plugin and make recommendations (tooling-trusted-releases)
Posted by "dave2wave (via GitHub)" <gi...@apache.org>.
dave2wave commented on issue #926:
URL: https://github.com/apache/tooling-trusted-releases/issues/926#issuecomment-4263749548
What co-ordinates would be used in Maven Central?
If tooling is responsible we will need a public `apache/tooling-maven-plugins` git repository.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@tooling.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tooling.apache.org
For additional commands, e-mail: dev-help@tooling.apache.org
Re: [I] Review Maven ATR plugin and make recommendations (tooling-trusted-releases)
Posted by "slawekjaranowski (via GitHub)" <gi...@apache.org>.
slawekjaranowski commented on issue #926:
URL: https://github.com/apache/tooling-trusted-releases/issues/926#issuecomment-4395390361
> I need to discuss how we would handle write permissions on a tooling team version of this repository.
Also the questions are:
- what groupId will be used
- what release procedure we be for it
- as we deploy it to Central Repository we also need access to proper groupId in nexus - for staging and release
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@tooling.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tooling.apache.org
For additional commands, e-mail: dev-help@tooling.apache.org
Re: [I] Review Maven ATR plugin and make recommendations (tooling-trusted-releases)
Posted by "dave2wave (via GitHub)" <gi...@apache.org>.
dave2wave commented on issue #926:
URL: https://github.com/apache/tooling-trusted-releases/issues/926#issuecomment-4423489393
I created the repository. Still need to work on write permissions.
> A new repository has been set up by [wave@apache.org](mailto:wave@apache.org): tooling-maven-release-plugin.git
> Commit mail target: [commits@tooling.apache.org](mailto:commits@tooling.apache.org)
> Dev/issue mail target: [dev@tooling.apache.org](mailto:dev@tooling.apache.org)
> The repository can be found at:
> GitBox: https://gitbox.apache.org/repos/asf/tooling-maven-release-plugin.git
> GitHub: https://github.com/apache/tooling-maven-release-plugin.git
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@tooling.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tooling.apache.org
For additional commands, e-mail: dev-help@tooling.apache.org
Re: [I] Review Maven ATR plugin and make recommendations (tooling-trusted-releases)
Posted by "slawekjaranowski (via GitHub)" <gi...@apache.org>.
slawekjaranowski commented on issue #926:
URL: https://github.com/apache/tooling-trusted-releases/issues/926#issuecomment-4247013907
I'm open to help for testing and future maintain 😄
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@tooling.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tooling.apache.org
For additional commands, e-mail: dev-help@tooling.apache.org
Re: [I] Review Maven ATR plugin and make recommendations (tooling-trusted-releases)
Posted by "dave2wave (via GitHub)" <gi...@apache.org>.
dave2wave commented on issue #926:
URL: https://github.com/apache/tooling-trusted-releases/issues/926#issuecomment-4246863010
If we go the tooling route then I would expect that you and other maven domain experts would be available to maintain the plugin. I'm not sure about how much Dependabot work would be needed for example.
We would need to create an `apache/tooling-maven-plugins` repository and make sure that I can grant you and potentially others write access.
How easy is it to iterate with the plugin deployed only at repository.apache.org?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@tooling.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tooling.apache.org
For additional commands, e-mail: dev-help@tooling.apache.org
Re: [I] Review Maven ATR plugin and make recommendations (tooling-trusted-releases)
Posted by "hboutemy (via GitHub)" <gi...@apache.org>.
hboutemy commented on issue #926:
URL: https://github.com/apache/tooling-trusted-releases/issues/926#issuecomment-4246642379
@dave2wave by the end of the week, I'd like to start releasing a first beta of this plugin: I'll need to get your decision about doing it at Tooling or at Maven
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@tooling.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tooling.apache.org
For additional commands, e-mail: dev-help@tooling.apache.org
Re: [I] Review Maven ATR plugin and make recommendations (tooling-trusted-releases)
Posted by "slawekjaranowski (via GitHub)" <gi...@apache.org>.
slawekjaranowski commented on issue #926:
URL: https://github.com/apache/tooling-trusted-releases/issues/926#issuecomment-4246984068
> How easy is it to iterate with the plugin deployed only at repository.apache.org?
I think that all artifacts from repository.apache.org are sync to central
We can add a jankins/github action to publish snapshot version after each commit ...
deploy it is standard release, so voting and so on ....
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@tooling.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tooling.apache.org
For additional commands, e-mail: dev-help@tooling.apache.org
Re: [I] Review Maven ATR plugin and make recommendations (tooling-trusted-releases)
Posted by "hboutemy (via GitHub)" <gi...@apache.org>.
hboutemy commented on issue #926:
URL: https://github.com/apache/tooling-trusted-releases/issues/926#issuecomment-4247121720
> How easy is it to iterate with the plugin deployed only at repository.apache.org?
what do you expect from that? Why not do normal releases at maven Central like any other plugin?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@tooling.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tooling.apache.org
For additional commands, e-mail: dev-help@tooling.apache.org
Re: [I] Review Maven ATR plugin and make recommendations (tooling-trusted-releases)
Posted by "hboutemy (via GitHub)" <gi...@apache.org>.
hboutemy commented on issue #926:
URL: https://github.com/apache/tooling-trusted-releases/issues/926#issuecomment-4249994734
> I would prefer to iterate on a pre-release.
This is what we do by doing releases on Maven Central like `1.0.0-beta-1`, this is usual for 20 years:
1. pre-release = SNAPSHOT:
people who do pre-release tests even for that beta, like Slawek, build (`mvn install` precisely) locally the SNAPSHOT to be able to use it for tests = what we'll do with the few Maven devs who used ATR for a few releases, doing composition file upload with ATR UI.
2. beta release (using ATR beta URL `https://release-test.apache.org/`):
The beta release will be done in a next step, once the few very early "self install" testers are confident, that we'll do a public release (even beta) that can be integrated for public consumption, probably integrated as an option in [ASF parent POM that currently provides `apache-release` profile](https://maven.apache.org/pom/asf/)
3. release (using ATR GA URL when it is available):
I expect to be able to do a final release when ATR GA public url becomes final. This plugin will always remain small, it's just to upload for release composition preparation during the build phase with `mvn`, it will never grow very big: wider automation is what you do with GHA ATR actions. Steps 1 & 2 will have given us the expected confidence by ATR GA.
this 3 stages plan is what implicitely any Maven user would expect.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@tooling.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tooling.apache.org
For additional commands, e-mail: dev-help@tooling.apache.org
Re: [I] Review Maven ATR plugin and make recommendations (tooling-trusted-releases)
Posted by "dave2wave (via GitHub)" <gi...@apache.org>.
dave2wave commented on issue #926:
URL: https://github.com/apache/tooling-trusted-releases/issues/926#issuecomment-4248935066
> what do you expect from that? Why not do normal releases at maven Central like any other plugin?
I would prefer to iterate on a pre-release. Once that works well then yes it would be a release at `org.apache.tooling.*`
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@tooling.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tooling.apache.org
For additional commands, e-mail: dev-help@tooling.apache.org
Re: [I] Review Maven ATR plugin and make recommendations (tooling-trusted-releases)
Posted by "slawekjaranowski (via GitHub)" <gi...@apache.org>.
slawekjaranowski commented on issue #926:
URL: https://github.com/apache/tooling-trusted-releases/issues/926#issuecomment-4424031387
to be consistent with the apache-releases-client should be (now I see):
repo: tooling-atr-maven-plugin
plugin org.apache.tooling:atr-maven-plugin
and we can call
`mvn atr:goal` as we have for apache-releases-client `atr command ...`
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@tooling.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tooling.apache.org
For additional commands, e-mail: dev-help@tooling.apache.org
Re: [I] Review Maven ATR plugin and make recommendations (tooling-trusted-releases)
Posted by "slawekjaranowski (via GitHub)" <gi...@apache.org>.
slawekjaranowski commented on issue #926:
URL: https://github.com/apache/tooling-trusted-releases/issues/926#issuecomment-4423961311
next proposition for name:
repo: `tooling-maven-plugin`
plugin `org.apache.tooling:tooling-maven-plugin`
😄 I always have a challenge to choose a name
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@tooling.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tooling.apache.org
For additional commands, e-mail: dev-help@tooling.apache.org
Re: [I] Review Maven ATR plugin and make recommendations (tooling-trusted-releases)
Posted by "dave2wave (via GitHub)" <gi...@apache.org>.
dave2wave commented on issue #926:
URL: https://github.com/apache/tooling-trusted-releases/issues/926#issuecomment-4425041201
Repository https://github.com/apache/tooling-atr-maven-plugin is available and the Maven PMC and tooling should have write access.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@tooling.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tooling.apache.org
For additional commands, e-mail: dev-help@tooling.apache.org
Re: [I] Review Maven ATR plugin and make recommendations (tooling-trusted-releases)
Posted by "dave2wave (via GitHub)" <gi...@apache.org>.
dave2wave commented on issue #926:
URL: https://github.com/apache/tooling-trusted-releases/issues/926#issuecomment-4424459293
Rename coming ...
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@tooling.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tooling.apache.org
For additional commands, e-mail: dev-help@tooling.apache.org