Graham, There have been some recent discussions over on the mojo-dev list regarding JBoss packagings and how best to implement them in the jboss-packaging-maven-plugin. Specifically, the very issue you note (name clashing) did come up, thought dismissed as a very unlikely use case.
One thought that surfaced is to use classifiers in situations where the file extension is insufficient. eg., bar-artifact-1.0.0-ejb.jar or foo-artifact-1.0.0-jboss.har, just like the sources plugin does. I'm working on some patches to the jboss-packaging-maven-plugin, so chime in if you have any suggestions. Doug On 8/1/06, Graham Leggett <[EMAIL PROTECTED]> wrote:
Stephane Nicoll wrote: >> Embedded error: Unknown artifact type[har] >> >> Looking in the docs, the configuration option "artifactTypeMappings" >> seems >> to offer a clue, but apart from the text "PlexusConfiguration", there is >> no indication what needs to be done to get this to work, or whether this >> option does I what I think it might do. > > Well, it does [1]. > > <configuration> > <artifactTypeMappings> > <artifactTypeMapping type="har" mapping="jar"/> > </artifactTypeMappings> > </configuration> This option won't work for us, as the project that creates the har file, already creates an ejb mapped to a jar file, which creates a filename clash. Ideally the ear plugin shouldn't try to know about every single file extension ever made, because invariably someone (in this case JBoss) invents a new one, and the ear plugin stops working. A sane default would be to assume the suffix maps to the type for files that are not recognised. Regards, Graham --
