Unable to successfully run mvn install on downloaded or git cloned project about org.hl7.fhir.core

[debashish-github]

Also attached the logs when run in debug mode ..

Error.txt

[jamesagnew]

That looks to me like a corrupted ZIP file has snuck into your local Maven repo. Try deleting your [home]/.m2 directory and trying again. If that fails, have a look at of the erroring files (e.g. C:\fhir\org.hl7.fhir.core-master\org.hl7.fhir.utilities\pom.xml ) and see if the contents offer any hints.

…

On Tue, Jun 2, 2020 at 1:44 PM debashish-github ***@***.***> wrote: Also attached the logs when run in debug mode .. Error.txt <https://github.com/hapifhir/org.hl7.fhir.core/files/4718805/Error.txt> — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#212 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AA2N7HKULY7FXZ467F5R62TRUU263ANCNFSM4NQ52BTA> .

[debashish-github]

Nope I tried crearing out .m2 .. Also tried in a different m/c .. same error . The jar maven-bundle-plugin-3.5.0 seems to be corrupted . I tried opening it and it kept giving the error that it is corrupted. I also tried another version 4.2.1 and it kept giving the same error and that jar too is corrupted. I am using maven 3.6.3 and my JDK is 11.0.3 .. Is there anything else that I have to have ?

Thanks

[jamesagnew]

What does the maven-bundle-plugin-3.5.0.jar actually contain? (i.e. how big is it? how does it look if you open it with a text editor?)

…

On Tue, Jun 2, 2020 at 3:57 PM debashish-github ***@***.***> wrote: Nope I tried crearing out .m2 .. Also tried in a different m/c .. same error . The jar maven-bundle-plugin-3.5.0 seems to be corrupted . I tried opening it and it kept giving the error that it is corrupted. I also tried another version 4.2.1 and it kept giving the same error and that jar too is corrupted. I am using maven 3.6.3 and my JDK is 11.0.3 .. Is there anything else that I have to have ? Thanks — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#212 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AA2N7HPN52UKMRP6F7CHDJTRUVKT3ANCNFSM4NQ52BTA> .

[debashish-github]

There definitely seems to be some problem in the way it is downloaded. I only see it about 2 KB . I have attached the textual content .
maven-bundle-contents.txt

[jamesagnew]

That file contains the following contents: https://searchassist.verizon.com/main?ParticipantID=euekiz39ksg8nwp7iqj2fp5wzfwi5q Assuming you are on Verizon internet, I am betting it's your ISP that is mangling the response unfortunately.. All you can do is delete the affected JAR and try again until you get a success

…

On Tue, Jun 2, 2020 at 4:36 PM debashish-github ***@***.***> wrote: There definitely seems to be some problem in the way it is downloaded. I only see it about 2 KB . I have attached the textual content . maven-bundle-contents.txt <https://github.com/hapifhir/org.hl7.fhir.core/files/4719564/maven-bundle-contents.txt> — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#212 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AA2N7HL4XSHSDOJKDJG2YNLRUVPGJANCNFSM4NQ52BTA> .

[debashish-github]

Found the root cause .. This doesn't happen to all downloads since some of my colleagues were able to successfully download and run mvn install. For my download for some reasons the first pom downloaded C:\m2repo\ca\uhn\hapi\fhir\hapi-fhir\4.2.0\hapi-fhir-4.2.0.pom was refering to incorrect plugin repository

	<pluginRepository>
		<id>maven2</id>
		<name>Maven2</name>
		<url>http://central.maven.org/maven2/</url>
		<snapshots>
			<enabled>true</enabled>
		</snapshots>
	</pluginRepository>

It took a while for me to manually fix this to point to repo https://repo.maven.apache.org/maven2/ to make this work. Can this be fixed so that others don't end up with the same issue I had ?

[markiantorno]

@debashish-github this should not still be an issue since the automated build process was put in place.