You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

org.eclipse.pde.api.tools.prefs 4.7KB

Support LFS protocol and a file system based LFS storage Implement LfsProtocolServlet handling the "Git LFS v1 Batch API" protocol [1]. Add a simple file system based LFS content store and the debug-lfs-store command to simplify testing. Introduce a LargeFileRepository interface to enable additional storage implementation while reusing the same protocol implementation. At the client side we have to configure the lfs.url, specify that we use the batch API and we don't use authentication: [lfs] url = http://host:port/lfs batch = true [lfs "http://host:port/lfs"] access = none the git-lfs client appends the "objects/batch" to the lfs.url. Hard code an Authorization header in the FileLfsRepository.getAction because then git-lfs client will skip asking for credentials. It will just forward the Authorization header from the response to the download/upload request. The FileLfsServlet supports file content storage for "Large File Storage" (LFS) server as defined by the Github LFS API [2]. - upload and download of large files is probably network bound hence use an asynchronous servlet for good scalability - simple object storage in file system with 2 level fan-out - use LockFile to protect writing large objects against multiple concurrent uploads of the same object - to prevent corrupt uploads the uploaded file is rejected if its hash doesn't match id given in URL The debug-lfs-store command is used to run the LfsProtocolServlet and, optionally, the FileLfsServlet which makes it easier to setup a local test server. [1] https://github.com/github/git-lfs/blob/master/docs/api/http-v1-batch.md [2] https://github.com/github/git-lfs/tree/master/docs/api Bug: 472961 Change-Id: I7378da5575159d2195138d799704880c5c82d5f3 Signed-off-by: Matthias Sohn <matthias.sohn@sap.com> Signed-off-by: Sasa Zivkov <sasa.zivkov@sap.com>
8 years ago
Support LFS protocol and a file system based LFS storage Implement LfsProtocolServlet handling the "Git LFS v1 Batch API" protocol [1]. Add a simple file system based LFS content store and the debug-lfs-store command to simplify testing. Introduce a LargeFileRepository interface to enable additional storage implementation while reusing the same protocol implementation. At the client side we have to configure the lfs.url, specify that we use the batch API and we don't use authentication: [lfs] url = http://host:port/lfs batch = true [lfs "http://host:port/lfs"] access = none the git-lfs client appends the "objects/batch" to the lfs.url. Hard code an Authorization header in the FileLfsRepository.getAction because then git-lfs client will skip asking for credentials. It will just forward the Authorization header from the response to the download/upload request. The FileLfsServlet supports file content storage for "Large File Storage" (LFS) server as defined by the Github LFS API [2]. - upload and download of large files is probably network bound hence use an asynchronous servlet for good scalability - simple object storage in file system with 2 level fan-out - use LockFile to protect writing large objects against multiple concurrent uploads of the same object - to prevent corrupt uploads the uploaded file is rejected if its hash doesn't match id given in URL The debug-lfs-store command is used to run the LfsProtocolServlet and, optionally, the FileLfsServlet which makes it easier to setup a local test server. [1] https://github.com/github/git-lfs/blob/master/docs/api/http-v1-batch.md [2] https://github.com/github/git-lfs/tree/master/docs/api Bug: 472961 Change-Id: I7378da5575159d2195138d799704880c5c82d5f3 Signed-off-by: Matthias Sohn <matthias.sohn@sap.com> Signed-off-by: Sasa Zivkov <sasa.zivkov@sap.com>
8 years ago
Support LFS protocol and a file system based LFS storage Implement LfsProtocolServlet handling the "Git LFS v1 Batch API" protocol [1]. Add a simple file system based LFS content store and the debug-lfs-store command to simplify testing. Introduce a LargeFileRepository interface to enable additional storage implementation while reusing the same protocol implementation. At the client side we have to configure the lfs.url, specify that we use the batch API and we don't use authentication: [lfs] url = http://host:port/lfs batch = true [lfs "http://host:port/lfs"] access = none the git-lfs client appends the "objects/batch" to the lfs.url. Hard code an Authorization header in the FileLfsRepository.getAction because then git-lfs client will skip asking for credentials. It will just forward the Authorization header from the response to the download/upload request. The FileLfsServlet supports file content storage for "Large File Storage" (LFS) server as defined by the Github LFS API [2]. - upload and download of large files is probably network bound hence use an asynchronous servlet for good scalability - simple object storage in file system with 2 level fan-out - use LockFile to protect writing large objects against multiple concurrent uploads of the same object - to prevent corrupt uploads the uploaded file is rejected if its hash doesn't match id given in URL The debug-lfs-store command is used to run the LfsProtocolServlet and, optionally, the FileLfsServlet which makes it easier to setup a local test server. [1] https://github.com/github/git-lfs/blob/master/docs/api/http-v1-batch.md [2] https://github.com/github/git-lfs/tree/master/docs/api Bug: 472961 Change-Id: I7378da5575159d2195138d799704880c5c82d5f3 Signed-off-by: Matthias Sohn <matthias.sohn@sap.com> Signed-off-by: Sasa Zivkov <sasa.zivkov@sap.com>
8 years ago
Support LFS protocol and a file system based LFS storage Implement LfsProtocolServlet handling the "Git LFS v1 Batch API" protocol [1]. Add a simple file system based LFS content store and the debug-lfs-store command to simplify testing. Introduce a LargeFileRepository interface to enable additional storage implementation while reusing the same protocol implementation. At the client side we have to configure the lfs.url, specify that we use the batch API and we don't use authentication: [lfs] url = http://host:port/lfs batch = true [lfs "http://host:port/lfs"] access = none the git-lfs client appends the "objects/batch" to the lfs.url. Hard code an Authorization header in the FileLfsRepository.getAction because then git-lfs client will skip asking for credentials. It will just forward the Authorization header from the response to the download/upload request. The FileLfsServlet supports file content storage for "Large File Storage" (LFS) server as defined by the Github LFS API [2]. - upload and download of large files is probably network bound hence use an asynchronous servlet for good scalability - simple object storage in file system with 2 level fan-out - use LockFile to protect writing large objects against multiple concurrent uploads of the same object - to prevent corrupt uploads the uploaded file is rejected if its hash doesn't match id given in URL The debug-lfs-store command is used to run the LfsProtocolServlet and, optionally, the FileLfsServlet which makes it easier to setup a local test server. [1] https://github.com/github/git-lfs/blob/master/docs/api/http-v1-batch.md [2] https://github.com/github/git-lfs/tree/master/docs/api Bug: 472961 Change-Id: I7378da5575159d2195138d799704880c5c82d5f3 Signed-off-by: Matthias Sohn <matthias.sohn@sap.com> Signed-off-by: Sasa Zivkov <sasa.zivkov@sap.com>
8 years ago
Support LFS protocol and a file system based LFS storage Implement LfsProtocolServlet handling the "Git LFS v1 Batch API" protocol [1]. Add a simple file system based LFS content store and the debug-lfs-store command to simplify testing. Introduce a LargeFileRepository interface to enable additional storage implementation while reusing the same protocol implementation. At the client side we have to configure the lfs.url, specify that we use the batch API and we don't use authentication: [lfs] url = http://host:port/lfs batch = true [lfs "http://host:port/lfs"] access = none the git-lfs client appends the "objects/batch" to the lfs.url. Hard code an Authorization header in the FileLfsRepository.getAction because then git-lfs client will skip asking for credentials. It will just forward the Authorization header from the response to the download/upload request. The FileLfsServlet supports file content storage for "Large File Storage" (LFS) server as defined by the Github LFS API [2]. - upload and download of large files is probably network bound hence use an asynchronous servlet for good scalability - simple object storage in file system with 2 level fan-out - use LockFile to protect writing large objects against multiple concurrent uploads of the same object - to prevent corrupt uploads the uploaded file is rejected if its hash doesn't match id given in URL The debug-lfs-store command is used to run the LfsProtocolServlet and, optionally, the FileLfsServlet which makes it easier to setup a local test server. [1] https://github.com/github/git-lfs/blob/master/docs/api/http-v1-batch.md [2] https://github.com/github/git-lfs/tree/master/docs/api Bug: 472961 Change-Id: I7378da5575159d2195138d799704880c5c82d5f3 Signed-off-by: Matthias Sohn <matthias.sohn@sap.com> Signed-off-by: Sasa Zivkov <sasa.zivkov@sap.com>
8 years ago
Support LFS protocol and a file system based LFS storage Implement LfsProtocolServlet handling the "Git LFS v1 Batch API" protocol [1]. Add a simple file system based LFS content store and the debug-lfs-store command to simplify testing. Introduce a LargeFileRepository interface to enable additional storage implementation while reusing the same protocol implementation. At the client side we have to configure the lfs.url, specify that we use the batch API and we don't use authentication: [lfs] url = http://host:port/lfs batch = true [lfs "http://host:port/lfs"] access = none the git-lfs client appends the "objects/batch" to the lfs.url. Hard code an Authorization header in the FileLfsRepository.getAction because then git-lfs client will skip asking for credentials. It will just forward the Authorization header from the response to the download/upload request. The FileLfsServlet supports file content storage for "Large File Storage" (LFS) server as defined by the Github LFS API [2]. - upload and download of large files is probably network bound hence use an asynchronous servlet for good scalability - simple object storage in file system with 2 level fan-out - use LockFile to protect writing large objects against multiple concurrent uploads of the same object - to prevent corrupt uploads the uploaded file is rejected if its hash doesn't match id given in URL The debug-lfs-store command is used to run the LfsProtocolServlet and, optionally, the FileLfsServlet which makes it easier to setup a local test server. [1] https://github.com/github/git-lfs/blob/master/docs/api/http-v1-batch.md [2] https://github.com/github/git-lfs/tree/master/docs/api Bug: 472961 Change-Id: I7378da5575159d2195138d799704880c5c82d5f3 Signed-off-by: Matthias Sohn <matthias.sohn@sap.com> Signed-off-by: Sasa Zivkov <sasa.zivkov@sap.com>
8 years ago
123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104
  1. ANNOTATION_ELEMENT_TYPE_ADDED_FIELD=Error
  2. ANNOTATION_ELEMENT_TYPE_ADDED_METHOD_WITHOUT_DEFAULT_VALUE=Error
  3. ANNOTATION_ELEMENT_TYPE_CHANGED_TYPE_CONVERSION=Error
  4. ANNOTATION_ELEMENT_TYPE_REMOVED_FIELD=Error
  5. ANNOTATION_ELEMENT_TYPE_REMOVED_METHOD=Error
  6. ANNOTATION_ELEMENT_TYPE_REMOVED_TYPE_MEMBER=Error
  7. API_COMPONENT_ELEMENT_TYPE_REMOVED_API_TYPE=Error
  8. API_COMPONENT_ELEMENT_TYPE_REMOVED_REEXPORTED_API_TYPE=Error
  9. API_COMPONENT_ELEMENT_TYPE_REMOVED_REEXPORTED_TYPE=Error
  10. API_COMPONENT_ELEMENT_TYPE_REMOVED_TYPE=Error
  11. API_USE_SCAN_FIELD_SEVERITY=Error
  12. API_USE_SCAN_METHOD_SEVERITY=Error
  13. API_USE_SCAN_TYPE_SEVERITY=Error
  14. CLASS_ELEMENT_TYPE_ADDED_FIELD=Error
  15. CLASS_ELEMENT_TYPE_ADDED_METHOD=Error
  16. CLASS_ELEMENT_TYPE_ADDED_RESTRICTIONS=Error
  17. CLASS_ELEMENT_TYPE_ADDED_TYPE_PARAMETER=Error
  18. CLASS_ELEMENT_TYPE_CHANGED_CONTRACTED_SUPERINTERFACES_SET=Error
  19. CLASS_ELEMENT_TYPE_CHANGED_DECREASE_ACCESS=Error
  20. CLASS_ELEMENT_TYPE_CHANGED_NON_ABSTRACT_TO_ABSTRACT=Error
  21. CLASS_ELEMENT_TYPE_CHANGED_NON_FINAL_TO_FINAL=Error
  22. CLASS_ELEMENT_TYPE_CHANGED_TYPE_CONVERSION=Error
  23. CLASS_ELEMENT_TYPE_REMOVED_CONSTRUCTOR=Error
  24. CLASS_ELEMENT_TYPE_REMOVED_FIELD=Error
  25. CLASS_ELEMENT_TYPE_REMOVED_METHOD=Error
  26. CLASS_ELEMENT_TYPE_REMOVED_SUPERCLASS=Error
  27. CLASS_ELEMENT_TYPE_REMOVED_TYPE_MEMBER=Error
  28. CLASS_ELEMENT_TYPE_REMOVED_TYPE_PARAMETER=Error
  29. CONSTRUCTOR_ELEMENT_TYPE_ADDED_TYPE_PARAMETER=Error
  30. CONSTRUCTOR_ELEMENT_TYPE_CHANGED_DECREASE_ACCESS=Error
  31. CONSTRUCTOR_ELEMENT_TYPE_CHANGED_VARARGS_TO_ARRAY=Error
  32. CONSTRUCTOR_ELEMENT_TYPE_REMOVED_TYPE_PARAMETER=Error
  33. ENUM_ELEMENT_TYPE_CHANGED_CONTRACTED_SUPERINTERFACES_SET=Error
  34. ENUM_ELEMENT_TYPE_CHANGED_TYPE_CONVERSION=Error
  35. ENUM_ELEMENT_TYPE_REMOVED_ENUM_CONSTANT=Error
  36. ENUM_ELEMENT_TYPE_REMOVED_FIELD=Error
  37. ENUM_ELEMENT_TYPE_REMOVED_METHOD=Error
  38. ENUM_ELEMENT_TYPE_REMOVED_TYPE_MEMBER=Error
  39. FIELD_ELEMENT_TYPE_ADDED_VALUE=Error
  40. FIELD_ELEMENT_TYPE_CHANGED_DECREASE_ACCESS=Error
  41. FIELD_ELEMENT_TYPE_CHANGED_FINAL_TO_NON_FINAL_STATIC_CONSTANT=Error
  42. FIELD_ELEMENT_TYPE_CHANGED_NON_FINAL_TO_FINAL=Error
  43. FIELD_ELEMENT_TYPE_CHANGED_NON_STATIC_TO_STATIC=Error
  44. FIELD_ELEMENT_TYPE_CHANGED_STATIC_TO_NON_STATIC=Error
  45. FIELD_ELEMENT_TYPE_CHANGED_TYPE=Error
  46. FIELD_ELEMENT_TYPE_CHANGED_VALUE=Error
  47. FIELD_ELEMENT_TYPE_REMOVED_TYPE_ARGUMENT=Error
  48. FIELD_ELEMENT_TYPE_REMOVED_VALUE=Error
  49. ILLEGAL_EXTEND=Warning
  50. ILLEGAL_IMPLEMENT=Warning
  51. ILLEGAL_INSTANTIATE=Warning
  52. ILLEGAL_OVERRIDE=Warning
  53. ILLEGAL_REFERENCE=Warning
  54. INTERFACE_ELEMENT_TYPE_ADDED_DEFAULT_METHOD=Error
  55. INTERFACE_ELEMENT_TYPE_ADDED_FIELD=Error
  56. INTERFACE_ELEMENT_TYPE_ADDED_METHOD=Error
  57. INTERFACE_ELEMENT_TYPE_ADDED_RESTRICTIONS=Error
  58. INTERFACE_ELEMENT_TYPE_ADDED_SUPER_INTERFACE_WITH_METHODS=Error
  59. INTERFACE_ELEMENT_TYPE_ADDED_TYPE_PARAMETER=Error
  60. INTERFACE_ELEMENT_TYPE_CHANGED_CONTRACTED_SUPERINTERFACES_SET=Error
  61. INTERFACE_ELEMENT_TYPE_CHANGED_TYPE_CONVERSION=Error
  62. INTERFACE_ELEMENT_TYPE_REMOVED_FIELD=Error
  63. INTERFACE_ELEMENT_TYPE_REMOVED_METHOD=Error
  64. INTERFACE_ELEMENT_TYPE_REMOVED_TYPE_MEMBER=Error
  65. INTERFACE_ELEMENT_TYPE_REMOVED_TYPE_PARAMETER=Error
  66. INVALID_ANNOTATION=Ignore
  67. INVALID_JAVADOC_TAG=Ignore
  68. INVALID_REFERENCE_IN_SYSTEM_LIBRARIES=Error
  69. LEAK_EXTEND=Warning
  70. LEAK_FIELD_DECL=Warning
  71. LEAK_IMPLEMENT=Warning
  72. LEAK_METHOD_PARAM=Warning
  73. LEAK_METHOD_RETURN_TYPE=Warning
  74. METHOD_ELEMENT_TYPE_ADDED_RESTRICTIONS=Error
  75. METHOD_ELEMENT_TYPE_ADDED_TYPE_PARAMETER=Error
  76. METHOD_ELEMENT_TYPE_CHANGED_DECREASE_ACCESS=Error
  77. METHOD_ELEMENT_TYPE_CHANGED_NON_ABSTRACT_TO_ABSTRACT=Error
  78. METHOD_ELEMENT_TYPE_CHANGED_NON_FINAL_TO_FINAL=Error
  79. METHOD_ELEMENT_TYPE_CHANGED_NON_STATIC_TO_STATIC=Error
  80. METHOD_ELEMENT_TYPE_CHANGED_STATIC_TO_NON_STATIC=Error
  81. METHOD_ELEMENT_TYPE_CHANGED_VARARGS_TO_ARRAY=Error
  82. METHOD_ELEMENT_TYPE_REMOVED_ANNOTATION_DEFAULT_VALUE=Error
  83. METHOD_ELEMENT_TYPE_REMOVED_TYPE_PARAMETER=Error
  84. MISSING_EE_DESCRIPTIONS=Warning
  85. TYPE_PARAMETER_ELEMENT_TYPE_ADDED_CLASS_BOUND=Error
  86. TYPE_PARAMETER_ELEMENT_TYPE_ADDED_INTERFACE_BOUND=Error
  87. TYPE_PARAMETER_ELEMENT_TYPE_CHANGED_CLASS_BOUND=Error
  88. TYPE_PARAMETER_ELEMENT_TYPE_CHANGED_INTERFACE_BOUND=Error
  89. TYPE_PARAMETER_ELEMENT_TYPE_REMOVED_CLASS_BOUND=Error
  90. TYPE_PARAMETER_ELEMENT_TYPE_REMOVED_INTERFACE_BOUND=Error
  91. UNUSED_PROBLEM_FILTERS=Warning
  92. automatically_removed_unused_problem_filters=false
  93. changed_execution_env=Error
  94. eclipse.preferences.version=1
  95. incompatible_api_component_version=Error
  96. incompatible_api_component_version_include_major_without_breaking_change=Disabled
  97. incompatible_api_component_version_include_minor_without_api_change=Disabled
  98. incompatible_api_component_version_report_major_without_breaking_change=Warning
  99. incompatible_api_component_version_report_minor_without_api_change=Ignore
  100. invalid_since_tag_version=Error
  101. malformed_since_tag=Error
  102. missing_since_tag=Error
  103. report_api_breakage_when_major_version_incremented=Disabled
  104. report_resolution_errors_api_component=Warning