[ 
https://issues.apache.org/jira/browse/MNG-6948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17147327#comment-17147327
 ] 

Robert Scholte commented on MNG-6948:
-------------------------------------

The issue is that Maven has always been using its own parser, just seeing it 
all as text. Now that Maven uses XMLFilters, you can get this error, but it is 
out of the users hands for repsotiory files.
It is just a symptom that too much files go through the filters. If you would 
have it in your own pom file, now you will see the error and you can fix it.


> Repository files should not pass build-filters
> ----------------------------------------------
>
>                 Key: MNG-6948
>                 URL: https://issues.apache.org/jira/browse/MNG-6948
>             Project: Maven
>          Issue Type: Improvement
>          Components: POM
>    Affects Versions: 3.7.0
>            Reporter: Robert Scholte
>            Assignee: Robert Scholte
>            Priority: Major
>
> When building Models, only reactor poms should go through the build xml 
> filters.
> If all poms go through it, there will be an unnecesary resource lost, and it 
> might introduce security issues, because not all pomsin the local repository 
> seem to be valid.
> One symptom is that once the poms are collected, you might see the following 
> line:
> {noformat}ERROR:  'The entity "oslash" was referenced, but not 
> declared.'{noformat}
> One of the poms with this issue is the {{org.codehaus.plexus:1.0.5:pom}}, 
> which contains:
> {code:xml}
> <developer>
>  <name>Trygve Laugst&oslash;l</name>
>  <id>trygvis</id>
>  <email>tryg...@codehaus.org</email>
>  <roles>
>  <role>Developer</role>
>  </roles>
>  </developer>
> {code}
> However, the &oslash; is not registered in the file.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to