Should not require <distributionManagement> to be set if altDeploymentRepository is defined

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Duplicate
  • Affects Version/s: 2.3
  • Fix Version/s: None
  • Component/s: None
  • Labels:
    None

Description

Currently, the plugin errors if <distributionManagement> is not configured - even if altDeploymentRepository is specified. It should not be necessary to have a <distributionManagement> section in a project that is being deployed with altDeploymentRepository.

Use case: Deploying a project into an organization repository, when the upstream has no <distributionManagement>, or has it only in a profile which also adds unwanted settings.

Issue Links

duplicates

Bug - A problem which impairs or prevents the functions of the product. MDEPLOY-50 deploy:deploy fails without distributionManagment despite altDeploymentRepository being specified

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Activity

There are no comments yet on this issue.

People

  • Assignee:
    Unassigned
    Reporter:
    Max Bowsher
Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: