[ 
http://jira.codehaus.org/browse/MRM-952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Maria Odea Ching updated MRM-952:
---------------------------------

    Fix Version/s:     (was: 1.2)
                   1.2-M1

> Patch for several issues while processing poms (effective model, expressions 
> resolving, storing to database)
> ------------------------------------------------------------------------------------------------------------
>
>                 Key: MRM-952
>                 URL: http://jira.codehaus.org/browse/MRM-952
>             Project: Archiva
>          Issue Type: Improvement
>          Components: repository interface, repository scanning
>    Affects Versions: 1.1.2
>            Reporter: Michal Stochmialek
>            Assignee: Maria Odea Ching
>             Fix For: 1.2-M1
>
>         Attachments: archiva-1.1.1-fixes-svn.patch, archiva-1.1.1-fixes.patch
>
>
> I'm submitting a bigger patch for serveral issues that drived my crazy after 
> installation of archiva in our company.
> The patch is for 1.1.1 and 1.1.2 releases. 
> The patch:
> - fixes problems with expression resolving (${pom.version}) in dependencies,
> - adds support for parent.{groupId, artifactId, version) properties,
> - fixes issues with jdo detachCopy called from ProjectModelToDatabaseListener 
> while creating effective pom,
> - fixes inconsistency in key format used in effective model cache,
> - add merging parentProject and properties while creating effective pom,
> - ArchivaProjectModel.setOrgin("filesystem") was moved to readers (where IMO 
> should be),
> - adds few new test cases.
> I will be very happy if you apply the patch on the code base. It will save me 
> a bit of work 
> with merging my changes with new releases in the future.

-- 
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

        

Reply via email to