[GitHub] [commons-release-plugin] kinow merged pull request #73: Bump maven-scm.version from 1.11.3 to 1.12.0
kinow merged pull request #73: URL: https://github.com/apache/commons-release-plugin/pull/73 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@commons.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Comment Edited] (DBCP-581) BigDecimal precision lossing when reusing prepared statement for INSERT / UPDATE queries in DB2
[
https://issues.apache.org/jira/browse/DBCP-581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17417882#comment-17417882
]
Barry Sham edited comment on DBCP-581 at 9/21/21, 1:19 AM:
---
Thanks for your suggestion. We will look into H2 and see if we can reproduce
our test case on H2 as well.
Besides, our teammate found flag *poolPreparedStatements* seems trigger the
behavor like *maxStatements* which provided by DB2 driver for statement pooling
purpose.
We enabled trace log and found that the DBCP library calles
*PreparedStatement.clearParameters()* after the update query executed.
Is there have any reference material for the +implemenation of statement
pooling in DBCP+?
Many thanks.
was (Author: bcfsham):
Thanks for your suggestion. We will look into H2 and see if we can reproduce
our test case on H2 as well.
Besides, our teammate found flag *poolPreparedStatements* seems trigger the
behavor like *maxStatements* which provided by DB2 driver for statement pooling
purpose.
We enabled trace log and found that the DBCP library calles
*PreparedStatement.clearParameters()* after the update query execuated.
Is there have any reference material for the +implemenation of statement
pooling in DBCP+?
Many thanks.
> BigDecimal precision lossing when reusing prepared statement for INSERT /
> UPDATE queries in DB2
> ---
>
> Key: DBCP-581
> URL: https://issues.apache.org/jira/browse/DBCP-581
> Project: Commons DBCP
> Issue Type: Bug
>Affects Versions: 1.4, 2.9.0
> Environment: *Java Version*
> +DBCP 1.4+
> * IBM 64-bit SDK for Windows AMD64/EM64T architecture, Java Technology
> Edition, Version 7 Release 1
> * Open JDK Zulu 8.31.0.1
> +DBCP 2.9.0+
> * Open JDK Zulu 8.31.0.1
>
> *Database*
> +IBM DB2 10.5+
> +IBM DB2 11.5+
> We are using IBM DB2 driver 4.25.13, but the problem exists in other versions
> as well (see below)
> * 3.69.76
> * 4.19.77
> * 4.25.13
> * 4.26.14
> * 4.27.25
> * 4.28.11
> * 4.29.24
>
> +MySql Ver 8.0.17 for Linux on x86_64 (MySQL Community Server - GPL)+
>Reporter: Barry Sham
>Priority: Blocker
> Attachments: DBCPTest.zip
>
>
> We use DBCP1.4 (with *poolPreparedStatements enabled*) to insert records that
> contains {{*BigDecimal* and it will store into a *Decimal(11, 2)*}} column.
> Although BigDecimal in the first insertion can be rounded up propertly, the
> remains {color:#ff}_fails_{color}: (see the bottom output)
> {code:java}
> 2021-09-07 10:22:13:186 INFO JdbcDbcpTest:81 - JDK version 1.8.0_181
> 2021-09-07 10:22:13:190 INFO JdbcDbcpTest:83 - [Connection class:
> org.apache.commons.dbcp.PoolingDataSource$PoolGuardConnectionWrapper]
> connected to jdbc:db2://localhost:5/mydb
> 2021-09-07 10:22:13:232 DEBUG JdbcDbcpTest:103 - [Perform 1 insert] 1 record
> inserted (value = 0.1099940395355224609375)
> 2021-09-07 10:22:13:235 DEBUG JdbcDbcpTest:103 - [Perform 2 insert] 1 record
> inserted (value = 100.1099940395355224609375)
> 2021-09-07 10:22:13:241 INFO JdbcDbcpTest:113 - Execute query SELECT DECTEST
> FROM TBL_DECTEST
> 2021-09-07 10:22:13:262 INFO CompareUtils:27 - ***
> 2021-09-07 10:22:13:263 INFO CompareUtils:28 - * Value set: [0.11, 100.10]
> 2021-09-07 10:22:13:263 INFO CompareUtils:29 -
> ***{code}
> Then we upgraded the DBCP from 1.4 to 2.9.0 but the problem
> {color:#ff}still exists{color}: (see the connection class in line 2)
> {code:java}
> 2021-09-07 10:22:13:533 INFO JdbcDbcpTest:81 - JDK version 1.8.0_181
> 2021-09-07 10:22:13:534 INFO JdbcDbcpTest:83 - [Connection class:
> org.apache.commons.dbcp2.PoolingDataSource$PoolGuardConnectionWrapper]
> connected to jdbc:db2://localhost:5/mydb
> 2021-09-07 10:22:13:562 DEBUG JdbcDbcpTest:103 - [Perform 1 insert] 1 record
> inserted (value = 0.1099940395355224609375)
> 2021-09-07 10:22:13:564 DEBUG JdbcDbcpTest:103 - [Perform 2 insert] 1 record
> inserted (value = 100.1099940395355224609375)
> 2021-09-07 10:22:13:571 INFO JdbcDbcpTest:113 - Execute query SELECT DECTEST
> FROM TBL_DECTEST
> 2021-09-07 10:22:13:574 INFO CompareUtils:27 -
> ***
> 2021-09-07 10:22:13:574 INFO CompareUtils:28 - * Value set: [0.11, 100.10]
> 2021-09-07 10:22:13:574 INFO CompareUtils:29 -
> *** {code}
> We found all BigDecimal can rounded up properly if we *disable
> poolPreparedStatements*. However this is not an option due to performance
> condition.
> Also we tried to insert BigDecimal with only JDBC and all BigDecimal rounded
> up properly as well:
> {code:java}
> 2021-09-07 10:22:13:345 INFO JdbcDbcpTest:81 - JDK version 1.8.0_181
> 2021-09-07 10:22:13:345 INFO
[jira] [Commented] (DBCP-581) BigDecimal precision lossing when reusing prepared statement for INSERT / UPDATE queries in DB2
[
https://issues.apache.org/jira/browse/DBCP-581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17417882#comment-17417882
]
Barry Sham commented on DBCP-581:
-
Thanks for your suggestion. We will look into H2 and see if we can reproduce
our test case on H2 as well.
Besides, our teammate found flag *poolPreparedStatements* seems trigger the
behavor like *maxStatements* which provided by DB2 driver for statement pooling
purpose.
We enabled trace log and found that the DBCP library calles
*PreparedStatement.clearParameters()* after the update query execuated.
Is there have any reference material for the +implemenation of statement
pooling in DBCP+?
Many thanks.
> BigDecimal precision lossing when reusing prepared statement for INSERT /
> UPDATE queries in DB2
> ---
>
> Key: DBCP-581
> URL: https://issues.apache.org/jira/browse/DBCP-581
> Project: Commons DBCP
> Issue Type: Bug
>Affects Versions: 1.4, 2.9.0
> Environment: *Java Version*
> +DBCP 1.4+
> * IBM 64-bit SDK for Windows AMD64/EM64T architecture, Java Technology
> Edition, Version 7 Release 1
> * Open JDK Zulu 8.31.0.1
> +DBCP 2.9.0+
> * Open JDK Zulu 8.31.0.1
>
> *Database*
> +IBM DB2 10.5+
> +IBM DB2 11.5+
> We are using IBM DB2 driver 4.25.13, but the problem exists in other versions
> as well (see below)
> * 3.69.76
> * 4.19.77
> * 4.25.13
> * 4.26.14
> * 4.27.25
> * 4.28.11
> * 4.29.24
>
> +MySql Ver 8.0.17 for Linux on x86_64 (MySQL Community Server - GPL)+
>Reporter: Barry Sham
>Priority: Blocker
> Attachments: DBCPTest.zip
>
>
> We use DBCP1.4 (with *poolPreparedStatements enabled*) to insert records that
> contains {{*BigDecimal* and it will store into a *Decimal(11, 2)*}} column.
> Although BigDecimal in the first insertion can be rounded up propertly, the
> remains {color:#ff}_fails_{color}: (see the bottom output)
> {code:java}
> 2021-09-07 10:22:13:186 INFO JdbcDbcpTest:81 - JDK version 1.8.0_181
> 2021-09-07 10:22:13:190 INFO JdbcDbcpTest:83 - [Connection class:
> org.apache.commons.dbcp.PoolingDataSource$PoolGuardConnectionWrapper]
> connected to jdbc:db2://localhost:5/mydb
> 2021-09-07 10:22:13:232 DEBUG JdbcDbcpTest:103 - [Perform 1 insert] 1 record
> inserted (value = 0.1099940395355224609375)
> 2021-09-07 10:22:13:235 DEBUG JdbcDbcpTest:103 - [Perform 2 insert] 1 record
> inserted (value = 100.1099940395355224609375)
> 2021-09-07 10:22:13:241 INFO JdbcDbcpTest:113 - Execute query SELECT DECTEST
> FROM TBL_DECTEST
> 2021-09-07 10:22:13:262 INFO CompareUtils:27 - ***
> 2021-09-07 10:22:13:263 INFO CompareUtils:28 - * Value set: [0.11, 100.10]
> 2021-09-07 10:22:13:263 INFO CompareUtils:29 -
> ***{code}
> Then we upgraded the DBCP from 1.4 to 2.9.0 but the problem
> {color:#ff}still exists{color}: (see the connection class in line 2)
> {code:java}
> 2021-09-07 10:22:13:533 INFO JdbcDbcpTest:81 - JDK version 1.8.0_181
> 2021-09-07 10:22:13:534 INFO JdbcDbcpTest:83 - [Connection class:
> org.apache.commons.dbcp2.PoolingDataSource$PoolGuardConnectionWrapper]
> connected to jdbc:db2://localhost:5/mydb
> 2021-09-07 10:22:13:562 DEBUG JdbcDbcpTest:103 - [Perform 1 insert] 1 record
> inserted (value = 0.1099940395355224609375)
> 2021-09-07 10:22:13:564 DEBUG JdbcDbcpTest:103 - [Perform 2 insert] 1 record
> inserted (value = 100.1099940395355224609375)
> 2021-09-07 10:22:13:571 INFO JdbcDbcpTest:113 - Execute query SELECT DECTEST
> FROM TBL_DECTEST
> 2021-09-07 10:22:13:574 INFO CompareUtils:27 -
> ***
> 2021-09-07 10:22:13:574 INFO CompareUtils:28 - * Value set: [0.11, 100.10]
> 2021-09-07 10:22:13:574 INFO CompareUtils:29 -
> *** {code}
> We found all BigDecimal can rounded up properly if we *disable
> poolPreparedStatements*. However this is not an option due to performance
> condition.
> Also we tried to insert BigDecimal with only JDBC and all BigDecimal rounded
> up properly as well:
> {code:java}
> 2021-09-07 10:22:13:345 INFO JdbcDbcpTest:81 - JDK version 1.8.0_181
> 2021-09-07 10:22:13:345 INFO JdbcDbcpTest:83 - [Connection class:
> com.ibm.db2.jcc.t4.b] connected to jdbc:db2://localhost:5/mydb
> 2021-09-07 10:22:13:364 DEBUG JdbcDbcpTest:103 - [Perform 1 insert] 1 record
> inserted (value = 0.1099940395355224609375)
> 2021-09-07 10:22:13:371 DEBUG JdbcDbcpTest:103 - [Perform 2 insert] 1 record
> inserted (value = 100.1099940395355224609375)
> 2021-09-07 10:22:13:372 INFO JdbcDbcpTest:113 - Execute query SELECT DECTEST
> FROM TBL_DECTEST
> 2021-09-07 10:22:13:374 INFO CompareUtils:27 -
> ***
> 2021-09-07 10:22:13:374 INFO CompareUtils:28
[jira] [Commented] (MATH-1618) Change in Existing Design
[ https://issues.apache.org/jira/browse/MATH-1618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1741#comment-1741 ] Gilles Sadowski commented on MATH-1618: --- Although you've [modified|https://github.com/apache/commons-math/pull/197/commits/732b0d60826180ae0ff97217dea98eb36253c9e8] the indentation, be aware that other tools (e.g. SonarQube) will raise warning flags if you don't simplify such lambda expressions. > Change in Existing Design > - > > Key: MATH-1618 > URL: https://issues.apache.org/jira/browse/MATH-1618 > Project: Commons Math > Issue Type: Sub-task >Affects Versions: 3.6.1 >Reporter: AVIJIT BASAK >Priority: Major > > *1) Creation of abstraction for GeneticAlgorithm*: In order to have different > types of implementation for Genetic Algorithm like adaptive GA along with the > existing one, we need to introduce an abstraction and a hierarchy of > algorithm. AbstracttGeneticAlgorithm class needs to be implemented which > would be extended by all other Algorithm class. This would also ease any > future extension. > Removed Components: None > New Components: AbstractGeneticAlgorithm > Affected Components: GeneticAlgorithm > *2) Delegation of fitness calculation*: As per the current design Fitness > interface is implemented by chromosome class, which forces implementation of > fitness() method for any concrete chromosome. However this restricts the use > of same concrete chromosome implementation to be reused for different problem > domain. This inheritance based implementation should be replaced by > composition. A new interface FitnessCalculator would be introduced. An > instance of FitnessCalculator will be provided during creation of every > concrete chromosome. This will enable reuse of concrete chromosome classes in > different problem domain and hence improve extensibility and re-usability. > This will require addition of an argument for each factory method and > constructors. > Removed Components: Fitness > New Components: FitnessFunction > Affected Components: Chromosome, AbstractListChromosome, BinaryChromosome, > RandomKey > *3) Enable finer control for mutation and crossover probability*: Current > design uses the crossover and mutation probability at the chromosome level. > For finer control of mutation and crossover process the probability would be > managed within MutationPolicy and CrossoverPolicy implementations. > Probability would be passed as an argument to the respective operations. This > way the corresponding operations will be responsible for managing probability > and apply in convenient way. I have seen the controlling the mutation > probability at the allele(gene) level improves the exploring capability of > the optimization process and hence improves robustness. > Removed Components: None > New Components: None > Affected Components: MutationPolicy, CrossoverPolicy and all other > implementation classes > *4) Addition of new Simulation Stopping conditions*: New simulation stopping > conditions would be added based on population statistical characteristics. > The simulation can be stopped based on variations of population average > fitness or best fitness. These parameters are much better to represent nature > of convergence. This will improve robustness to a considerable extent. > Removed Components: None > New Components: UnchangedAvgFitness, UnchangedBestFitness, > Affected Components: SimulationStoppingCondition, GeneticAlgorithm, > FixedElapsedTime, FixedGenerationCount > *5) Introduction of Convergence listeners*: New convergence listener > interface and registry would be introduced to enable tracking of convergence. > Removed components: None > New Components: ConvergenceListener, ListenerRegistry, > PopulationStatisticalSummary > Affected Components: AbstractGeneticAlgorithm, GeneticAlgorithm > *6) Restructuring Elitism*: Elitism can be handled by the hierarchy of > Algorithm classes. Use of a separate ElitisticListPopulation class may not be > necessary. The method nextGeneration() in Population would accept the elitism > rate as an argument. Any concrete instance of Population would provide the > necessary implementation. > Removed components: ElitisticListPopulation > New Component: None > Affected Components: AbstractGeneticAlgorithm, GeneticAlgorithm, Population, > ListPopulation > *7) Introducing Hierarchy in Crossover and Mutation Operator*: Abstract > classes has been introduced for crossover and mutation operators. > Removed components: None > New Component: AbstractChromosomeCrossoverPolicy, > AbstractListChromosomeCrossoverPolicy, AbstractListChromosomeMutationPolicy > Affected Components: All concrete implementation classes for crossover and > mutation. > *8) Rename the method newFixedLengthChromosome() in >
[GitHub] [commons-io] jonfreedman commented on pull request #32: Add Tailable interface to tail files accessed using alternative libraries such as jCIFS or commons-vfs
jonfreedman commented on pull request #32: URL: https://github.com/apache/commons-io/pull/32#issuecomment-923148409 Thanks for finally getting the change in there, it's a bit of a shame you weren't able to merge but the project has improved so I'll take what I can get. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@commons.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [commons-io] jonfreedman closed pull request #32: Add Tailable interface to tail files accessed using alternative libraries such as jCIFS or commons-vfs
jonfreedman closed pull request #32: URL: https://github.com/apache/commons-io/pull/32 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@commons.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [commons-math] avijitbasak edited a comment on pull request #197: Feature/math 1563
avijitbasak edited a comment on pull request #197: URL: https://github.com/apache/commons-math/pull/197#issuecomment-922933961 The following errors have been received after build. These are due to formatting of lambda expression. I have formatted the manually. It will be helpful if anyone can share eclipse configuration to resolve this. [INFO] There are 6 errors reported by Checkstyle 8.29 with /home/travis/build/apache/commons-math/commons-math4-genetics/../src/main/resources/checkstyle/checkstyle.xml ruleset. [ERROR] src/test/java/org/apache/commons/math4/genetics/selection/TournamentSelectionTest.java:[51] (indentation) Indentation: 'block' child has incorrect indentation level 16, expected level should be 20. [ERROR] src/test/java/org/apache/commons/math4/genetics/selection/TournamentSelectionTest.java:[52] (indentation) Indentation: 'block rcurly' has incorrect indentation level 12, expected level should be 16. [ERROR] src/test/java/org/apache/commons/math4/genetics/dummy/DummyChromosome.java:[27] (indentation) Indentation: 'block' child has incorrect indentation level 12, expected level should be 16. [ERROR] src/test/java/org/apache/commons/math4/genetics/dummy/DummyChromosome.java:[28] (indentation) Indentation: 'block rcurly' has incorrect indentation level 8, expected level should be 12. [ERROR] src/test/java/org/apache/commons/math4/genetics/utils/ChromosomeRepresentationUtilsTest.java:[114] (indentation) Indentation: 'block' child has incorrect indentation level 20, expected level should be 12. [ERROR] src/test/java/org/apache/commons/math4/genetics/utils/ChromosomeRepresentationUtilsTest.java:[115] (indentation) Indentation: 'block rcurly' has incorrect indentation level 16, expected level should be 8. [INFO] -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@commons.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [commons-cli] garydgregory merged pull request #67: Bump maven-pmd-plugin from 3.14.0 to 3.15.0
garydgregory merged pull request #67: URL: https://github.com/apache/commons-cli/pull/67 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@commons.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [commons-cli] garydgregory merged pull request #65: Bump actions/cache from 2.1.5 to 2.1.6
garydgregory merged pull request #65: URL: https://github.com/apache/commons-cli/pull/65 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@commons.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Comment Edited] (MATH-1618) Change in Existing Design
[
https://issues.apache.org/jira/browse/MATH-1618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17417665#comment-17417665
]
Gilles Sadowski edited comment on MATH-1618 at 9/20/21, 1:44 PM:
-
*Note*: I've no GH account, so I'm
[commenting|https://github.com/apache/commons-math/pull/197#issuecomment-922933961]
here.
{quote}
{code}
private static class DummyChromosome extends AbstractChromosome {
DummyChromosome() {
super(c -> {
return counter++;
}, c -> {
return "0";
});
}
{code}
{quote}
Please try something (untested) along:
{code}
private static class DummyChromosome extends AbstractChromosome {
DummyChromosome() {
super(c -> counter++, c -> "0");
}
{code}
was (Author: erans):
*Note*: I've no GH account, so I'm
[commenting|https://github.com/apache/commons-math/pull/197#issuecomment-922933961]
here.
{quote}
{code}
private static class DummyChromosome extends AbstractChromosome {
DummyChromosome() {
super(c -> {
return counter++;
}, c -> {
return "0";
});
}
{code}
{quote}
Please try something (unstested) along:
{code}
private static class DummyChromosome extends AbstractChromosome {
DummyChromosome() {
super(c -> counter++, c -> "0");
}
{code}
> Change in Existing Design
> -
>
> Key: MATH-1618
> URL: https://issues.apache.org/jira/browse/MATH-1618
> Project: Commons Math
> Issue Type: Sub-task
>Affects Versions: 3.6.1
>Reporter: AVIJIT BASAK
>Priority: Major
>
> *1) Creation of abstraction for GeneticAlgorithm*: In order to have different
> types of implementation for Genetic Algorithm like adaptive GA along with the
> existing one, we need to introduce an abstraction and a hierarchy of
> algorithm. AbstracttGeneticAlgorithm class needs to be implemented which
> would be extended by all other Algorithm class. This would also ease any
> future extension.
> Removed Components: None
> New Components: AbstractGeneticAlgorithm
> Affected Components: GeneticAlgorithm
> *2) Delegation of fitness calculation*: As per the current design Fitness
> interface is implemented by chromosome class, which forces implementation of
> fitness() method for any concrete chromosome. However this restricts the use
> of same concrete chromosome implementation to be reused for different problem
> domain. This inheritance based implementation should be replaced by
> composition. A new interface FitnessCalculator would be introduced. An
> instance of FitnessCalculator will be provided during creation of every
> concrete chromosome. This will enable reuse of concrete chromosome classes in
> different problem domain and hence improve extensibility and re-usability.
> This will require addition of an argument for each factory method and
> constructors.
> Removed Components: Fitness
> New Components: FitnessFunction
> Affected Components: Chromosome, AbstractListChromosome, BinaryChromosome,
> RandomKey
> *3) Enable finer control for mutation and crossover probability*: Current
> design uses the crossover and mutation probability at the chromosome level.
> For finer control of mutation and crossover process the probability would be
> managed within MutationPolicy and CrossoverPolicy implementations.
> Probability would be passed as an argument to the respective operations. This
> way the corresponding operations will be responsible for managing probability
> and apply in convenient way. I have seen the controlling the mutation
> probability at the allele(gene) level improves the exploring capability of
> the optimization process and hence improves robustness.
> Removed Components: None
> New Components: None
> Affected Components: MutationPolicy, CrossoverPolicy and all other
> implementation classes
> *4) Addition of new Simulation Stopping conditions*: New simulation stopping
> conditions would be added based on population statistical characteristics.
> The simulation can be stopped based on variations of population average
> fitness or best fitness. These parameters are much better to represent nature
> of convergence. This will improve robustness to a considerable extent.
> Removed Components: None
> New Components: UnchangedAvgFitness, UnchangedBestFitness,
> Affected Components: SimulationStoppingCondition, GeneticAlgorithm,
> FixedElapsedTime, FixedGenerationCount
> *5) Introduction of Convergence listeners*: New convergence listener
> interface and registry would be introduced to enable tracking of convergence.
> Removed components: None
> New Components: ConvergenceListener, ListenerRegistry,
> PopulationStatisticalSummary
> Affected Components:
[jira] [Commented] (MATH-1618) Change in Existing Design
[
https://issues.apache.org/jira/browse/MATH-1618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17417665#comment-17417665
]
Gilles Sadowski commented on MATH-1618:
---
*Note*: I've no GH account, so I'm
[commenting|https://github.com/apache/commons-math/pull/197#issuecomment-922933961]
here.
{quote}
{code}
private static class DummyChromosome extends AbstractChromosome {
DummyChromosome() {
super(c -> {
return counter++;
}, c -> {
return "0";
});
}
{code}
{quote}
Please try something (unstested) along:
{code}
private static class DummyChromosome extends AbstractChromosome {
DummyChromosome() {
super(c -> counter++, c -> "0");
}
{code}
> Change in Existing Design
> -
>
> Key: MATH-1618
> URL: https://issues.apache.org/jira/browse/MATH-1618
> Project: Commons Math
> Issue Type: Sub-task
>Affects Versions: 3.6.1
>Reporter: AVIJIT BASAK
>Priority: Major
>
> *1) Creation of abstraction for GeneticAlgorithm*: In order to have different
> types of implementation for Genetic Algorithm like adaptive GA along with the
> existing one, we need to introduce an abstraction and a hierarchy of
> algorithm. AbstracttGeneticAlgorithm class needs to be implemented which
> would be extended by all other Algorithm class. This would also ease any
> future extension.
> Removed Components: None
> New Components: AbstractGeneticAlgorithm
> Affected Components: GeneticAlgorithm
> *2) Delegation of fitness calculation*: As per the current design Fitness
> interface is implemented by chromosome class, which forces implementation of
> fitness() method for any concrete chromosome. However this restricts the use
> of same concrete chromosome implementation to be reused for different problem
> domain. This inheritance based implementation should be replaced by
> composition. A new interface FitnessCalculator would be introduced. An
> instance of FitnessCalculator will be provided during creation of every
> concrete chromosome. This will enable reuse of concrete chromosome classes in
> different problem domain and hence improve extensibility and re-usability.
> This will require addition of an argument for each factory method and
> constructors.
> Removed Components: Fitness
> New Components: FitnessFunction
> Affected Components: Chromosome, AbstractListChromosome, BinaryChromosome,
> RandomKey
> *3) Enable finer control for mutation and crossover probability*: Current
> design uses the crossover and mutation probability at the chromosome level.
> For finer control of mutation and crossover process the probability would be
> managed within MutationPolicy and CrossoverPolicy implementations.
> Probability would be passed as an argument to the respective operations. This
> way the corresponding operations will be responsible for managing probability
> and apply in convenient way. I have seen the controlling the mutation
> probability at the allele(gene) level improves the exploring capability of
> the optimization process and hence improves robustness.
> Removed Components: None
> New Components: None
> Affected Components: MutationPolicy, CrossoverPolicy and all other
> implementation classes
> *4) Addition of new Simulation Stopping conditions*: New simulation stopping
> conditions would be added based on population statistical characteristics.
> The simulation can be stopped based on variations of population average
> fitness or best fitness. These parameters are much better to represent nature
> of convergence. This will improve robustness to a considerable extent.
> Removed Components: None
> New Components: UnchangedAvgFitness, UnchangedBestFitness,
> Affected Components: SimulationStoppingCondition, GeneticAlgorithm,
> FixedElapsedTime, FixedGenerationCount
> *5) Introduction of Convergence listeners*: New convergence listener
> interface and registry would be introduced to enable tracking of convergence.
> Removed components: None
> New Components: ConvergenceListener, ListenerRegistry,
> PopulationStatisticalSummary
> Affected Components: AbstractGeneticAlgorithm, GeneticAlgorithm
> *6) Restructuring Elitism*: Elitism can be handled by the hierarchy of
> Algorithm classes. Use of a separate ElitisticListPopulation class may not be
> necessary. The method nextGeneration() in Population would accept the elitism
> rate as an argument. Any concrete instance of Population would provide the
> necessary implementation.
> Removed components: ElitisticListPopulation
> New Component: None
> Affected Components: AbstractGeneticAlgorithm, GeneticAlgorithm, Population,
> ListPopulation
> *7) Introducing Hierarchy in Crossover and Mutation Operator*: Abstract
> classes has been introduced for crossover and
[jira] [Commented] (MATH-1618) Change in Existing Design
[ https://issues.apache.org/jira/browse/MATH-1618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17417660#comment-17417660 ] AVIJIT BASAK commented on MATH-1618: Here are the build errors. Need help to resolve these. https://github.com/apache/commons-math/pull/197#issuecomment-922933961 > Change in Existing Design > - > > Key: MATH-1618 > URL: https://issues.apache.org/jira/browse/MATH-1618 > Project: Commons Math > Issue Type: Sub-task >Affects Versions: 3.6.1 >Reporter: AVIJIT BASAK >Priority: Major > > *1) Creation of abstraction for GeneticAlgorithm*: In order to have different > types of implementation for Genetic Algorithm like adaptive GA along with the > existing one, we need to introduce an abstraction and a hierarchy of > algorithm. AbstracttGeneticAlgorithm class needs to be implemented which > would be extended by all other Algorithm class. This would also ease any > future extension. > Removed Components: None > New Components: AbstractGeneticAlgorithm > Affected Components: GeneticAlgorithm > *2) Delegation of fitness calculation*: As per the current design Fitness > interface is implemented by chromosome class, which forces implementation of > fitness() method for any concrete chromosome. However this restricts the use > of same concrete chromosome implementation to be reused for different problem > domain. This inheritance based implementation should be replaced by > composition. A new interface FitnessCalculator would be introduced. An > instance of FitnessCalculator will be provided during creation of every > concrete chromosome. This will enable reuse of concrete chromosome classes in > different problem domain and hence improve extensibility and re-usability. > This will require addition of an argument for each factory method and > constructors. > Removed Components: Fitness > New Components: FitnessFunction > Affected Components: Chromosome, AbstractListChromosome, BinaryChromosome, > RandomKey > *3) Enable finer control for mutation and crossover probability*: Current > design uses the crossover and mutation probability at the chromosome level. > For finer control of mutation and crossover process the probability would be > managed within MutationPolicy and CrossoverPolicy implementations. > Probability would be passed as an argument to the respective operations. This > way the corresponding operations will be responsible for managing probability > and apply in convenient way. I have seen the controlling the mutation > probability at the allele(gene) level improves the exploring capability of > the optimization process and hence improves robustness. > Removed Components: None > New Components: None > Affected Components: MutationPolicy, CrossoverPolicy and all other > implementation classes > *4) Addition of new Simulation Stopping conditions*: New simulation stopping > conditions would be added based on population statistical characteristics. > The simulation can be stopped based on variations of population average > fitness or best fitness. These parameters are much better to represent nature > of convergence. This will improve robustness to a considerable extent. > Removed Components: None > New Components: UnchangedAvgFitness, UnchangedBestFitness, > Affected Components: SimulationStoppingCondition, GeneticAlgorithm, > FixedElapsedTime, FixedGenerationCount > *5) Introduction of Convergence listeners*: New convergence listener > interface and registry would be introduced to enable tracking of convergence. > Removed components: None > New Components: ConvergenceListener, ListenerRegistry, > PopulationStatisticalSummary > Affected Components: AbstractGeneticAlgorithm, GeneticAlgorithm > *6) Restructuring Elitism*: Elitism can be handled by the hierarchy of > Algorithm classes. Use of a separate ElitisticListPopulation class may not be > necessary. The method nextGeneration() in Population would accept the elitism > rate as an argument. Any concrete instance of Population would provide the > necessary implementation. > Removed components: ElitisticListPopulation > New Component: None > Affected Components: AbstractGeneticAlgorithm, GeneticAlgorithm, Population, > ListPopulation > *7) Introducing Hierarchy in Crossover and Mutation Operator*: Abstract > classes has been introduced for crossover and mutation operators. > Removed components: None > New Component: AbstractChromosomeCrossoverPolicy, > AbstractListChromosomeCrossoverPolicy, AbstractListChromosomeMutationPolicy > Affected Components: All concrete implementation classes for crossover and > mutation. > *8) Rename the method newFixedLengthChromosome() in > AbstractList**Chromosome***: The method newFixedLengthChromosome would be > renamed as newChromosome. As we are not considering any variable length >
[GitHub] [commons-math] avijitbasak closed pull request #197: Feature/math 1563
avijitbasak closed pull request #197: URL: https://github.com/apache/commons-math/pull/197 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@commons.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [commons-math] avijitbasak commented on pull request #197: Feature/math 1563
avijitbasak commented on pull request #197: URL: https://github.com/apache/commons-math/pull/197#issuecomment-922933961 The following errors have been received after build. These are due to formatting of lambda expression. Need help to resolve this. [INFO] There are 6 errors reported by Checkstyle 8.29 with /home/travis/build/apache/commons-math/commons-math4-genetics/../src/main/resources/checkstyle/checkstyle.xml ruleset. [ERROR] src/test/java/org/apache/commons/math4/genetics/selection/TournamentSelectionTest.java:[51] (indentation) Indentation: 'block' child has incorrect indentation level 16, expected level should be 20. [ERROR] src/test/java/org/apache/commons/math4/genetics/selection/TournamentSelectionTest.java:[52] (indentation) Indentation: 'block rcurly' has incorrect indentation level 12, expected level should be 16. [ERROR] src/test/java/org/apache/commons/math4/genetics/dummy/DummyChromosome.java:[27] (indentation) Indentation: 'block' child has incorrect indentation level 12, expected level should be 16. [ERROR] src/test/java/org/apache/commons/math4/genetics/dummy/DummyChromosome.java:[28] (indentation) Indentation: 'block rcurly' has incorrect indentation level 8, expected level should be 12. [ERROR] src/test/java/org/apache/commons/math4/genetics/utils/ChromosomeRepresentationUtilsTest.java:[114] (indentation) Indentation: 'block' child has incorrect indentation level 20, expected level should be 12. [ERROR] src/test/java/org/apache/commons/math4/genetics/utils/ChromosomeRepresentationUtilsTest.java:[115] (indentation) Indentation: 'block rcurly' has incorrect indentation level 16, expected level should be 8. [INFO] -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@commons.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (MATH-1618) Change in Existing Design
[ https://issues.apache.org/jira/browse/MATH-1618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17417654#comment-17417654 ] Gilles Sadowski commented on MATH-1618: --- Hi [~avijit.basak]. Thanks for your current work on the GA implementation. However please note again that the build does not pass; this is delaying review(s)... I noticed that you use TSP as benchmark/example; it makes me wonder whether to share code with the SOFM example application. IOW, there could be an "examples-ml" module (within the "commons-math-examples" module) with a TSP application that could launch the various algorithms and provide their respective performance. > Change in Existing Design > - > > Key: MATH-1618 > URL: https://issues.apache.org/jira/browse/MATH-1618 > Project: Commons Math > Issue Type: Sub-task >Affects Versions: 3.6.1 >Reporter: AVIJIT BASAK >Priority: Major > > *1) Creation of abstraction for GeneticAlgorithm*: In order to have different > types of implementation for Genetic Algorithm like adaptive GA along with the > existing one, we need to introduce an abstraction and a hierarchy of > algorithm. AbstracttGeneticAlgorithm class needs to be implemented which > would be extended by all other Algorithm class. This would also ease any > future extension. > Removed Components: None > New Components: AbstractGeneticAlgorithm > Affected Components: GeneticAlgorithm > *2) Delegation of fitness calculation*: As per the current design Fitness > interface is implemented by chromosome class, which forces implementation of > fitness() method for any concrete chromosome. However this restricts the use > of same concrete chromosome implementation to be reused for different problem > domain. This inheritance based implementation should be replaced by > composition. A new interface FitnessCalculator would be introduced. An > instance of FitnessCalculator will be provided during creation of every > concrete chromosome. This will enable reuse of concrete chromosome classes in > different problem domain and hence improve extensibility and re-usability. > This will require addition of an argument for each factory method and > constructors. > Removed Components: Fitness > New Components: FitnessFunction > Affected Components: Chromosome, AbstractListChromosome, BinaryChromosome, > RandomKey > *3) Enable finer control for mutation and crossover probability*: Current > design uses the crossover and mutation probability at the chromosome level. > For finer control of mutation and crossover process the probability would be > managed within MutationPolicy and CrossoverPolicy implementations. > Probability would be passed as an argument to the respective operations. This > way the corresponding operations will be responsible for managing probability > and apply in convenient way. I have seen the controlling the mutation > probability at the allele(gene) level improves the exploring capability of > the optimization process and hence improves robustness. > Removed Components: None > New Components: None > Affected Components: MutationPolicy, CrossoverPolicy and all other > implementation classes > *4) Addition of new Simulation Stopping conditions*: New simulation stopping > conditions would be added based on population statistical characteristics. > The simulation can be stopped based on variations of population average > fitness or best fitness. These parameters are much better to represent nature > of convergence. This will improve robustness to a considerable extent. > Removed Components: None > New Components: UnchangedAvgFitness, UnchangedBestFitness, > Affected Components: SimulationStoppingCondition, GeneticAlgorithm, > FixedElapsedTime, FixedGenerationCount > *5) Introduction of Convergence listeners*: New convergence listener > interface and registry would be introduced to enable tracking of convergence. > Removed components: None > New Components: ConvergenceListener, ListenerRegistry, > PopulationStatisticalSummary > Affected Components: AbstractGeneticAlgorithm, GeneticAlgorithm > *6) Restructuring Elitism*: Elitism can be handled by the hierarchy of > Algorithm classes. Use of a separate ElitisticListPopulation class may not be > necessary. The method nextGeneration() in Population would accept the elitism > rate as an argument. Any concrete instance of Population would provide the > necessary implementation. > Removed components: ElitisticListPopulation > New Component: None > Affected Components: AbstractGeneticAlgorithm, GeneticAlgorithm, Population, > ListPopulation > *7) Introducing Hierarchy in Crossover and Mutation Operator*: Abstract > classes has been introduced for crossover and mutation operators. > Removed components: None > New Component: AbstractChromosomeCrossoverPolicy, >
[GitHub] [commons-io] garydgregory merged pull request #274: Bump spotbugs-maven-plugin from 4.3.0 to 4.4.1
garydgregory merged pull request #274: URL: https://github.com/apache/commons-io/pull/274 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@commons.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [commons-pool] dependabot[bot] opened a new pull request #102: Bump spotbugs-maven-plugin from 4.3.0 to 4.4.1
dependabot[bot] opened a new pull request #102: URL: https://github.com/apache/commons-pool/pull/102 Bumps [spotbugs-maven-plugin](https://github.com/spotbugs/spotbugs-maven-plugin) from 4.3.0 to 4.4.1. Commits https://github.com/spotbugs/spotbugs-maven-plugin/commit/741f662a0d32ca1d4307d5bf47f75424893104ff;>741f662 [maven-release-plugin] prepare release spotbugs-maven-plugin-4.4.1 https://github.com/spotbugs/spotbugs-maven-plugin/commit/4dacc01757f654035fb0b73a13fc2fe8dace83d5;>4dacc01 [pom] Bump junit to 5.8.0 https://github.com/spotbugs/spotbugs-maven-plugin/commit/c8c8a689788a252bfeab6f323995e9ff2ce6dcd8;>c8c8a68 [maven] Bump maven wrapper to 3.8.2 https://github.com/spotbugs/spotbugs-maven-plugin/commit/0b029a8ef834765dae9dd1ea2c8cffe0e77f7ea2;>0b029a8 Merge pull request https://github-redirect.dependabot.com/spotbugs/spotbugs-maven-plugin/issues/357;>#357 from spotbugs/dependabot/maven/scmPluginVersion-1.12.0 https://github.com/spotbugs/spotbugs-maven-plugin/commit/34c1c995c0f8af3685b6f81f4cd12a5f00500700;>34c1c99 Bump scmPluginVersion from 1.11.3 to 1.12.0 https://github.com/spotbugs/spotbugs-maven-plugin/commit/1a259f2f057ef25a6ce289776d91629dce3bfd90;>1a259f2 Merge pull request https://github-redirect.dependabot.com/spotbugs/spotbugs-maven-plugin/issues/356;>#356 from spotbugs/dependabot/maven/jgit.version-5.13.0.20... https://github.com/spotbugs/spotbugs-maven-plugin/commit/915e5a027908d1ee01d87dcf1092c64a65096756;>915e5a0 Bump jgit.version from 5.12.0.202106070339-r to 5.13.0.202109080827-r https://github.com/spotbugs/spotbugs-maven-plugin/commit/675b7a3f7576bc2788691cb285b6ae517619d6fd;>675b7a3 Merge pull request https://github-redirect.dependabot.com/spotbugs/spotbugs-maven-plugin/issues/355;>#355 from hazendaz/spotbugs https://github.com/spotbugs/spotbugs-maven-plugin/commit/39d9fc641b99c9df7c567451abda5e5d4f9f8eab;>39d9fc6 Create codeql-analysis.yml https://github.com/spotbugs/spotbugs-maven-plugin/commit/febf924641a1f006bc6b424321b6bad42abfc2f6;>febf924 [pom] Bump spotbugs to 4.4.1 Additional commits viewable in https://github.com/spotbugs/spotbugs-maven-plugin/compare/spotbugs-maven-plugin-4.3.0...spotbugs-maven-plugin-4.4.1;>compare view [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@commons.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [commons-bsf] dependabot[bot] opened a new pull request #23: Bump spotbugs-maven-plugin from 4.2.0 to 4.4.1
dependabot[bot] opened a new pull request #23: URL: https://github.com/apache/commons-bsf/pull/23 Bumps [spotbugs-maven-plugin](https://github.com/spotbugs/spotbugs-maven-plugin) from 4.2.0 to 4.4.1. Commits https://github.com/spotbugs/spotbugs-maven-plugin/commit/741f662a0d32ca1d4307d5bf47f75424893104ff;>741f662 [maven-release-plugin] prepare release spotbugs-maven-plugin-4.4.1 https://github.com/spotbugs/spotbugs-maven-plugin/commit/4dacc01757f654035fb0b73a13fc2fe8dace83d5;>4dacc01 [pom] Bump junit to 5.8.0 https://github.com/spotbugs/spotbugs-maven-plugin/commit/c8c8a689788a252bfeab6f323995e9ff2ce6dcd8;>c8c8a68 [maven] Bump maven wrapper to 3.8.2 https://github.com/spotbugs/spotbugs-maven-plugin/commit/0b029a8ef834765dae9dd1ea2c8cffe0e77f7ea2;>0b029a8 Merge pull request https://github-redirect.dependabot.com/spotbugs/spotbugs-maven-plugin/issues/357;>#357 from spotbugs/dependabot/maven/scmPluginVersion-1.12.0 https://github.com/spotbugs/spotbugs-maven-plugin/commit/34c1c995c0f8af3685b6f81f4cd12a5f00500700;>34c1c99 Bump scmPluginVersion from 1.11.3 to 1.12.0 https://github.com/spotbugs/spotbugs-maven-plugin/commit/1a259f2f057ef25a6ce289776d91629dce3bfd90;>1a259f2 Merge pull request https://github-redirect.dependabot.com/spotbugs/spotbugs-maven-plugin/issues/356;>#356 from spotbugs/dependabot/maven/jgit.version-5.13.0.20... https://github.com/spotbugs/spotbugs-maven-plugin/commit/915e5a027908d1ee01d87dcf1092c64a65096756;>915e5a0 Bump jgit.version from 5.12.0.202106070339-r to 5.13.0.202109080827-r https://github.com/spotbugs/spotbugs-maven-plugin/commit/675b7a3f7576bc2788691cb285b6ae517619d6fd;>675b7a3 Merge pull request https://github-redirect.dependabot.com/spotbugs/spotbugs-maven-plugin/issues/355;>#355 from hazendaz/spotbugs https://github.com/spotbugs/spotbugs-maven-plugin/commit/39d9fc641b99c9df7c567451abda5e5d4f9f8eab;>39d9fc6 Create codeql-analysis.yml https://github.com/spotbugs/spotbugs-maven-plugin/commit/febf924641a1f006bc6b424321b6bad42abfc2f6;>febf924 [pom] Bump spotbugs to 4.4.1 Additional commits viewable in https://github.com/spotbugs/spotbugs-maven-plugin/compare/spotbugs-maven-plugin-4.2.0...spotbugs-maven-plugin-4.4.1;>compare view [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@commons.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [commons-bsf] dependabot[bot] closed pull request #19: Bump spotbugs-maven-plugin from 4.2.0 to 4.3.0
dependabot[bot] closed pull request #19: URL: https://github.com/apache/commons-bsf/pull/19 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@commons.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [commons-bsf] dependabot[bot] commented on pull request #19: Bump spotbugs-maven-plugin from 4.2.0 to 4.3.0
dependabot[bot] commented on pull request #19: URL: https://github.com/apache/commons-bsf/pull/19#issuecomment-922840785 Superseded by #23. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@commons.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [commons-logging] dependabot[bot] commented on pull request #53: Bump spotbugs-maven-plugin from 4.2.0 to 4.3.0
dependabot[bot] commented on pull request #53: URL: https://github.com/apache/commons-logging/pull/53#issuecomment-922803717 Superseded by #57. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@commons.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [commons-logging] dependabot[bot] closed pull request #53: Bump spotbugs-maven-plugin from 4.2.0 to 4.3.0
dependabot[bot] closed pull request #53: URL: https://github.com/apache/commons-logging/pull/53 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@commons.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [commons-logging] dependabot[bot] opened a new pull request #57: Bump spotbugs-maven-plugin from 4.2.0 to 4.4.1
dependabot[bot] opened a new pull request #57: URL: https://github.com/apache/commons-logging/pull/57 Bumps [spotbugs-maven-plugin](https://github.com/spotbugs/spotbugs-maven-plugin) from 4.2.0 to 4.4.1. Commits https://github.com/spotbugs/spotbugs-maven-plugin/commit/741f662a0d32ca1d4307d5bf47f75424893104ff;>741f662 [maven-release-plugin] prepare release spotbugs-maven-plugin-4.4.1 https://github.com/spotbugs/spotbugs-maven-plugin/commit/4dacc01757f654035fb0b73a13fc2fe8dace83d5;>4dacc01 [pom] Bump junit to 5.8.0 https://github.com/spotbugs/spotbugs-maven-plugin/commit/c8c8a689788a252bfeab6f323995e9ff2ce6dcd8;>c8c8a68 [maven] Bump maven wrapper to 3.8.2 https://github.com/spotbugs/spotbugs-maven-plugin/commit/0b029a8ef834765dae9dd1ea2c8cffe0e77f7ea2;>0b029a8 Merge pull request https://github-redirect.dependabot.com/spotbugs/spotbugs-maven-plugin/issues/357;>#357 from spotbugs/dependabot/maven/scmPluginVersion-1.12.0 https://github.com/spotbugs/spotbugs-maven-plugin/commit/34c1c995c0f8af3685b6f81f4cd12a5f00500700;>34c1c99 Bump scmPluginVersion from 1.11.3 to 1.12.0 https://github.com/spotbugs/spotbugs-maven-plugin/commit/1a259f2f057ef25a6ce289776d91629dce3bfd90;>1a259f2 Merge pull request https://github-redirect.dependabot.com/spotbugs/spotbugs-maven-plugin/issues/356;>#356 from spotbugs/dependabot/maven/jgit.version-5.13.0.20... https://github.com/spotbugs/spotbugs-maven-plugin/commit/915e5a027908d1ee01d87dcf1092c64a65096756;>915e5a0 Bump jgit.version from 5.12.0.202106070339-r to 5.13.0.202109080827-r https://github.com/spotbugs/spotbugs-maven-plugin/commit/675b7a3f7576bc2788691cb285b6ae517619d6fd;>675b7a3 Merge pull request https://github-redirect.dependabot.com/spotbugs/spotbugs-maven-plugin/issues/355;>#355 from hazendaz/spotbugs https://github.com/spotbugs/spotbugs-maven-plugin/commit/39d9fc641b99c9df7c567451abda5e5d4f9f8eab;>39d9fc6 Create codeql-analysis.yml https://github.com/spotbugs/spotbugs-maven-plugin/commit/febf924641a1f006bc6b424321b6bad42abfc2f6;>febf924 [pom] Bump spotbugs to 4.4.1 Additional commits viewable in https://github.com/spotbugs/spotbugs-maven-plugin/compare/spotbugs-maven-plugin-4.2.0...spotbugs-maven-plugin-4.4.1;>compare view [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@commons.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [commons-logging] dependabot[bot] closed pull request #54: Bump spotbugs from 4.2.0 to 4.4.0
dependabot[bot] closed pull request #54: URL: https://github.com/apache/commons-logging/pull/54 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@commons.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [commons-logging] dependabot[bot] opened a new pull request #56: Bump spotbugs from 4.2.0 to 4.4.1
dependabot[bot] opened a new pull request #56: URL: https://github.com/apache/commons-logging/pull/56 Bumps [spotbugs](https://github.com/spotbugs/spotbugs) from 4.2.0 to 4.4.1. Release notes Sourced from https://github.com/spotbugs/spotbugs/releases;>spotbugs's releases. SpotBugs 4.4.1 CHANGELOG https://github.com/spotbugs/spotbugs/blob/4.4.1/CHANGELOG.md;>https://github.com/spotbugs/spotbugs/blob/4.4.1/CHANGELOG.md CHECKSUM file checksum (sha256) spotbugs-4.4.1-javadoc.jar 7021a519365315a5fc0f98a0d2c3ed2b73eb20e61baf5b937453b6d085fa02ef spotbugs-4.4.1-sources.jar 4e6f932cf21f826d30873b0d51c250d5fc5307fd177ec782d38d82f1019c711d spotbugs-4.4.1.tgz 341873c7c4a73508aca6f32f03339aad38c926703accb2e799b5b632b0832bd9 spotbugs-4.4.1.zip 414152869130c22646ff0e6898bba09e9e20d6ade87eeebe912e645b578b9385 spotbugs-annotations-4.4.1-javadoc.jar cd290d907c4ab7a0ef0fcdacbe9059d8fa15a9de2b98f6ab9f5e02625f9ef557 spotbugs-annotations-4.4.1-sources.jar b338136e3e82d585348cde58a8fe3a678e16f51a35c31c1463e05fefef557aad spotbugs-annotations.jar fa5d3b17d585868c74c0e25b3c57c17282f9a3328c73ea5259bfd9ac99c6933a spotbugs-ant-4.4.1-javadoc.jar eb5600fbe8c01fb9d2f0bf33a079ba7f60ca1ffd0fc41bb7f21a1728d7823e9b spotbugs-ant-4.4.1-sources.jar c74dec42c0ed0dd1ae02a7410d8e0f0dbbee23e8e7da4a21910863677fcdbc8e spotbugs-ant.jar 9233e48d37882ae4e7a42e9f42ef4c63d6f802cf8f3b03ba575bee26e5032367 spotbugs.jar 48c53d2fdefbcd7292a05e23b50dbaab29047e3c87096e5129e4e7a627c354a3 test-harness-4.4.1-javadoc.jar 01c8e43294e9c2a394dcdb5224441e65bc9023a414efcd974b7af92ce10ce60a test-harness-4.4.1-sources.jar 2c1f5ef929453f3b682c7eb7c1e22db3082b5f74c5a5be439be5dc31dd7a31aa test-harness-4.4.1.jar 55d3a590b81ffec48293a76c45c0695914b405bf9f02bfb930e3ab99b5867d4f test-harness-core-4.4.1-javadoc.jar 74b76f75cb4e4a8504d6ff09ca8fcff6d0dba19b24979998ae214b230e44c018 test-harness-core-4.4.1-sources.jar f320f5eb4069e9686b760b2a6a0760989753225f9e9ce1226e3258ec64795d8a test-harness-core-4.4.1.jar cbec03867e077079d011e85f9932fb230fae3d909f741cffaa4c8097e91fdf40 test-harness-jupiter-4.4.1-javadoc.jar ad8111b37ab5ff2d33415fbb8bd559526259f316028a4129182a98e5966631e8 test-harness-jupiter-4.4.1-sources.jar 210353a57016e26b1a654d936a15f039613fa1ac532d485c1b1d03902f6c6315 test-harness-jupiter-4.4.1.jar 17e8d78d1868f86e63f3e5e3d878e86f3d7fb1b8cf1a8d5f89c982bfd3e2 SpotBugs 4.4.0 CHANGELOG https://github.com/spotbugs/spotbugs/blob/4.4.0/CHANGELOG.md;>https://github.com/spotbugs/spotbugs/blob/4.4.0/CHANGELOG.md CHECKSUM file checksum (sha256) spotbugs-4.4.0-javadoc.jar c25c0a3056ccf1ce9ae4c182ab73f6c9626d9031a30bf48857941d6c56ba3cc7 spotbugs-4.4.0-sources.jar 7b9b931b258f1db321fc5fb2e00946594dea976ad51a79a7f3ae48cac17d6c6e spotbugs-4.4.0.tgz 126b952cf248c92fbb7ba07462a71b3400bd1726fed96e179d8a50edd3e40745 spotbugs-4.4.0.zip f5f8b9aba1f3c87a508fbcb6045dcdc748e1ca4ce16803d6676417c9d82fb862 spotbugs-annotations-4.4.0-javadoc.jar 33a7ccc8917b9c5d2a6b133dceb5b212c0079986232a876471df4d7eb843bc8a spotbugs-annotations-4.4.0-sources.jar b338136e3e82d585348cde58a8fe3a678e16f51a35c31c1463e05fefef557aad spotbugs-annotations.jar 383fe580c90e1fea94a3387a8245e096beb792efdca7e04a0bbb4a8cbb81dea2 spotbugs-ant-4.4.0-javadoc.jar da10c9d3273d4367d8c940eec20e2799eba9ae54b920c506478236c241b75a55 spotbugs-ant-4.4.0-sources.jar c74dec42c0ed0dd1ae02a7410d8e0f0dbbee23e8e7da4a21910863677fcdbc8e spotbugs-ant.jar 9233e48d37882ae4e7a42e9f42ef4c63d6f802cf8f3b03ba575bee26e5032367 spotbugs.jar eb02e80126a4cdfb997fe90a1a2c6ff128b114cc7daab77ed3a773bef3adc2ca test-harness-4.4.0-javadoc.jar 4aee854334bb0dbcfd4697443abc0594a96c8c7db12e9e5408839fad4bf75162 test-harness-4.4.0-sources.jar 2c1f5ef929453f3b682c7eb7c1e22db3082b5f74c5a5be439be5dc31dd7a31aa test-harness-4.4.0.jar 55d3a590b81ffec48293a76c45c0695914b405bf9f02bfb930e3ab99b5867d4f test-harness-core-4.4.0-javadoc.jar 76c8694c8051dbc3f5e989448f3746f6da5374e24db22a022b5c2ffe73336f01 ... (truncated) Changelog Sourced from https://github.com/spotbugs/spotbugs/blob/master/CHANGELOG.md;>spotbugs's changelog. 4.4.1 - 2021-09-07 Changed Bump gson from 2.8.7 to 2.8.8 (https://github-redirect.dependabot.com/spotbugs/spotbugs/pull/1658;>#1658) Lower ExitCodes logger to debug level (https://github-redirect.dependabot.com/spotbugs/spotbugs/issues/1661;>#1661) Fixed SARIF format to be compatible with Github
[GitHub] [commons-logging] dependabot[bot] commented on pull request #54: Bump spotbugs from 4.2.0 to 4.4.0
dependabot[bot] commented on pull request #54: URL: https://github.com/apache/commons-logging/pull/54#issuecomment-922798753 Superseded by #56. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@commons.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [commons-dbutils] dependabot[bot] commented on pull request #77: Bump spotbugs-maven-plugin from 4.2.0 to 4.3.0
dependabot[bot] commented on pull request #77: URL: https://github.com/apache/commons-dbutils/pull/77#issuecomment-922768614 Superseded by #85. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@commons.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [commons-dbutils] dependabot[bot] opened a new pull request #85: Bump spotbugs-maven-plugin from 4.2.0 to 4.4.1
dependabot[bot] opened a new pull request #85: URL: https://github.com/apache/commons-dbutils/pull/85 Bumps [spotbugs-maven-plugin](https://github.com/spotbugs/spotbugs-maven-plugin) from 4.2.0 to 4.4.1. Commits https://github.com/spotbugs/spotbugs-maven-plugin/commit/741f662a0d32ca1d4307d5bf47f75424893104ff;>741f662 [maven-release-plugin] prepare release spotbugs-maven-plugin-4.4.1 https://github.com/spotbugs/spotbugs-maven-plugin/commit/4dacc01757f654035fb0b73a13fc2fe8dace83d5;>4dacc01 [pom] Bump junit to 5.8.0 https://github.com/spotbugs/spotbugs-maven-plugin/commit/c8c8a689788a252bfeab6f323995e9ff2ce6dcd8;>c8c8a68 [maven] Bump maven wrapper to 3.8.2 https://github.com/spotbugs/spotbugs-maven-plugin/commit/0b029a8ef834765dae9dd1ea2c8cffe0e77f7ea2;>0b029a8 Merge pull request https://github-redirect.dependabot.com/spotbugs/spotbugs-maven-plugin/issues/357;>#357 from spotbugs/dependabot/maven/scmPluginVersion-1.12.0 https://github.com/spotbugs/spotbugs-maven-plugin/commit/34c1c995c0f8af3685b6f81f4cd12a5f00500700;>34c1c99 Bump scmPluginVersion from 1.11.3 to 1.12.0 https://github.com/spotbugs/spotbugs-maven-plugin/commit/1a259f2f057ef25a6ce289776d91629dce3bfd90;>1a259f2 Merge pull request https://github-redirect.dependabot.com/spotbugs/spotbugs-maven-plugin/issues/356;>#356 from spotbugs/dependabot/maven/jgit.version-5.13.0.20... https://github.com/spotbugs/spotbugs-maven-plugin/commit/915e5a027908d1ee01d87dcf1092c64a65096756;>915e5a0 Bump jgit.version from 5.12.0.202106070339-r to 5.13.0.202109080827-r https://github.com/spotbugs/spotbugs-maven-plugin/commit/675b7a3f7576bc2788691cb285b6ae517619d6fd;>675b7a3 Merge pull request https://github-redirect.dependabot.com/spotbugs/spotbugs-maven-plugin/issues/355;>#355 from hazendaz/spotbugs https://github.com/spotbugs/spotbugs-maven-plugin/commit/39d9fc641b99c9df7c567451abda5e5d4f9f8eab;>39d9fc6 Create codeql-analysis.yml https://github.com/spotbugs/spotbugs-maven-plugin/commit/febf924641a1f006bc6b424321b6bad42abfc2f6;>febf924 [pom] Bump spotbugs to 4.4.1 Additional commits viewable in https://github.com/spotbugs/spotbugs-maven-plugin/compare/spotbugs-maven-plugin-4.2.0...spotbugs-maven-plugin-4.4.1;>compare view [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@commons.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [commons-dbutils] dependabot[bot] closed pull request #77: Bump spotbugs-maven-plugin from 4.2.0 to 4.3.0
dependabot[bot] closed pull request #77: URL: https://github.com/apache/commons-dbutils/pull/77 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@commons.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [commons-release-plugin] dependabot[bot] opened a new pull request #73: Bump maven-scm.version from 1.11.3 to 1.12.0
dependabot[bot] opened a new pull request #73: URL: https://github.com/apache/commons-release-plugin/pull/73 Bumps `maven-scm.version` from 1.11.3 to 1.12.0. Updates `maven-scm-api` from 1.11.3 to 1.12.0 Commits https://github.com/apache/maven-scm/commit/50e8c04561383789aef1a70a8d70569ad7d0efe6;>50e8c04 [maven-release-plugin] prepare release maven-scm-1.12.0 https://github.com/apache/maven-scm/commit/6eb3e719e630aac7683fc5b2d6b5bc8de4e24f1a;>6eb3e71 [SCM-968] Reduce standard providers to non-deprecated ones https://github.com/apache/maven-scm/commit/e5b41e5459270094eb27ad28fe71c1339139cd1e;>e5b41e5 [SCM-967] MavenScmCli requires at least three args not less https://github.com/apache/maven-scm/commit/9b27fddeeeb386512949d87876945fef595cf47f;>9b27fdd [SCM-966] Deprecate maven-scm-provider-synergy https://github.com/apache/maven-scm/commit/2ce895fed0d54beb753b654360803c940f14766a;>2ce895f [SCM-965] Deprecate maven-scm-providers-cvs https://github.com/apache/maven-scm/commit/3bb58b54250f9bd55c84e0456d251c33d44db86c;>3bb58b5 [SCM-964] Deprecate maven-scm-provider-vss https://github.com/apache/maven-scm/commit/8bdb711005024c55600ce0dd5476d607124f4903;>8bdb711 [SCM-963] Deprecate maven-scm-provider-tfs https://github.com/apache/maven-scm/commit/864c9b1d6db95ca0aac6fd8ea2f7f81c866c0b69;>864c9b1 [SCM-962] Deprecate maven-scm-provider-starteam https://github.com/apache/maven-scm/commit/bb405b02d2b17f3b3a87856d76207f34c3ff371a;>bb405b0 [SCM-961] Deprecate maven-scm-provider-perforce https://github.com/apache/maven-scm/commit/878d7172ad98401345eb1e364a1788e75f990706;>878d717 [SCM-960] Deprecate maven-scm-provider-jazz Additional commits viewable in https://github.com/apache/maven-scm/compare/maven-scm-1.11.3...maven-scm-1.12.0;>compare view Updates `maven-scm-provider-svnexe` from 1.11.3 to 1.12.0 Updates `maven-scm-provider-svn-commons` from 1.11.3 to 1.12.0 Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@commons.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [commons-build-plugin] dependabot[bot] opened a new pull request #42: Bump spotbugs-maven-plugin from 4.3.0 to 4.4.1
dependabot[bot] opened a new pull request #42: URL: https://github.com/apache/commons-build-plugin/pull/42 Bumps [spotbugs-maven-plugin](https://github.com/spotbugs/spotbugs-maven-plugin) from 4.3.0 to 4.4.1. Commits https://github.com/spotbugs/spotbugs-maven-plugin/commit/741f662a0d32ca1d4307d5bf47f75424893104ff;>741f662 [maven-release-plugin] prepare release spotbugs-maven-plugin-4.4.1 https://github.com/spotbugs/spotbugs-maven-plugin/commit/4dacc01757f654035fb0b73a13fc2fe8dace83d5;>4dacc01 [pom] Bump junit to 5.8.0 https://github.com/spotbugs/spotbugs-maven-plugin/commit/c8c8a689788a252bfeab6f323995e9ff2ce6dcd8;>c8c8a68 [maven] Bump maven wrapper to 3.8.2 https://github.com/spotbugs/spotbugs-maven-plugin/commit/0b029a8ef834765dae9dd1ea2c8cffe0e77f7ea2;>0b029a8 Merge pull request https://github-redirect.dependabot.com/spotbugs/spotbugs-maven-plugin/issues/357;>#357 from spotbugs/dependabot/maven/scmPluginVersion-1.12.0 https://github.com/spotbugs/spotbugs-maven-plugin/commit/34c1c995c0f8af3685b6f81f4cd12a5f00500700;>34c1c99 Bump scmPluginVersion from 1.11.3 to 1.12.0 https://github.com/spotbugs/spotbugs-maven-plugin/commit/1a259f2f057ef25a6ce289776d91629dce3bfd90;>1a259f2 Merge pull request https://github-redirect.dependabot.com/spotbugs/spotbugs-maven-plugin/issues/356;>#356 from spotbugs/dependabot/maven/jgit.version-5.13.0.20... https://github.com/spotbugs/spotbugs-maven-plugin/commit/915e5a027908d1ee01d87dcf1092c64a65096756;>915e5a0 Bump jgit.version from 5.12.0.202106070339-r to 5.13.0.202109080827-r https://github.com/spotbugs/spotbugs-maven-plugin/commit/675b7a3f7576bc2788691cb285b6ae517619d6fd;>675b7a3 Merge pull request https://github-redirect.dependabot.com/spotbugs/spotbugs-maven-plugin/issues/355;>#355 from hazendaz/spotbugs https://github.com/spotbugs/spotbugs-maven-plugin/commit/39d9fc641b99c9df7c567451abda5e5d4f9f8eab;>39d9fc6 Create codeql-analysis.yml https://github.com/spotbugs/spotbugs-maven-plugin/commit/febf924641a1f006bc6b424321b6bad42abfc2f6;>febf924 [pom] Bump spotbugs to 4.4.1 Additional commits viewable in https://github.com/spotbugs/spotbugs-maven-plugin/compare/spotbugs-maven-plugin-4.3.0...spotbugs-maven-plugin-4.4.1;>compare view [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@commons.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Updated] (MATH-1618) Change in Existing Design
[ https://issues.apache.org/jira/browse/MATH-1618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] AVIJIT BASAK updated MATH-1618: --- Description: *1) Creation of abstraction for GeneticAlgorithm*: In order to have different types of implementation for Genetic Algorithm like adaptive GA along with the existing one, we need to introduce an abstraction and a hierarchy of algorithm. AbstracttGeneticAlgorithm class needs to be implemented which would be extended by all other Algorithm class. This would also ease any future extension. Removed Components: None New Components: AbstractGeneticAlgorithm Affected Components: GeneticAlgorithm *2) Delegation of fitness calculation*: As per the current design Fitness interface is implemented by chromosome class, which forces implementation of fitness() method for any concrete chromosome. However this restricts the use of same concrete chromosome implementation to be reused for different problem domain. This inheritance based implementation should be replaced by composition. A new interface FitnessCalculator would be introduced. An instance of FitnessCalculator will be provided during creation of every concrete chromosome. This will enable reuse of concrete chromosome classes in different problem domain and hence improve extensibility and re-usability. This will require addition of an argument for each factory method and constructors. Removed Components: Fitness New Components: FitnessFunction Affected Components: Chromosome, AbstractListChromosome, BinaryChromosome, RandomKey *3) Enable finer control for mutation and crossover probability*: Current design uses the crossover and mutation probability at the chromosome level. For finer control of mutation and crossover process the probability would be managed within MutationPolicy and CrossoverPolicy implementations. Probability would be passed as an argument to the respective operations. This way the corresponding operations will be responsible for managing probability and apply in convenient way. I have seen the controlling the mutation probability at the allele(gene) level improves the exploring capability of the optimization process and hence improves robustness. Removed Components: None New Components: None Affected Components: MutationPolicy, CrossoverPolicy and all other implementation classes *4) Addition of new Simulation Stopping conditions*: New simulation stopping conditions would be added based on population statistical characteristics. The simulation can be stopped based on variations of population average fitness or best fitness. These parameters are much better to represent nature of convergence. This will improve robustness to a considerable extent. Removed Components: None New Components: UnchangedAvgFitness, UnchangedBestFitness, Affected Components: SimulationStoppingCondition, GeneticAlgorithm, FixedElapsedTime, FixedGenerationCount *5) Introduction of Convergence listeners*: New convergence listener interface and registry would be introduced to enable tracking of convergence. Removed components: None New Components: ConvergenceListener, ListenerRegistry, PopulationStatisticalSummary Affected Components: AbstractGeneticAlgorithm, GeneticAlgorithm *6) Restructuring Elitism*: Elitism can be handled by the hierarchy of Algorithm classes. Use of a separate ElitisticListPopulation class may not be necessary. The method nextGeneration() in Population would accept the elitism rate as an argument. Any concrete instance of Population would provide the necessary implementation. Removed components: ElitisticListPopulation New Component: None Affected Components: AbstractGeneticAlgorithm, GeneticAlgorithm, Population, ListPopulation *7) Introducing Hierarchy in Crossover and Mutation Operator*: Abstract classes has been introduced for crossover and mutation operators. Removed components: None New Component: AbstractChromosomeCrossoverPolicy, AbstractListChromosomeCrossoverPolicy, AbstractListChromosomeMutationPolicy Affected Components: All concrete implementation classes for crossover and mutation. *8) Rename the method newFixedLengthChromosome() in AbstractList**Chromosome***: The method newFixedLengthChromosome would be renamed as newChromosome. As we are not considering any variable length chromosome and chromosome representation is immutable in AbstractListChromosome we don't need any explicit mention of the phrase 'FixedLength' as part of the method. *9) Introduction of Decoder and Phenotype:* Phenotype has been introduced as Generic. Decoder has been also introduced to transform the chromosome genotype to phenotype. The phenotype would be used for majority of computation like calculation of fitness, chromosome comparison etc. This is major design change from the previous model. This will enable same genotype to be used for both direct and indirect encoding of
