[
https://issues.apache.org/jira/browse/MNG-7114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17319496#comment-17319496
]
Andreas Sewe commented on MNG-7114:
-----------------------------------
{quote}
Can you observe the same behavior with regular dependencies, not plugins?
{quote}
Yes, the above output of the {{maven-dependency-plugin}} is for regular
dependencies, for example.
{quote}
Just to keep focus: this seems unrelated to the title of this issue, so better
discuss it in a separate ticket.
{quote}
Makes sense. So this ticket should probably focus on what's organizationally
more feasible:
# Produce a single (primary) JAR with all the various XSDs from different Maven
subprojects or
# Let each subproject produce secondary JARs for its XSDs only.
The latter would, at the moment, benefit from if not require the
{{<exclusion>}} workaround I described above, but I would compare the two
approaches primarily based on their organizational overhead only. But that's
just my 2 cents.
> 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)
