Class AccuRevScmProviderRepository

    • Constructor Detail

      • AccuRevScmProviderRepository

        public AccuRevScmProviderRepository()
    • Method Detail

      • getTagFormat

        public String getTagFormat()
      • setTagFormat

        public void setTagFormat​(String tagFormat)
      • getStreamName

        public String getStreamName()
      • setStreamName

        public void setStreamName​(String streamName)
      • getProjectPath

        public String getProjectPath()
      • setProjectPath

        public void setProjectPath​(String projectPath)
      • getAccuRev

        public AccuRev getAccuRev()
      • setAccuRev

        public void setAccuRev​(AccuRev accurev)
      • isWorkSpaceRoot

        public boolean isWorkSpaceRoot​(AccuRevInfo info)
        Parameters:
        info -
        Returns:
        true if info indicates a root of the workspace.
      • isWorkSpaceTop

        public boolean isWorkSpaceTop​(AccuRevInfo info)
      • setLogger

        public void setLogger​(ScmLogger logger)
      • getCheckoutRelativePath

        public String getCheckoutRelativePath()
        The relative path of the directory of the checked out project in comparison to the checkout directory, or an empty String in case the checkout directory equals the project directory.

        With most SCMs, this is just an empty String, meaning that the checkout directory equals the project directory. But there are cases (e.g. ClearCase) where within the checkout directory, the directory structure of the SCM system is repeated. E.g. if you check out the project "my/project" to "/some/dir", the project sources are actually checked out to "some/dir/my/project". In this example, relativePathProjectDirectory would contain "my/project".

      • setCheckoutRelativePath

        public void setCheckoutRelativePath​(String checkoutRelativePath)
      • shouldUseExportForNonPersistentCheckout

        public boolean shouldUseExportForNonPersistentCheckout()
        When checkout is not expected to be refreshed or committed, should export be used instead? Perforce, Clearcase and AccuRev store their meta-data about file status within the server rather than files in the source tree. This makes checkouts within checkouts (eg release:perform) difficult. Typically there is a way to do a lightweight export instead which can be implemented as the "export" command. This is a hint to downstream applications that "export" is available and should be used in preference to "checkout" in cases where "update" and "commit" are not intended to be used. (ie release:perform)
        Returns:
        false by default
      • setShouldUseExportForNonPersistentCheckout

        public void setShouldUseExportForNonPersistentCheckout​(boolean shouldUseExportForNonPersistentCheckout)
      • getDepotRelativeProjectPath

        public String getDepotRelativeProjectPath()
      • getSnapshotName

        public String getSnapshotName​(String tagName)
      • getRevision

        public String getRevision​(String stream,
                                  long fromTranId)
      • formatTimeSpec

        public static String formatTimeSpec​(Date when)