You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "ruel loehr (JIRA)" <ji...@codehaus.org> on 2006/03/16 00:41:32 UTC
[jira] Commented: (MNG-1954) Need better handling of malformed poms
in local cache, like check for an update every run
[ http://jira.codehaus.org/browse/MNG-1954?page=comments#action_61170 ]
ruel loehr commented on MNG-1954:
---------------------------------
Agreed, this is a problem. A user shouldn't have to wipe out things in his repo to get a pom update.
Another possible use case:
A user runs a maven build. He gets a dependency, foo.jar & foo.pom from the central repo. Now the user runs a different build for a different project, however this time the build uses a company internal repository. The internal build references foo.jar & foo.pom from the internal repo, but the internal repo's foo.pom has more information defined (e.g. a new transitive dependency, or license information) without which, the build will fail.
> Need better handling of malformed poms in local cache, like check for an update every run
> -----------------------------------------------------------------------------------------
>
> Key: MNG-1954
> URL: http://jira.codehaus.org/browse/MNG-1954
> Project: Maven 2
> Type: Improvement
> Components: Artifacts and Repositories
> Versions: 2.0
> Reporter: Steve Loughran
>
>
> If a pom has a typo in it, it is downloaded and parsed with a (misspelled) error message printed
> [m2:libraries] [WARNING] POM for 'org.hibernate:hibernate-tools:pom:3.1.0.beta2' is invalid. It will be ignored for artifact resolution. Reason: Parse error reading POM. Reason: expected > to finsh end tag not < from line 7 (position: TEXT seen ...</dependency>\r\n </dependencies\r\n<... @29:2)
> but if the pom is corrected in the source repository, the local system doesnt check for a change, it just goes with what is there.
> Invalid pom files should be remembered and replacements looked for, because there is no value in retaining them.
--
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