[
https://issues.apache.org/jira/browse/MNG-7114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17300413#comment-17300413
]
Andreas Sewe commented on MNG-7114:
-----------------------------------
{quote}Would it be sufficient to bundle the XSD in the JAR's META-INF/xsd and
you'd add the JARs as dependencies?
{quote}
Depends on the JAR. If you mean putting {{archetype-descriptor-1.1.0.xsd}} into
the {{META-INF/xsd}} of, say,
{{org.apache.maven.archetype:archetype-descriptor}}, then I would be oppoosed
to it, as that would "pollute" the classpath of the consuming plug-in with
{{org.apache.maven.archetype:archetype-descriptor}} and its dependencies.
For plug-ins like the {{xml-maven-plugin}} adding stuff to the classpath just
increases the risk of conflicts; you are likely adding plugin dependencies for
your XSLT or Schematron processor already, and the more (transitive)
dependencies, the higher the risk (too bad that Maven doesn't allow
{{<execution>}}-level {{<dependencies>}}, which would reduce the risk somewhat).
So, whatever artifact the XSDs go into, it should not have any (code)
dependencies of its own. Does that make sense?
> Publish XSDs as artifact to Central
> -----------------------------------
>
> Key: MNG-7114
> URL: https://issues.apache.org/jira/browse/MNG-7114
> Project: Maven
> Issue Type: Improvement
> Reporter: Andreas Sewe
> Priority: Minor
>
> At the moment, a number of XML Schema files for descriptor-like file formats
> like archetype or assembly descriptors are only available at
> [https://maven.apache.org/xsd/].
> This makes them hard to consume, for example, by the {{xml:validate}} goal,
> which is IMHO quite well suited for sanity-checking your descriptor files
> before packaging and subsequently releasing them.
> Would it be possible to release the XSDs under {{org.apache.maven:maven-xsd}}
> or a similar coordinate?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
