Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://github.com/pmd/pmd/issues/4736 below:

[ci] Improve build procedure · Issue #4736 · pmd/pmd · GitHub

With the latest changes introduced in #4700 we have now the following problems:

1. Release build failed (https://github.com/pmd/pmd/actions/runs/6363796662): couldn't determine version via mvn (https://github.com/pmd/build-tools/blob/9ae35886e103e0821d345668f61325eddb402a4d/scripts/inc/maven.bash#L39-L41) because inconsistent pom:

[ERROR] Some problems were encountered while processing the POMs:
[FATAL] Non-resolvable parent POM for net.sourceforge.pmd:pmd-cli:7.0.0-SNAPSHOT: The following artifacts could not be resolved: net.sourceforge.pmd:pmd:pom:7.0.0-SNAPSHOT (absent): Could not find artifact net.sourceforge.pmd:pmd:pom:7.0.0-SNAPSHOT and 'parent.relativePath' points at wrong local POM @ line 7, column 13
[FATAL] Non-resolvable parent POM for net.sourceforge.pmd:pmd-dist:7.0.0-SNAPSHOT: The following artifacts could not be resolved: net.sourceforge.pmd:pmd:pom:7.0.0-SNAPSHOT (absent): Could not find artifact net.sourceforge.pmd:pmd:pom:7.0.0-SNAPSHOT and 'parent.relativePath' points at wrong local POM @ line 8, column 13
@ 
Error:  The build could not read 2 projects -> [Help 1]
Error:    
Error:    The project net.sourceforge.pmd:pmd-cli:7.0.0-SNAPSHOT (/Users/runner/work/pmd/pmd/pmd-cli/pom.xml) has 1 error
Error:      Non-resolvable parent POM for net.sourceforge.pmd:pmd-cli:7.0.0-SNAPSHOT: The following artifacts could not be resolved: net.sourceforge.pmd:pmd:pom:7.0.0-SNAPSHOT (absent): Could not find artifact net.sourceforge.pmd:pmd:pom:7.0.0-SNAPSHOT and 'parent.relativePath' points at wrong local POM @ line 7, column 13 -> [Help 2]
Error:    
Error:    The project net.sourceforge.pmd:pmd-dist:7.0.0-SNAPSHOT (/Users/runner/work/pmd/pmd/pmd-dist/pom.xml) has 1 error
Error:      Non-resolvable parent POM for net.sourceforge.pmd:pmd-dist:7.0.0-SNAPSHOT: The following artifacts could not be resolved: net.sourceforge.pmd:pmd:pom:7.0.0-SNAPSHOT (absent): Could not find artifact net.sourceforge.pmd:pmd:pom:7.0.0-SNAPSHOT and 'parent.relativePath' points at wrong local POM @ line 8, column 13 -> [Help 2]
Error:  
Error:  To see the full stack trace of the errors, re-run Maven with the -e switch.
Error:  Re-run Maven using the -X switch to enable full debug logging.
Error:  
Error:  For more information about the errors and possible solutions, please read the following articles:
Error:  [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException
Error:  [Help 2] http://cwiki.apache.org/confluence/display/MAVEN/UnresolvableModelException

That made the build on github fail pretty fast.

1. The 2nd stage build also failed (https://github.com/pmd/pmd/actions/runs/6364543855)
   artifacts were not signed because I forgot to add the correct profile and therfore maven-gpg-plugin was not executed.
   Already fixed in 70e2564

2. cli and dist are not included anymore in reproducible builds: https://github.com/jvm-repo-rebuild/reproducible-central/blob/master/content/net/sourceforge/pmd/README.md
   with rc3 we had 125 artifacts, with rc4 only 118
   missing is: pmd-cli pom/jar/sources/completion and pmd-dist pom/jar/sources
   note: the completion script is for some reason not reproducible, the parameters are generated sometimes in a different order
   -> https://github.com/jvm-repo-rebuild/reproducible-central/blob/master/content/net/sourceforge/pmd/pmd-7.0.0-rc3.diffoscope
   -> but that's anyway removed (see [java] Make LawOfDemeter results deterministic #4549)
   I've manually tested reproducibility of rc4 including cli/dist: Building from tag 7.0.0-rc4-dist and enabling profile cli-dist -> still works ✔️

3. local build: make sure to enable profile "cli-dist"... (if you have activeProfiles in your settings.xml...)
   -> https://stackoverflow.com/questions/5309379/how-to-keep-maven-profiles-which-are-activebydefault-active-even-if-another-prof
   I didn't build these projects for a while locally, because I have generate-rule-docs activated via settings.xml, so
   all activeByDefault profile are not active...
   See also PMD not building PMD-CLI and PMD-Distribution packages #4735

• have profile "cli-dist" active always and deactivate it with -Dskip-cli-dist
  • should fix the determine_project_version problem and PMD not building PMD-CLI and PMD-Distribution packages #4735
  • should fix regression tester not finding the pmd-dist-bin zip file. Fixed now by 1ac1bde
• Update version of all projects immediately
  • maybe can't use maven-release-plugin:prepare? because the project now references a non-existing pmd-designer version, so maven-release-plugin won't be able to test-build the project
  • need to manually enforce no snapshot dependencies
  • need to manually perform a test-build
  • should fix the determine_project_info problem
• only one tag 7.0.0-rc4 and no 7.0.0-rc4-dist
• Instead of pushing a second tag, trigger the build workflow manually via "workflow_dispatch" with a parameter (https://docs.github.com/en/actions/using-workflows/triggering-a-workflow#defining-inputs-for-manually-triggered-workflows). The parameters says e.g. "build cli-dist and publish release".
  -> https://github.com/pmd/pmd/actions/workflows/build.yml - see button "Run workflow"

• [ci] Introduce a two-step release process #4700
• Circular dependencies between pmd-designer, pmd-core, pmd-cli #4446
• PMD not building PMD-CLI and PMD-Distribution packages #4735

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4