[
https://issues.apache.org/jira/browse/SLING-3681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14051225#comment-14051225
]
Robert Munteanu edited comment on SLING-3681 at 7/3/14 10:01 AM:
-----------------------------------------------------------------
(Sorry, this dropped off my radar). I looked at what the Jackrabbit project
does, and they have a top-level /dtd/ directory -
https://jackrabbit.apache.org/dtd/ . I would incline to follow the same route
and use https://sling.apache.org/xsd/bundle-list-1.0.0.xsd . The reasons would
be
* it's not really a Maven artifact, but an xsd file, so maven -> xsd
* prefixing it with the version does not add much, and for instance
bundle-list-1.0.0.xsd with some-other-file-1.0.0.xsd have no relation but the
version.
WDYT?
was (Author: rombert):
(Sorry, this dropped on my radar). I looked at what the Jackrabbit project
does, and they have a top-level /dtd/ directory -
https://jackrabbit.apache.org/dtd/ . I would incline to follow the same route
and use https://sling.apache.org/xsd/bundle-list-1.0.0.xsd . The reasons would
be
* it's not really a Maven artifact, but an xsd file, so maven -> xsd
* prefixing it with the version does not add much, and for instance
bundle-list-1.0.0.xsd with some-other-file-1.0.0.xsd have no relation but the
version.
WDYT?
> Enable the maven-launchpad-plugin to generate the XSD for bundles list XML
> document
> -----------------------------------------------------------------------------------
>
> Key: SLING-3681
> URL: https://issues.apache.org/jira/browse/SLING-3681
> Project: Sling
> Issue Type: Improvement
> Components: Maven Plugins and Archetypes
> Affects Versions: Maven Launchpad Plugin 2.3.2
> Reporter: Simone Tripodi
> Assignee: Robert Munteanu
> Fix For: Maven Launchpad Plugin 2.3.2
>
> Attachments: SLING-3681.patch, Screen Shot 2014-06-19 at 11.05.11.pdf
>
>
> More recent versions of the Modello plugin for Maven is able to generate the
> model's XSchema that, once published on Sling's public site and declared in
> {{list.xml}} documents, would be really useful in "intelligent" IDEs able to
> read the schema, understand the structure and assist users for content
> creation, otherwise it is not clear at all which elements are allowed and
> which not.
> Patch going to be submitted!
--
This message was sent by Atlassian JIRA
(v6.2#6252)
