Rob McDougall created SLING-10061:
-------------------------------------
Summary: slingUrl configuration parameter is ignored during
install-bundle step
Key: SLING-10061
URL: https://issues.apache.org/jira/browse/SLING-10061
Project: Sling
Issue Type: Bug
Components: Maven Plugins and Archetypes
Affects Versions: Sling Maven Plugin 2.4.2, Sling Maven Plugin 2.4.0
Reporter: Rob McDougall
I have a pom.xml file with the following dependency in it:
{code:java}
<!-- Apache Sling Plugin -->
<plugin>
<groupId>org.apache.sling</groupId>
<artifactId>maven-sling-plugin</artifactId>
<version>2.3.8</version> <!-- Use 2.4.0 or later seems to cause the slingUrl
to be ignored. -->
<configuration>
<slingUrl>http://${aem.host}:${aem.port}/system/console</slingUrl>
<deploymentMethod>WebConsole</deploymentMethod>
</configuration>
</plugin>
{code}
${aem.host} is set to localhost and ${aem.port} is set to 4502.
It works fine when the version is set to 2.3.8 but when I moved to 2.4.0 or
2.4.2 I get the following message on the console:
{code:java}
[INFO] --- sling-maven-plugin:2.4.0:install (install-bundle) @ fluentforms.core
---
[INFO] Installing Bundle
com._4point.aem.fluentforms.core(C:\Users\Rob.McDougall\OneDrive - 4Point
Solutions Ltd\Documents\Eclipse FluentAPI
Workspace\fluentforms\core\target\fluentforms.core-0.0.2-SNAPSHOT.jar) to
http://localhost:8080/system/console via WebConsole
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 22.770 s
[INFO] Finished at: 2021-01-12T16:58:35-05:00
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal
org.apache.sling:sling-maven-plugin:2.4.0:install (install-bundle) on project
fluentforms.core: Installation on http://localhost:8080/system/console failed,
cause: Installation failed, cause: Not Found -> [Help 1]{code}
I have tried manipulating the value in <slingUrl> but the plugin appears to be
ignoring that setting completely and using the default value.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
