Low blow.

I know. 😉

I'm thinking that it might be the way aether is called on local repository.

Don't know much about aether, but isn't there an option to set the repo id when fetching?

Yup

How about

org.eclipse.aether.internal.impl.EnhancedLocalRepositoryManager

?

That apparently checks both locally and remotely, according to:

<http://ggrzybek.blogspot.com/2016/10/using-maven-with-osgi-part-3.html>

That article does mention the local metadata xml file.

Stabbing in the dark here, but that article seems to be on point.

In all fairness, that is only a problem if no version if specified for the dependency (

com.example:foo:

).

Which highlight another problem with Kobalt. When using

publishToMavenLocal

, it does not create (or update) the

maven-metadata.xml

file. Technically, it's an invalid maven publication then.

That part I'm pretty sure I can fix, the aether stuff, probably not from what I've heard you complain about. 😉

Yes fixing local should be easy

Actually, looks like the Maven Artifact Resolver includes updating/creating the metadata.

That's where local vs remote comes in play.

Looking at

org.eclipse.aether

docs gives me a headache.

Anyway, I'll create an issue and look at the code and see what I can figure out. Not a big issue since there is a workaround (specify a dependency version), but it would be nice to do it 'right'.

BTW, Gradle wasn't doing it right either, they just created a

maven-metadata.xml

until version 4.

That's how I spotted it. 😉

haha nice catch

@cedric https://github.com/cbeust/kobalt/blob/ffc56002c359c4ea9aca8e71f0c2f0a0de9a6456/modules/kobalt-plugin-api/src/main/kotlin/com/beust/kobalt/maven/UnversionedDep.kt#L14

I guess it's a bug after all, already in there but obviously not working right.

toMetadataXmlPath

doesn't seem to be used but in a test file.

There’s a bug in that implementation?

That implementation is not used apparently.

oh

I just stumbled upon it by luck.

Well at least it’s nicely commented 😄

Yeah, give the man a cigar. 😉

Looks to me like all repositories are treated as remote in

KobaltMavenResolver.kt

.