Skip to content
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

ui.tests (both cypress and wdio) throw errors with "install" or "deploy" phases #1172

Closed
kwin opened this issue Feb 21, 2024 · 2 comments · Fixed by #1179
Closed

ui.tests (both cypress and wdio) throw errors with "install" or "deploy" phases #1172

kwin opened this issue Feb 21, 2024 · 2 comments · Fixed by #1179

Comments

@kwin
Copy link
Contributor

kwin commented Feb 21, 2024

The modules at https://github.com/adobe/aem-project-archetype/blob/develop/src/main/archetype/ui.tests.cypress/pom.xml and https://github.com/adobe/aem-project-archetype/blob/develop/src/main/archetype/ui.tests.wdio/pom.xml have default packaging (=jar) but only build a secondary/attached artifact with the maven-archiver-plugin. That leads to issues with more recent versions of maven-install-plugin and maven-deploy-plugin (https://issues.apache.org/jira/browse/MINSTALL-118) failing the build with

The packaging plugin for this project did not assign a main file to the project but it has attachments. Change packaging to 'pom'

The packaging should be pom and also the tar.gz should only be conditionally created (in a profile only active in Cloud Manager), as for local execution with docker it is not used at all.

@buuhuu
Copy link
Contributor

buuhuu commented Mar 20, 2024

@dulvac something you could look into?

@dulvac
Copy link
Member

dulvac commented Mar 22, 2024

should only be conditionally created (in a profile only active in Cloud Manager)

@kwin, unfortunately I can't change the behaviour, but I will change the packaging

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants