Is there a way to get the build-setup plugin to use a local repository instead of Maven Central?

(Scott Palmer) #1

setupBuild is failing to find the parent pom for my project because it isn’t asking our Artifactory repo. Is there some property I could set via -P to change the repo used to resolve the dependencies?

(Scott Palmer) #2

Note that the asset in question is already present in the local maven cache, but it still tries to find it in Maven Central and fails.

(Scott Palmer) #3

I have a repositories section in my pom, but this is what happens:

  • What went wrong:

Execution failed for task ‘:setupBuild’.

Could not convert Maven POM /Users/scott/dev/MyProjectCore/MyProject/pom.xml to a Gradle build.

Unable to create Maven project model using POM /Users/scott/dev/Project/MyProject/pom.xml.

1 problem was encountered while building the effective model for example.domain.project:MyProject:1.2.1-SNAPSHOT

[FATAL] Non-resolvable parent POM: Could not transfer artifact example.domain.project:MyProjectCore:pom:1.2.0 from/to repo.domain.example (http://my-local-repo/repo/): No connector available to access repository repo.domain.example (http://my-local-repo/repo/) of type default using the available factories and ‘parent.relativePath’ points at wrong local POM @ line 4, column 10

for project example.domain.project:MyProject:1.2.1-SNAPSHOT at /Users/scott/dev/MyProjectCore/MyProject/pom.xml

The Maven build works though, so I don’t understand the “‘parent.relativePath’ points at wrong local POM…” What is it talking about? The parent pom is one level up in the folder hierarchy, but the project is not a “module” of the parent.

(Scott Palmer) #4

I had an error in the pom and got lucky with the Maven builds because of the order that I was building in Maven. Please disregard.