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.

release-notes.apt.vm 8.0KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259
  1. -----
  2. Release Notes for Archiva ${project.version}
  3. -----
  4. ~~ Licensed to the Apache Software Foundation (ASF) under one
  5. ~~ or more contributor license agreements. See the NOTICE file
  6. ~~ distributed with this work for additional information
  7. ~~ regarding copyright ownership. The ASF licenses this file
  8. ~~ to you under the Apache License, Version 2.0 (the
  9. ~~ "License"); you may not use this file except in compliance
  10. ~~ with the License. You may obtain a copy of the License at
  11. ~~
  12. ~~ http://www.apache.org/licenses/LICENSE-2.0
  13. ~~
  14. ~~ Unless required by applicable law or agreed to in writing,
  15. ~~ software distributed under the License is distributed on an
  16. ~~ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
  17. ~~ KIND, either express or implied. See the License for the
  18. ~~ specific language governing permissions and limitations
  19. ~~ under the License.
  20. Release Notes for Archiva ${project.version}
  21. The Apache Archiva team is pleased to announce the release of Archiva
  22. ${project.version}. Archiva is {{{http://archiva.apache.org/download.html}
  23. available for download from the web site}}.
  24. Archiva is an application for managing one or more remote repositories,
  25. including administration, artifact handling, browsing and searching.
  26. If you have any questions, please consult:
  27. * the web site: {{http://archiva.apache.org/}}
  28. * the archiva-user mailing list: {{http://archiva.apache.org/mailing-lists.html}}
  29. * New in Archiva ${project.version}
  30. Apache Archiva ${project.version} is a security fix release:
  31. ** Compatibility Changes
  32. * There are no compatibility changes
  33. ** New Feature
  34. * There are no new features in this release.
  35. ** Improvements
  36. * There are no improvements
  37. ** Bug/Security Fix
  38. * CVE-2022-29405 Apache Archiva Arbitrary user password reset vulnerability
  39. Previous Release Notes
  40. * Release Notes for Archiva 2.2.7
  41. Apache Archiva 2.2.7 is a security fix release:
  42. Released: 2022-12-22
  43. ** Compatibility Changes
  44. * [MRM-2021] There is a new flag 'literalVersion=true/false' for service archivaServices/searchService/artifact
  45. which allows to change the behaviour for v=LATEST search.
  46. ** New Feature
  47. * There are no new features in this release.
  48. ** Improvements
  49. * There are no improvements
  50. ** Bug/Security Fix
  51. * [MRM-2027] Update of the log4j2 version to 2.17.0
  52. * [MRM-2020] Fixed the behaviour of the startup script, if ARCHIVA_BASE is set (separating installation and data directory)
  53. * [MRM-2022] Fixed the handling of X-XSRF-TOKEN header in Javascript calls
  54. * Release Notes for Archiva 2.2.6
  55. Apache Archiva 2.2.6 is a security fix release:
  56. Released: 2021-12-15
  57. ** Compatibility Changes
  58. * No API changes or known side effects.
  59. ** New Feature
  60. * There are no new features in this release.
  61. ** Improvements
  62. * There are no improvements
  63. ** Bug/Security Fix
  64. * Update of the log4j2 version to mitigate the log4j2 vulnerability (CVE-2021-44228)
  65. * Deactivated directory listings by the file servlet
  66. * Release Notes for Archiva 2.2.5
  67. Apache Archiva 2.2.5 is a bug fix release:
  68. Released: 2020-06-19
  69. ** Compatibility Changes
  70. * No API changes or known side effects.
  71. ** New Feature
  72. * There are no new features in this release.
  73. ** Improvements
  74. * There are no improvements
  75. ** Bug Fix
  76. * [MRM-2008] Fix for group names with slashes
  77. * Better handling of LDAP filter
  78. * Release Notes for Archiva 2.2.4
  79. Apache Archiva 2.2.4 is a bug fix release:
  80. * Fixes for handling of artifacts
  81. * Improved validation of REST calls
  82. ** Compatibility Changes
  83. No API changes or known side effects.
  84. Released: 2019-04-30
  85. ** New Feature
  86. * There are no new features in this release.
  87. ** Improvements
  88. * Adding additional validation to REST service calls for artifact upload
  89. ** Bug Fix
  90. * [MRM-1972] Stored XSS in Web UI Organization Name
  91. * [MRM-1966] Repository-purge not working
  92. * [MRM-1958] Purge by retention count deletes files but leaves history on website.
  93. * [MRM-1929] Repository purge is not reflected in index
  94. * Release Notes for Archiva 2.2.3
  95. ** New in Archiva 2.2.3
  96. Apache Archiva 2.2.3 is a bug fix release:
  97. >>>>>>> Stashed changes
  98. * Some fixes for the REST API were added to detect requests from unknown origin
  99. * Some bugfixes were added
  100. * Compatibility Changes
  101. * The REST services are now checking for the origin of the requests by analysing Origin
  102. and Referer header of the HTTP requests and adding an validation token to the Header.
  103. This prevents requests from malicious sites if they are open in the same browser. If you use
  104. the REST services from other clients you may change the behaviour with the new
  105. configuration properties for the redback security (<<<rest.csrffilter.*>>>, <<<rest.baseUrl>>>).
  106. For more information see {{{./adminguide/customising-security.html}Archiva Security Configuration}} and
  107. the {{{/redback/integration/rest.html}Redback REST documentation }}.
  108. <<Note:>> If your archiva installation is behind a reverse proxy or load balancer, it may be possible
  109. that the Archiva Web UI does not load after the upgrade. If this is the case you may access the WebUI
  110. via localhost or edit archiva.xml manually. In the "Redback Runtime Configuration" properties you have to
  111. enter the base URLs of your archiva installation to the <<<rest.baseUrl>>> field.
  112. * Archiva uses redback for authentication and authorization in version 2.6
  113. * Release Notes
  114. The Archiva ${project.version} features set can be seen in the {{{./tour/index.html} feature tour}}.
  115. * Changes in Archiva ${project.version}
  116. Released: <<${releaseDate}>>
  117. ** New Feature
  118. ** Improvement
  119. * [MRM-1925] - Make User-Agent header configurable for HTTP requests
  120. * [MRM-1861], [MRM-1924] - Increasing timeouts for repository check
  121. * [MRM-1937] - Prevent creating initial admin user with wrong name.
  122. * Adding origin header validation checks for REST requests
  123. ** Bugs fixed
  124. * [MRM-1859] - Error upon viewing 'Artifacts' tab when browsing an artifact
  125. * [MRM-1874] - Login Dialog triggers multiple events (+messages)
  126. * [MRM-1908] - Logged on users can write any repository
  127. * [MRM-1909] - Remote repository check fails for https://repo.maven.apache.org/maven2
  128. * [MRM-1923] - Fixing bind issue with certain ldap servers, when user not found
  129. * [MRM-1926] - Invalid checksum files in Archiva repository after download from remote repository
  130. * [MRM-1928] - Bad redirect URL when using Archiva through HTTP reverse proxy
  131. * [MRM-1933] - No message body writer has been found for class org.apache.archiva.rest.services.ArchivaRestError
  132. * [MRM-1940] - Slashes appended to remote repo url
  133. ** Task
  134. * History
  135. Archiva was started in November 2005, building a simple framework on top of some existing repository conversion
  136. tools within the Maven project. Initial development focused on repository conversion, error reporting, and indexing.
  137. From January 2006 a web application was started to visualise the information and to start incorporating
  138. functionality from the unmaintained maven-proxy project.
  139. Development continued through many stops and starts. Initial versions of Archiva were built from source by contributors,
  140. and the first alpha version was not released until April 2007. Some significant changes were made to improve
  141. performance and functionality in June 2007 and over the next 6 months and a series of alpha and beta releases, a concerted effort
  142. was made to release the 1.0 version.
  143. Archiva became an Apache "top level project" in March 2008.