# The form data below was edited by perforce # Perforce Workshop Jobs # # Job: The job name. 'new' generates a sequenced job number. # # Status: Job status; required field. There is no enforced or # promoted workflow for transition of jobs from one # status to another, just a set of job status values # for users to apply as they see fit. Possible values: # # open - Issue is available to be worked on. # # inprogress - Active development is in progress. # # blocked - Issue cannot be implemented for some reason. # # fixed - Fixed, optional status to use before closed. # # closed - Issue has been dealt with definitively. # # punted - Decision made not to address the issue, # possibly not ever. # # suspended - Decision made not to address the issue # in the immediate future, but noting that it may # have some merit and may be revisited later. # # duplicate - Duplicate of another issue that. # # obsolete - The need behind the request has become # overcome by events. # # Project: The project this job is for. Required. # # Severity: [A/B/C] (A is highest) Required. # # ReportedBy The user who created the job. Can be changed. # # ReportedDate: The date the job was created. Automatic. # # ModifiedBy: The user who last modified this job. Automatic. # # ModifiedDate: The date this job was last modified. Automatic. # # OwnedBy: The owner, responsible for doing the job. Optional. # # Description: Description of the job. Required. # # DevNotes: Developer's comments. Optional. Can be used to # explain a status, e.g. for blocked, punted, # obsolete or duplicate jobs. May also provide # additional information such as the earliest release # in which a bug is known to exist. # # Component: Projects may use this optional field to indicate # which component of the project a givenjob is associated # with. # # For the SDP, the list of components is defined in: # //guest/perforce_software/sdp/tools/components.txt # # Type: Type of job [Bug/Feature]. Required. # # Release: Release in which job is intended to be fixed. Job: job000714 Status: open Project: perforce_software-p4polarion Severity: A ReportedBy: karl_wirth ReportedDate: 2017/06/28 06:43:23 ModifiedBy: perforce ModifiedDate: 2019/02/19 10:51:37 OwnedBy: karl_wirth Description: P4Polarion does not work with Polarion ALM 17.1. 2017-06-28 14:33:43,867 [main | u:p] ERROR com.polarion.platform.repository.internal.config.RepositoryConfigService$ConfigProblemCatcher - Failed to work with configuration: Unable to construct service com.polarion.platform.repository.repositoriesDataHandler: Error building service com.polarion.platform.repository.repositoriesDataHandler: Failure invoking constructor for class com.polarion.platform.repository.external.internal.RepositoriesDataHandler: com/polarion/platform/repository/external/IExternalRepositoryProvider$IExternalRepositoryConfiguration [configId=externalRepositories, locations=[Location[repository default, path /.polarion/repositories/repositories.xml]]] org.apache.hivemind.ApplicationRuntimeException: Unable to construct service com.polarion.platform.repository.repositoriesDataHandler: Error building service com.polarion.platform.repository.repositoriesDataHandler: Failure invoking constructor for class com.polarion.platform.repository.external.internal.RepositoriesDataHandler: com/polarion/platform/repository/external/IExternalRepositoryProvider$IExternalRepositoryConfiguration [bundleresource://31/META-INF/hivemodule.xml, line 102, column 19] at org.apache.hivemind.impl.servicemodel.AbstractServiceModelImpl.constructNewServiceImplementation(AbstractServiceModelImpl.java:169) DevNotes: Type: Bug