Taking a deeper look the whole package
org.apache.commons.geometry.core.internal seems to be required elsewhere
and should be public+exported. Is there any rationale to make this
"internal"? Internal packages should really only be used in the module
itself.
If its proven to be usefull in
Another thing I noted:
DoubleFunction2N is used but resides in the
org.apache.commons.geometry.core.internal package and thus is also not
exported/useable in an OSGi environment this would give CNF exceptions
if actually run inside one.
Am 20.03.21 um 13:25 schrieb Matt Juntunen:
It's
Hi Matt,
I try to use the new package in an OSGi application but only the
org.apache.commons.geometry.euclidean package is exported. Is thsi
intentional?
I'd like to use AffineTransformMatrix2D from the
org.apache.commons.geometry.euclidean.twod package for example but don't
understand how
It's available on maven central [1]. You can find the code on the Apache git
repo [2] or on Github [3]. The user guide [4] gives an overview of the library
along with code examples so you can get a feel for how it works. Don't hesitate
to ask if you have any questions.
-Matt
[1]
Thanks for the clarification, I would be happy to try out beta1 of
commons-geometry, is there a staging repo for it?
/Patrik
Den fre 19 mars 2021 kl 00:29 skrev Matt Juntunen :
> Hello.
>
> I agree that the docs are not really clear on the "natural orientation"
> part there. Basically, the
