You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@archiva.apache.org by "Brett Porter (JIRA)" <ji...@codehaus.org> on 2010/02/23 15:47:55 UTC
[jira] Created: (MRM-1331) various clean up tasks related to
database removal
various clean up tasks related to database removal
--------------------------------------------------
Key: MRM-1331
URL: http://jira.codehaus.org/browse/MRM-1331
Project: Archiva
Issue Type: Task
Affects Versions: 1.4
Reporter: Brett Porter
- review FIXME and TODO markers in new code (to fix, or to migrate to issues instead and mark in code)
- review test coverage of new code (should be ok, but worth checking with EMMA)
- remove the duplication of mocks and test repositories across various modules to do the same thing
- go back over new code and remove PlexusInSpringTestCase where possible
** in favour of just creating the objects, or look into an alternative with Mockito
** remove getTestFile and look up from resources or user.dir
- review suitable places for logging
--
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
[jira] Updated: (MRM-1331) various clean up tasks related to
database removal
Posted by "Olivier Lamy (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRM-1331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Olivier Lamy updated MRM-1331:
------------------------------
Fix Version/s: (was: 1.4-M1)
1.4-M2
> various clean up tasks related to database removal
> --------------------------------------------------
>
> Key: MRM-1331
> URL: https://jira.codehaus.org/browse/MRM-1331
> Project: Archiva
> Issue Type: Task
> Affects Versions: 1.4
> Reporter: Brett Porter
> Assignee: Brett Porter
> Fix For: 1.4-M2
>
>
> - review FIXME and TODO markers in new code (to fix, or to migrate to issues instead and mark in code)
> - review test coverage of new code (should be ok, but worth checking with EMMA)
> - remove the duplication of mocks and test repositories across various modules to do the same thing
> - review suitable places for logging
> - go back over new code and remove PlexusInSpringTestCase where possible
> ** in favour of just creating the objects, or look into an alternative with Mockito
> ** remove getTestFile and look up from resources or user.dir
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MRM-1331) various clean up tasks related to
database removal
Posted by "Olivier Lamy (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRM-1331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=280134#comment-280134 ]
Olivier Lamy commented on MRM-1331:
-----------------------------------
mostly done IMHO ?
> various clean up tasks related to database removal
> --------------------------------------------------
>
> Key: MRM-1331
> URL: https://jira.codehaus.org/browse/MRM-1331
> Project: Archiva
> Issue Type: Task
> Affects Versions: 1.4
> Reporter: Brett Porter
> Assignee: Brett Porter
> Fix For: 1.4-M1
>
>
> - review FIXME and TODO markers in new code (to fix, or to migrate to issues instead and mark in code)
> - review test coverage of new code (should be ok, but worth checking with EMMA)
> - remove the duplication of mocks and test repositories across various modules to do the same thing
> - review suitable places for logging
> - go back over new code and remove PlexusInSpringTestCase where possible
> ** in favour of just creating the objects, or look into an alternative with Mockito
> ** remove getTestFile and look up from resources or user.dir
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MRM-1331) various clean up tasks related to database
removal
Posted by "Olivier Lamy (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRM-1331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=316025#comment-316025 ]
Olivier Lamy commented on MRM-1331:
-----------------------------------
Just reviewed FIXME.
Do you see any still related ?
> various clean up tasks related to database removal
> --------------------------------------------------
>
> Key: MRM-1331
> URL: https://jira.codehaus.org/browse/MRM-1331
> Project: Archiva
> Issue Type: Task
> Affects Versions: 1.4
> Reporter: Brett Porter
> Assignee: Brett Porter
> Fix For: 1.4-M4
>
>
> - review FIXME and TODO markers in new code (to fix, or to migrate to issues instead and mark in code)
> - review test coverage of new code (should be ok, but worth checking with EMMA)
> - remove the duplication of mocks and test repositories across various modules to do the same thing
> - review suitable places for logging
> - go back over new code and remove PlexusInSpringTestCase where possible
> ** in favour of just creating the objects, or look into an alternative with Mockito
> ** remove getTestFile and look up from resources or user.dir
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MRM-1331) various clean up tasks related to
database removal
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-1331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter updated MRM-1331:
------------------------------
Description:
- review FIXME and TODO markers in new code (to fix, or to migrate to issues instead and mark in code)
- review test coverage of new code (should be ok, but worth checking with EMMA)
- remove the duplication of mocks and test repositories across various modules to do the same thing
- review suitable places for logging
- go back over new code and remove PlexusInSpringTestCase where possible
** in favour of just creating the objects, or look into an alternative with Mockito
** remove getTestFile and look up from resources or user.dir
was:
- review FIXME and TODO markers in new code (to fix, or to migrate to issues instead and mark in code)
- review test coverage of new code (should be ok, but worth checking with EMMA)
- remove the duplication of mocks and test repositories across various modules to do the same thing
- go back over new code and remove PlexusInSpringTestCase where possible
** in favour of just creating the objects, or look into an alternative with Mockito
** remove getTestFile and look up from resources or user.dir
- review suitable places for logging
Fix Version/s: 1.4
Assignee: Brett Porter
> various clean up tasks related to database removal
> --------------------------------------------------
>
> Key: MRM-1331
> URL: http://jira.codehaus.org/browse/MRM-1331
> Project: Archiva
> Issue Type: Task
> Affects Versions: 1.4
> Reporter: Brett Porter
> Assignee: Brett Porter
> Fix For: 1.4
>
>
> - review FIXME and TODO markers in new code (to fix, or to migrate to issues instead and mark in code)
> - review test coverage of new code (should be ok, but worth checking with EMMA)
> - remove the duplication of mocks and test repositories across various modules to do the same thing
> - review suitable places for logging
> - go back over new code and remove PlexusInSpringTestCase where possible
> ** in favour of just creating the objects, or look into an alternative with Mockito
> ** remove getTestFile and look up from resources or user.dir
--
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
[jira] (MRM-1331) various clean up tasks related to database
removal
Posted by "Olivier Lamy (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRM-1331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Olivier Lamy updated MRM-1331:
------------------------------
Fix Version/s: (was: 1.4-M3)
1.4-M4
> various clean up tasks related to database removal
> --------------------------------------------------
>
> Key: MRM-1331
> URL: https://jira.codehaus.org/browse/MRM-1331
> Project: Archiva
> Issue Type: Task
> Affects Versions: 1.4
> Reporter: Brett Porter
> Assignee: Brett Porter
> Fix For: 1.4-M4
>
>
> - review FIXME and TODO markers in new code (to fix, or to migrate to issues instead and mark in code)
> - review test coverage of new code (should be ok, but worth checking with EMMA)
> - remove the duplication of mocks and test repositories across various modules to do the same thing
> - review suitable places for logging
> - go back over new code and remove PlexusInSpringTestCase where possible
> ** in favour of just creating the objects, or look into an alternative with Mockito
> ** remove getTestFile and look up from resources or user.dir
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MRM-1331) various clean up tasks related to
database removal
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRM-1331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=280137#comment-280137 ]
Brett Porter commented on MRM-1331:
-----------------------------------
there's a lot of FIXME - I can look over those this weekend too and turn them into issues
> various clean up tasks related to database removal
> --------------------------------------------------
>
> Key: MRM-1331
> URL: https://jira.codehaus.org/browse/MRM-1331
> Project: Archiva
> Issue Type: Task
> Affects Versions: 1.4
> Reporter: Brett Porter
> Assignee: Brett Porter
> Fix For: 1.4-M1
>
>
> - review FIXME and TODO markers in new code (to fix, or to migrate to issues instead and mark in code)
> - review test coverage of new code (should be ok, but worth checking with EMMA)
> - remove the duplication of mocks and test repositories across various modules to do the same thing
> - review suitable places for logging
> - go back over new code and remove PlexusInSpringTestCase where possible
> ** in favour of just creating the objects, or look into an alternative with Mockito
> ** remove getTestFile and look up from resources or user.dir
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MRM-1331) various clean up tasks related to database
removal
Posted by "Olivier Lamy (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRM-1331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Olivier Lamy updated MRM-1331:
------------------------------
Fix Version/s: (was: 1.4-M4)
1.4-M5
> various clean up tasks related to database removal
> --------------------------------------------------
>
> Key: MRM-1331
> URL: https://jira.codehaus.org/browse/MRM-1331
> Project: Archiva
> Issue Type: Task
> Affects Versions: 1.4
> Reporter: Brett Porter
> Assignee: Brett Porter
> Fix For: 1.4-M5
>
>
> - review FIXME and TODO markers in new code (to fix, or to migrate to issues instead and mark in code)
> - review test coverage of new code (should be ok, but worth checking with EMMA)
> - remove the duplication of mocks and test repositories across various modules to do the same thing
> - review suitable places for logging
> - go back over new code and remove PlexusInSpringTestCase where possible
> ** in favour of just creating the objects, or look into an alternative with Mockito
> ** remove getTestFile and look up from resources or user.dir
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira