[BUILD-301] Project info reports resolves non-existing artifacts for dependencyManagement Created: 07/May/18 Updated: 21/May/18 Resolved: 16/May/18 |
|
| Status: | Closed |
| Project: | Build |
| Component/s: | Poms |
| Affects Version/s: | BOM 5.6.4 |
| Fix Version/s: | BOM 5.6.5, BOM 5.7 |
| Type: | Bug | Priority: | Major |
| Reporter: | Evzen Fochr | Assignee: | Dai Ha |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | jbpm, maven | ||
| Remaining Estimate: | 0d | ||
| Time Spent: | 1.75d | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||||||
| Issue Links: |
|
||||||||
| Template: |
|
||||||||
| Acceptance criteria: |
Empty
|
||||||||
| Date of First Response: | |||||||||
| Sprint: | Saigon 145 | ||||||||
| Story Points: | 8 | ||||||||
| Description |
|
Releasing sites is extremely slow; it took around 3 hours for UI. Maybe it is connected with: [INFO] Generating "Dependency Management" report --- maven-project-info-reports-plugin:2.9:dependency-management [WARNING] Unable to create Maven project for org.drools:drools-wb-categories-editor-client:pom:6.4.0.Final from repository. org.apache.maven.project.ProjectBuildingException: Error resolving project artifact: Failure to find org.drools:drools-wb-categories-editor-client:pom:6.4.0.Final in https://nexus.magnolia-cms.com/content/groups/staff was cached in the local repository, resolution will not be reattempted until the update interval of magnolia.nexus has elapsed or updates are forced for project org.drools:drools-wb-categories-editor-client:pom:6.4.0.Final at org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:351) at org.apache.maven.project.DefaultMavenProjectBuilder.buildFromRepository(DefaultMavenProjectBuilder.java:236) at org.apache.maven.project.DefaultMavenProjectBuilder.buildFromRepository(DefaultMavenProjectBuilder.java:251) at org.apache.maven.report.projectinfo.dependencies.RepositoryUtils.getMavenProjectFromRepository(RepositoryUtils.java:298) |
| Comments |
| Comment by Mikaël Geljić [ 07/May/18 ] |
|
This happens everywhere the Magnolia BOM 5.6.4 is used (dam, UI), because we started importing the jBPM, Drools, and KIE BOMs. These BOMs contain obsolete/missing artifacts which they apparently dropped releasing over time (even in latest version 7.sth, they are still managed, so it doesn't look like they're keen on removing those). This can be reproduced simply with: mvn project-info-reports:dependency-management Consequence is "just" a huge waste of time and amount of stack traces when generating reports. Missing artifacts in 6.4.0.Final are: org.drools drools-wb-categories-editor-client pom 6.4.0.Final org.drools drools-wb-webapp pom 6.4.0.Final org.jbpm jbpm-console-ng-distribution-wars pom 6.4.0.Final org.kie kie-drools-wb-home-page-product pom 6.4.0.Final org.kie kie-wb-distribution-home-api pom 6.4.0.Final org.kie kie-wb-distribution-home-client pom 6.4.0.Final org.kie kie-wb-home-page-product pom 6.4.0.Final org.kie.remote.ws kie-remote-ws-wsdl-cmd pom 6.4.0.Final org.kie.server kie-server-ws pom 6.4.0.Final |
| Comment by Mikaël Geljić [ 07/May/18 ] |
|
As for potential solutions: A. Exclusions: I'm not too keen on excluding these one by one, as within next upgrade there might be new ones popping up; but maybe we can find a few good wildcards for it. B. Hoping for ways to disable artifact resolution for the dependency-management report (like I also wish this report remained scoped to the dependencies which are actually used within the project. C. Disable/drop the dependency-management report. D. Revert the BOM imports from jBPM |
| Comment by Dai Ha [ 11/May/18 ] |
|
Tried maven-project-info-reports-plugin 3.0.0-SNAPSHOT with both options <dependencyLocationsEnabled>false</dependencyLocationsEnabled> <dependencyDetailsEnabled>false</dependencyDetailsEnabled> artifact resolving still happens and problem still there. |
| Comment by Mikaël Geljić [ 11/May/18 ] |
|
|