[
https://issues.apache.org/jira/browse/MWAR-406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15983369#comment-15983369
]
Jimmy Praet commented on MWAR-406:
----------------------------------
These artifacts have type "xsd" or "wsdl", but are packaged as zip files.
components.xml
{code}
...
<component>
<role>org.apache.maven.artifact.handler.ArtifactHandler</role>
<role-hint>wsdl</role-hint>
<implementation>org.apache.maven.artifact.handler.DefaultArtifactHandler</implementation>
<configuration>
<type>wsdl</type>
<extension>zip</extension>
<language>java</language>
<addedToClasspath>true</addedToClasspath>
</configuration>
</component>
...
{code}
But you make a very good point as it turns out that the servlet spec only talks
about jar files in the WEB-INF/lib directory. I just tested it and indeed, it
doesn't work even when I put these zip files manually in the WEB-INF/lib folder.
However, if I were to change the components.xml to package these artifacts as
jar, then the maven-war-plugin will still not copy them to the WEB-INF/lib.
That's because it checks the artifact type, not the file extension.
> custom artifact types don't get copied to WEB-INF/lib
> -----------------------------------------------------
>
> Key: MWAR-406
> URL: https://issues.apache.org/jira/browse/MWAR-406
> Project: Maven WAR Plugin
> Issue Type: Improvement
> Affects Versions: 3.0.0
> Reporter: Jimmy Praet
>
> We are attempting to switch our projects over from ejb+ear packaging to war
> packaging. But we have a series of custom maven artifact types (e.g. xsd,
> wsdl), and these don't get copied to the WEB-INF/lib folder.
> For the maven-ear-plugin there was the option to configure [custom artifact
> types|http://maven.apache.org/plugins/maven-ear-plugin/modules.html#Custom_Artifact_Types].
> It doesn't look like such a thing exists for the maven-war-plugin?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
