Karl Heinz Marbaise-3 wrote
> The distributionManagement should be offered by a company parent pom
> which handles this...and it is a good idea to use placeholders here to
> have chance to change that in particular with CI environments which can
> control this...
OK that's workable. One layer i
Hi,
On 10/07/18 11:09, ahardy42 wrote:
Hi maven-users,
it seems this issue was last discussed almost 10 years ago but despite
reading the docs and the email lists there is still an issue with
distribution management that I don't understand.
I do not wish to declare our company's internal relea
altDeploymentRepository (or alternatively
altReleaseDeploymentRepository/altSnapshotDeploymentRepository) sounds like
THE solution to this problem:
https://maven.apache.org/plugins/maven-deploy-plugin/deploy-mojo.html#altDeploymentRepository
mvn deploy -DaltDeploymentRepository=company-repo:defaul
Hi Adam,
'distributionManagement' is part of the pom not part of settings : maven is
like that.
If you do not want to expose some company repositories or if those ones are
often changing then you can:
- either use placeholders in some predefined `distributionManagement` tags
(in project or in par
Hi maven-users,
it seems this issue was last discussed almost 10 years ago but despite
reading the docs and the email lists there is still an issue with
distribution management that I don't understand.
I do not wish to declare our company's internal release and snapshot
repositories in pom files
