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

Releasing ACS AEM Commons fails due to a several POM configurations #2137

Closed
davidjgonzalez opened this issue Dec 18, 2019 · 4 comments
Closed
Milestone

Comments

@davidjgonzalez
Copy link
Contributor

Required Information

The release of 4.4.0 kept failing:

  • Unit test case randomly fail (but work when executed directly) - appears to be due to the updated multi-thread count config
  • RetireJS dependency check fails
  • Javadocs generation failure

It appears there were a number of changes made to the POMs of late which are causing these issues.

@joerghoh
Copy link
Contributor

I had these randomly failing unittests a few times during the migration to the new mockito version as documented in #2104, but I was able to fix that by tweaks on surefire [1]. I am also not aware of failed builds since then.

Can you share your "mvn -version" output?

[1] f255545

@davidjgonzalez
Copy link
Contributor Author

@joerghoh

Apache Maven 3.6.3 (cecedd343002696d0abb50b32b541b8a6ba2883f)
Maven home: /usr/local/Cellar/maven/3.6.3/libexec
Java version: 11.0.4, vendor: Oracle Corporation, runtime: /Library/Java/JavaVirtualMachines/jdk-11.0.4.jdk/Contents/Home
Default locale: en_US, platform encoding: UTF-8
OS name: "mac os x", version: "10.15", arch: "x86_64", family: "Mac"

Can you successfully perform a dry-run of maven release prepare/perform? My setup hasn't changed and this worked fine from the last release I did.

@joerghoh
Copy link
Contributor

joerghoh commented Dec 30, 2019

A first run was ok (as expected)

[INFO] Executing completion goals - since this is simulation mode it is running against the original project, not the rewritten ones
[INFO] Full run would be commit 6 files with message: '[maven-release-plugin] prepare for next development iteration'
[INFO] Release preparation simulation complete.
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary for ACS AEM Commons - Reactor Project 4.4.1-SNAPSHOT:
[INFO]
[INFO] ACS AEM Commons - Reactor Project .................. SUCCESS [03:44 min]
[INFO] ACS AEM Commons Bundle ............................. SKIPPED
[INFO] ACS AEM Commons Oakpal Checks ...................... SKIPPED
[INFO] ACS AEM Commons UI.Apps Package .................... SKIPPED
[INFO] ACS AEM Commons UI.Content Package ................. SKIPPED
[INFO] ACS AEM Commons Package ............................ SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  03:45 min
[INFO] Finished at: 2019-12-30T20:35:42+01:00
[INFO] ------------------------------------------------------------------------

I was using

Apache Maven 3.6.2 (SUSE 3.6.2-1.1)
Maven home: /usr/share/maven
Java version: 11.0.5, vendor: Oracle Corporation, runtime: /usr/lib64/jvm/java-11-openjdk-11
Default locale: de_DE, platform encoding: UTF-8
OS name: "linux", version: "5.3.12-2-default", arch: "amd64", family: "unix"

not exactly the Java you were using, but close enough.

If you run mvn clean test do you get the same problems as in the release process?

@stale
Copy link

stale bot commented Feb 28, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the wontfix label Feb 28, 2020
@davidjgonzalez davidjgonzalez unpinned this issue Mar 25, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants