[ http://jira.codehaus.org/browse/MRM-127?page=comments#action_70569 ] Milos Kleint commented on MRM-127: ----------------------------------
also please consider how the pom models ought to be stored. (and retrieved) - MRM-121 I noticed you did some changes that involved merging the pom and artifact index lately. However it's still using the MavenXpp3Reader to load the pom model. That gives incomplete info on 1. version+groupId in case you have a parent pom (you seemed to workaround it by setting the parent's version+groupId) 2. dependencies, plugin information is also incomplete 3. if any of the values are defined as property it will list them as such (not sure haven't tested) > refactor and review indexing and search > --------------------------------------- > > Key: MRM-127 > URL: http://jira.codehaus.org/browse/MRM-127 > Project: Maven Repository Manager > Issue Type: Bug > Components: indexing > Affects Versions: 1.0-beta-1 > Reporter: Brett Porter > Assigned To: Brett Porter > Fix For: 1.0-beta-1 > > Original Estimate: 6 hours > Remaining Estimate: 6 hours > > the indexing that is currently in place doesn't seem to be working well. > - creating the metadata index erases all artifacts > - the ms count for the initial index seems shorter than it takes > - design improvements needed > for search: > - general search simply iterates all fields looking for keywords, which > probably doesn't rank optimally > - search fails on "maven" as it tries to load a metadata file that contains > it incorrectly. It shouldn't need to read the metadata files of the search > results. > - general search doesn't appear to search metadata > - design improvements needed -- 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
