You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Trygve Laugstol (JIRA)" <ji...@codehaus.org> on 2007/02/12 09:03:21 UTC

[jira] Commented: (MNG-2816) Pom without xsd import is not validated

    [ http://jira.codehaus.org/browse/MNG-2816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_87339 ] 

Trygve Laugstol commented on MNG-2816:
--------------------------------------

This is a feature, not a bug! ;)

Maven doesn't use the schemas to validate in any case, and in addition it allows any element as a way to be flexible so that other tools can add extenstions without breaking maven.

> Pom without xsd import is not validated
> ---------------------------------------
>
>                 Key: MNG-2816
>                 URL: http://jira.codehaus.org/browse/MNG-2816
>             Project: Maven 2
>          Issue Type: Improvement
>          Components: Bootstrap & Build
>    Affects Versions: 2.0.4
>            Reporter: Kristoffer Moum
>
> I added a dependency to a module a couple of days ago. I did it just a tad too quickly (copy and paste from dependency management), and forgot to enclose with the dependency tag, i.e. I had the following structure:
> <dependencies>
>   <groupId>org.springframework</groupId>
>   <artifactId>spring-web</artifactId>
> </dependencies>
> So - what happened when I did an "mvn install" the dependency was ignored rather than producing an error message as the pom was actually valid xml. It would be nice to have some defaulting of xsd if none was specified.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira