[MAGNOLIA-1910] unable to do a mvn -Dall=true -Pwith-optional-modules clean install as of rev. 13323 Created: 30/Nov/07  Updated: 03/Dec/07  Resolved: 03/Dec/07

Status: Closed
Project: Magnolia
Component/s: build
Affects Version/s: 3.5 RC2
Fix Version/s: None

Type: Improvement Priority: Major
Reporter: Tom Jensen Assignee: Magnolia International
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: 5m
Time Spent: Not Specified
Original Estimate: 5m

Issue Links:
dependency
relation
is related to DOCU-43 Document build process Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Date of First Response:

 Description   

Trying to build magnolia at rev. 13323 I get the following from maven:

[INFO] Scanning for projects...
Downloading: http://repo1.maven.org/maven2/info/magnolia/magnolia-project/3.5-rc2/magnolia-project-3.5-rc2.pom
[INFO] ------------------------------------------------------------------------
[ERROR] FATAL ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Failed to resolve artifact.

GroupId: info.magnolia
ArtifactId: magnolia-project
Version: 3.5-rc2

Reason: Unable to download the artifact from any repository

info.magnolia:magnolia-project:pom:3.5-rc2

from the specified remote repositories:
central (http://repo1.maven.org/maven2)

...

I don't understand maven but did some poking around and figured out how to add magnolia's maven repository as a mirror (in settings.xml) that fixed the problem so I could build, but I'd imagine no one else who is just doing a default install will be able to build; needs to be fixed in the appropriate pom.xml I guess?



 Comments   
Comment by Magnolia International [ 03/Dec/07 ]

Tom,

The DMS module has a separate lifecycle than the main Magnolia project. Hence, we won't change the dependencies back to snapshot after each release.
The current solutions for you are either:

  • change the dms' pom.xml locally (least preferred)
  • grab the main project's corresponding tag and build/install that to your local repo, at least the parent pom (mvn -N clean install from the root)
  • get the magnolia repositories in your settings.xml (subject to change in the coming weeks/month)
  • specify the repository from command line (can't find the specific parameters just now)
    The only clean/real solution will be:SYS-19
Generated at Mon Feb 12 03:31:31 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.