-
Notifications
You must be signed in to change notification settings - Fork 28
Unable to build Third Party using maven CLI #125
Comments
Is there any known workaround? I ran into the same error when attempting to install. |
Thanks for adding this issue. Totally unaware there was a problem. I'll look into it over the 4th week-end John |
(ps: it is likely just that the common lib has has not be rebuilt.) |
It could also be the version of Maven or Java. What is the last working version that has been tested on? |
I think (if this is happening to you on your local machine) that this is fixed by first building common, then building ThirdParty - you local library cache either has a 1.2 version of common.jar (unlikely) or no version of common.jar. This error occurs b/c we have never place the jar files on a maven repo (again, I think). |
So it's was error with Maven on Bitnami Stack. I was able to fix that in settings.xml. With the following addition.
It didn't however get me all the way there, in building common.jar I ran into the following errors.
I will continue debugging another day. I am a bit of a novice in the Java world. |
Haven't made any progress building common jar. What Java stack do you use for your build? |
Any update on this issue ? I am using maven (3.5.4) and Java (10.0.1). Getting the same error when building ThirdParty 1.3-SNAPSHOT |
@Anmol-Porwal18 Can you provide the following information:
|
@dfcoffin I am using maven CLI for build and yes, I tried building OpenESPI-Common-Java jar file but the build fails with the surefire plugin error:
|
@Anmol-Porwal18 Please provide the complete maven CLI command you are using to build the OpenESPI-Common-java JAR and the OpenESPI-ThirdParty-Java WAR files. The JUnit test have been deprecated are although in the source file have not been maintained. Use the following maven commands to build the Common and ThirdParty modules:
|
Ack, I was just doing |
Attempting to build the Data Custodian using the following maven CLI format produces a failed build:
Results in the following build error and subsequent failure:
The text was updated successfully, but these errors were encountered: