mvn clean install -autoInstallPackage fails due Connection refused

[tim-schwalbe-NZ]

Hello, I am developing locally with an author instance only and it has always worked. But I think I deleted something in my instance and now it fails when I try to deploy the package. Is there any configuration to turn of deployment to publish? It looks strange that maven tries to deploy to http://localhost:4503/

It already tried a fresh AEM instance and it does also not work. I tried it for the last 4 hours and set everything up as far as I know.

Does the require a system user? I have deleted the user once and recreated it, but maybe I miss something.

Is there a maven or AEM config to solve this issue?

Thanks and regards!

[INFO] --- content-package-maven-plugin:0.0.23:install (install-package) @ test-com-relaunch.apps ---

[INFO] Installing test-com-relaunch.apps (C:\dev\projects\test\test-com-new\test-com-relaunch\apps\target\test-com-relaunch.apps-1.0.0-SNAPSHOT.zip) to http://localhost:4503/crx/packmgr/service.jsp [INFO] HttpMethodDirector - I/O exception (java.net.ConnectException) caught when processing request: Connection refused: connect

[INFO] HttpMethodDirector - Retrying request

[INFO] HttpMethodDirector - I/O exception (java.net.ConnectException) caught when processing request: Connection refused: connect

[INFO] HttpMethodDirector - Retrying request [INFO] HttpMethodDirector - I/O exception (java.net.ConnectException) caught when processing request: Connection refused: connect

[INFO] HttpMethodDirector - Retrying request

ERROR] Failed to execute goal com.day.jcr.vault:content-package-maven-plugin:0.0.23:install (install-package) on project test-com-relaunch.apps: Connection refused: connect -> [Help 1]

[tim-schwalbe-NZ · Accepted solution]

Okay I got it now. It was a wrong config in the parent pom...

[RamMeeran728687]

Could you please tell me what configuration has given in parent POM? I am also facing the same error. Thanks !!

[smacdonald2008]

See this -- it shows building an AEM Project successfully via Maven Archetype 13....

[White_clock]

In my case, though the pom.xml was a standard configuration, we had the proxy installed to pull in all dependencies, and so was not able to access the localhost/127.0.0.1 via the proxy. So did a small change in parent's pom.xml, where in I added <useProxy>false</useProxy> after the <targetURL> tag.