oracle/opengrok

Clearcase vobs keyword

Open

Aperta il 18 apr 2019

Vedi su GitHub
 (5 commenti) (0 reazioni) (0 assegnatari)Java (4060 star) (747 fork)batch import
bughelp wanted

Descrizione

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.

Guida contributor

Tech stack
java
Dominio
backendsearch
Tipo issue
bug
DifficoltàQuanto dovrebbe essere impegnativa per un nuovo contributor.
3
Tempo stimatoTempo stimato per completare e verificare uno scope piccolo.
1-3 hours
Stato attivitàQuanto è probabile che la issue sia ancora attiva e reviewable.
stale
ChiarezzaQuanto chiaramente la issue descrive problema, scope e risultato atteso.
mostly clear
Prerequisiti
Understanding of OpenGrok's history indexingJava
Adatta ai principiantiQuanto la issue è adatta a contributor alla prima esperienza.
30
Direzione di ricerca
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.