Maven 2 & 3

repository conversion tool

Details

  • Type: New Feature New Feature
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: None
  • Fix Version/s: 2.0-alpha-1
  • Component/s: None
  • Labels:
    None
  • Number of attachments :
    0

Description

we need a way to covert repository/ibiblio-v1 into a new layout, as specified by:
http://docs.codehaus.org/pages/viewpage.action?pageId=22230

It should be able to process files on the way with pluggable processors/validators and produce a small report.

Basic validators:

  • check for a missing POM
  • check for an invalid format POM
  • check for missing/incorrect MD5, and create

These would also need to be able to run on an existing repository as part of the same tool without doing a conversion.

Other validators will be filed separately, but are probably not needed for v1.

The repository converter will also need to ensure that it can convert v3 poms to v4.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
John Casey added a comment -

should work. Tested on local m1 repository, only error was vdoclet/jars/qdox-current.jar, which is sort of a lost cause. (I can't reliably pull enough Artifact info from that path).

Should be ready for a trial run against ibiblio-v1.

Show
John Casey added a comment - should work. Tested on local m1 repository, only error was vdoclet/jars/qdox-current.jar, which is sort of a lost cause. (I can't reliably pull enough Artifact info from that path). Should be ready for a trial run against ibiblio-v1.
Hide
Permalink
John Casey added a comment -

wow, was that too soon to speak. It's almost akin to saying "Well, it compiles, it must work."

Alright, will not re-resolve until I get a successful run on the repo itself, including any distribution artifacts that conform to legal repo usage/naming.

We will NOT be accommodating those projects who chose to abuse the old repo conventions. If this policy should be changed, let me know.

Show
John Casey added a comment - wow, was that too soon to speak. It's almost akin to saying "Well, it compiles, it must work." Alright, will not re-resolve until I get a successful run on the repo itself, including any distribution artifacts that conform to legal repo usage/naming. We will NOT be accommodating those projects who chose to abuse the old repo conventions. If this policy should be changed, let me know.
Hide
Permalink
John Casey added a comment -

Should be running reasonably well now. Observed about a 6.75% kickout rate, of which most were due to XML entities inside the POM. This number does not include those with invalid artifact paths within the repository (someone <cough>jbehave</cough> had put an entire website up there!).

It may be possible to improve on this success rate, but I'm definitely up against the law of diminishing returns at this point.

Show
John Casey added a comment - Should be running reasonably well now. Observed about a 6.75% kickout rate, of which most were due to XML entities inside the POM. This number does not include those with invalid artifact paths within the repository (someone <cough>jbehave</cough> had put an entire website up there!). It may be possible to improve on this success rate, but I'm definitely up against the law of diminishing returns at this point.

People

  • Assignee:
    John Casey
    Reporter:
    Brett Porter
Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved:

Time Tracking

Estimated:
Not Specified
Original Estimate - Not Specified
Remaining:
0m
Remaining Estimate - 0 minutes
Logged:
19h
Time Spent - 19 hours