You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The currently-implemented packaging configuration setting works on a per-module basis, but builds that use custom types extensively would benefit from the ability to configure this setting in one place.
The text was updated successfully, but these errors were encountered:
atomicknight
added a commit
to atomicknight/maven-jrebel-plugin
that referenced
this issue
May 12, 2016
This change adds a new 'packagingTypeMappings' configuration setting to
support mapping of custom packaging types to standard packaging types.
Example configuration:
<configuration>
<packagingTypeMappings>
<packagingTypeMapping>
<type>custom-jar</type>
<mapping>jar</mapping>
</packagingTypeMapping>
</packagingTypeMappings>
</configuration>
It would be nice if the plugin could support custom Maven packaging types via a mapping mechanism. For example,
maven-ear-plugin
provides a configuration setting for mapping custom types to known types: http://maven.apache.org/plugins/maven-ear-plugin/modules.html#Custom_Artifact_TypesThe currently-implemented
packaging
configuration setting works on a per-module basis, but builds that use custom types extensively would benefit from the ability to configure this setting in one place.The text was updated successfully, but these errors were encountered: