It's not pulling down the latest version of archetype published in a remote server when using JBDS maven plugin.

Solution Verified - Updated -

Issue

When using RELEASE in local archetype catalog (archetype-catalog.xml) JBDS doesn't pull down the latest release version of our archetypes unless the maven local repository is deleted first. If stand alone maven commands are used it works fine without having to delete from local repository.

Environment

  • JBoss Developer Studio(JBDS)

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content