[ 
https://jira.codehaus.org/browse/MPLUGIN-248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=329055#comment-329055
 ] 

Mirko Friedenhagen commented on MPLUGIN-248:
--------------------------------------------

Hervé, the Maven site still shows it wrong, so probably it has to be 
regenerated?
                
> XML-Namespace in ITs for ant-based mojos are wrong.
> ---------------------------------------------------
>
>                 Key: MPLUGIN-248
>                 URL: https://jira.codehaus.org/browse/MPLUGIN-248
>             Project: Maven 2.x Plugin Tools
>          Issue Type: Bug
>          Components: maven-plugin-tools-ant
>    Affects Versions: 3.2
>         Environment: git-svn-id: 
> https://svn.apache.org/repos/asf/maven/plugin-tools/trunk@1470122 
> 13f79535-47bb-0310-9956-ffa450edef68
>            Reporter: Mirko Friedenhagen
>            Assignee: Herve Boutemy
>             Fix For: 3.3
>
>         Attachments: MPLUGIN-248.patch
>
>
> Example error:
> {code}
> [mifr@LMKA-2HPPHFDTY3 maven-plugin-tools]$ xmllint --schema 
> http://maven.apache.org/xsd/plugin-metadata-1.0.0.xsd 
> maven-plugin-plugin/src/it/ant-basic/src/main/scripts/touch.mojos.xml  > 
> /dev/null
> maven-plugin-plugin/src/it/ant-basic/src/main/scripts/touch.mojos.xml:23: 
> element pluginMetadata: Schemas validity error : Element 
> '{http://maven.apache.org/POM/4.0.0}pluginMetadata': No matching global 
> declaration available for the validation root.
> maven-plugin-plugin/src/it/ant-basic/src/main/scripts/touch.mojos.xml fails 
> to validate
> {code}
> While Maven seems not choke on this, XML support in IDEs is broken because of 
> this. I consider this major because the documentation 
> (http://maven.apache.org/plugin-tools/maven-plugin-plugin/examples/ant-mojo.html)
>  just references the ITs and all the examples therefore are broken for users. 
> I will submit a patch and Github-Pull request for this.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to