[BUILD-466] Issue on building a new war file Created: 17/May/21  Updated: 17/May/21  Resolved: 17/May/21

Status: Closed
Project: Build
Component/s: Build Resources
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Blocker
Reporter: Christian Balang Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: 1d
Time Spent: Not Specified
Original Estimate: 1d
Environment:

Developer Environment


Issue Links:
duplicate
Template:
Acceptance criteria:
Empty
Date of First Response:

 Description   

Steps to reproduce

  1.  On rebuilding the Magnolia application to have a new war file, encountered an issue below:

[INFO] ------------------------------------------------------------------------

[ERROR] Failed to execute goal on project mansion-webapp: Could not resolve dependencies for project com.mansion.cms:mansion-webapp:war:1.0-SNAPSHOT: Failed to collect dependencies at info.magnolia.dx:magnolia-dx-core-webapp:pom:6.2.3 -> info.magnolia.publishing:magnolia-publishing-transactional-core:jar:1.0.7: Failed to read artifact descriptor for info.magnolia.publishing:magnolia-publishing-transactional-core:jar:1.0.7: Failure to find info.magnolia.publishing:magnolia-publishing-parent:pom:1.0.9 in https://repo1.maven.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced -> [Help 1]

org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal on project mansion-webapp: Could not resolve dependencies for project com.mansion.cms:mansion-webapp:war:1.0-SNAPSHOT: Failed to collect dependencies at info.magnolia.dx:magnolia-dx-core-webapp:pom:6.2.3 -> info.magnolia.publishing:magnolia-publishing-transactional-core:jar:1.0.7

Expected results

Building of application must have no error to have a new war file. The new war file contains a new update to be deployed to our Dev Environment.



 Comments   
Comment by Mercedes Iruela [ 17/May/21 ]

Closed as duplicated

Generated at Sun Feb 11 23:42:09 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.