The following document contains the listing of user tags found in the code. Below is the summary of the occurrences per tag.
| Tag Class | Total number of occurrences | Tag strings used by tag class |
|---|---|---|
| @todo | 6 | @todo |
| TODO | 34 | TODO |
Each tag is detailed below:
Number of occurrences found in the code: 6
| org.apache.continuum.dao.DaoUtilsImpl | Line |
|---|---|
| Move to a better place | 154 |
| Move to a better place | 196 |
| Move to a better place | 270 |
| org.apache.maven.continuum.store.AbstractContinuumStoreTestCase | Line |
| push down to a Jdo specific test | 1671 |
| org.apache.maven.continuum.store.ContinuumStoreTest | Line |
| I think this should have all the JDO stuff from the abstract test, and the abstract test should use a mock continuum store with the exception of the integration tests which should be running against a fully deployed plexus application instead | 57 |
| review for ambiguities and ensure it is all encapsulated in the store, otherwise the code may make the same mistake about not deleting things, etc | 60 |
Number of occurrences found in the code: 34
| org.apache.continuum.dao.BuildDefinitionDaoImpl | Line |
|---|---|
| Move this method to a service class | 278 |
| org.apache.continuum.dao.BuildResultDaoImpl | Line |
| Use projectDao | 74 |
| these are in the wrong spot - set them on success (though currently some depend on latest build being the one in progress) | 104 |
| org.apache.continuum.dao.ProjectGroupDaoImpl | Line |
| why do we need to do this? if not - build results are not removed and a integrity constraint is violated. I assume its because of the fetch groups | 78 |
| org.apache.maven.continuum.store.AbstractContinuumStoreTestCase | Line |
| simplify by deep copying the relationships in createTest... ? | 345 |
| better way? this assumes that some untested methods already work! | 369 |
| !!! -- definitely need to test the changeset stuff since it uses modello.refid | 801 |
| simplify by deep copying the relationships in createTest... ? | 818 |
| org.apache.maven.continuum.store.ContinuumStoreTest | Line |
| test if it has any attachments | 345 |
| test if it has any attachments | 424 |
| test the project group's notifiers are physically deleted | 669 |
| test the project group's build definitions are physically deleted | 670 |
| test the build result was physically deleted | 697 |
| test the build result's SCM result was physically deleted | 698 |
| test the build result's SCM result's change sets and change files were physically deleted | 699 |
| reports, artifacts, data | 740 |
| test the developer was physically deleted | 849 |
| test the dependency was physically deleted | 897 |
| test the notifier was physically deleted | 944 |
| test the def was physically deleted | 1006 |
| test the schedule/profile was NOT physically deleted | 1007 |
| test the notifier was physically deleted | 1059 |
| test the def was physically deleted | 1119 |
| test the schedule/profile was NOT physically deleted | 1120 |
| test the project's checkout SCM result was physically deleted | 1420 |
| test the project's checkout SCM result's change sets and change files were physically deleted | 1421 |
| test the project's dependencies are physically deleted | 1422 |
| test the project's developers are physically deleted | 1423 |
| test the project's builds are physically deleted | 1424 |
| test the project's notifiers are physically deleted | 1425 |
| test the project's build definitions are physically deleted | 1426 |
| artifacts | 1567 |
| report | 1568 |
| long error data } | 1569 |