Story #854

Create a plugin to support syncing & publishing Maven artifacts

Added by bcourt almost 6 years ago. Updated almost 2 years ago.

Start date:
Due date:
% Done:


Estimated time:
Platform Release:
Sprint Candidate:
Pulp 2


This content has been moved here:

Create an initial framework for supporting syncing & publishing Maven artifacts from within Pulp. This issue is an ok place for planning and gathering comments and information, but that should be broken up into smaller stories if/when implemented.


  • A plugin module for maven artifacts
    • The plugin supports creating maven repositories
    • As a user, I can provide a URL, and possibly some additional information about how to discover specific content, that Pulp will use to sync a remote repository.
    • The plugin supports deleting maven repositories
    • As a user syncing from a remote Pulp, I only need to provide a URL to sync. Additional information about how to discover content should not be necessary.
    • The plugin supports uploading of maven modules to a repository
    • The plugin DOES NOT support lazy loading or syncing content from maven central
  • CLI support for creating maven repositories
  • CLI support for deleting maven repositories
  • CLI support for uploading a maven artifact
  • CLI support for deleting a maven artifact



Some maven repositories appear to have an index of content named archetype-catalog.xml, and some do not. What are the expectations around that file? When is/should it be present?

When Pulp does a sync, if that catalog is not present, we will need some other way for a user to specify what content to get. Should they provide a pom.xml file to the importer? Or perhaps csv/json that enumerates the content to get?

When Pulp does a publish, is it always safe for it to create an archetype-catalog.xml file? It is handy to have so that other Pulp deployments can sync from it and duplicate the exact same content.


Should Pulp support "snapshot" repositories?

The challenge is that the content with a given unique identifier that includes "-SNAPSHOT" can change from one sync to the next, and there's no way to know if it did. So it would need to be downloaded every time. We would also have to accept that if the content had been promoted into an additional repository, it could get updated in-place without another promote operation.


Is there a use case for upload? What does that look like? In what format would data get uploaded?



#1 Updated by jackhill almost 6 years ago

bcourt on IRC asked me to comment on this issue. I would find Maven repository support useful as a way to distribute our own artifacts.


#2 Updated by cduryee over 5 years ago

  • Groomed set to No
  • Sprint Candidate set to No

It may be worth looking at just to see if there's any opportunity to integrate with that.

#3 Updated by mhrivnak over 3 years ago

  • Subject changed from Create a plugin to support uploading & publishing Maven artifacts to Create a plugin to support syncing & publishing Maven artifacts
  • Description updated (diff)

#4 Updated by mhrivnak over 3 years ago

  • Description updated (diff)

#5 Updated by over 3 years ago

We need to expand the deliverables to include publish and copy actions.

#6 Updated by over 3 years ago

Before this is broken into new stories, a new redmine project should be created for pulp_maven.

Here are some bootstrapping stories for python that might be a helpful story template:

#7 Updated by bmbouter almost 3 years ago

  • Status changed from NEW to CLOSED - NOTABUG

This content is moving into the wiki for further planning. The reasoning is that this tracker is for core planning and not plugin planning. It's new home is here:

#8 Updated by bmbouter almost 3 years ago

  • Description updated (diff)

#9 Updated by bmbouter almost 2 years ago

  • Tags Pulp 2 added

Please register to edit this issue

Also available in: Atom PDF