Hazenet
Enthusiast
Enthusiast

vRO Plugin Development - 'https://vro-server-fqdn:8281/vco-repo/archetype-catalog.xml' is not supported anymore

Jump to solution

I am trying to get started with learning vRO Plugin Development, and are have issues setting up my "dev-machine".

I have deployed a vRO Appliance version 7.3.0.21553 Build 5521409

I have a Windows Server 2012 R2, where I have installed JDK, JRE and Maven in the following locations:

C:\Java\jdk1.8.0_144

C:\Java\jre1.8.0_144

C:\Maven\apache-maven-3.5.0

I have added a User Environment Variable for %JAVA_HOME% pointing to "C:\Java\jdk1.8.0_144" and I have added "C:\Maven\apache-maven-3.5.0\bin" to the %PATH% System Enviroment Variable.

Going to my vRO Appliance's Development site, I get a instruction like this:

mvn archetype:generate -DarchetypeCatalog=https://vro-server-fqdn:8281/vco-repo/archetype-catalog.xml -DrepoUrl=https://vro-server-fqdn:8281/vco-repo -Dmaven.repo.remote=https://vro-server-fqdn:8281/vco-repo -Dmaven.wagon.http.ssl.insecure=true -Dmaven.wagon.http.ssl.allowall=true

I have created a work folder: C:\vROPluginDevelopment
Been in that folder while executing the above instruction from the vRO Appliance's Development site, results in this:

[ERROR] Failed to execute goal org.apache.maven.plugins:maven-archetype-plugin:3.0.1:generate (default-cli) on project standalone-pom: archetypeCatalog 'https://vro-server-fqdn:8281/vco-repo/archetype-catalog.xml' is not supported anymore. Please read the plugin documentation for details. -> [Help 1]

Anyone have an idea why this is happening?
The "plugin documentation" I have been able to find, does not include anything about this.

Tags (1)
0 Kudos
1 Solution

Accepted Solutions
iiliev
VMware Employee
VMware Employee

Hi,

You are hitting a controversial change in maven-archetype-plugin 3.x. Here are a couple of links on the topic, if you are interested:

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

http://mail-archives.apache.org/mod_mbox/maven-dev/201705.mbox/thread  (search for the thread 'The maven-archetype-plugin paradox')

TL;DR - the effect is that some parameters like archetypeCatalog don't work anymore with the latest version 3.x of this plug-in.

Perhaps the easiest workaround for now is to use a previous version of this plug-in. So, on the command line, instead of:

mvn archetype:generate <parameters>

you should use:

mvn org.apache.maven.plugins:maven-archetype-plugin:2.4:generate <parameters>

View solution in original post

0 Kudos
1 Reply
iiliev
VMware Employee
VMware Employee

Hi,

You are hitting a controversial change in maven-archetype-plugin 3.x. Here are a couple of links on the topic, if you are interested:

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

http://mail-archives.apache.org/mod_mbox/maven-dev/201705.mbox/thread  (search for the thread 'The maven-archetype-plugin paradox')

TL;DR - the effect is that some parameters like archetypeCatalog don't work anymore with the latest version 3.x of this plug-in.

Perhaps the easiest workaround for now is to use a previous version of this plug-in. So, on the command line, instead of:

mvn archetype:generate <parameters>

you should use:

mvn org.apache.maven.plugins:maven-archetype-plugin:2.4:generate <parameters>

0 Kudos