Repository navigation
[MDEPLOY-277] better deploy-file integration #552
Description
Delany opened MDEPLOY-277 and commented
I have a script which deploys hundreds of static JARs to a Nexus repo. I use the deploy-file goal, which requires the url and repositoryId properties. Currently I have to hard-code these into the script.
I want to be able to use the repository url and id I set in the distributionManagement of my project.
Affects: 3.0.0-M1
Activity
jira-importer commentedon Nov 12, 2020
Michael Osipov commented
This seems to be a contradiction. Manually deploying JARs means that they are not Maven managed. The POM will be generated on the repo. In which POM do you want to store those attributes?
jira-importer commentedon Nov 12, 2020
Delany commented
I set a property <repo.thirdparty>${build.remote}/repository/${build.name}-endorsed</repo.thirdparty>
and then use that in ${repo.thirdparty}
It makes it easier to override. That much is fine. Now I want to deploy to the same repository.
I create a new profile with ${repo.thirdparty} which I only activate when provisioning repo.thirdparty with my static JARs. But the deploy-file goal cannot access this URL.
jira-importer commentedon Nov 12, 2020
Delany commented
BTW, when I use deploy-file to deploy an artefact with a classifier, it overwrites the same artefact sans the classifier. Is there a ticket for this?
jira-importer commentedon Nov 12, 2020
Michael Osipov commented
Can you provide a command line sample you are passing?
jira-importer commentedon Nov 12, 2020
Michael Osipov commented
Provide a reproducer with a new ticket for MDEPLOY.