[ https://issues.apache.org/jira/browse/MDEPLOY-276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Osipov updated MDEPLOY-276: ----------------------------------- Fix Version/s: wontfix-candidate > Warning when a pom is not able to be updated in remote repository > ----------------------------------------------------------------- > > Key: MDEPLOY-276 > URL: https://issues.apache.org/jira/browse/MDEPLOY-276 > Project: Maven Deploy Plugin > Issue Type: New Feature > Components: deploy:deploy > Affects Versions: 3.0.0-M1 > Reporter: sylvain mouquet > Priority: Major > Fix For: wontfix-candidate > > > Hello, > > I explain my context. > I have some maven projects with a pom parent and modules. > To speed up the CI/CD pipelines for the CI, we have created a profile foreach > module or group of module which allow us to // the build of the maven project > On the release job we cannot use the // because maven push the parent pom in > the release repository and for best practice the release repository is able > to write but not re-write/update. > One solution is to add an option to allow to continue the deploy even if the > pom parent is not able to be updated in the remote repository. > It's possible to add this feature ? > > Currently we don't use the // in the release step due to this -- This message was sent by Atlassian Jira (v8.3.4#803005)