topic Unresolvable Build Extension: Pamp-to-war in Alfresco Archive

Unresolvable Build Extension: Pamp-to-war

funwithwhips — Thu, 03 Nov 2016 08:52:05 GMT

I have a development copy of our corporate DMS Alfresco 5.1.f community edition on Win7 64bit and am using Maven 3.3.9 alongside jdk8.0_112.I'm new to alfresco, java and maven but have been developing in c# and php for over 12 years. I have been following the SDK setup and trying to get this to wo

Re: Unresolvable Build Extension: Pamp-to-war

jpotts — Thu, 03 Nov 2016 17:42:58 GMT

The PKIX messages make me think maybe there is a problem with how your machine or a machine you are going through to connect to the internet is handling the SSL cert.

What happens when you try to browse directly to https://artifacts.alfresco.com/nexus/content/groups/public?

Re: Unresolvable Build Extension: Pamp-to-war

funwithwhips — Fri, 04 Nov 2016 08:33:25 GMT

Hi Jeff,

Thanks for replying.

I don't have any problem reaching the artifacts site. I'm taken straight to the index

Re: Unresolvable Build Extension: Pamp-to-war

jpotts — Fri, 04 Nov 2016 20:33:36 GMT

Can I assume that this is an out-of-the-box project created from the archetype with zero modifications? If not, please create a new, empty project, like using the repo archetype, and let's see if we can re-create the problem.

Once you create the new, empty project, run mvn -X compile and see what happens.

At the start of the output you should see some debug statements that look like this:

[DEBUG] Reading global settings from /opt/local/share/java/maven3/conf/settings.xml

[DEBUG] Reading user settings from /Users/jpotts/.m2/settings.xml

[DEBUG] Reading global toolchains from /opt/local/share/java/maven3/conf/toolchains.xml

[DEBUG] Reading user toolchains from /Users/jpotts/.m2/toolchains.xml

[DEBUG] Using local repository at /Users/jpotts/.m2/repository

Those might help you figure out what's going on. For example, maybe in your settings.xml you have something that's throwing off the build.

If the new empty project builds successfully then you can start comparing the difference between the fresh project and the one that is failing.

If the new empty project also fails, then it is probably something having to do with how you created the project or your maven settings or your local maven repo.

Re: Unresolvable Build Extension: Pamp-to-war

funwithwhips — Mon, 07 Nov 2016 12:26:58 GMT

Hi Jeff,

Thanks. Nearly there.

Looks like it was a certificate issue and you were right. I downloaded the alfresco certificate and then imported it into into the JRE cacerts file using the keytool. Running any maven command (including compile, clean etc.) now gets a lot further but now hangs on the same line regardless of virus on/off, using the cmd or using the poweshell:

Downloading: https://artifacts.alfresco.com/nexus/content/groups/public/org/clojars/pmonks/spinner/0.3.0/spinner-0.3.0.jar

No errors or any other messages even using debug switch.

Any clues?

Re: Unresolvable Build Extension: Pamp-to-war

jpotts — Mon, 07 Nov 2016 17:25:37 GMT

That artifact is not in the Alfresco artifacts repo, nor is it in Maven

central.

Where is that dependency coming from? Can you do mvn dependency:tree and

see if it gives us any clues?

Re: Unresolvable Build Extension: Pamp-to-war

funwithwhips — Tue, 08 Nov 2016 09:21:27 GMT

Hi Jeff,

Thanks for your patience. I really appreciate your help.

I deleted the files in my .m2 repository and generated a vanilla alfresco archetype.

I then ran the dependency tree and It hung on the same line as usual. I have included the output file if that is any help.

I tried running again in powershell. This told me that at least part of the file (656kb) is being loaded.

I had to initially reconfigure my settings.xml in m2 to get the archetype to generate at all. I added a mirror with the id of “central” pointing to the http://repo1.maven.org/maven2 repository. I don’t know if this is part of the problem or not.

Again, many thanks.

Re: Unresolvable Build Extension: Pamp-to-war

jego — Thu, 10 Nov 2016 21:10:47 GMT

My guess is that you are using a proxy like nexus or artifactory which does not proxy the clojars repository.

How to solve that?

1. add a proxy to your central proxy.

2. do not use the central maven proxy in your company

see AVT clojars-dependencies · Issue #253 · Alfresco/alfresco-sdk · GitHub

I hope this helps.

Thanks

Jens