[DOCU-940] Update mvn archetype command - due to Maven archetype plugin regression Created: 14/Feb/17  Updated: 03/Jul/17  Resolved: 15/Feb/17

Status: Closed
Project: Documentation
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Neutral
Reporter: Espen Jervidalo Assignee: Christoph Meier
Resolution: Done Votes: 0
Labels: core
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
causality
Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Date of First Response:

 Description   

A new version of the Maven archetype plugin has been released, which seems to have introduced a regression.
To get Magnolia's archetypes resolved properly the following command needs to change ...

From:

mvn archetype:generate -DarchetypeCatalog=https://nexus.magnolia-cms.com/content/groups/public/

To:

mvn org.apache.maven.plugins:maven-archetype-plugin:2.4:generate -DarchetypeCatalog=https://nexus.magnolia-cms.com/content/groups/public/

Affected pages



 Comments   
Comment by Christoph Meier [ 15/Feb/17 ]

ejervidalo - thanks for the heads-up. I have edited it according to your "proposal". And, yes it works.

Do we know when the "workaround" can be removed? Waiting for the next version of the Maven archetype plugin?

Comment by Christoph Meier [ 15/Feb/17 ]

Since the command was used on many pages, i have moved the command to an "includable junk" page
=> https://wiki.magnolia-cms.com/display/INCL/_mvn+archetype+command
Then i was just including the page on the affected pages.

If the Maven artifact plugin is fixed, we just have to change the _mvn archetype command

Comment by Espen Jervidalo [ 15/Feb/17 ]

Hey, there's a ticket created by pmundt which we have to keep an eye on. Let's hope they revert it back to the command line argument.

https://issues.apache.org/jira/browse/ARCHETYPE-519

Generated at Mon Feb 12 01:13:42 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.