If Forge is unable to resolve the parent POM, then chances are good that Maven builds will have the same problem. My recommendation is to either: A) Fix the relativePath location so that it points to the correct parent POM B) Remove the relativePath entirely.
I hope this helps,
Hi thanks for your reply!
The maven build runs fine. There also isn't any relativePath location in my pom.xml:
<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd">
Could it be that forge isn't finding my .m2/settings.xml file which specifies the local Nexus repository that contains the parent pom?
1 of 1 people found this helpful
If I modify my pom and explictly add my local Nexus repository it works. However I expect forge to use the repos I have specified in maven conf\settings.xml, just as mvn package does.
I've posted details for replicating the issue to email@example.com
Okay. Forge may be ignoring repositories in settings.xml, which is not good. I'll have a look at this.
Fixed in latest SNAPSHOT. Could you try building forge from source (or waiting for a new snapshot build) and try again?
1.1.1-SNAPSHOT - you might have to wait for the CI build if you don't do it yourself.
Thanks very much for the fix - however I tried forge-distribution-1.1.1-20121010.225553-23.zip and it still has the error (and some others beside).
On a side note, to clarify the above - when I said local Nexus repository I really meant non-public coporate Nexus repository.
If a locally cached copy of the parent pom and it's .sha1 file exist in my machine's local repository (ie: .m2/repository) then there is no problem for forge.