JIRA ClearCase Plugin

Added by Binyan, last edited by Gunnar Velle on Jan 25, 2008  (view change)
Name JIRA ClearCase Plugin
Version 1.0.4
Author(s) n/a
Homepage JIRA ClearCase Plugin
Price free!
License Apache 2.0
JavaDocs docs
Download JAR jira-clearcase-plugin-1.0.4, jira-clearcase-plugin-1.0.2, all versions
Download Source http://svn.atlassian.com/svn/public/contrib/jira/jira-clearcase-plugin/trunk/

Plugin Status

- This plugin is externally developed and unsupported by Atlassian. For help, please leave a comment at the bottom of this page.

Key: = working, = untested, = broken

JIRA 3.2 3.3 3.4 3.5 3.6 3.7 3.8 3.9 3.10 3.11 3.12
Plugin v1.0
Plugin v1.0.2
Plugin v1.0.4

Please help us improve the compatibility matrix by relating your installation experiences (product version, success/failure) in a comment below.

Description/Features

The jiraext-clearcase-plugin.jar file adds the ability to associate ClearCase checkins to JIRA issues. The plugin works by periodically retrieving all new log entries for the specified vobs since the last retrieval (or the Revision Indexing Start Time if the index is missing or this is the 1st time the plugin has run) and indexing the new entries with Apache's Lucene.

The plugin adds a panel to each JIRA issue that shows all of the ClearCase history logs in chronological order that are associated with the current issue.

Warning
JIRA is case-sensitive with respect to JIRA issue #'s. Even though the "Quick Search" field resolves Foo-1 and foo-1 to the same issue, the underlying API's do not. As a result, a clearcase log entry for foo-1 will not be associated with project Foo and ClearCase committers will need to be aware of the proper case for the issue they are referencing.

Installation

1. Add the jiraext-clearcase-plugin.jar to JIRA's WEB-INF/lib directory.
2. Start JIRA and log in as a user with the appropriate permissions to add services to the JIRA installation.
3. To add the ClearCase service enter the following (Screenshot 1):

Name: ClearCase Integration Service
Class: net.sf.jiraext.plugin.clearcase.services.ClearCaseIndexService
Delay: 10

5. Clik the "Add Service" button to add the service and proceed to the configuration screen.

6. To configure the service (Screenshot 2):

Directory Name: jira-clearcase-indexes
ClearCase VOB Paths: D:\views\myview01_snap4\jiraVOB
ChangeSet Association Time: 60000
Revision Indexing Start Time: 01/01/2005 00:00:00 AM

Useful Information About The ChangeSet Association Time

The checkin times of 2-3 files can have the exact same time associated with their respective comment entries. However, when checking in many files or performing ClearCase opertaions over a slow link (VPN/Dial Up) the checkin times can vary from seconds to minutes. The 'ChangeSet Association Time' property is the amount time that entries with the same committer and comment are grouped together as specified in milliseconds.

For Example:
If the ChangeSet Association Time property is set to 30000, and it takes 1 second to checkin in a file, then anyone checking in 31 files will generate 2 changesets, 1 with 30 entries and 1 with 1 entry. Nonetheless, both changesets will be accurately associated with the issue, if the JIRA issue # was included in the original checkin comment.

7. Click the "Update" button to complete the JIRA/ClearCase integration.

Todo

  1. link the JIRA issue numbers in the commit messages (see JiraKeyUtils.linkBugKeys(string) method.
  2. Link diffs back to ClearCase web interface
  3. Expand into a Project Tab that shows all changesets for entire project in order.

Version History

Version Comments
1.0 Initial version
1.0.2 Added support for jira 3.9
1.0.3 Added support for jira 3.12

Screenshots

Screenshots
(view as slideshow)
     
  How to add the ClearCase Service   How to configure the Service  
 
     
  ClearCase commits in action 1   ClearCase commits in action 2  
 
       
       
 

Labels

 

Comments (69)

 

  1. Jun 28, 2005

    Espen Tjonneland says:

    I had a go on a window xp box with Jira installed. However I'm getting a few err...

    I had a go on a window xp box with Jira installed. However I'm getting a few errors. One is that the index directory seems to prepend jira standard indexing dir in front of the index specified in services settings. Is it possible to have a look at the source in order to correct/investigate issues (I noticed you have sourceforge package structures in the jar), but I cannot seem to find the source at sourceforge. I love the general idea though and will contribute to the plugin if you allow it.

    1. Jun 28, 2005

      Binyan says:

      Currently that is the preferred behavior, in that the clearcase indexes would be...

      Currently that is the preferred behavior, in that the clearcase indexes would be stored in a subfolder of the jira index directory, thus a user only has to backup one directory. Nonetheless, this is something that could have a default and allow the user to change at will.

      As for the code, I've been on other duties and just haven't gotten to putting it in SF, but I'll try and accomplish this in the next day or 2.

      1. Sep 13, 2005

        Espen Tjonneland says:

        Sorry for bothering you again with this Binyan, but have you been able to plug t...

        Sorry for bothering you again with this Binyan, but have you been able to plug this plugin on sourceforge? If not can I have a look at he code to fix a few bugs(Velocity related nullpointers, and stricter config checking). I won't stress you about any coding issues as I'm sure this plugin was created on top of a otherwise fully loaded workday.....

        Cheers, Espen.

  2. Jun 29, 2005

    Espen Tjonneland says:

    Another Issue I am a bit unsure of is specifying multiple views. It says it is p...

    Another Issue I am a bit unsure of is specifying multiple views. It says it is possible but I've been unable to get it to work. I've specified the following comma delimited list of views(VOB_PATHS):

    C:\jira\views\mainline\s-appls,C:\jira\views\jbug037_view,C:\jira\views\tom3_view

    I'm assuming you actually use the default tokenizer constructor in java which is the "new public StringTokenizer(String str)"

    The javadoc states that:
    "Constructs a string tokenizer for the specified string. The tokenizer uses the default delimiter set, which is " \t\n\r\f": the space character, the tab character, the newline character, the carriage-return character, and the form-feed character. Delimiter characters themselves will not be treated as tokens."

    This would mean that
    1:, if you have spaces in vob-paths you are asking for trouble ,
    2: "," for delimiter doesen't work.....

    Am I right?

  3. Jul 15, 2005

    Anonymous says:

    Having some issues getting things to work here. The directions above are somewha...

    Having some issues getting things to work here. The directions above are somewhat lacking in explanations of what the examples are doing. In particular, I'm not sure how deep in the path to go in defining my VOBpath - which apparently is actually a view?? Do I just point at the vobs directory in my view, or at the particular vob I am interested in or what?

    1. Jul 15, 2005

      Anonymous says:

      for further reference, here are the lines i get in the catalina.out log file whe...

      for further reference, here are the lines i get in the catalina.out log file when i try to update the ClearCase Integration Service

      262277: at net.sf.jiraext.plugin.clearcase.services.ClearCaseIndexService.update
      Properties(ClearCaseIndexService.java:140)
      262278: at net.sf.jiraext.plugin.clearcase.services.ClearCaseIndexService.run(Cl
      earCaseIndexService.java:74)

    2. Jul 15, 2005

      Binyan says:

      You need to list the full path to the vob which you want to index, not just the ...

      You need to list the full path to the vob which you want to index, not just the path to the view. I thought of just using a view path, but we typically load vobs for reviewing etc, that we have no intention of indexing so I just went with the complete vob path.

      I'll try and work on the instructions next week after the big demo I'm working on.

      1. Jul 15, 2005

        Anonymous says:

        okay, I've got the following settings and still having the same errors in the lo...

        okay, I've got the following settings and still having the same errors in the log

        REVISION_INDEXING_START_TIME: 01/01/2005 00:00:00 AM
        INDEX_DIRECTORY_NAME: jira-clearcase-indexes
        CHANGESET_ASSOCIATION_TIME: 60000
        VOB_PATHS: /view/joel_SCSBUILD_REL1.0/vobs/scsbuild

      2. Jul 15, 2005

        Anonymous says:

        nm, I got it working. I seemed to need to delete the jiraclearcaseindexes direct...

        nm, I got it working. I seemed to need to delete the jira-clearcase-indexes directory and contents after removing the service and then re-add with the correct VOB_PATHS set. i.e. simply editing the service to specify the correct vob paths didn't seem to fix things once the index was created with an erroneous VOB_PATHS

  4. Aug 23, 2005

    Lehky, Miro says:

    I am installing this plugin but am slightly confused by two items. 1. How deep ...

    I am installing this plug-in but am slightly confused by two items.

    1. How deep into the VOB path should i be listing in the configuration? Do i simply include the path to the directory that is the home to all the VOB directories, or do i have to list each VOB directory.

    2. How do i list multiple directories. I tried separating them all with "," but end up with an error.

    Sorry for the basic question, unfortunately we are not overly ClearCase proficient here. We use CVS for most projects and due to customer requirements have ClearCase for only a single small project.

  5. Aug 23, 2005

    Lehky, Miro says:

    If it is of any help here is the catalina log excerpt. 20050823 12:21:47,090 ER...

    If it is of any help here is the catalina log excerpt.

    2005-08-23 12:21:47,090 ERROR [plugin.clearcase.internal.ClearCaseHistoryParser] cleartool execution error
    java.io.IOException: java.io.IOException: cleartool: not found
    at java.lang.UNIXProcess.<init>(UNIXProcess.java:148)
    at java.lang.ProcessImpl.start(ProcessImpl.java:65)
    at java.lang.ProcessBuilder.start(ProcessBuilder.java:451)
    at java.lang.Runtime.exec(Runtime.java:591)
    at java.lang.Runtime.exec(Runtime.java:429)
    at net.sf.jiraext.plugin.clearcase.internal.ClearCaseHistoryParser.getRevisions(ClearCaseHistoryParser.java:134)
    at net.sf.jiraext.plugin.clearcase.internal.ClearCaseHistoryParser.getRevisions(ClearCaseHistoryParser.java:340)
    at net.sf.jiraext.plugin.clearcase.services.ClearCaseIndexService.run(ClearCaseIndexService.java:124)
    at com.atlassian.jira.service.JiraServiceContainer.run(JiraServiceContainer.java:59)
    at com.atlassian.jira.service.ServiceRunner.execute(ServiceRunner.java:50)
    at org.quartz.core.JobRunShell.run(JobRunShell.java:191)
    at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:516)
    2005-08-23 12:21:55,364 WARN [sf.statcvs.input.Builder] Revision 1.1.1.1 has no main branch - ignoring revision.
    2005-08-23 12:21:55,364 WARN [sf.statcvs.input.Builder] Revision 1.1.1.1 has no main branch - ignoring revision.
    2005-08-23 12:21:55,364 WARN [sf.statcvs.input.Builder] Revision 1.1.1.1 has no main branch - ignoring revision.
    2005-08-23 12:21:55,364 WARN [sf.statcvs.input.Builder] Revision 1.1.1.1 has no main branch - ignoring revision.
    2005-08-23 12:21:55,365 WARN [sf.statcvs.input.Builder] Revision 1.1.1.1 has no main branch - ignoring revision.
    2005-08-23 12:21:55,365 WARN [sf.statcvs.input.Builder] Revision 1.1.1.1 has no main branch - ignoring revision.

    1. Aug 23, 2005

      Binyan says:

      The clearcase cleartool executable needs to be in the path your server.

      The clearcase cleartool executable needs to be in the path your server.

  6. Aug 24, 2005

    Espen Tjonneland says:

    ClearCase VOB Paths: I list the full path of these....

    ClearCase VOB Paths:
    I list the full path of these. On a windows machine I have it configured like this:
    C:\jira\views\mainline
    C:\jira\views\jbug037_view
    C:\jira\views\tom3_view
    C:\jira\views\eos_post037_view

    Note that entries are separated by newline(note my post in the beginning pointing out a bug when using ;

  7. Aug 25, 2005

    Lehky, Miro says:

    Thanks...i got it going. One thing i did not think of before knowing that thi...

    Thanks...i got it going.

    One thing i did not think of before knowing that this service needed access to Cleartool is that it would take up a license. Is there any way to schedule the service to run at a specific time (ie 2am) instead of at an interval. I suspect this may actualy be a change required in JIRA and not in the service itself.

    Thanks

    1. Aug 25, 2005

      Binyan says:

      Jira will execute the plugin at a specified interval, so have you tried setting ...

      Jira will execute the plugin at a specified interval, so have you tried setting the interval to be say every 24 hours? Also I believe the interval time is controlled by the time jira starts so you can either restart jira at 2:00 AM or you might be able to update the service's interval value which also may reset the interval time. Of course the reset would need to be done at 2:00 AM.

      Btw, I wasn't aware that the jira integration uses a clearcase license, however when you mentioned it, I was like of couse it would, clearcase is anal that way, even for just reading the logs.

      1. Aug 25, 2005

        Lehky, Miro says:

        Yes, I was thinking of restarting the service at 2am. But that works only until ...

        Yes, I was thinking of restarting the service at 2am. But that works only until our IT department decides to restart the entire box at 9am. Atlassian has on open issue on this;

        http://jira.atlassian.com/browse/JRA-1865

        The license thing would not be an issue if we did not have as few licenses as we do. We only use it for one project and thus have 2 licenses.

        Miro

  8. Sep 21, 2005

    Jonathan Nolen says:

    Unless anyone objects, I would like to move this page into the JIRAEXT: space al...

    Unless anyone objects, I would like to move this page into the JIRA Extensions space along side the other JIRA+VCS plugins. [~Binyan], is that OK with you?

    1. Sep 26, 2005

      Binyan says:

      1 for the move.

      +1 for the move.

      1. Sep 26, 2005

        Jonathan Nolen says:

        done.

        done.

  9. Oct 14, 2005

    Espen Tjonneland says:

    Excellent work Binyan\! Can you contact me with password information for source ...

    Excellent work Binyan!

    Can you contact me with password information for source access?

    etj@unified.no

    Regards Espen

    1. Oct 14, 2005

      Jonathan Nolen says:

      You can get readonly source access from

      You can get read-only source access from

      http://svn.atlassian.com/svn/public/contrib/jira/jira-clearcase-plugin/

      If you need write access, contact me directly.

  10. Oct 14, 2005

    Binyan says:

    What additional features are people looking for? I had planned on working out ho...

    What additional features are people looking for? I had planned on working out how to link source code similar to the files in a changeset.

    1. Oct 14, 2005

      Mike Cannon-Brookes says:

      Binyan, On obvious feature to add would be to link any issue keys mentioned in ...

      Binyan,

      On obvious feature to add would be to link any issue keys mentioned in a commit message to the issues themselves. This is very easy to add.

      You can do this very simply using this method

      String linked = JiraKeyUtils.linkBugKeys(commitMessage);

  11. Oct 17, 2005

    Binyan says:

    Thanks Mike. I have already added support for this, since it was low hanging fru...

    Thanks Mike. I have already added support for this, since it was low hanging fruit. I just haven't pushed out a new version yet. I'll likely do that in the next day or so after some minor cleanup.

  12. Oct 20, 2005

    Anonymous says:

    Hello all I have a couple of questions: (1) Is there a more complete build.xml f...

    Hello all - I have a couple of questions:

    (1) Is there a more complete build.xml file for this plugin available - or should I be embedding the source into the Jira tree, and building globally?

    (2) The "stock" jar is not producing any content under my issues - I check in a file and add a comment "ECF-3" matching an issue ID, but nothing ever shows up in the new issues tab...  Browsing the log files show that a "segment" file can't be found...

  13. Oct 20, 2005

    Binyan says:

    I will be checking in an updated project with a minor change this weekend.&nbsp;...

    I will be checking in an updated project with a minor change this weekend.  As for your last point can you post the exception you are likely given as the lack of a segment looks like something involving Lucene (the indexer)?  You can always delete your old index files and they will be recreated after a restart.

    1. Oct 20, 2005

      Anonymous says:

      Here is the log excerpt (sorry about the length...) looks like Lucene is definat...

      Here is the log excerpt (sorry about the length...) looks like Lucene is definately mentioned.  Is Lucene used for the other  indexing services?  The other issue indexes seem to work fine...

      Oct 20, 2005 12:57:34 PM net.sf.jiraext.plugin.clearcase.issuetabpanels.ClearCaseRevisionsTabPanel getActions
      SEVERE: Error creating Lucene IndexSearcher
      java.io.FileNotFoundException: C:\ecfjira\indexes\jira-clearcase-indexes\segments (The system cannot find the file specified)
          at java.io.RandomAccessFile.open(Native Method)
          at java.io.RandomAccessFile.<init>(RandomAccessFile.java:212)
          at org.apache.lucene.store.FSInputStream$Descriptor.<init>(FSDirectory.java:376)
          at org.apache.lucene.store.FSInputStream.<init>(FSDirectory.java:405)
          at org.apache.lucene.store.FSDirectory.openFile(FSDirectory.java:268)
          at org.apache.lucene.index.SegmentInfos.read(SegmentInfos.java:40)
          at org.apache.lucene.index.IndexReader$1.doBody(IndexReader.java:116)
          at org.apache.lucene.store.Lock$With.run(Lock.java:109)
          at org.apache.lucene.index.IndexReader.open(IndexReader.java:111)
          at org.apache.lucene.index.IndexReader.open(IndexReader.java:95)
          at org.apache.lucene.search.IndexSearcher.<init>(IndexSearcher.java:38)
          at net.sf.jiraext.plugin.clearcase.issuetabpanels.ClearCaseRevisionsTabPanel.getActions(ClearCaseRevisionsTabPanel.java:93)
          at com.atlassian.jira.plugin.issuetabpanel.IssueTabPanelModuleDescriptor.getActions(IssueTabPanelModuleDescriptor.java:72)
          at com.atlassian.jira.issue.managers.DefaultActionManager.getPluginModuleActions(DefaultActionManager.java:198)
          at com.atlassian.jira.web.action.issue.ViewIssue.getActions(ViewIssue.java:430)
          at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
          at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
          at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
          at java.lang.reflect.Method.invoke(Method.java:585)
          at webwork.util.InjectionUtils$DefaultInjectionImpl.invoke(InjectionUtils.java:61)
          at webwork.util.InjectionUtils.invoke(InjectionUtils.java:52)
          at webwork.util.ValueStack.findValue(ValueStack.java:346)
          at webwork.util.ValueStack.findValue(ValueStack.java:175)
          at webwork.view.taglib.WebWorkBodyTagSupport.findValue(WebWorkBodyTagSupport.java:61)
          at webwork.view.taglib.BasicPropertyTag.doStartTag(BasicPropertyTag.java:54)
          at org.apache.jsp.includes.panels.issue.actions_jsp._jspx_meth_webwork_property_0(org.apache.jsp.includes.panels.issue.actions_jsp:109)
          at org.apache.jsp.includes.panels.issue.actions_jsp._jspService(org.apache.jsp.includes.panels.issue.actions_jsp:83)
          at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:97)
          at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
          at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:322)
          at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:291)
          at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:241)
          at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
          at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
          at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
          at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:672)
          at org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:574)
          at org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:499)
          at org.apache.jasper.runtime.JspRuntimeLibrary.include(JspRuntimeLibrary.java:966)
          at org.apache.jsp.secure.views.issue.viewissue_jsp._jspService(org.apache.jsp.secure.views.issue.viewissue_jsp:354)
          at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:97)
          at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
          at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:322)
          at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:291)
          at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:241)
          at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
          at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
          at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
          at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:672)
          at org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:463)
          at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:398)
          at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:301)
          at com.atlassian.jira.web.dispatcher.JiraServletDispatcher.service(JiraServletDispatcher.java:256)
          at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
          at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
          at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
          at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:672)
          at org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:463)
          at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:398)
          at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:301)
          at com.atlassian.jira.servlet.QuickLinkServlet.service(QuickLinkServlet.java:61)
          at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
          at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
          at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
          at com.atlassian.jira.web.filters.AccessLogFilter.doFilter(AccessLogFilter.java:51)
          at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
          at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
          at com.opensymphony.module.sitemesh.filter.PageFilter.parsePage(PageFilter.java:118)
          at com.opensymphony.module.sitemesh.filter.PageFilter.doFilter(PageFilter.java:52)
          at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
          at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
          at com.atlassian.seraph.filter.SecurityFilter.doFilter(SecurityFilter.java:182)
          at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
          at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
          at com.atlassian.seraph.filter.LoginFilter.doFilter(LoginFilter.java:177)
          at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
          at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
          at com.atlassian.util.profiling.filters.ProfilingFilter.doFilter(ProfilingFilter.java:132)
          at com.atlassian.jira.web.filters.ProfilingAndErrorFilter.doFilter(ProfilingAndErrorFilter.java:25)
          at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
          at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
          at com.atlassian.jira.web.filters.ActionCleanupDelayFilter.doFilter(ActionCleanupDelayFilter.java:37)
          at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
          at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
          at com.atlassian.core.filters.AbstractEncodingFilter.doFilter(AbstractEncodingFilter.java:36)
          at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
          at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
          at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
          at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
          at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
          at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
          at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
          at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
          at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:856)
          at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:744)
          at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
          at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80)
          at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)
          at java.lang.Thread.run(Thread.java:595)
      Oct 20, 2005 1:29:37 PM net.sf.jiraext.plugin.clearcase.services.ClearCaseRevisionIndexer updateIndexes
      SEVERE: java.io.FileNotFoundException: C:\ecfjira\indexes\jira-clearcase-indexes\segments (The system cannot find the file specified)

    2. Oct 20, 2005

      Anonymous says:

      OK I&nbsp; found the issue. One needs to let JIRA create the specified index fol...

      OK - I  found the issue.

      One needs to let JIRA create the specified index folder.  I deleted the folder I created, and let Jira create it, and all is well.

  14. Oct 24, 2005

    Espen Tjonneland says:

    Future changes/ideas. Is it possible to get a JIRA project on the JIRAClearcase ...

    Future changes/ideas.

    Is it possible to get a JIRA project on the JIRA-Clearcase plugin? This would be a good place to start adding ideas, open for voting etc. I currently have a development team ready at my workplace who could contribute to the project. The first steps would be starting to prepare the source for community work. The steps in this would be:

    1. Introduce Maven as a common build platform
    --Benefits: Uniform way to build the system.
                    No link to preferred IDE
                    JAR dependencies are resolved and downloaded for you
    2. Add Unittesting as part of the build(requires JMock for web mocking)
    --Benefits: Introduces a securityharness when contributing to the plugin.

    Anothe idea that comes to mind is to spilt the code so that it possible to run the ClearCase part on a separate machine.

    1. Oct 24, 2005

      Jonathan Nolen says:

      We are very close to having a new JIRA instance for the developer network. Watch...

      We are very close to having a new JIRA instance for the developer network. Watch the blog for details very soon.