You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by Sven Rathgeber <sv...@web.de> on 2019/05/22 07:23:28 UTC

[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-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org


Re: [geometry] release

Posted by Matt Juntunen <ma...@hotmail.com>.
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<Vector2D>().difference(a.copySelf(), b.copySelf());

double area = c.getSize();


--- New API ---

DoublePrecisionContext precision = ...;
List<Vector2D> aVertices = ...;
List<Vector2D> 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 <ch...@gmail.com>
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 <ch...@gmail.com> a écrit :
>>
>>
>>> On May 23, 2019, at 7:25 AM, Gilles Sadowski <gi...@gmail.com> wrote:
>>>
>>> Hi.
>>>
>>>> Le mer. 22 mai 2019 à 14:07, Matt Juntunen <ma...@hotmail.com> 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-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org


Re: [geometry] release

Posted by Rob Tompkins <ch...@gmail.com>.
On 5/23/2019 9:49 AM, Gilles Sadowski wrote:
> Hi.
>
> Le jeu. 23 mai 2019 à 15:37, Rob Tompkins <ch...@gmail.com> a écrit :
>>
>>
>>> On May 23, 2019, at 7:25 AM, Gilles Sadowski <gi...@gmail.com> wrote:
>>>
>>> Hi.
>>>
>>>> Le mer. 22 mai 2019 à 14:07, Matt Juntunen <ma...@hotmail.com> 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-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org


Re: [geometry] release

Posted by Gilles Sadowski <gi...@gmail.com>.
Hi.

Le jeu. 23 mai 2019 à 15:37, Rob Tompkins <ch...@gmail.com> a écrit :
>
>
>
> > On May 23, 2019, at 7:25 AM, Gilles Sadowski <gi...@gmail.com> wrote:
> >
> > Hi.
> >
> >> Le mer. 22 mai 2019 à 14:07, Matt Juntunen <ma...@hotmail.com> 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-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org


Re: [geometry] release

Posted by Rob Tompkins <ch...@gmail.com>.

> On May 23, 2019, at 7:25 AM, Gilles Sadowski <gi...@gmail.com> wrote:
> 
> Hi.
> 
>> Le mer. 22 mai 2019 à 14:07, Matt Juntunen <ma...@hotmail.com> 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 <sv...@web.de>
>> 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-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org


Aw: Re: [geometry] release

Posted by Sven Rathgeber <sv...@web.de>.
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-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org


Re: [geometry] release

Posted by Gilles Sadowski <gi...@gmail.com>.
Hi.

Le mer. 22 mai 2019 à 14:07, Matt Juntunen <ma...@hotmail.com> 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 <sv...@web.de>
> 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-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org


Re: [geometry] release

Posted by Matt Juntunen <ma...@hotmail.com>.
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 <sv...@web.de>
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-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org