Deploying to alternate repo specified by -DrepositoryId=

Details

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

Description

It's useful to be able to build an artifact (such as a snapshot of a plugin) and deploy it to a local repository (such as on a corporate intranet).

A good way to do this seems to be putting the corporate repo into settings.xml and using -DrepositoryId=xxx on the command line, but this doesn't work.

Issue Links

is related to

Bug - A problem which impairs or prevents the functions of the product. MDEPLOY-46 "mvn -DaltDeploymentRepository=... deploy" of a SNAPSHOT doesn't replace date.buildnumber

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

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Jason van Zyl added a comment -

Issue has been fixed in trunk.

Show
Jason van Zyl added a comment - Issue has been fixed in trunk.
Hide
Permalink
Geoffrey De Smet added a comment -

Nice, but for SNAPSHOT it doesn't quite work a 100% yet (the remote repo might even be considered slightly corrupted by it), see MDEPLOY-46

Show
Geoffrey De Smet added a comment - Nice, but for SNAPSHOT it doesn't quite work a 100% yet (the remote repo might even be considered slightly corrupted by it), see MDEPLOY-46

People

  • Assignee:
    Jason van Zyl
    Reporter:
    Brian Topping
Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: