[
https://issues.apache.org/jira/browse/IVY-637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12553278
]
Gilles Scokart commented on IVY-637:
------------------------------------
One thing is sure, we need to store the result of the parsing into a temporary
structure before we can do anything (the properties comes at the end).
We have different choice for that :
1. Continue with SAX and write our own partial pom data model
2. Go for DOM
3. Use the maven-model (means adding a dependency)
I don't like 1.
I'm rather in favor of 2.
I have checked the maven-model. It is actually generated code that starts
from an XML description of the model. The problem is that the generated code
depends on plexus-utils. Which is I think something we want to avoid.
Note that the aproach 3 will could allow us to work around a problem that I
found recently : the maven pom are not all valid XML. But I would preffer to
fix that by asking maven people to make sure their pom are valid xml. (See
http://markmail.org/message/2sbfzptfl4bozq5u)
> m2 incompatibility - IVY does not recognize property section
> ------------------------------------------------------------
>
> Key: IVY-637
> URL: https://issues.apache.org/jira/browse/IVY-637
> Project: Ivy
> Issue Type: Bug
> Components: Core
> Affects Versions: 2.0.0-alpha-2
> Reporter: David Yuctan Hodge
> Priority: Critical
> Fix For: 2.0.0-beta-2
>
>
> Ivy does not recognize the property section for example
> http://repo1.maven.org/maven2/org/mortbay/jetty/project/6.1.5/project-6.1.5.pom
> This is related to IVY-636
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
