Re: Apache Commons Geometry Release
Alrighty! I will replace that model, save my tutorial changes for later, and see if I can start on a release later tonight. -Matt From: Gilles Sadowski Sent: Tuesday, June 30, 2020 2:35 PM To: Commons Developers List Subject: Re: Apache Commons Geometry Release Hello. Le mar. 30 juin 2020 à 18:29, Matt Juntunen a écrit : > > Hi Baljit, > > The only things keeping the release from happening at this time are > > 1. the legal issue of including a 3D model which I opened a ticket for in > JIRA yesterday [1], and It doesn't look like this site https://s2018.siggraph.org/3d-model-portal/ tries hard to prevent use of their (?) data. ;-) > 2. the tutorial requested in GEOMETRY-95. > > The first issue I can solve easily by just not including that model and just > using one that I make myself. It won't be as good but it would work. As for > the second issue, I'm working on the tutorial right now and hope to be done > within the next week or so. However, I wouldn't have a problem releasing > beta1 without it, assuming that Gilles and others are on board with that. > > Gilles, WDYT? It would be great to release "beta1"; the mentioned items can of course be added later. Best, Gilles >>> [...] - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: Apache Commons Geometry Release
Hello. Le mar. 30 juin 2020 à 18:29, Matt Juntunen a écrit : > > Hi Baljit, > > The only things keeping the release from happening at this time are > > 1. the legal issue of including a 3D model which I opened a ticket for in > JIRA yesterday [1], and It doesn't look like this site https://s2018.siggraph.org/3d-model-portal/ tries hard to prevent use of their (?) data. ;-) > 2. the tutorial requested in GEOMETRY-95. > > The first issue I can solve easily by just not including that model and just > using one that I make myself. It won't be as good but it would work. As for > the second issue, I'm working on the tutorial right now and hope to be done > within the next week or so. However, I wouldn't have a problem releasing > beta1 without it, assuming that Gilles and others are on board with that. > > Gilles, WDYT? It would be great to release "beta1"; the mentioned items can of course be added later. Best, Gilles >>> [...] - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: Apache Commons Geometry Release
Hi Baljit, The only things keeping the release from happening at this time are 1. the legal issue of including a 3D model which I opened a ticket for in JIRA yesterday [1], and 2. the tutorial requested in GEOMETRY-95. The first issue I can solve easily by just not including that model and just using one that I make myself. It won't be as good but it would work. As for the second issue, I'm working on the tutorial right now and hope to be done within the next week or so. However, I wouldn't have a problem releasing beta1 without it, assuming that Gilles and others are on board with that. Gilles, WDYT? Regards, Matt [1] https://issues.apache.org/jira/projects/LEGAL/issues/LEGAL-525 From: Singh, Baljit (GE Aviation, US) Sent: Tuesday, June 30, 2020 10:59 AM To: Matt Juntunen ; Gilles Sadowski ; dev@commons.apache.org Subject: Re: Apache Commons Geometry Release Matt, Can someone release the beta? I can migrate our test environment, and report back if any new or known Math3 issues are still present. Regards, Baljit From: Matt Juntunen Date: Tuesday, May 26, 2020 at 9:57 AM To: "Singh, Baljit (GE Aviation, US)" , Gilles Sadowski , "dev@commons.apache.org" Subject: EXT: Re: Apache Commons Geometry Release Hi Bajit, My plan is to get a release of commons-geometry out as soon as possible, although I have been saying this for more than a year at this point:-) However, I actually believe we are very close now. There are only a few remaining issues for the beta1 release and I currently have branches ready to merge for most of them. The following issues are ready and waiting for merge: -GEOMETRY-94: This adds Triangle3D and ConvexPolygon3D types, which are essentially required for working with 3D models. I have a PR in [1] and am just waiting another day or so to see if anyone has any feedback. -GEOMETRY-77: Adds useful Bounds2D and Bounds3D classes. This is included in the PR mentioned above. -GEOMETRY-97: Changes from using the term "barycenter" to "centroid" for describing the geometric center of objects. This is ready and waiting in the wings for when the PR above is merged. The following issues are not complete: -GEOMETRY-50: Bug report submitted by you quite a while ago regarding overflow in norm calculations. This is a tiny change in the code and I think we can just go ahead and do it. However, I did find one small issue that I'd like to discuss more that I put in the comments there yesterday. -GEOMETRY-95: This is a request from Gilles to add a tutorial or more detailed step-by-step user guide on how to use the library to perform constructive solid geometry operations. We are currently discussing exactly what this means in the comments on the issue. There would be some minor development work needed on this but it will most likely be in one of the examples modules and not in the main library. The main thing I can think of that we'd need would be a 3D model file reader for some format. I'm picturing using the obj format since we already have a writer for that. These are the only remaining issues I see for the beta1 release, so things are very close. I would also like to use this library in my day job, so the sooner we can get it out the better. Regards, Matt J [1] https://github.com/apache/commons-geometry/pull/77 From: Singh, Baljit (GE Aviation, US) Sent: Tuesday, May 26, 2020 9:20 AM To: Gilles Sadowski ; dev@commons.apache.org Cc: mattjuntu...@apache.org Subject: Re: Apache Commons Geometry Release Gilles, Thanks for replying. I do not know (yet) if Commons Geometry has the same issues (or even other issues), but I would rather use something being actively developed vs. something that is EOL (Commons-Math3 v3.6.1 was released 4+ years ago). At least this way, I can report/fix any bugs and get the improvements with the new releases. And yes, I'm willing to be the first test subject. __ I would love to help with more improvements, but if there is no sight for the releases and the library thus cannot be used, I can't justify spending time on it. Commons Devs, Adding the Commons Dev ML per Gilles's request. In the email below, I asked when the first release of Commons Geometry will be. Some context (and intro): using Commons-Math3, I write geometry algorithms for our UAV flight management product at AiRXOS (part of GE Aviation). However, I'm discovering bugs in Commons-Math3, one of which I helped fix in Commons Geometry. I would like to use Commons Geometry instead (for reasons mentioned above). Regards, Baljit On 5/21/20, 9:02 PM, "Gilles Sadowski" wrote: Hello. 2020-05-21 20:32 UTC+02:00, Singh, Baljit (GE Aviation, US) : > Hi Matt, Gilles, > > Any updates on when the commons-geometry release is going to be? The question
Re: Apache Commons Geometry Release
Matt, Can someone release the beta? I can migrate our test environment, and report back if any new or known Math3 issues are still present. Regards, Baljit From: Matt Juntunen Date: Tuesday, May 26, 2020 at 9:57 AM To: "Singh, Baljit (GE Aviation, US)" , Gilles Sadowski , "dev@commons.apache.org" Subject: EXT: Re: Apache Commons Geometry Release Hi Bajit, My plan is to get a release of commons-geometry out as soon as possible, although I have been saying this for more than a year at this point:-) However, I actually believe we are very close now. There are only a few remaining issues for the beta1 release and I currently have branches ready to merge for most of them. The following issues are ready and waiting for merge: -GEOMETRY-94: This adds Triangle3D and ConvexPolygon3D types, which are essentially required for working with 3D models. I have a PR in [1] and am just waiting another day or so to see if anyone has any feedback. -GEOMETRY-77: Adds useful Bounds2D and Bounds3D classes. This is included in the PR mentioned above. -GEOMETRY-97: Changes from using the term "barycenter" to "centroid" for describing the geometric center of objects. This is ready and waiting in the wings for when the PR above is merged. The following issues are not complete: -GEOMETRY-50: Bug report submitted by you quite a while ago regarding overflow in norm calculations. This is a tiny change in the code and I think we can just go ahead and do it. However, I did find one small issue that I'd like to discuss more that I put in the comments there yesterday. -GEOMETRY-95: This is a request from Gilles to add a tutorial or more detailed step-by-step user guide on how to use the library to perform constructive solid geometry operations. We are currently discussing exactly what this means in the comments on the issue. There would be some minor development work needed on this but it will most likely be in one of the examples modules and not in the main library. The main thing I can think of that we'd need would be a 3D model file reader for some format. I'm picturing using the obj format since we already have a writer for that. These are the only remaining issues I see for the beta1 release, so things are very close. I would also like to use this library in my day job, so the sooner we can get it out the better. Regards, Matt J [1] https://github.com/apache/commons-geometry/pull/77 From: Singh, Baljit (GE Aviation, US) Sent: Tuesday, May 26, 2020 9:20 AM To: Gilles Sadowski ; dev@commons.apache.org Cc: mattjuntu...@apache.org Subject: Re: Apache Commons Geometry Release Gilles, Thanks for replying. I do not know (yet) if Commons Geometry has the same issues (or even other issues), but I would rather use something being actively developed vs. something that is EOL (Commons-Math3 v3.6.1 was released 4+ years ago). At least this way, I can report/fix any bugs and get the improvements with the new releases. And yes, I'm willing to be the first test subject. __ I would love to help with more improvements, but if there is no sight for the releases and the library thus cannot be used, I can't justify spending time on it. Commons Devs, Adding the Commons Dev ML per Gilles's request. In the email below, I asked when the first release of Commons Geometry will be. Some context (and intro): using Commons-Math3, I write geometry algorithms for our UAV flight management product at AiRXOS (part of GE Aviation). However, I'm discovering bugs in Commons-Math3, one of which I helped fix in Commons Geometry. I would like to use Commons Geometry instead (for reasons mentioned above). Regards, Baljit On 5/21/20, 9:02 PM, "Gilles Sadowski" wrote: Hello. 2020-05-21 20:32 UTC+02:00, Singh, Baljit (GE Aviation, US) : > Hi Matt, Gilles, > > Any updates on when the commons-geometry release is going to be? The question is of general interest. Could you please post it to the "dev" ML? > I’m finding > more and more issues with the package > org.apache.commons.math3.geometry.spherical.twod, and its causing issues > with our product. Is the code in "Commons Geometry" free of those issues? It would be nice to have unit tests that check those cases. > I would like to upgrade to something that is actively > being developed. Sure. So, you are user number "1" (?). ;-) > Looking at JIRA, it looks like the release is almost ready, > only 3 (minor) issues to go. If you can help with those... Thanks, Gilles > Regards, > Baljit > > >
Re: Apache Commons Geometry Release
Matt, Thank for you the detailed response. It looks like most of the issues are addressed or are already being addressed. I’ll try to contribute where I can to close this out. Looking forward to the beta! Regards, Baljit From: Matt Juntunen Date: Tuesday, May 26, 2020 at 9:57 AM To: "Singh, Baljit (GE Aviation, US)" , Gilles Sadowski , "dev@commons.apache.org" Subject: EXT: Re: Apache Commons Geometry Release Hi Bajit, My plan is to get a release of commons-geometry out as soon as possible, although I have been saying this for more than a year at this point:-) However, I actually believe we are very close now. There are only a few remaining issues for the beta1 release and I currently have branches ready to merge for most of them. The following issues are ready and waiting for merge: -GEOMETRY-94: This adds Triangle3D and ConvexPolygon3D types, which are essentially required for working with 3D models. I have a PR in [1] and am just waiting another day or so to see if anyone has any feedback. -GEOMETRY-77: Adds useful Bounds2D and Bounds3D classes. This is included in the PR mentioned above. -GEOMETRY-97: Changes from using the term "barycenter" to "centroid" for describing the geometric center of objects. This is ready and waiting in the wings for when the PR above is merged. The following issues are not complete: -GEOMETRY-50: Bug report submitted by you quite a while ago regarding overflow in norm calculations. This is a tiny change in the code and I think we can just go ahead and do it. However, I did find one small issue that I'd like to discuss more that I put in the comments there yesterday. -GEOMETRY-95: This is a request from Gilles to add a tutorial or more detailed step-by-step user guide on how to use the library to perform constructive solid geometry operations. We are currently discussing exactly what this means in the comments on the issue. There would be some minor development work needed on this but it will most likely be in one of the examples modules and not in the main library. The main thing I can think of that we'd need would be a 3D model file reader for some format. I'm picturing using the obj format since we already have a writer for that. These are the only remaining issues I see for the beta1 release, so things are very close. I would also like to use this library in my day job, so the sooner we can get it out the better. Regards, Matt J [1] https://github.com/apache/commons-geometry/pull/77 From: Singh, Baljit (GE Aviation, US) Sent: Tuesday, May 26, 2020 9:20 AM To: Gilles Sadowski ; dev@commons.apache.org Cc: mattjuntu...@apache.org Subject: Re: Apache Commons Geometry Release Gilles, Thanks for replying. I do not know (yet) if Commons Geometry has the same issues (or even other issues), but I would rather use something being actively developed vs. something that is EOL (Commons-Math3 v3.6.1 was released 4+ years ago). At least this way, I can report/fix any bugs and get the improvements with the new releases. And yes, I'm willing to be the first test subject. __ I would love to help with more improvements, but if there is no sight for the releases and the library thus cannot be used, I can't justify spending time on it. Commons Devs, Adding the Commons Dev ML per Gilles's request. In the email below, I asked when the first release of Commons Geometry will be. Some context (and intro): using Commons-Math3, I write geometry algorithms for our UAV flight management product at AiRXOS (part of GE Aviation). However, I'm discovering bugs in Commons-Math3, one of which I helped fix in Commons Geometry. I would like to use Commons Geometry instead (for reasons mentioned above). Regards, Baljit On 5/21/20, 9:02 PM, "Gilles Sadowski" wrote: Hello. 2020-05-21 20:32 UTC+02:00, Singh, Baljit (GE Aviation, US) : > Hi Matt, Gilles, > > Any updates on when the commons-geometry release is going to be? The question is of general interest. Could you please post it to the "dev" ML? > I’m finding > more and more issues with the package > org.apache.commons.math3.geometry.spherical.twod, and its causing issues > with our product. Is the code in "Commons Geometry" free of those issues? It would be nice to have unit tests that check those cases. > I would like to upgrade to something that is actively > being developed. Sure. So, you are user number "1" (?). ;-) > Looking at JIRA, it looks like the release is almost ready, > only 3 (minor) issues to go. If you can help with those... Thanks, Gilles > Regards, > Baljit > > > - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: Apache Commons Geometry Release
Hi Bajit,
My plan is to get a release of commons-geometry out as soon as possible,
although I have been saying this for more than a year at this point:-) However,
I actually believe we are very close now. There are only a few remaining issues
for the beta1 release and I currently have branches ready to merge for most of
them. The following issues are ready and waiting for merge:
-GEOMETRY-94: This adds Triangle3D and ConvexPolygon3D types, which are
essentially required for working with 3D models. I have a PR in [1] and am just
waiting another day or so to see if anyone has any feedback.
-GEOMETRY-77: Adds useful Bounds2D and Bounds3D classes. This is included in
the PR mentioned above.
-GEOMETRY-97: Changes from using the term "barycenter" to "centroid" for
describing the geometric center of objects. This is ready and waiting in the
wings for when the PR above is merged.
The following issues are not complete:
-GEOMETRY-50: Bug report submitted by you quite a while ago regarding overflow
in norm calculations. This is a tiny change in the code and I think we can just
go ahead and do it. However, I did find one small issue that I'd like to
discuss more that I put in the comments there yesterday.
-GEOMETRY-95: This is a request from Gilles to add a tutorial or more detailed
step-by-step user guide on how to use the library to perform constructive solid
geometry operations. We are currently discussing exactly what this means in the
comments on the issue. There would be some minor development work needed on
this but it will most likely be in one of the examples modules and not in the
main library. The main thing I can think of that we'd need would be a 3D model
file reader for some format. I'm picturing using the obj format since we
already have a writer for that.
These are the only remaining issues I see for the beta1 release, so things are
very close. I would also like to use this library in my day job, so the sooner
we can get it out the better.
Regards,
Matt J
[1] https://github.com/apache/commons-geometry/pull/77
From: Singh, Baljit (GE Aviation, US)
Sent: Tuesday, May 26, 2020 9:20 AM
To: Gilles Sadowski ; dev@commons.apache.org
Cc: mattjuntu...@apache.org
Subject: Re: Apache Commons Geometry Release
Gilles,
Thanks for replying. I do not know (yet) if Commons Geometry has the same
issues (or even other issues), but I would rather use something being actively
developed vs. something that is EOL (Commons-Math3 v3.6.1 was released 4+ years
ago). At least this way, I can report/fix any bugs and get the improvements
with the new releases. And yes, I'm willing to be the first test subject. __ I
would love to help with more improvements, but if there is no sight for the
releases and the library thus cannot be used, I can't justify spending time on
it.
Commons Devs,
Adding the Commons Dev ML per Gilles's request. In the email below, I asked
when the first release of Commons Geometry will be. Some context (and intro):
using Commons-Math3, I write geometry algorithms for our UAV flight management
product at AiRXOS (part of GE Aviation). However, I'm discovering bugs in
Commons-Math3, one of which I helped fix in Commons Geometry. I would like to
use Commons Geometry instead (for reasons mentioned above).
Regards,
Baljit
On 5/21/20, 9:02 PM, "Gilles Sadowski" wrote:
Hello.
2020-05-21 20:32 UTC+02:00, Singh, Baljit (GE Aviation, US)
:
> Hi Matt, Gilles,
>
> Any updates on when the commons-geometry release is going to be?
The question is of general interest. Could you please post it
to the "dev" ML?
> I’m finding
> more and more issues with the package
> org.apache.commons.math3.geometry.spherical.twod, and its causing issues
> with our product.
Is the code in "Commons Geometry" free of those issues?
It would be nice to have unit tests that check those cases.
> I would like to upgrade to something that is actively
> being developed.
Sure.
So, you are user number "1" (?). ;-)
> Looking at JIRA, it looks like the release is almost ready,
> only 3 (minor) issues to go.
If you can help with those...
Thanks,
Gilles
> Regards,
> Baljit
>
>
>
Re: Apache Commons Geometry Release
Gilles,
Thanks for replying. I do not know (yet) if Commons Geometry has the same
issues (or even other issues), but I would rather use something being actively
developed vs. something that is EOL (Commons-Math3 v3.6.1 was released 4+ years
ago). At least this way, I can report/fix any bugs and get the improvements
with the new releases. And yes, I'm willing to be the first test subject. __ I
would love to help with more improvements, but if there is no sight for the
releases and the library thus cannot be used, I can't justify spending time on
it.
Commons Devs,
Adding the Commons Dev ML per Gilles's request. In the email below, I asked
when the first release of Commons Geometry will be. Some context (and intro):
using Commons-Math3, I write geometry algorithms for our UAV flight management
product at AiRXOS (part of GE Aviation). However, I'm discovering bugs in
Commons-Math3, one of which I helped fix in Commons Geometry. I would like to
use Commons Geometry instead (for reasons mentioned above).
Regards,
Baljit
On 5/21/20, 9:02 PM, "Gilles Sadowski" wrote:
Hello.
2020-05-21 20:32 UTC+02:00, Singh, Baljit (GE Aviation, US)
:
> Hi Matt, Gilles,
>
> Any updates on when the commons-geometry release is going to be?
The question is of general interest. Could you please post it
to the "dev" ML?
> I’m finding
> more and more issues with the package
> org.apache.commons.math3.geometry.spherical.twod, and its causing issues
> with our product.
Is the code in "Commons Geometry" free of those issues?
It would be nice to have unit tests that check those cases.
> I would like to upgrade to something that is actively
> being developed.
Sure.
So, you are user number "1" (?). ;-)
> Looking at JIRA, it looks like the release is almost ready,
> only 3 (minor) issues to go.
If you can help with those...
Thanks,
Gilles
> Regards,
> Baljit
>
>
>
Re: [geometry] release
Gilles,
In regard to the roadmap, there has been steady progress but not much is
visible yet from the GitHub or JIRA point of view, unfortunately. I'm currently
working on the final items from the initial roadmap email I sent out, namely
the ones related to the BSP tree and Region API cleanup (GEOMETRY-32,
GEOMETRY-33, GEOMETRY-34, and GEOMETRY-24). It made the most sense to handle
all of these issues with a general refactoring of the core classes, which is
what I'm doing on my working branch
(https://github.com/darkma773r/commons-geometry/tree/geometry-32-working). I
currently have all of the BSP tree code done (the biggest chunk of this) along
with the 1D and most of the 2D Euclidean classes. I have yet to do Euclidean 3D
and spherical 1D and 2D. Here is a comparison of the old API vs the new API for
calculating the area of the difference of two 2D regions defined by vertex
paths:
--- Old API ---
DoublePrecisionContext precision = ...;
Vector2D[] aVertices = { ... };
Vector2D[] bVertices = { ... };
PolygonsSet a = new PolygonsSet(precision, aVertices);
PolygonsSet b = new PolygonsSet(precision, bVertices);
PolygonsSet c = (PolygonsSet) new
RegionFactory().difference(a.copySelf(), b.copySelf());
double area = c.getSize();
--- New API ---
DoublePrecisionContext precision = ...;
List aVertices = ...;
List bVertices = ...;
RegionBSPTree2D a = LineSegmentPath.fromVertices(aVertices, precision).toTree();
RegionBSPTree2D b = LineSegmentPath.fromVertices(bVertices, precision).toTree();
a.difference(b);
double area = a.getSize();
I'll keep you updated as I get closer to finishing. It is a large change so we
will undoubtedly need to discuss quite a few things. Also, if anyone has free
time and wants to help with the spherical classes on my working branch, that
would definitely help speed things along.
Regards,
Matt
From: Rob Tompkins
Sent: Thursday, May 23, 2019 12:31 PM
To: dev@commons.apache.org
Subject: Re: [geometry] release
On 5/23/2019 9:49 AM, Gilles Sadowski wrote:
> Hi.
>
> Le jeu. 23 mai 2019 à 15:37, Rob Tompkins a écrit :
>>
>>
>>> On May 23, 2019, at 7:25 AM, Gilles Sadowski wrote:
>>>
>>> Hi.
>>>
>>>> Le mer. 22 mai 2019 à 14:07, Matt Juntunen a
>>>> écrit :
>>>>
>>>> Hi Sven,
>>>>
>>>> Until we can roll out an actual release of numbers and geometry,
>>> Any update of the roadmap? :-)
>> Do we have a reason to not release?
> Code is in the middle of being refactored, and contains many
> to-be-deleted classes.
Gotcha...was going to offer to send it up if there was an appetite.
>
> Gilles
>
>> -Rob
>>
>>>> [...]
> -
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
>
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
Re: [geometry] release
On 5/23/2019 9:49 AM, Gilles Sadowski wrote: Hi. Le jeu. 23 mai 2019 à 15:37, Rob Tompkins a écrit : On May 23, 2019, at 7:25 AM, Gilles Sadowski wrote: Hi. Le mer. 22 mai 2019 à 14:07, Matt Juntunen a écrit : Hi Sven, Until we can roll out an actual release of numbers and geometry, Any update of the roadmap? :-) Do we have a reason to not release? Code is in the middle of being refactored, and contains many to-be-deleted classes. Gotcha...was going to offer to send it up if there was an appetite. Gilles -Rob [...] - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: [geometry] release
Hi. Le jeu. 23 mai 2019 à 15:37, Rob Tompkins a écrit : > > > > > On May 23, 2019, at 7:25 AM, Gilles Sadowski wrote: > > > > Hi. > > > >> Le mer. 22 mai 2019 à 14:07, Matt Juntunen a > >> écrit : > >> > >> Hi Sven, > >> > >> Until we can roll out an actual release of numbers and geometry, > > > > Any update of the roadmap? :-) > > Do we have a reason to not release? Code is in the middle of being refactored, and contains many to-be-deleted classes. Gilles > > -Rob > > > > >> [...] - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: [geometry] release
> On May 23, 2019, at 7:25 AM, Gilles Sadowski wrote: > > Hi. > >> Le mer. 22 mai 2019 à 14:07, Matt Juntunen a >> écrit : >> >> Hi Sven, >> >> Until we can roll out an actual release of numbers and geometry, > > Any update of the roadmap? :-) Do we have a reason to not release? -Rob > >> I think your best bet is to fork commons-geometry and all of its SNAPSHOT >> dependencies, change the groupIds and/or artifactIds in the poms to >> something custom (to avoid conflicts later on), and then release those >> directly to your artifactory server. You'll probably need to make other >> modifications to the poms in order to get this to work. This process will >> most likely be very painful. If you only use small portions of the geometry >> code, another option would be to temporarily copy some of the classes from >> commons-geometry directly into your application code. This would avoid a lot >> of messing around with release processes and would make the commons-geometry >> behavior that your application relies on directly visible. I would use this >> approach, if at all possible, until a real release can be made. >> >> Godspeed. >> >> -Matt >> ____ >> From: Sven Rathgeber >> Sent: Wednesday, May 22, 2019 3:23 AM >> To: dev@commons.apache.org >> Subject: [geometry] release >> >> Hi, >> >> I use in one of our applications the current state >> of https://github.com/apache/commons-geometry >> (c45647f45df7d81819e47ad6bd0d342069fb305d ). >> (... which has a couple of child projects and relies on the current state of >> common-numbers -> in sum about 15 jars.) >> >> Now I have to release my application in order to bring it to our testsystem, >> but maven >> is not happy about the SNAPSHOT release of commons-geometry. >> >> I tried with a profile to release it to our artifactory server but that >> looks like a pretty hard >> way. Currently maven wants me to commit to 'https://gitbox.apache.org' :), >> which is not exactly what I want. >> >> Do you see a way how I can release my application ? > > This could be an approach: >https://maven.apache.org/plugins/maven-shade-plugin/ > > Regards, > Gilles > >> >> Cheers. >> Sven >> >> > > - > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Aw: Re: [geometry] release
Hi, > This could be an approach: > https://maven.apache.org/plugins/maven-shade-plugin/[https://maven.apache.org/plugins/maven-shade-plugin/] I started to think in a similar direction and finally got it with the assembly-plugin (jar-with-dependencies). And "mvn deploy:deploy-file ..." did the rest :) Thanks for your ideas. Sven - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: [geometry] release
Hi. Le mer. 22 mai 2019 à 14:07, Matt Juntunen a écrit : > > Hi Sven, > > Until we can roll out an actual release of numbers and geometry, Any update of the roadmap? :-) > I think your best bet is to fork commons-geometry and all of its SNAPSHOT > dependencies, change the groupIds and/or artifactIds in the poms to something > custom (to avoid conflicts later on), and then release those directly to your > artifactory server. You'll probably need to make other modifications to the > poms in order to get this to work. This process will most likely be very > painful. If you only use small portions of the geometry code, another option > would be to temporarily copy some of the classes from commons-geometry > directly into your application code. This would avoid a lot of messing around > with release processes and would make the commons-geometry behavior that your > application relies on directly visible. I would use this approach, if at all > possible, until a real release can be made. > > Godspeed. > > -Matt > > From: Sven Rathgeber > Sent: Wednesday, May 22, 2019 3:23 AM > To: dev@commons.apache.org > Subject: [geometry] release > > Hi, > > I use in one of our applications the current state > of https://github.com/apache/commons-geometry > (c45647f45df7d81819e47ad6bd0d342069fb305d ). > (... which has a couple of child projects and relies on the current state of > common-numbers -> in sum about 15 jars.) > > Now I have to release my application in order to bring it to our testsystem, > but maven > is not happy about the SNAPSHOT release of commons-geometry. > > I tried with a profile to release it to our artifactory server but that > looks like a pretty hard > way. Currently maven wants me to commit to 'https://gitbox.apache.org' :), > which is not exactly what I want. > > Do you see a way how I can release my application ? This could be an approach: https://maven.apache.org/plugins/maven-shade-plugin/ Regards, Gilles > > Cheers. > Sven > > - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: [geometry] release
Hi Sven, Until we can roll out an actual release of numbers and geometry, I think your best bet is to fork commons-geometry and all of its SNAPSHOT dependencies, change the groupIds and/or artifactIds in the poms to something custom (to avoid conflicts later on), and then release those directly to your artifactory server. You'll probably need to make other modifications to the poms in order to get this to work. This process will most likely be very painful. If you only use small portions of the geometry code, another option would be to temporarily copy some of the classes from commons-geometry directly into your application code. This would avoid a lot of messing around with release processes and would make the commons-geometry behavior that your application relies on directly visible. I would use this approach, if at all possible, until a real release can be made. Godspeed. -Matt From: Sven Rathgeber Sent: Wednesday, May 22, 2019 3:23 AM To: dev@commons.apache.org Subject: [geometry] release Hi, I use in one of our applications the current state of https://github.com/apache/commons-geometry (c45647f45df7d81819e47ad6bd0d342069fb305d ). (... which has a couple of child projects and relies on the current state of common-numbers -> in sum about 15 jars.) Now I have to release my application in order to bring it to our testsystem, but maven is not happy about the SNAPSHOT release of commons-geometry. I tried with a profile to release it to our artifactory server but that looks like a pretty hard way. Currently maven wants me to commit to 'https://gitbox.apache.org' :), which is not exactly what I want. Do you see a way how I can release my application ? Cheers. Sven - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
[geometry] release
Hi, I use in one of our applications the current state of https://github.com/apache/commons-geometry (c45647f45df7d81819e47ad6bd0d342069fb305d ). (... which has a couple of child projects and relies on the current state of common-numbers -> in sum about 15 jars.) Now I have to release my application in order to bring it to our testsystem, but maven is not happy about the SNAPSHOT release of commons-geometry. I tried with a profile to release it to our artifactory server but that looks like a pretty hard way. Currently maven wants me to commit to 'https://gitbox.apache.org' :), which is not exactly what I want. Do you see a way how I can release my application ? Cheers. Sven - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
