[
http://jira.codehaus.org/browse/MRM-622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_117512
]
Maria Odea Ching commented on MRM-622:
--------------------------------------
Hi Dario, I re-applied the patch again and did as was specified in the test
scenario. The result was still the same for me though :( I still got the same
error. Maybe there were some other changes in your local copy that didn't get
included in the patches you've submitted? Anyway, I'll also look into why I'm
getting the error.
For the tests, you could take a look at some of the test cases in Archiva as
reference. As much as possible, it is recommended to use mock objects for the
tests and cover as many different scenarios as you can. Another tip too (though
not related to the tests), is you can also submit just one patch for all your
changes. Instead of doing a diff per module, you can just diff on the top level
directory ;)
Thanks again!
> database not being updated with project model information
> ---------------------------------------------------------
>
> Key: MRM-622
> URL: http://jira.codehaus.org/browse/MRM-622
> Project: Archiva
> Issue Type: Bug
> Affects Versions: 1.0
> Environment: OS: Windows XP
> Software: Java 5 Update 12 and Maven 2.0.4
> Reporter: Dário Oliveros
> Fix For: 1.1
>
> Attachments: archiva-database-consumers.patch,
> archiva-database.patch, archiva-scheduled.patch
>
>
> I noticed Archiva database was not being updated with project model
> information in the following scenario:
> 1) Project B (1.0-SNAPSHOT) depends on Project A (1.0)
> 2) Project B is deployed to Archiva repository
> 3) Project B changes Project A dependency version from 1.0 to 1.1-SNAPSHOT
> 4) Project B is deployed to Archiva repository again.
> 5) The user executes 'Scan Repository Now' and 'Update Database Now' using
> Archiva.
> At this point, if you browse project B, you'll notice it still keeps the
> reference to the former version of Project A, 1.0, and not 1.1-SNAPSHOT.
> However, if you download the POM file, you will see it has the lastet
> dependency version as expected.
> NOTE: In project B POM file the snapshotRepository is configured with
> uniqueVersion equals to false.
--
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
