You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 11, 2024. It is now read-only.
When trying to generate the mobile sdk for a DXP server, I've checked out the tags/builder-7.1.0 from your repo, run the ./gradlew createModule -P=all --console plain --no-daemon
input the data requested
executed gradlew generate and gradlew jar
I've dived in the files, and found that settings.gradle had include "modules/${module.name}" which I promptly changed into include "modules:${module.name}"
I re-ran gradlew generate and now I get
Task 'generate' not found in project ':modules:mcdrp'.
I deleted the (empty) generated modules and started from scratch with ./gradlew createModule -P=all --console plain --no-daemon and got
Execution failed for task ':createModule'.
Could not normalize path for file 'C:\Dev\liferay-mobile-sdk:modules:mcdrp'.
Can you provide some insight, please?
The text was updated successfully, but these errors were encountered:
frangeveris
changed the title
Issue with "/"
Using "/" in 'modules/$context' is deprecated in Gradle
Nov 4, 2020
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
When trying to generate the mobile sdk for a DXP server, I've checked out the tags/builder-7.1.0 from your repo, run the
./gradlew createModule -P=all --console plain --no-daemon
input the data requested
executed
gradlew generate
andgradlew jar
What I get is
I've dived in the files, and found that settings.gradle had
include "modules/${module.name}"
which I promptly changed intoinclude "modules:${module.name}"
I re-ran
gradlew generate
and now I getI deleted the (empty) generated modules and started from scratch with
./gradlew createModule -P=all --console plain --no-daemon
and gotCan you provide some insight, please?
The text was updated successfully, but these errors were encountered: