You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "jira-importer (via GitHub)" <gi...@apache.org> on 2025/04/02 07:06:42 UTC
[I] [MDEPLOY-124] Deploy without build [maven-deploy-plugin]
jira-importer opened a new issue, #333:
URL: https://github.com/apache/maven-deploy-plugin/issues/333
**[Paul Gier](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=pgier)** opened **[MDEPLOY-124](https://issues.apache.org/jira/browse/MDEPLOY-124?redirect=false)** and commented
We have a use case where we would like to run a build (up to the install phase) and then deploy at a later time. Currently, the deploy plugin requires that a full build be re-run in order to deploy. Since the build does not record the list of attached artifacts, the deploy plugin would need some way to record the list of attached artifacts, and then read them later for deployment.
Possibly a new goal could be introduced which would create a list of attached artfiacts. Then the deploy goal could optionally read from this list.
---
**Issue Links:**
- [MDEPLOY-157](https://issues.apache.org/jira/browse/MDEPLOY-157) Add deployAtEnd option for multimodule projects
3 votes, 5 watchers
--
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: issues-unsubscribe@maven.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [MDEPLOY-124] Deploy without build [maven-deploy-plugin]
Posted by "jira-importer (via GitHub)" <gi...@apache.org>.
jira-importer commented on issue #333:
URL: https://github.com/apache/maven-deploy-plugin/issues/333#issuecomment-2771531992
**[Stephen Connolly](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=stephenc)** commented
I'd rather separate goals than a property. That way it is explicit what the user is requesting (two phase versus one phase) a mojo property could be set for one module in a multi-module build and then the user who is use to one phase deploy gets caught off-guard and never does the second phase because they were not watching the build log like a hawk and the build did not fail
--
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: issues-unsubscribe@maven.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [MDEPLOY-124] Deploy without build [maven-deploy-plugin]
Posted by "jira-importer (via GitHub)" <gi...@apache.org>.
jira-importer commented on issue #333:
URL: https://github.com/apache/maven-deploy-plugin/issues/333#issuecomment-2771531987
**[Wendy Smoak](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=wsmoak)** commented
It sounds like the release staging feature of one of the various artifact repositories would be useful here.
You deploy to one place, do whatever, and then promote the release later.
--
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: issues-unsubscribe@maven.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [MDEPLOY-124] Deploy without build [maven-deploy-plugin]
Posted by "jira-importer (via GitHub)" <gi...@apache.org>.
jira-importer commented on issue #333:
URL: https://github.com/apache/maven-deploy-plugin/issues/333#issuecomment-2771532012
**[Elliotte Rusty Harold](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=elharo)** commented
seems useful, but also risky. What if the artifacts change in between build and deploy?
--
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: issues-unsubscribe@maven.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [MDEPLOY-124] Deploy without build [maven-deploy-plugin]
Posted by "jira-importer (via GitHub)" <gi...@apache.org>.
jira-importer commented on issue #333:
URL: https://github.com/apache/maven-deploy-plugin/issues/333#issuecomment-2771531981
**[Stephen Connolly](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=stephenc)** commented
so this would be a pair of goals, e.g.
deploy:imprint (which takes persists all the attached artifacts and I'm guessing checksums of them for safety to a file in ${project.build.directory})
deploy:publish (which reads back in the persisted artifact file and publishes those artifacts)
--
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: issues-unsubscribe@maven.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [MDEPLOY-124] Deploy without build [maven-deploy-plugin]
Posted by "jira-importer (via GitHub)" <gi...@apache.org>.
jira-importer commented on issue #333:
URL: https://github.com/apache/maven-deploy-plugin/issues/333#issuecomment-2771531996
**[Paul Gier](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=pgier)** commented
I agree it should be a separate goal, however it also needs some way to determine which files to deploy. My previous suggestion was to add property to the existing deploy go which only creates a list of files to deploy instead of actually deploying them. Then the second goal reads the list and deploys the files. Another option is to just manually configure the list of files to deploy in the plugin. Maybe this could be done as an enhancement to the existing deploy-file goal.
--
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: issues-unsubscribe@maven.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [MDEPLOY-124] Deploy without build [maven-deploy-plugin]
Posted by "jira-importer (via GitHub)" <gi...@apache.org>.
jira-importer closed issue #333: [MDEPLOY-124] Deploy without build
URL: https://github.com/apache/maven-deploy-plugin/issues/333
--
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: issues-unsubscribe@maven.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [MDEPLOY-124] Deploy without build [maven-deploy-plugin]
Posted by "jira-importer (via GitHub)" <gi...@apache.org>.
jira-importer commented on issue #333:
URL: https://github.com/apache/maven-deploy-plugin/issues/333#issuecomment-2771531990
**[Paul Gier](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=pgier)** commented
Maybe instead of a new "imprint" goal, there could just be an option to the existing "deploy" goal which would create the list instead of uploading the artifacts. Something like "-DprepareForPublish". Then the second goal "publish" could read the list of files and actually do the deployment.
--
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: issues-unsubscribe@maven.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [MDEPLOY-124] Deploy without build [maven-deploy-plugin]
Posted by "jira-importer (via GitHub)" <gi...@apache.org>.
jira-importer commented on issue #333:
URL: https://github.com/apache/maven-deploy-plugin/issues/333#issuecomment-2771532003
**[Julien CARSIQUE](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=jcarsique)** commented
I made a similar suggestion on MDEPLOY-160
Taking into account Stephen's comment, I would rather
- create a dedicated goal for the first step which does not actually deploy but registers what to deploy,
- then a property can be used on the existing deploy goal to provide the list of artifacts to deploy. That way, in the worst case, the build would happen while not expected, or the deploy would fail because of a missing file.
Using the deploy-file goal would make sense but the deploy goal could be even more relevant: allowing to browse the modules and skip the build (or not), check that the artifact previously produced is consistent with the module being processed...
--
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: issues-unsubscribe@maven.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org