glelouet
glelouet
at least two paths : 1. get_avoidance that returns a list of the avoided systems 2. post_avoidance that is a post, takes an array of system ids as parameter, and...
Most of those are answered by : you are making a multi module project. In that case, all the modules are supposed to work together. That avoids typically the issue...
WRT Geost : if a module is no more maintained but may be maintained later, just remove it from its parent children. It remains in the git, can be added...
WRT Upper and lower case first letter : it's to be sure the code you are using is in a packaged module and not a pom . It also mimics...
> remove children that are not supposed to change that often Frequency of updates is irrelevant. What is relevant is, if your modules adds "services" (not web services, more like...
> have one unique version, declared in the parent pom.xml Yes for unicity, no for parent pom.xml . ALL children must have their own version specified, which MUST be the...
> remove Geost dependency, since the projet is not maintained anymore. The correct term is : yes remove it from dependencies, and also remove it from its parent as a...
> Consider a child that is stable (no bug, no features), what is the point to keep it in an active big project ? How do you prove there is...
https://github.com/chocoteam/choco-solver/pull/435
no test yet though.