Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

Don_Edwards
Community profile Don_Edwards Level 1
Job title here
Location here
1 BADGE
Level 1

Level 1

Learn more
Joined the community 30-05-2017 5:38:14 AM
Offline
Top badges earned by Don_Edwards
Customize the badges you want to showcase on your profile
Re: maven clean install command failure
Avatar
Boost 1
Level 1
Don_Edwards
Level 1

Likes

2 likes

Total Posts

5 posts

Correct reply

0 solutions
Top badges earned
Boost 1
View profile
Don_Edwards
- Adobe Experience Manager
SOLVED --> I had a feeling the issue was related to my Macbook environment and it was... it turned out to be a setting in my /etc/hosts where the IP that "localhost" pointed to was modified (for other reasons not related to AEM), so when mvn tried to connect to packageMgr via http://${aem.host}:${aem.port}/crx/packmgr/service.jsp, it timed out!

Views

998

Likes

2

Replies

1
Re: maven clean install command failure
Avatar
Boost 1
Level 1
Don_Edwards
Level 1

Likes

2 likes

Total Posts

5 posts

Correct reply

0 solutions
Top badges earned
Boost 1
View profile
Don_Edwards
- Adobe Experience Manager
Unfortunately, I was mistaken yesterday when I said it worked! I inadvertently executed, "mvn clean install" and that worked. The command, "mvn -PautoInstallPackage clean install -DskipTests -Padobe-public" did NOT work...so any suggestions on how to resolve this are appreciated!

Views

998

Likes

0

Replies

2
Re: maven clean install command failure
Avatar
Boost 1
Level 1
Don_Edwards
Level 1

Likes

2 likes

Total Posts

5 posts

Correct reply

0 solutions
Top badges earned
Boost 1
View profile
Don_Edwards
- Adobe Experience Manager
On a whim I decided to install acs-commons and was surprised to see it succeed, so I thought I'd retry installing my xxx project and it worked. I'm not sure why installing acs-commons made my other projects successful (since I was following Creating an Adobe Experience Manager 6.4 Project using Adobe Maven Archetype 13 and there was no mention of acs-commons)...My 6.4.4 AEM instance was a fresh install so maybe there's something in ACS commons that was required...whatever, it worked for me.

Views

998

Likes

0

Replies

4
Re: maven clean install command failure
Avatar
Boost 1
Level 1
Don_Edwards
Level 1

Likes

2 likes

Total Posts

5 posts

Correct reply

0 solutions
Top badges earned
Boost 1
View profile
Don_Edwards
- Adobe Experience Manager
Thanks for the reply but there's nothing showing up in the logs when i execute the mvn cmd, and I checked all of logs (error, request, stdout, access, etc.). One more thing, the curl cmd works and installs the package (but of course this isn't the way we want it to work):curl -u admin:admin -F file=@"/Users/donald.edwards/git/aem/xxxx/ui.apps/target/xxxx-commons.ui.apps-1.0-SNAPSHOT.zip" -F name="xxxx-commons.ui.apps" -F force=true -F install=true http://localhost:4502/crx/packmgr/service.jsp

Views

998

Likes

0

Replies

5
Re: maven clean install command failure
Avatar
Boost 1
Level 1
Don_Edwards
Level 1

Likes

2 likes

Total Posts

5 posts

Correct reply

0 solutions
Top badges earned
Boost 1
View profile
Don_Edwards
- Adobe Experience Manager
I have been battling this error for 2 days. I'm on AEM v6.4.4, mvn 3.6.1 and tried also tried 3.3.9. I even tried building different projects as well, one using newly created archetype (Creating an Adobe Experience Manager 6.4 Project using Adobe Maven Archetype 13 ), I'm using version 0.0.24 of the content-package-maven-plugin (even tried other versions, e.g. 0.0.51.). The -X reveals:[DEBUG] Set parameter http.authentication.preemptive = true[DEBUG] Proxying disabled (useProxy=true) or no proxi...

Views

998

Likes

0

Replies

7
Likes from