[
https://issues.apache.org/jira/browse/NET-710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sebb resolved NET-710.
--
Resolution: Not A Problem
OK, glad your issue has been solved.
If there is some Javadoc or other documentation that
[
https://issues.apache.org/jira/browse/NET-710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17844357#comment-17844357
]
Sebb commented on NET-710:
--
Remember that the listing is generated in the timezone of the server, so
timestamps
[
https://issues.apache.org/jira/browse/NET-710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17844338#comment-17844338
]
Sebb commented on NET-710:
--
I still cannot reproduce the issue.
What TZ are you running the test under?
Note that
[
https://issues.apache.org/jira/browse/NET-710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17844233#comment-17844233
]
Sebb commented on NET-710:
--
I've added a separate branch which tests against the release jars from 3.7
through to
[
https://issues.apache.org/jira/browse/NET-710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17844070#comment-17844070
]
Sebb commented on NET-710:
--
Cannot reproduce the error on 3.10.0 or 3.9.0 using Java8 and Ubuntu.
See the GHA log
[
https://issues.apache.org/jira/browse/IO-851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17832224#comment-17832224
]
Sebb commented on IO-851:
-
That's IllegalArgumentException, not IllegalStateException.
I just did a search for
Sebb created IO-851:
---
Summary: FileSystemUtils no longer throws IllegalStateException
Key: IO-851
URL: https://issues.apache.org/jira/browse/IO-851
Project: Commons IO
Issue Type: Bug
[
https://issues.apache.org/jira/browse/COMPRESS-651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17824955#comment-17824955
]
Sebb commented on COMPRESS-651:
---
I tried halving BZip2Constants.BASEBLOCKSIZE to 50_000, and the output
[
https://issues.apache.org/jira/browse/IO-413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sebb resolved IO-413.
-
Resolution: Won't Do
Agreed
> deleteQuietly(File) should try to closeOnDelete too
>
[
https://issues.apache.org/jira/browse/LANG-1713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sebb reopened LANG-1713:
> ArrayUtils will return null when adding two null arrays, but undocumented
>
[
https://issues.apache.org/jira/browse/LANG-1639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sebb closed LANG-1639.
--
Resolution: Won't Do
With the advent of Java8, it's possible to do this with not much code, for
example:
[
https://issues.apache.org/jira/browse/CRYPTO-158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sebb resolved CRYPTO-158.
-
Resolution: Fixed
Fixed in {color:#22}b51442e5{color}
> Illegal reflective access
>
[
https://issues.apache.org/jira/browse/CRYPTO-136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sebb resolved CRYPTO-136.
-
Resolution: Won't Do
Needs to be redefined in terms of OpenSSL3
> Expose FIPS_mode_set() and FIPS_selftest()
[
https://issues.apache.org/jira/browse/CRYPTO-158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17791758#comment-17791758
]
Sebb commented on CRYPTO-158:
-
I have seen this regularly in tests using Java 11 on Ubuntu and macOs.
The
[
https://issues.apache.org/jira/browse/CRYPTO-136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17790274#comment-17790274
]
Sebb commented on CRYPTO-136:
-
FIPS_mode was not enabled in 1.1, and has been removed in 3.x
See
[
https://issues.apache.org/jira/browse/CRYPTO-180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sebb resolved CRYPTO-180.
-
Resolution: Fixed
> Need instructions for building distributions
>
[
https://issues.apache.org/jira/browse/CRYPTO-179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sebb resolved CRYPTO-179.
-
Resolution: Fixed
> Crash on macOS with default crypto library
> --
>
>
[
https://issues.apache.org/jira/browse/CRYPTO-132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sebb resolved CRYPTO-132.
-
Resolution: Fixed
Subsumed into CRYPTO-180
> Instructions in BUILDING.txt don't work on MacOS
>
[
https://issues.apache.org/jira/browse/CRYPTO-120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sebb resolved CRYPTO-120.
-
Resolution: Fixed
Subsumed into CRYPTO-180
> Add instructions for native build at wiki
>
Sebb created CRYPTO-180:
---
Summary: Need instructions for building distributions
Key: CRYPTO-180
URL: https://issues.apache.org/jira/browse/CRYPTO-180
Project: Commons Crypto
Issue Type: Bug
[
https://issues.apache.org/jira/browse/CRYPTO-166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sebb resolved CRYPTO-166.
-
Resolution: Fixed
> Library is reloaded multiple times
> --
>
>
[
https://issues.apache.org/jira/browse/CRYPTO-166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17789525#comment-17789525
]
Sebb commented on CRYPTO-166:
-
Library reloading was fixed by CRYPTO-168.
However, the symbols are also
[
https://issues.apache.org/jira/browse/CRYPTO-168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sebb updated CRYPTO-168:
Fix Version/s: 1.2.0
> Centralise access to the crypto dynamic library
>
[
https://issues.apache.org/jira/browse/CRYPTO-168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sebb resolved CRYPTO-168.
-
Resolution: Fixed
> Centralise access to the crypto dynamic library
>
[
https://issues.apache.org/jira/browse/CRYPTO-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17789506#comment-17789506
]
Sebb commented on CRYPTO-168:
-
This was done in:
Sebb created CRYPTO-179:
---
Summary: Crash on macOS with default crypto library
Key: CRYPTO-179
URL: https://issues.apache.org/jira/browse/CRYPTO-179
Project: Commons Crypto
Issue Type: Bug
[
https://issues.apache.org/jira/browse/CRYPTO-164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17788678#comment-17788678
]
Sebb commented on CRYPTO-164:
-
Looks like this is already being tested on ubuntu-latest.
> Add Support for
[
https://issues.apache.org/jira/browse/CRYPTO-164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17788571#comment-17788571
]
Sebb commented on CRYPTO-164:
-
Another issue is ensuring the native code can compile under 3.x, i.e. using
[
https://issues.apache.org/jira/browse/CRYPTO-164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17788569#comment-17788569
]
Sebb commented on CRYPTO-164:
-
I'm concerned that the release notes for 3.0 mention some big changes, but
[
https://issues.apache.org/jira/browse/CRYPTO-115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sebb resolved CRYPTO-115.
-
Resolution: Fixed
Can now override the default name using the property
commons.crypto.OpenSslNativeJn[ai]
>
[
https://issues.apache.org/jira/browse/CRYPTO-159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sebb resolved CRYPTO-159.
-
Resolution: Fixed
Should be fixed in latest code.
If no, please open with suitable test case
> JRE (x86) crash
[
https://issues.apache.org/jira/browse/CRYPTO-169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sebb resolved CRYPTO-169.
-
Resolution: Fixed
AFAICT, this is fixed.
Please re-open with a test that shows the issue if not
> Unable to
[
https://issues.apache.org/jira/browse/CRYPTO-147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sebb resolved CRYPTO-147.
-
Resolution: Fixed
This was fixed by CRYPTO-177
> Link in OpenSslJnaCipher code or remove as option for
[
https://issues.apache.org/jira/browse/CRYPTO-162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17788530#comment-17788530
]
Sebb commented on CRYPTO-162:
-
It's not at all clear what is wanted here.
> openSslCipher support engine
>
[
https://issues.apache.org/jira/browse/CRYPTO-156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sebb resolved CRYPTO-156.
-
Resolution: Abandoned
AFAICT this has been abandoned
> Common Class Padding, Transform and AlgorithmMode
>
[
https://issues.apache.org/jira/browse/CRYPTO-175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sebb resolved CRYPTO-175.
-
Resolution: Fixed
> JNA tests rely on JNI code
> --
>
> Key: CRYPTO-175
[
https://issues.apache.org/jira/browse/CRYPTO-164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17788186#comment-17788186
]
Sebb commented on CRYPTO-164:
-
Tests currently run under OpenSSL 3.0.x.
More tests are likely needed.
> Add
[
https://issues.apache.org/jira/browse/CRYPTO-169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17788185#comment-17788185
]
Sebb commented on CRYPTO-169:
-
OpenSslCryptoRandom static block issue reported as CRYPTO-178; now fixed
>
[
https://issues.apache.org/jira/browse/CRYPTO-178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sebb updated CRYPTO-178:
Description:
OpenSslCryptoRandom.isNativeCodeEnabled() currently throws an Exception if the
native cannot be
[
https://issues.apache.org/jira/browse/CRYPTO-178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sebb resolved CRYPTO-178.
-
Resolution: Fixed
Removed check from static block
> OpenSslCryptoRandom.isNativeCodeEnabled() throws if library
[
https://issues.apache.org/jira/browse/CRYPTO-178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17787920#comment-17787920
]
Sebb commented on CRYPTO-178:
-
For example, docker test using Ubuntu and invalid library name:
$ docker
Sebb created CRYPTO-178:
---
Summary: OpenSslCryptoRandom.isNativeCodeEnabled() throws if
library cannot be loaded
Key: CRYPTO-178
URL: https://issues.apache.org/jira/browse/CRYPTO-178
Project: Commons Crypto
[
https://issues.apache.org/jira/browse/CRYPTO-169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17787684#comment-17787684
]
Sebb commented on CRYPTO-169:
-
I think there is a problem with the recent changes to OpenSslCryptoRandom.
It
[
https://issues.apache.org/jira/browse/CRYPTO-177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sebb resolved CRYPTO-177.
-
Resolution: Fixed
> Cipher and Random Factory classes don't include JNA
>
[
https://issues.apache.org/jira/browse/CRYPTO-177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sebb updated CRYPTO-177:
Summary: Cipher and Random Factory classes don't include JNA (was: Cipher
and Random Factor classes don't include
[
https://issues.apache.org/jira/browse/CRYPTO-171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sebb resolved CRYPTO-171.
-
Resolution: Fixed
No longer needed, now that 1.0.x is no longer supported
> OpenSslCryptoRandomNative.c uses
[
https://issues.apache.org/jira/browse/CRYPTO-173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sebb resolved CRYPTO-173.
-
Resolution: Fixed
> docker build does not work on macOS M1
> --
>
>
Sebb created CRYPTO-177:
---
Summary: Cipher and Random Factor classes don't include JNA
Key: CRYPTO-177
URL: https://issues.apache.org/jira/browse/CRYPTO-177
Project: Commons Crypto
Issue Type: Bug
[
https://issues.apache.org/jira/browse/CRYPTO-176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sebb resolved CRYPTO-176.
-
Resolution: Won't Fix
> Drop dependency on Commons IO?
> --
>
> Key:
[
https://issues.apache.org/jira/browse/CRYPTO-176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17784623#comment-17784623
]
Sebb commented on CRYPTO-176:
-
There is bound to be some code duplication across components, so I don't see
[
https://issues.apache.org/jira/browse/CRYPTO-176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17784514#comment-17784514
]
Sebb commented on CRYPTO-176:
-
Note that there are already versions of readFully and closeQuietly in
[
https://issues.apache.org/jira/browse/CRYPTO-176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17784514#comment-17784514
]
Sebb edited comment on CRYPTO-176 at 11/9/23 3:29 PM:
--
Note that there are already
Sebb created CRYPTO-176:
---
Summary: Drop dependency on Commons IO?
Key: CRYPTO-176
URL: https://issues.apache.org/jira/browse/CRYPTO-176
Project: Commons Crypto
Issue Type: Improvement
Sebb created CRYPTO-175:
---
Summary: JNA tests rely on JNI code
Key: CRYPTO-175
URL: https://issues.apache.org/jira/browse/CRYPTO-175
Project: Commons Crypto
Issue Type: Bug
Reporter: Sebb
[
https://issues.apache.org/jira/browse/CRYPTO-174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sebb resolved CRYPTO-174.
-
Resolution: Fixed
> Allow override of SSL library name
> --
>
>
Sebb created CRYPTO-174:
---
Summary: Allow override of SSL library name
Key: CRYPTO-174
URL: https://issues.apache.org/jira/browse/CRYPTO-174
Project: Commons Crypto
Issue Type: New Feature
[
https://issues.apache.org/jira/browse/CRYPTO-167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sebb resolved CRYPTO-167.
-
Resolution: Fixed
> Cannot use env to report missing env!
> -
>
>
[
https://issues.apache.org/jira/browse/CRYPTO-167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17782940#comment-17782940
]
Sebb commented on CRYPTO-167:
-
I now think this issue is wrong; the problem is that the code should not be
[
https://issues.apache.org/jira/browse/CRYPTO-172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sebb resolved CRYPTO-172.
-
Resolution: Fixed
> Add support for Linux-riscv64
> -
>
> Key:
[
https://issues.apache.org/jira/browse/CRYPTO-170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sebb resolved CRYPTO-170.
-
Resolution: Fixed
Using the appropriate definition for jni.library.path (and the same for
jna.library.path)
Sebb created CRYPTO-173:
---
Summary: docker build does not work on macOS M1
Key: CRYPTO-173
URL: https://issues.apache.org/jira/browse/CRYPTO-173
Project: Commons Crypto
Issue Type: Bug
[
https://issues.apache.org/jira/browse/CRYPTO-170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17781831#comment-17781831
]
Sebb commented on CRYPTO-170:
-
It looks like this can be avoided by defining jni.library.path and
[
https://issues.apache.org/jira/browse/CRYPTO-133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sebb resolved CRYPTO-133.
-
Resolution: Feedback Received
Seems to be resolved
> OpenSslCryptoRandomNative.nextRandBytes not thread safe
>
[
https://issues.apache.org/jira/browse/CRYPTO-150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sebb resolved CRYPTO-150.
-
Resolution: Duplicate
> An illegal reflective access operation has occurred
>
[
https://issues.apache.org/jira/browse/CRYPTO-144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sebb resolved CRYPTO-144.
-
Resolution: Duplicate
> Illegal reflective access by
> org.apache.commons.crypto.stream.CryptoInputStream
>
[
https://issues.apache.org/jira/browse/CRYPTO-158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17780738#comment-17780738
]
Sebb commented on CRYPTO-158:
-
The class CryptoInputStream does currently use reflection to deallocate the
[
https://issues.apache.org/jira/browse/CRYPTO-166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17780733#comment-17780733
]
Sebb commented on CRYPTO-166:
-
I wonder if this is related to CRYPTO-170?
> Library is reloaded multiple
[
https://issues.apache.org/jira/browse/CRYPTO-167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17780732#comment-17780732
]
Sebb commented on CRYPTO-167:
-
[~adbhonsle] If you have a GitHub account, feel free to raise a PR to fix the
Sebb created CRYPTO-171:
---
Summary: OpenSslCryptoRandomNative.c uses syscall(2) which is
deprecated on macos M1
Key: CRYPTO-171
URL: https://issues.apache.org/jira/browse/CRYPTO-171
Project: Commons Crypto
Sebb created CRYPTO-170:
---
Summary: Test fails with "java is loading libcrypto in an unsafe
way" on macos-11/Java21
Key: CRYPTO-170
URL: https://issues.apache.org/jira/browse/CRYPTO-170
Project: Commons Crypto
[
https://issues.apache.org/jira/browse/VALIDATOR-368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17779802#comment-17779802
]
Sebb commented on VALIDATOR-368:
Seems to me that this changes the behaviour of the existing
[
https://issues.apache.org/jira/browse/IO-427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17778557#comment-17778557
]
Sebb commented on IO-427:
-
Why don't you just write the stream to a temporary file, and check the hash on
end of
[
https://issues.apache.org/jira/browse/CRYPTO-169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17778316#comment-17778316
]
Sebb commented on CRYPTO-169:
-
That should be OK.
> Unable to load native library on Apple Silicon (M1 Mac)
[
https://issues.apache.org/jira/browse/CRYPTO-169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17778297#comment-17778297
]
Sebb commented on CRYPTO-169:
-
No, it is never acceptable to catch Throwable. Some exceptions should never be
[
https://issues.apache.org/jira/browse/COMMONSSITE-129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17778098#comment-17778098
]
Sebb commented on COMMONSSITE-129:
--
Note that Maven 4 does not support the Ant Mojo Extractor (or
[
https://issues.apache.org/jira/browse/COMMONSSITE-46?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sebb resolved COMMONSSITE-46.
-
Resolution: Abandoned
The rc profile no longer exists
> Multi-module projects fail when using the
[
https://issues.apache.org/jira/browse/COMMONSSITE-167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17778096#comment-17778096
]
Sebb commented on COMMONSSITE-167:
--
See also https://issues.apache.org/jira/browse/RNG-38
>
[
https://issues.apache.org/jira/browse/COMMONSSITE-150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17778095#comment-17778095
]
Sebb commented on COMMONSSITE-150:
--
Need more detail if this is to be resolved. The mail link is
[
https://issues.apache.org/jira/browse/COMMONSSITE-85?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sebb resolved COMMONSSITE-85.
-
Resolution: Fixed
Original issue fixed some while ago
> https for images
>
>
>
Sebb created COMMONSSITE-167:
Summary: [build-plugin] makes assumptions about workflow names to
create badges
Key: COMMONSSITE-167
URL: https://issues.apache.org/jira/browse/COMMONSSITE-167
Project:
[
https://issues.apache.org/jira/browse/JEXL-408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17776931#comment-17776931
]
Sebb commented on JEXL-408:
---
I am happy with the create() method, as that makes it easy to enable a few
specific
[
https://issues.apache.org/jira/browse/JEXL-410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17776928#comment-17776928
]
Sebb commented on JEXL-410:
---
It's not about convenience, it's about not honouring the Javadoc.
As to breaking
[
https://issues.apache.org/jira/browse/JEXL-410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17776765#comment-17776765
]
Sebb commented on JEXL-410:
---
I think that is the wrong fix.
I think the original Javadoc should be honoured; that
[
https://issues.apache.org/jira/browse/JEXL-408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17776759#comment-17776759
]
Sebb commented on JEXL-408:
---
It is also tedious to create an instance that disables a single feature.
Originally
Sebb created JEXL-410:
-
Summary: JexlFeatures: ctor does not enable all features
Key: JEXL-410
URL: https://issues.apache.org/jira/browse/JEXL-410
Project: Commons JEXL
Issue Type: Bug
Sebb created JEXL-409:
-
Summary: Disable LEXICAL should disable LEXICAL_SHADE
Key: JEXL-409
URL: https://issues.apache.org/jira/browse/JEXL-409
Project: Commons JEXL
Issue Type: Bug
Sebb created JEXL-408:
-
Summary: Using JexlFeatures is tedious
Key: JEXL-408
URL: https://issues.apache.org/jira/browse/JEXL-408
Project: Commons JEXL
Issue Type: Improvement
Reporter: Sebb
[
https://issues.apache.org/jira/browse/IO-414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17772886#comment-17772886
]
Sebb commented on IO-414:
-
e.g.
https://github.com/apache/commons-io/actions/runs/6441844619/job/17492833682
Looks
[
https://issues.apache.org/jira/browse/IO-815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sebb resolved IO-815.
-
Resolution: Fixed
> XmlStreamReader encoding match RE is too strict
> ---
>
>
[
https://issues.apache.org/jira/browse/IO-815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17771647#comment-17771647
]
Sebb commented on IO-815:
-
Fixed in
[
https://issues.apache.org/jira/browse/IO-815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sebb updated IO-815:
Fix Version/s: 2.14.1
> XmlStreamReader encoding match RE is too strict
> ---
>
>
Sebb created IO-815:
---
Summary: XmlStreamReader encoding match RE is too strict
Key: IO-815
URL: https://issues.apache.org/jira/browse/IO-815
Project: Commons IO
Issue Type: Bug
Components:
[
https://issues.apache.org/jira/browse/VALIDATOR-490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17762218#comment-17762218
]
Sebb commented on VALIDATOR-490:
Note that you can instantiate a version of the class with updates to
[
https://issues.apache.org/jira/browse/POOL-411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17741381#comment-17741381
]
Sebb commented on POOL-411:
---
The process of upgrading the lock has an inherent window when other threads can
[
https://issues.apache.org/jira/browse/POOL-411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17741254#comment-17741254
]
Sebb commented on POOL-411:
---
I think it would be worth temporarily adding some sleeps/yields in the lock
upgrade
[
https://issues.apache.org/jira/browse/POOL-411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17740943#comment-17740943
]
Sebb commented on POOL-411:
---
To simplify testing, it might be worth temporarily adding a sleep where you
think
[
https://issues.apache.org/jira/browse/POOL-411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17740941#comment-17740941
]
Sebb commented on POOL-411:
---
Surely it should not be possible to obtain a write lock whilst others are
holding
[
https://issues.apache.org/jira/browse/IO-438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17729119#comment-17729119
]
Sebb commented on IO-438:
-
The Javadoc needs to be more specific as to when it is appropriate to use the
method.
[
https://issues.apache.org/jira/browse/COMMONSSITE-165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17688753#comment-17688753
]
Sebb commented on COMMONSSITE-165:
--
{quote}> missing version number in the sub-header
That's
[
https://issues.apache.org/jira/browse/COMMONSSITE-165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17687649#comment-17687649
]
Sebb commented on COMMONSSITE-165:
--
There were good reasons for creating Commons Skin originally; I
1 - 100 of 5344 matches
Mail list logo
