pulp / pulp/pulp_maven

As a user, I can sync Maven Central repository

Open
#50 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Migrated from Redmine New stale Story
Dominant language
Python
Stars
5
Forks
24
Avg merge
1d 6h
Merged PRs (30d)
39

Description

Author: @dkliban (dkliban@redhat.com)

Redmine Issue: 3592, https://pulp.plan.io/issues/3592


Maven central provides an archetype-catalog.xml at the root of the repository. Some other Maven repositories also provide the same catalog in the root. As a result of this story the user will be able to

1) Create a remote with a URL pointing to http://hostname/blah/archetype-catalog.xml
2) Sync from the remote.
3) Use the REST API to verify that all Archetypes listed in the catalog were created in Pulp and all their Maven Artifacts were also created in Pulp.

Some inspiration might be drawn from https://github.com/jiptool/jip

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing how a remote URL is handled through the REST API and sync flow. Inspect how the archetype-catalog.xml and its Maven artifacts would be represented, then compare any existing repository-sync behavior. Done means a remote can sync the catalog and the REST API verifies every listed archetype and artifact was created.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
api, backend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.