An unexpected error occurred while migrating artifact metadata: 'xsi' is an undeclared prefix

[parthu.reddy]

Getting this error while moving from classic maven to new maven on 2024.22

[dean-houston]

Hi @parthu-reddy ,

This error means that the previously listed pom file (ant-1.6.5.pom) is somehow corrupted. It cannot be loaded as XML due to the error.

I assume it's this artifact:
https://repo1.maven.org/maven2/ant/ant/1.6.5/

That one is fine at the source. I would just remove it from your old/classic feed, since I assume it's just something from maven central. And it can then be downloaded again.

-- Dean

[parthu.reddy]

An empty feed is getting this error

[parthu.reddy]

@dean-houston

https://repo1.maven.org/maven2/com/sun/activation/jakarta.activation/2.0.0-RC2/jakarta.activation-2.0.0-RC2.pom

Getting error for jakarta.activation-2.0.0 versions

Looks like there's some problem in orginal repo itself

Another example:
https://repo1.maven.org/maven2/com/sun/xml/bind/mvn/jaxb-parent/3.0.0/jaxb-parent-3.0.0.pom

I'm getting few of these errors.

[parthu.reddy]

This post is deleted!

[dean-houston]

Hi @parthu-reddy ,

Huh... that's interesting... but not surprising. The Maven (New) feeds assume POM files are valid XML, but I guess Marvin supports invalid XML for POM files

I fixed this via PG-2859 which add Add Support for Invalid POM files on Maven (New) Feeds. You can access it via 2024.23-rc.1 on the prerelease feed (InedoHub), or the 24.0.23-rc.1 Docker image.

Hopefully this will work-around these migration issues.

-- Dean

[parthu.reddy]

@dean-houston Thanks

[parthu.reddy]

A small question, can we upgrade proget but continue using classic maven for some time

[dean-houston]

@parthu-reddy yes, but we do recommend migrating...

There are some known bugs/quirks with Maven (Classic) feeds and we will not fix them.

We will likely not migrate them to PostgresSQL, which means you won't be able to migrate to PostgreSQL in ProGet 2025+.

So it's likely that ProGet 2027 will not support them.