Hi Gilles,
I like that idea. I'm picturing that as something that could happen after the
first beta release. Here is my current roadmap (of sorts):
1. Wrap up a few issues (GEOMETRY-92, 93, and 94)
2. Release 1.0-beta1
3. Add model-specific example code as you have started with the exa
You can probably use maven-dependency-plugin and maven-assembly-plugin
to form a coherent whole:
https://maven.apache.org/plugins/maven-dependency-plugin/unpack-mojo.html
https://maven.apache.org/plugins/maven-assembly-plugin/examples/multimodule/module-binary-inclusion-simple.html
On Fri, 17 Apr
> Note that this build uses profiles and each binary is named for its target
> platform.
Except the release artifact on Maven central contains all the shared
libs in one jar in org/apache/commons/crypto/native/OS/ARCH. The
makefile takes the artifact from
targer/commons-crypto--- and places it in
Hello.
I guess that the [Geometry] code is readily usable as described
in e.g. this paper:
https://www.semanticscholar.org/paper/Constructive-Solid-Geometry-Using-BSP-Tree-Segura-Stine/eeb5014f86750c54a87f214b03246799e970d114
If so, it would help BSP newbies (like me) if the userguide follow
