[jira] [Created] (CRYPTO-139) adding suuport for AARCH64 architecture in common crypto
puresoftware created CRYPTO-139: --- Summary: adding suuport for AARCH64 architecture in common crypto Key: CRYPTO-139 URL: https://issues.apache.org/jira/browse/CRYPTO-139 Project: Commons Crypto Issue Type: New Feature Reporter: puresoftware AARCH 64 architecture support is missing in the exiting common-crypto code. Now we did some modification in the code level and add the support for AARCH64. Now the common-crypto project can be used in aarch64 platform and also compatible with openssl 1.1.x. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CONFIGURATION-700) Issue With backslash(\) and Forwardslash(/)
[ https://issues.apache.org/jira/browse/CONFIGURATION-700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16471485#comment-16471485 ] Amitabh Pandey commented on CONFIGURATION-700: -- 1-Original Property File Content has been attached .I was not able to attach the property file here so I have attached the image file of the property file content 2-Code .I that I am using motioned above. In property file I have to update only id,which I am updating from 1 to 3 or any other value from code. 3-Attached with Getting output. All backslash got converted with two backslash. 4-Expecting output will be that only id should be updated and nothing else. No slash should be changed In any other tag. Hope now it will be clear. Let me know if you need anything else. > Issue With backslash(\) and Forwardslash(/) > --- > > Key: CONFIGURATION-700 > URL: https://issues.apache.org/jira/browse/CONFIGURATION-700 > Project: Commons Configuration > Issue Type: Bug > Components: Build >Affects Versions: 1.10 >Reporter: Amitabh Pandey >Priority: Major > Fix For: 1.10 > > Attachments: Getting Output.jpg, Original Property File Contenet.jpg > > > Dear Team, > I am using commons-configuration-1.10.jar for updating property file in java. > I have achieve all my requirement(Preserve comment, White space) with this > API.But stuck at one point.It is not working as per my expectations with > slash.Below is one example. > I have below url in my properties file. > *C\:ABC.net/wsdl* > Now it is getting change to below after modification > *C:ABC.net\/wsdl* > Means it is removing the backslash and changing forwardslash to \/.I know it > is escaping character. But is there any way to prevent this. I cant not > change any thing in property file. I have to handle through code only. > Because of only this issue I again moved to Java util API. > Please check fix of this. Rest is excellent. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (CONFIGURATION-700) Issue With backslash(\) and Forwardslash(/)
[ https://issues.apache.org/jira/browse/CONFIGURATION-700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amitabh Pandey updated CONFIGURATION-700: - Attachment: Getting Output.jpg > Issue With backslash(\) and Forwardslash(/) > --- > > Key: CONFIGURATION-700 > URL: https://issues.apache.org/jira/browse/CONFIGURATION-700 > Project: Commons Configuration > Issue Type: Bug > Components: Build >Affects Versions: 1.10 >Reporter: Amitabh Pandey >Priority: Major > Fix For: 1.10 > > Attachments: Getting Output.jpg, Original Property File Contenet.jpg > > > Dear Team, > I am using commons-configuration-1.10.jar for updating property file in java. > I have achieve all my requirement(Preserve comment, White space) with this > API.But stuck at one point.It is not working as per my expectations with > slash.Below is one example. > I have below url in my properties file. > *C\:ABC.net/wsdl* > Now it is getting change to below after modification > *C:ABC.net\/wsdl* > Means it is removing the backslash and changing forwardslash to \/.I know it > is escaping character. But is there any way to prevent this. I cant not > change any thing in property file. I have to handle through code only. > Because of only this issue I again moved to Java util API. > Please check fix of this. Rest is excellent. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (CONFIGURATION-700) Issue With backslash(\) and Forwardslash(/)
[ https://issues.apache.org/jira/browse/CONFIGURATION-700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amitabh Pandey updated CONFIGURATION-700: - Attachment: (was: 1.jpg) > Issue With backslash(\) and Forwardslash(/) > --- > > Key: CONFIGURATION-700 > URL: https://issues.apache.org/jira/browse/CONFIGURATION-700 > Project: Commons Configuration > Issue Type: Bug > Components: Build >Affects Versions: 1.10 >Reporter: Amitabh Pandey >Priority: Major > Fix For: 1.10 > > Attachments: Original Property File Contenet.jpg > > > Dear Team, > I am using commons-configuration-1.10.jar for updating property file in java. > I have achieve all my requirement(Preserve comment, White space) with this > API.But stuck at one point.It is not working as per my expectations with > slash.Below is one example. > I have below url in my properties file. > *C\:ABC.net/wsdl* > Now it is getting change to below after modification > *C:ABC.net\/wsdl* > Means it is removing the backslash and changing forwardslash to \/.I know it > is escaping character. But is there any way to prevent this. I cant not > change any thing in property file. I have to handle through code only. > Because of only this issue I again moved to Java util API. > Please check fix of this. Rest is excellent. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (CONFIGURATION-700) Issue With backslash(\) and Forwardslash(/)
[ https://issues.apache.org/jira/browse/CONFIGURATION-700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amitabh Pandey updated CONFIGURATION-700: - Attachment: 1.jpg > Issue With backslash(\) and Forwardslash(/) > --- > > Key: CONFIGURATION-700 > URL: https://issues.apache.org/jira/browse/CONFIGURATION-700 > Project: Commons Configuration > Issue Type: Bug > Components: Build >Affects Versions: 1.10 >Reporter: Amitabh Pandey >Priority: Major > Fix For: 1.10 > > Attachments: Original Property File Contenet.jpg > > > Dear Team, > I am using commons-configuration-1.10.jar for updating property file in java. > I have achieve all my requirement(Preserve comment, White space) with this > API.But stuck at one point.It is not working as per my expectations with > slash.Below is one example. > I have below url in my properties file. > *C\:ABC.net/wsdl* > Now it is getting change to below after modification > *C:ABC.net\/wsdl* > Means it is removing the backslash and changing forwardslash to \/.I know it > is escaping character. But is there any way to prevent this. I cant not > change any thing in property file. I have to handle through code only. > Because of only this issue I again moved to Java util API. > Please check fix of this. Rest is excellent. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (CONFIGURATION-700) Issue With backslash(\) and Forwardslash(/)
[ https://issues.apache.org/jira/browse/CONFIGURATION-700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amitabh Pandey updated CONFIGURATION-700: - Attachment: Original Property File Contenet.jpg > Issue With backslash(\) and Forwardslash(/) > --- > > Key: CONFIGURATION-700 > URL: https://issues.apache.org/jira/browse/CONFIGURATION-700 > Project: Commons Configuration > Issue Type: Bug > Components: Build >Affects Versions: 1.10 >Reporter: Amitabh Pandey >Priority: Major > Fix For: 1.10 > > Attachments: Original Property File Contenet.jpg > > > Dear Team, > I am using commons-configuration-1.10.jar for updating property file in java. > I have achieve all my requirement(Preserve comment, White space) with this > API.But stuck at one point.It is not working as per my expectations with > slash.Below is one example. > I have below url in my properties file. > *C\:ABC.net/wsdl* > Now it is getting change to below after modification > *C:ABC.net\/wsdl* > Means it is removing the backslash and changing forwardslash to \/.I know it > is escaping character. But is there any way to prevent this. I cant not > change any thing in property file. I have to handle through code only. > Because of only this issue I again moved to Java util API. > Please check fix of this. Rest is excellent. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (CONFIGURATION-700) Issue With backslash(\) and Forwardslash(/)
[ https://issues.apache.org/jira/browse/CONFIGURATION-700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amitabh Pandey updated CONFIGURATION-700: - Attachment: (was: 1.jpg) > Issue With backslash(\) and Forwardslash(/) > --- > > Key: CONFIGURATION-700 > URL: https://issues.apache.org/jira/browse/CONFIGURATION-700 > Project: Commons Configuration > Issue Type: Bug > Components: Build >Affects Versions: 1.10 >Reporter: Amitabh Pandey >Priority: Major > Fix For: 1.10 > > > Dear Team, > I am using commons-configuration-1.10.jar for updating property file in java. > I have achieve all my requirement(Preserve comment, White space) with this > API.But stuck at one point.It is not working as per my expectations with > slash.Below is one example. > I have below url in my properties file. > *C\:ABC.net/wsdl* > Now it is getting change to below after modification > *C:ABC.net\/wsdl* > Means it is removing the backslash and changing forwardslash to \/.I know it > is escaping character. But is there any way to prevent this. I cant not > change any thing in property file. I have to handle through code only. > Because of only this issue I again moved to Java util API. > Please check fix of this. Rest is excellent. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (WEAVER-26) Upgrade to commons-parent v46
Matt Benson created WEAVER-26: - Summary: Upgrade to commons-parent v46 Key: WEAVER-26 URL: https://issues.apache.org/jira/browse/WEAVER-26 Project: Commons Weaver Issue Type: Improvement Affects Versions: 1.4 Reporter: Matt Benson Assignee: Matt Benson Fix For: 1.4 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (WEAVER-26) Upgrade to commons-parent v46
[ https://issues.apache.org/jira/browse/WEAVER-26?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Benson resolved WEAVER-26. --- Resolution: Fixed b8be2baeaf10e54036b36a0d9ff6940a565192d5 > Upgrade to commons-parent v46 > - > > Key: WEAVER-26 > URL: https://issues.apache.org/jira/browse/WEAVER-26 > Project: Commons Weaver > Issue Type: Improvement >Affects Versions: 1.4 >Reporter: Matt Benson >Assignee: Matt Benson >Priority: Major > Fix For: 1.4 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (WEAVER-25) Reject blueprint methods that access entities that would be inaccessible
[
https://issues.apache.org/jira/browse/WEAVER-25?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Benson resolved WEAVER-25.
---
Resolution: Fixed
31583df219f3fb66ea9d362b2ef99b0a3120b789
> Reject blueprint methods that access entities that would be inaccessible
>
>
> Key: WEAVER-25
> URL: https://issues.apache.org/jira/browse/WEAVER-25
> Project: Commons Weaver
> Issue Type: Improvement
> Components: privilizer
>Affects Versions: 1.4
>Reporter: Matt Benson
>Assignee: Matt Benson
>Priority: Major
> Fix For: 1.4
>
>
> ...from the _importing_ type, i.e. classes, constructors, methods other than
> other {{static}} methods from the same class whose import is cascaded
> Blueprint methods access fields, but the rest imply the import of arbitrary
> whole types which is at least a slippery slope... choose your own metaphor.
> The safest course is to reject these. One immediate implication is that a
> valid blueprint method may not instantiate an anonymous type.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (WEAVER-25) Reject blueprint methods that access entities that would be inaccessible
Matt Benson created WEAVER-25:
-
Summary: Reject blueprint methods that access entities that would
be inaccessible
Key: WEAVER-25
URL: https://issues.apache.org/jira/browse/WEAVER-25
Project: Commons Weaver
Issue Type: Improvement
Components: privilizer
Affects Versions: 1.4
Reporter: Matt Benson
Assignee: Matt Benson
Fix For: 1.4
...from the _importing_ type, i.e. classes, constructors, methods other than
other {{static}} methods from the same class whose import is cascaded
Blueprint methods access fields, but the rest imply the import of arbitrary
whole types which is at least a slippery slope... choose your own metaphor. The
safest course is to reject these. One immediate implication is that a valid
blueprint method may not instantiate an anonymous type.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (WEAVER-24) Blueprint method references
[
https://issues.apache.org/jira/browse/WEAVER-24?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Benson resolved WEAVER-24.
---
Resolution: Fixed
31583df219f3fb66ea9d362b2ef99b0a3120b789
> Blueprint method references
> ---
>
> Key: WEAVER-24
> URL: https://issues.apache.org/jira/browse/WEAVER-24
> Project: Commons Weaver
> Issue Type: Improvement
> Components: privilizer
>Affects Versions: 1.4
>Reporter: Matt Benson
>Assignee: Matt Benson
>Priority: Major
> Fix For: 1.4
>
>
> Java 8 support in the privilizer module requires that static method
> references be imported just like static method calls indicated by the
> {{@CallTo}} annotation.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (WEAVER-24) Blueprint method references
Matt Benson created WEAVER-24:
-
Summary: Blueprint method references
Key: WEAVER-24
URL: https://issues.apache.org/jira/browse/WEAVER-24
Project: Commons Weaver
Issue Type: Improvement
Components: privilizer
Affects Versions: 1.4
Reporter: Matt Benson
Assignee: Matt Benson
Fix For: 1.4
Java 8 support in the privilizer module requires that static method references
be imported just like static method calls indicated by the {{@CallTo}}
annotation.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (WEAVER-23) Privilizer Weaver computes Object for all variable types in catch context
Matt Benson created WEAVER-23:
-
Summary: Privilizer Weaver computes Object for all variable types
in catch context
Key: WEAVER-23
URL: https://issues.apache.org/jira/browse/WEAVER-23
Project: Commons Weaver
Issue Type: Bug
Components: privilizer
Affects Versions: 1.3
Reporter: Matt Benson
Assignee: Matt Benson
Fix For: 1.4
First reported by [~rmannibucau] building Apache BVal with Java 8. Some
{{Throwable}} subclass is required in a catch context; resolve problem by
cloning {{ClassWriter#getCommonSuperClass()}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (WEAVER-23) Privilizer Weaver computes Object for all variable types in catch context
[
https://issues.apache.org/jira/browse/WEAVER-23?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Benson resolved WEAVER-23.
---
Resolution: Fixed
139fdf6e7a56bbf72b17bf5918331616724beaa9
> Privilizer Weaver computes Object for all variable types in catch context
> -
>
> Key: WEAVER-23
> URL: https://issues.apache.org/jira/browse/WEAVER-23
> Project: Commons Weaver
> Issue Type: Bug
> Components: privilizer
>Affects Versions: 1.3
>Reporter: Matt Benson
>Assignee: Matt Benson
>Priority: Major
> Fix For: 1.4
>
>
> First reported by [~rmannibucau] building Apache BVal with Java 8. Some
> {{Throwable}} subclass is required in a catch context; resolve problem by
> cloning {{ClassWriter#getCommonSuperClass()}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (WEAVER-22) Upgrade modules to ASM 6.1
[ https://issues.apache.org/jira/browse/WEAVER-22?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Benson resolved WEAVER-22. --- Resolution: Fixed afb97cfbcd6a1bd79b175d10fc4de09db86dcc0e 89b9d9a8e0c2abaf87aa5fa959d4b74484acce46 > Upgrade modules to ASM 6.1 > -- > > Key: WEAVER-22 > URL: https://issues.apache.org/jira/browse/WEAVER-22 > Project: Commons Weaver > Issue Type: Task > Components: normalizer, privilizer >Affects Versions: 1.4 >Reporter: Matt Benson >Assignee: Matt Benson >Priority: Major > Fix For: 1.4 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (WEAVER-22) Upgrade modules to ASM 6.1
Matt Benson created WEAVER-22: - Summary: Upgrade modules to ASM 6.1 Key: WEAVER-22 URL: https://issues.apache.org/jira/browse/WEAVER-22 Project: Commons Weaver Issue Type: Task Components: normalizer, privilizer Affects Versions: 1.4 Reporter: Matt Benson Assignee: Matt Benson Fix For: 1.4 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (WEAVER-21) Upgrade xbean-finder to v4.8
Matt Benson created WEAVER-21: - Summary: Upgrade xbean-finder to v4.8 Key: WEAVER-21 URL: https://issues.apache.org/jira/browse/WEAVER-21 Project: Commons Weaver Issue Type: Task Components: core Affects Versions: 1.4 Reporter: Matt Benson Assignee: Matt Benson Fix For: 1.4 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (WEAVER-21) Upgrade xbean-finder to v4.8
[ https://issues.apache.org/jira/browse/WEAVER-21?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Benson resolved WEAVER-21. --- Resolution: Fixed 9daa86bd086c9e78893cfb62060305f3b2685db1 > Upgrade xbean-finder to v4.8 > > > Key: WEAVER-21 > URL: https://issues.apache.org/jira/browse/WEAVER-21 > Project: Commons Weaver > Issue Type: Task > Components: core >Affects Versions: 1.4 >Reporter: Matt Benson >Assignee: Matt Benson >Priority: Major > Fix For: 1.4 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (WEAVER-20) Remove commons-io, commons-collections dependencies
[ https://issues.apache.org/jira/browse/WEAVER-20?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16471140#comment-16471140 ] Matt Benson edited comment on WEAVER-20 at 5/10/18 9:27 PM: e0a5ad5523abf248496f38333c6b378466e57110 e96aa699e2679df471be6a781275d165eea29f7d was (Author: mbenson): e0a5ad5523abf248496f38333c6b378466e57110 > Remove commons-io, commons-collections dependencies > --- > > Key: WEAVER-20 > URL: https://issues.apache.org/jira/browse/WEAVER-20 > Project: Commons Weaver > Issue Type: Task > Components: core, normalizer, privilizer >Affects Versions: 1.4 >Reporter: Matt Benson >Assignee: Matt Benson >Priority: Major > Fix For: 1.4 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (WEAVER-20) Remove commons-io, commons-collections dependencies
[ https://issues.apache.org/jira/browse/WEAVER-20?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Benson resolved WEAVER-20. --- Resolution: Fixed e0a5ad5523abf248496f38333c6b378466e57110 > Remove commons-io, commons-collections dependencies > --- > > Key: WEAVER-20 > URL: https://issues.apache.org/jira/browse/WEAVER-20 > Project: Commons Weaver > Issue Type: Task > Components: core, normalizer, privilizer >Affects Versions: 1.4 >Reporter: Matt Benson >Assignee: Matt Benson >Priority: Major > Fix For: 1.4 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (WEAVER-20) Remove commons-io, commons-collections dependencies
Matt Benson created WEAVER-20: - Summary: Remove commons-io, commons-collections dependencies Key: WEAVER-20 URL: https://issues.apache.org/jira/browse/WEAVER-20 Project: Commons Weaver Issue Type: Task Components: core, normalizer, privilizer Affects Versions: 1.4 Reporter: Matt Benson Assignee: Matt Benson Fix For: 1.4 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (WEAVER-19) Upgrade to Java 8
[ https://issues.apache.org/jira/browse/WEAVER-19?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Benson resolved WEAVER-19. --- Resolution: Fixed c79a0ad2597d5dffd82bc115c9a12e9ecc8d43dc > Upgrade to Java 8 > - > > Key: WEAVER-19 > URL: https://issues.apache.org/jira/browse/WEAVER-19 > Project: Commons Weaver > Issue Type: Task > Components: antlib, core, maven-plugin, normalizer, privilizer >Affects Versions: 1.4 >Reporter: Matt Benson >Assignee: Matt Benson >Priority: Major > Fix For: 1.4 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (WEAVER-19) Upgrade to Java 8
Matt Benson created WEAVER-19: - Summary: Upgrade to Java 8 Key: WEAVER-19 URL: https://issues.apache.org/jira/browse/WEAVER-19 Project: Commons Weaver Issue Type: Task Components: antlib, core, maven-plugin, normalizer, privilizer Affects Versions: 1.4 Reporter: Matt Benson Assignee: Matt Benson Fix For: 1.4 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (CONFIGURATION-687) Memory leak and related issues with CombinedConfigurationBuilder
[ https://issues.apache.org/jira/browse/CONFIGURATION-687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oliver Heger resolved CONFIGURATION-687. Resolution: Fixed Fix Version/s: 2.3 This was indeed a major problem. Many thanks for spotting it. A fix was committed in SVN revision 1831360. The builders for child configurations are now created only once. The trouble with unnecessary reloading operations should be solved by this fix as well. Could you please double-check? > Memory leak and related issues with CombinedConfigurationBuilder > > > Key: CONFIGURATION-687 > URL: https://issues.apache.org/jira/browse/CONFIGURATION-687 > Project: Commons Configuration > Issue Type: Bug > Components: File reloading >Affects Versions: 2.2 >Reporter: Luke Hamaty >Priority: Major > Fix For: 2.3 > > Attachments: ReloadCombinedBug.zip > > > In CombinedConfigurationBuilder, each call to resetResult() adds new builders > to the list of child builders. Likewise, and likely for the same reason, for > ReloadingCombinedConfigurationBuilder, the resetResult() call adds to the > list of subcontrollers. > When resetResult() is called because of an reload update, the next _n_ calls > to getReloadingController().checkForReloading() will also initiate reloading, > causing a reset and increasing the number of subcontrollers. So the first > change causes 1 reload, the second change causes 2 reloads, and it doubles > each time, so the 7th touch leads to 128 reloads! > Functionally, there are no apparent symptoms until memory exhaustion and/or > thrashing occur. > This seems to be happen because > CombinedConfigurationBuilder.initResultInstance rebuilds from the parameters > without clearing all of the existing state, particularly _sourceData_, so > SourceData ends up adding the reconstructed builders on top of the existing > ones. Correcting this could be as simple as cleaning up and clearing > sourceData to force creation of new SourceData. > Code in attached zip (maven project) demonstrates the issue. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (MATH-1459) Create a way to calculate the Jacobian Matrix using a Differentiator
[
https://issues.apache.org/jira/browse/MATH-1459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16465752#comment-16465752
]
Gilles edited comment on MATH-1459 at 5/10/18 1:23 PM:
---
{quote}Will the unit test extend AbstractLeastSquaresOptimizerAbstractTest? Or
will it extend nothing?
{quote}
As per my previous comment, it should not extend
{{AbstractLeastSquaresOptimizerAbstractTest}} since that class is meant to test
an optimizer, while the functionality here is an _input_ to the optimizer.
was (Author: erans):
bq. Will the unit test extend AbstractLeastSquaresOptimizerAbstractTest? Or
will it extend nothing?
As per my previous comment, it should not extend
{{AbstractLeastSquaresOptimizerAbstractTest}} since that class is meant to test
an optimizer, while the functionality here concerns is an _input_ to the
optimizer.
> Create a way to calculate the Jacobian Matrix using a Differentiator
>
>
> Key: MATH-1459
> URL: https://issues.apache.org/jira/browse/MATH-1459
> Project: Commons Math
> Issue Type: Improvement
>Affects Versions: 4.X
>Reporter: adrian
>Priority: Minor
> Fix For: 4.X
>
>
> Create a way to automatically calculate a Jacobian Matrix using a
> Differentiator.
> I have done this with a pull request, but would like feedback.
> edit: https://github.com/apache/commons-math/pull/84
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[GitHub] commons-lang issue #329: Travis: Add Java 10 "Oracle JDK", Java 10 "OpenJDK"...
Github user PascalSchumacher commented on the issue: https://github.com/apache/commons-lang/pull/329 I updated the pull request to allow failures on Java 11. ---
[jira] [Resolved] (LANG-1396) JsonToStringStyle does not escape string names
[ https://issues.apache.org/jira/browse/LANG-1396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebb resolved LANG-1396. Resolution: Fixed LANG-1396 - JsonToStringStyle does not escape string names Project: http://git-wip-us.apache.org/repos/asf/commons-lang/repo Commit: http://git-wip-us.apache.org/repos/asf/commons-lang/commit/3fadfdd6 Tree: http://git-wip-us.apache.org/repos/asf/commons-lang/tree/3fadfdd6 Diff: http://git-wip-us.apache.org/repos/asf/commons-lang/diff/3fadfdd6 > JsonToStringStyle does not escape string names > -- > > Key: LANG-1396 > URL: https://issues.apache.org/jira/browse/LANG-1396 > Project: Commons Lang > Issue Type: Bug >Reporter: Sebb >Priority: Major > > JSON objects consist of a string : value pair. > The string part can contain '"' and '\' etc provided it is properly escaped. > This is not currently supported. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (LANG-1396) JsonToStringStyle does not escape string names
Sebb created LANG-1396: -- Summary: JsonToStringStyle does not escape string names Key: LANG-1396 URL: https://issues.apache.org/jira/browse/LANG-1396 Project: Commons Lang Issue Type: Bug Reporter: Sebb JSON objects consist of a string : value pair. The string part can contain '"' and '\' etc provided it is properly escaped. This is not currently supported. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (BEANUTILS-500) Upgrade from Apache Commons Collections 3 to 4
[ https://issues.apache.org/jira/browse/BEANUTILS-500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16470203#comment-16470203 ] Melloware commented on BEANUTILS-500: - +1 Dave Brosius. I think it would be great to get a public release of this out there! > Upgrade from Apache Commons Collections 3 to 4 > -- > > Key: BEANUTILS-500 > URL: https://issues.apache.org/jira/browse/BEANUTILS-500 > Project: Commons BeanUtils > Issue Type: Improvement > Components: Bean / Property Utils >Affects Versions: 2.0.0 >Reporter: Dave Brosius >Priority: Minor > Fix For: 2.0.0 > > Attachments: BEANUTILS-500.2.txt, BEANUTILS-500.3.txt, > BEANUTILS-500.txt > > > uptake commons-collections4. > The main difference is the removal of 'FastHashMap', and replacement with > ConcurrentHashMap. > There are a few breaking changes for deprecated methods that return a > FastHashMap, that are exposed. > I made them package private, and undeprecated them, thus 2.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CONFIGURATION-700) Issue With backslash(\) and Forwardslash(/)
[ https://issues.apache.org/jira/browse/CONFIGURATION-700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16470155#comment-16470155 ] Sebb commented on CONFIGURATION-700: Sorry, but it's still not entirely clear what the input and output are, and what you expect the output to be. Can you please provide the following files: - original input - your code to transform the input - output file generated by your code - the output you are expecting That will make it much easier to investigate. > Issue With backslash(\) and Forwardslash(/) > --- > > Key: CONFIGURATION-700 > URL: https://issues.apache.org/jira/browse/CONFIGURATION-700 > Project: Commons Configuration > Issue Type: Bug > Components: Build >Affects Versions: 1.10 >Reporter: Amitabh Pandey >Priority: Major > Fix For: 1.10 > > Attachments: 1.jpg > > > Dear Team, > I am using commons-configuration-1.10.jar for updating property file in java. > I have achieve all my requirement(Preserve comment, White space) with this > API.But stuck at one point.It is not working as per my expectations with > slash.Below is one example. > I have below url in my properties file. > *C\:ABC.net/wsdl* > Now it is getting change to below after modification > *C:ABC.net\/wsdl* > Means it is removing the backslash and changing forwardslash to \/.I know it > is escaping character. But is there any way to prevent this. I cant not > change any thing in property file. I have to handle through code only. > Because of only this issue I again moved to Java util API. > Please check fix of this. Rest is excellent. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (COMPRESS-118) Simple high-level api to do with one line what you can do with one command in a command shell
[ https://issues.apache.org/jira/browse/COMPRESS-118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Bodewig updated COMPRESS-118: Fix Version/s: (was: 1.17) > Simple high-level api to do with one line what you can do with one command in > a command shell > - > > Key: COMPRESS-118 > URL: https://issues.apache.org/jira/browse/COMPRESS-118 > Project: Commons Compress > Issue Type: New Feature > Components: Archivers >Reporter: Eirik Maus >Priority: Major > Labels: API > Original Estimate: 48h > Remaining Estimate: 48h > > There should be a high-level api for basic operations with archives in Java. > This could be a place for it. There are a few apis for working with > compression archives in java, but all of them are fairly low-level. The most > basic operations therefore requires just as much code as more specific ones. > It is not possible to unzip an archive in less than 50 lines of code, can you > believe it! > Performing basic operations on archives should be as easy in java as on the > command line. I suggest adding something like: > HighLevelApi.extractAll(zipfile,destinationDirectory) > or, even > new ZipFile(file).extractAllTo(directory) > and > ZipFile archive = HighLevelApi.createFrom(directory, "*"); > or, even > ZipFile archive = ZipFile.from(directory); > In general: one line in bash should be one line in java (plus try-catch...) > for these kinds of operations. > See "zip --help" and "unzip --help" for further candidate methods in the > high-level API. > One could also consider a coordinated effort with the VFS-project, in order > to add such methods to all such hierarchies/storages. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (COMPRESS-452) "Stream is not in the BZip2 format" exception on valid archive
[
https://issues.apache.org/jira/browse/COMPRESS-452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated COMPRESS-452:
Assignee: Stefan Bodewig
> "Stream is not in the BZip2 format" exception on valid archive
> --
>
> Key: COMPRESS-452
> URL: https://issues.apache.org/jira/browse/COMPRESS-452
> Project: Commons Compress
> Issue Type: Bug
> Components: Archivers, Compressors
>Affects Versions: 1.16.1
>Reporter: Tomisław Kityński
>Assignee: Stefan Bodewig
>Priority: Major
> Fix For: 1.17
>
> Attachments: txt.7z
>
>
> The included 7z archive (with only one file), that is password protected, can
> be properly decompressed with 7z tool. Yet, getNextEntry() throws "Stream is
> not in the BZip2 format" exception.
> The code is:
> {code:java}
> private static final byte[] PASSWORD = "iBlm8NTigvru0Jr0".getBytes();
> public static void main(String[] args) throws IOException {
> String fileName = "r:/txt.7z";
> SevenZArchiveEntry entry;
> try (SevenZFile arch = new SevenZFile(new File(fileName), PASSWORD)) {
> while ((entry = arch.getNextEntry()) != null)
> { System.out.println(entry.getName()); }
> }
> {code}
> The same exception is thrown when one uses SevenZFile(SeekableByteChannel,
> byte[]) constructor. Password seems to be OK, since changing it yields
> different exception (and it also works in 7z tool).
> Full exception is:
> {noformat}
> Exception in thread "main" java.io.IOException: Stream is not in the BZip2
> format
> at
> org.apache.commons.compress.compressors.bzip2.BZip2CompressorInputStream.init(BZip2CompressorInputStream.java:252)
> at
> org.apache.commons.compress.compressors.bzip2.BZip2CompressorInputStream.(BZip2CompressorInputStream.java:134)
> at
> org.apache.commons.compress.compressors.bzip2.BZip2CompressorInputStream.(BZip2CompressorInputStream.java:112)
> at
> org.apache.commons.compress.archivers.sevenz.Coders$BZIP2Decoder.decode(Coders.java:254)
> at
> org.apache.commons.compress.archivers.sevenz.Coders.addDecoder(Coders.java:79)
> at
> org.apache.commons.compress.archivers.sevenz.SevenZFile.buildDecoderStack(SevenZFile.java:933)
> at
> org.apache.commons.compress.archivers.sevenz.SevenZFile.buildDecodingStream(SevenZFile.java:909)
> at
> org.apache.commons.compress.archivers.sevenz.SevenZFile.getNextEntry(SevenZFile.java:222)
> at UnpackTest.main(UnpackTest.java:17)
> {noformat}
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (COMPRESS-452) "Stream is not in the BZip2 format" exception on valid archive
[
https://issues.apache.org/jira/browse/COMPRESS-452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed COMPRESS-452.
---
> "Stream is not in the BZip2 format" exception on valid archive
> --
>
> Key: COMPRESS-452
> URL: https://issues.apache.org/jira/browse/COMPRESS-452
> Project: Commons Compress
> Issue Type: Bug
> Components: Archivers, Compressors
>Affects Versions: 1.16.1
>Reporter: Tomisław Kityński
>Assignee: Stefan Bodewig
>Priority: Major
> Fix For: 1.17
>
> Attachments: txt.7z
>
>
> The included 7z archive (with only one file), that is password protected, can
> be properly decompressed with 7z tool. Yet, getNextEntry() throws "Stream is
> not in the BZip2 format" exception.
> The code is:
> {code:java}
> private static final byte[] PASSWORD = "iBlm8NTigvru0Jr0".getBytes();
> public static void main(String[] args) throws IOException {
> String fileName = "r:/txt.7z";
> SevenZArchiveEntry entry;
> try (SevenZFile arch = new SevenZFile(new File(fileName), PASSWORD)) {
> while ((entry = arch.getNextEntry()) != null)
> { System.out.println(entry.getName()); }
> }
> {code}
> The same exception is thrown when one uses SevenZFile(SeekableByteChannel,
> byte[]) constructor. Password seems to be OK, since changing it yields
> different exception (and it also works in 7z tool).
> Full exception is:
> {noformat}
> Exception in thread "main" java.io.IOException: Stream is not in the BZip2
> format
> at
> org.apache.commons.compress.compressors.bzip2.BZip2CompressorInputStream.init(BZip2CompressorInputStream.java:252)
> at
> org.apache.commons.compress.compressors.bzip2.BZip2CompressorInputStream.(BZip2CompressorInputStream.java:134)
> at
> org.apache.commons.compress.compressors.bzip2.BZip2CompressorInputStream.(BZip2CompressorInputStream.java:112)
> at
> org.apache.commons.compress.archivers.sevenz.Coders$BZIP2Decoder.decode(Coders.java:254)
> at
> org.apache.commons.compress.archivers.sevenz.Coders.addDecoder(Coders.java:79)
> at
> org.apache.commons.compress.archivers.sevenz.SevenZFile.buildDecoderStack(SevenZFile.java:933)
> at
> org.apache.commons.compress.archivers.sevenz.SevenZFile.buildDecodingStream(SevenZFile.java:909)
> at
> org.apache.commons.compress.archivers.sevenz.SevenZFile.getNextEntry(SevenZFile.java:222)
> at UnpackTest.main(UnpackTest.java:17)
> {noformat}
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
