0
votes

I try to migrate from a legacy Ivy repository to a Maven self hosted instance (Artifactory) using Maven 2 compatible format. The legacy Ivy artifacts make use of all attributes that Ivy supports, to name it: "configuration (conf)", "extension (ext)", "type" and "name".

I can map most attributes to equivalents in Maven:

  • "conf" -> "scope"
  • "name" -> "artifactId"
  • "ext" -> "packaging"
  • "organization" -> "groupId"
  • "revision" -> "modelVersion"

But for "type" there no attribute left in the Maven artifact. The primary use of the "type" attribute is to control the artifacts deployment (where and how to deploy them).

I noticed that the Maven artifacts do not support "custom" attributes. So how could I store the "type" information in a standard conform way?

1

1 Answers

0
votes

Taken from the ivy documentation

the type of the published artifact. It's usually its extension, but not necessarily. For instance, ivy files are of type 'ivy' but have 'xml' extension

Unless specified the "type" of an artifact defaults to jar.

Update

Maven supports different types of module artifact using classifiers. This can be emulated in ivy using extra attributes.

Examples: