Please Note This forum exists for community support for the Mango product family and the Radix IoT Platform. Although Radix IoT employees participate in this forum from time to time, there is no guarantee of a response to anything posted here, nor can Radix IoT, LLC guarantee the accuracy of any information expressed or conveyed. Specific project questions from customers with active support contracts are asked to send requests to support@radixiot.com.
Cannot build with maven for custom module
-
Hi Radix Team, trying to build a custom dashboard package and I keep getting this error - looks like it's not in your repo anymore - got any suggestions?
[ERROR] Plugin org.codehaus.mojo:build-helper-maven-plugin:1.9.1 or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.codehaus.mojo:build-helper-maven-plugin:jar:1.9.1: Could not transfer artifact org.codehaus.mojo:build-helper-maven-plugin:pom:1.9.1 from/to ias-releases (https://maven.mangoautomation.net/repository/ias-release/): Transfer failed for https://maven.mangoautomation.net/repository/ias-release/org/codehaus/mojo/build-helper-maven-plugin/1.9.1/build-helper-maven-plugin-1.9.1.pom: Network is unreachable (connect failed) -> [Help 1]Fox
-
BUMP
-
Hey @MattFox ill try get some help from the dev team on this.
-
@MattFox the problem isn't specifically with our repo. The way maven works is that it checks all the repositories you have listed in the module's POM or its parent POMs in some order.
That plugin isn't owned by us and thus isn't hosted in our maven repository. What your goal should be is to figure out why your build isn't finding it on the public maven repositories such as this one:
https://mvnrepository.com/artifact/org.codehaus.mojo/build-helper-maven-plugin/1.9.1
or this one:
https://central.sonatype.com/artifact/org.codehaus.mojo/build-helper-maven-plugin/1.9.1
I'm pretty sure the problem is that your computer can't reach Maven central because of a proxy or some other problem. I would start by looking there, perhaps delete your
~/.m2directory and rebuild. Let me know if that solves it or you have a different problem.
-
@terrypacker Thanks Terry, I think you've hit the nail on the head with a proxy issue - I suspect the ISP is using some sort of NAT which is faltering my chances of getting anything through.
I'll see if I can use the above urls and go from there!
If I'm still unsuccessful, I can't just copy over another .m2 directory from a working instance can I?Fox
-
@MattFox Good news, was able to implement my own proxy server and direct all https traffic through it. Now can get on and finish what I started!
Have a great weekend all!Fox
