Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
1.1
-
Security Level: public (Regular issues)
-
None
Description
Currently the <pattern> used in the naming schema includes group, artifact, and version, but not type. In ENCConfigBuilder.buildAbstractNameQuery, the type is hardcoded to "car". This means that if you use a naming:pattern with an artifactId, it only works if the target module's type is actually "car". This is not true, for example, for several module types created by the admin console, as well as in general for user-defined modules.
The naming:pattern element should include a "type" element, and ENCConfigBuilder (and any other necessary code) should respect it.