1. 07 5月, 2021 1 次提交
  2. 01 5月, 2021 1 次提交
  3. 26 4月, 2021 1 次提交
  4. 23 4月, 2021 1 次提交
  5. 22 4月, 2021 1 次提交
  6. 19 4月, 2021 4 次提交
    • D
      Fix parsing of ant version in Travis script (#1341) · b56891b3
      Daniel Widdis 提交于
    • D
      Attempting to call the Advapi32 function RegNotifyChangeKeyValue doesn't work,... · 9794ec6c
      Daniel Krügler 提交于
      Attempting to call the Advapi32 function RegNotifyChangeKeyValue doesn't work, because this method is not declared yet in interface Advapi32. This adds the missing method declaration. (#1339)
      This also adds another unit test to Advapi32Test validating basic functionality of Advapi32#RegNotifyChangeKeyValue.
      Co-authored-by: NDaniel Widdis <widdis@gmail.com>
    • D
      constant REG_NOTIFY_THREAD_AGNOSTIC has been added, which is used as (#1337) · 1988f692
      Daniel Krügler 提交于
      possible control argument for RegNotifyChangeKeyValue's dwNotifyFilter
      function argument (see nf-winreg-regnotifychangekeyvalue) and whose
      underlying integral value has the value 0x10000000 (specified on the
      page linked above). This constant is currently missing in the existing
      set of REG_NOTIFY_CHANGE_* constants in
      com.sun.jna.platform.win32.WinNT. In addition to the lack of the
      constant, the second problem is, that for Windows systems of at least
      Windows 8, the existing combined constant, which is currently defined as
                  | REG_NOTIFY_CHANGE_SECURITY;
      is incorrect, because it needs to take the additional value of
      REG_NOTIFY_THREAD_AGNOSTIC into account.
      This change requests solves both problems by (a) providing the missing
      REG_NOTIFY_THREAD_AGNOSTIC constant in com.sun.jna.platform.win32.WinNT
      and (b) by updating the existing REG_LEGAL_CHANGE_FILTER constant in
      regard to the added REG_NOTIFY_THREAD_AGNOSTIC
    • D
      HKEY_CURRENT_USER_LOCAL_SETTINGS should be supported (#1336) · b21196ef
      Daniel Krügler 提交于
      Starting with Windows 7, Windows added the additional HKEY constant HKEY_CURRENT_USER_LOCAL_SETTINGS (see predefined-key) whose underlying integral value has the value 0x80000007 (Source: Visual Studio 2017, header <winreg.h>. This constant is currently missing in the existing set of HKEY_* constants in com.sun.jna.platform.win32.WinReg. This adds the new static field HKEY_CURRENT_USER_LOCAL_SETTINGS to the set of the other HKEY constants in WinReg.
  7. 23 3月, 2021 3 次提交
  8. 18 3月, 2021 1 次提交
  9. 17 3月, 2021 1 次提交
  10. 15 3月, 2021 3 次提交
  11. 07 3月, 2021 1 次提交
  12. 28 2月, 2021 2 次提交
  13. 27 2月, 2021 1 次提交
  14. 26 2月, 2021 1 次提交
    • M
      [GH-1313] Move default darwin prefix to darwin-$arch and support darwin as fallback · ab2cb98c
      Matthias Bläsing 提交于
      The darwin platform traditionally used fatbinaries to support multiple
      architectures. This works, but is a problem:
      a) when apple decides, that only certain architectures may be
         bundled (it was reported, that the presence of x86 caused
         appstore validation to fail)
      b) when upstream does not bundle the artifacts, but builds them
         in isolation.
      Given, that JNA also hit (b) and needed post processing to merge
      binaries, moving darwin to the same scheme as other OSes (<os>-<arch>)
      is considered sensible.
      While the resource prefix is changed, the old "darwin" prefix is still
      considered for extraction and thus old libraries will continue to work.
  15. 24 2月, 2021 2 次提交
  16. 23 2月, 2021 1 次提交
    • M
      Split jpms modules into independet artifacts instead of classifier based solution · b797901f
      Matthias Bläsing 提交于
      The jna-platform artifact depends on jna - this leads to problems when
      the JPMS artifacts are used, as the pom.xml for the classifier based
      artifacts are identical to the base artifacts. This leads to
      depending on
      so the jna-platform JPMS artifacts pulls in the non-JPMS jna artifact.
      To solve this, the JPMS artifacts are moved to custom artifact ids. So
  17. 18 2月, 2021 1 次提交
  18. 13 2月, 2021 1 次提交
  19. 12 2月, 2021 1 次提交
  20. 09 2月, 2021 2 次提交
  21. 02 2月, 2021 1 次提交
  22. 01 2月, 2021 1 次提交
  23. 31 1月, 2021 2 次提交
  24. 30 1月, 2021 4 次提交
  25. 29 1月, 2021 1 次提交
  26. 28 1月, 2021 1 次提交