[ARCH-36] Add "fix" to workaround scope:import bug of Maven 2 Created: 21/Jul/14  Updated: 16/Dec/15  Resolved: 21/Jul/14

Status: Closed
Project: Archetypes
Component/s: None
Affects Version/s: None
Fix Version/s: 1.2.1

Type: Bug Priority: Neutral
Reporter: Magnolia International Assignee: Magnolia International
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
relates to ARCH-46 Update 'magnolia-project-archetype' Closed
relation
is related to ARCH-37 Maven 2 will import the incorrect dep... Closed
Template:
Patch included:
Yes
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)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled

 Description   

When building a project with the archetype, one needs to either:

  • use Maven 3 (which is probably fine, but we're still using m2 internally), or
  • have magnolia-project:pom and magnolia-ui-project:pom in their local maven repository, or
  • add
    <dependency>
      <groupId>info.magnolia</groupId>
      <artifactId>magnolia-project</artifactId>
      <version>${magnoliaVersion}</version>
      <type>pom</type>
      <scope>import</scope>
    </dependency>
    <dependency>
      <groupId>info.magnolia.ui</groupId>
      <artifactId>magnolia-ui-project</artifactId>
      <version>${magnoliaVersion}</version>
      <type>pom</type>
      <scope>import</scope>
    </dependency>
    

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