oracle/opengrok

Clearcase vobs keyword

Open

#2,752 opened on Apr 18, 2019

View on GitHub
 (5 comments) (0 reactions) (0 assignees)Java (747 forks)batch import
bughelp wanted

Repository metrics

Stars
 (4,060 stars)
PR merge metrics
 (Avg merge 1d 22h) (17 merged PRs in 30d)

Description

I started Opegrok from the latest docker image (Tomcat 9, JRE 8) and configured it to point a mercurial repository that has many directories as follows:

/repository/software/vobs/application/1 /repository/software/vobs/application/2 /repository/software/vobs/application/3

Although the indexing is completed and the source code is searchable the history is not available through the user interface. It seems that even I use a different SCM, Opengrok's HistoryGuru messes with Clearcase. Discovered that the evaluation of Clearcase includes a check for the keyword "vobs" in the file paths which appears to be related.

Contributor guide

Research direction
Examine ClearCaseRepository.java line 246 to understand the vobs check. Determine how to restrict that check to only ClearCase repositories, possibly by checking the repository type or path prefix. Modify the condition to avoid false positives for non ClearCase SCMs.
Tech stack
java
Domain
backendsearch
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
Understanding of OpenGrok's history indexingJava
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30