-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Package Overlaps #11
Comments
Any update on this |
Closed
You should consider switching to the maintained fork at https://github.com/orbinson/aem-groovy-console/tree/main which has this issue (and several others) fixed. |
Switching to version 19.0.4 of be.orbinson.aem is fixing the package
overlaps issue
…On Wed, 10 Jan 2024 at 10:39, Narendiran100 ***@***.***> wrote:
Any update on this
—
Reply to this email directly, view it on GitHub
<#11 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AEF4F5NYD7MINR3U4OXXUBDYNZHTPAVCNFSM5Y2Q3EUKU5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TCOBYGQ2DANRZGIZA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Fixed in 18.0.0 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello,
We are using groovy console version 17.0.0 on AEM as a Cloud Service.
The pipeline execution includes some code scanning and one of its findings is this one:
File: org.cid15.aem.groovy.console:aem-groovy-console-ui.config:17.0.0
Issue: affected path /apps/groovyconsole/osgiconfig overlaps [aem-groovy-console:aem-groovy-console-ui.apps:17.0.0]
Adobe rule Package Overlaps is explained here https://experienceleague.adobe.com/docs/experience-manager-cloud-manager/using/how-to-use/custom-code-quality-rules.html?lang=en#oakpal-no-overlap (https://www.adobe.com/go/aem_cmcq_packageoverlaps_en)
In summary two packages aem-groovy-console-ui.config and aem-groovy-console-ui.apps are both writing to /apps/groovyconsole/osgiconfig. That should not happen.
Is is possible that this is fixed in some of the upcoming releases?
The text was updated successfully, but these errors were encountered: