[configuration]

classic Classic list List threaded Threaded
10 messages Options
Reply | Threaded
Open this post in threaded view
|

[configuration]

garydgregory
Hi All:

Has anyone seen this:

[INFO] Generating "JDepend" report       ---
jdepend-maven-plugin:2.0:generate-no-fork
[INFO]
------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO]
------------------------------------------------------------------------
[INFO] Total time:  02:40 min
[INFO] Finished at: 2019-05-21T19:50:56-04:00
[INFO]
------------------------------------------------------------------------
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-site-plugin:3.7.1:site (default-site) on
project commons-configuration2: Error during site generation:
C:\git\commons-configuration\target\site\org.apache.commons_commons-configuration2_2.4C:\git\commons-configuration\target\commons-configuration2-2.5-SNAPSHOT.jar_output.html
(The filename, directory name, or volume label syntax is incorrect) ->
[Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
goal org.apache.maven.plugins:maven-site-plugin:3.7.1:site (default-site)
on project commons-configuration2: Error during site generation
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:215)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:156)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:148)
    at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
(LifecycleModuleBuilder.java:117)
    at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
(LifecycleModuleBuilder.java:81)
    at
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
(SingleThreadedBuilder.java:56)
    at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
(LifecycleStarter.java:128)
    at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
    at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
    at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
    at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956)
    at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:288)
    at org.apache.maven.cli.MavenCli.main (MavenCli.java:192)
    at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke
(NativeMethodAccessorImpl.java:62)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke
(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke (Method.java:498)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
(Launcher.java:282)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launch
(Launcher.java:225)
    at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
(Launcher.java:406)
    at org.codehaus.plexus.classworlds.launcher.Launcher.main
(Launcher.java:347)
Caused by: org.apache.maven.plugin.MojoExecutionException: Error during
site generation
    at org.apache.maven.plugins.site.render.SiteMojo.execute
(SiteMojo.java:161)
    at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
(DefaultBuildPluginManager.java:137)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:210)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:156)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:148)
    at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
(LifecycleModuleBuilder.java:117)
    at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
(LifecycleModuleBuilder.java:81)
    at
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
(SingleThreadedBuilder.java:56)
    at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
(LifecycleStarter.java:128)
    at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
    at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
    at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
    at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956)
    at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:288)
    at org.apache.maven.cli.MavenCli.main (MavenCli.java:192)
    at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke
(NativeMethodAccessorImpl.java:62)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke
(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke (Method.java:498)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
(Launcher.java:282)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launch
(Launcher.java:225)
    at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
(Launcher.java:406)
    at org.codehaus.plexus.classworlds.launcher.Launcher.main
(Launcher.java:347)
Caused by: java.io.FileNotFoundException:
C:\git\commons-configuration\target\site\org.apache.commons_commons-configuration2_2.4C:\git\commons-configuration\target\commons-configuration2-2.5-SNAPSHOT.jar_output.html
(The filename, directory name, or volume label syntax is incorrect)
    at java.io.FileOutputStream.open0 (Native Method)
    at java.io.FileOutputStream.open (FileOutputStream.java:270)
    at java.io.FileOutputStream.<init> (FileOutputStream.java:213)
    at java.io.FileOutputStream.<init> (FileOutputStream.java:162)
    at org.codehaus.plexus.util.WriterFactory.newWriter
(WriterFactory.java:175)
    at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render
(DefaultSiteRenderer.java:347)
    at org.apache.maven.plugins.site.render.SiteMojo.renderLocale
(SiteMojo.java:198)
    at org.apache.maven.plugins.site.render.SiteMojo.execute
(SiteMojo.java:147)
    at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
(DefaultBuildPluginManager.java:137)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:210)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:156)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:148)
    at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
(LifecycleModuleBuilder.java:117)
    at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
(LifecycleModuleBuilder.java:81)
    at
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
(SingleThreadedBuilder.java:56)
    at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
(LifecycleStarter.java:128)
    at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
    at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
    at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
    at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956)
    at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:288)
    at org.apache.maven.cli.MavenCli.main (MavenCli.java:192)
    at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke
(NativeMethodAccessorImpl.java:62)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke
(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke (Method.java:498)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
(Launcher.java:282)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launch
(Launcher.java:225)
    at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
(Launcher.java:406)
    at org.codehaus.plexus.classworlds.launcher.Launcher.main
(Launcher.java:347)
[ERROR]
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions,
please read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException

I get it when I run:

mvn install site -DskipTests -Ddoclint=none -e

Using:

Apache Maven 3.6.1 (d66c9c0b3152b2e69ee9bac180bb8fcc8e6af555;
2019-04-04T15:00:29-04:00)
Maven home: C:\Java\apache-maven-3.6.1\bin\..
Java version: 1.8.0_212, vendor: Oracle Corporation, runtime: C:\Program
Files\Java\jdk1.8.0_212\jre
Default locale: en_US, platform encoding: Cp1252
OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"

Gary
Reply | Threaded
Open this post in threaded view
|

Re: [configuration]

Matt Sicker
That looks like it’s probably a typo of some sort from the parent pom. I
haven’t looked at the source though.

On Tue, May 21, 2019 at 18:53, Gary Gregory <[hidden email]> wrote:

> Hi All:
>
> Has anyone seen this:
>
> [INFO] Generating "JDepend" report       ---
> jdepend-maven-plugin:2.0:generate-no-fork
> [INFO]
> ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Total time:  02:40 min
> [INFO] Finished at: 2019-05-21T19:50:56-04:00
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-site-plugin:3.7.1:site (default-site) on
> project commons-configuration2: Error during site generation:
>
> C:\git\commons-configuration\target\site\org.apache.commons_commons-configuration2_2.4C:\git\commons-configuration\target\commons-configuration2-2.5-SNAPSHOT.jar_output.html
> (The filename, directory name, or volume label syntax is incorrect) ->
> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-site-plugin:3.7.1:site (default-site)
> on project commons-configuration2: Error during site generation
>     at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:215)
>     at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:156)
>     at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:148)
>     at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:117)
>     at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:81)
>     at
>
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
> (SingleThreadedBuilder.java:56)
>     at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
> (LifecycleStarter.java:128)
>     at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
>     at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
>     at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
>     at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956)
>     at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:288)
>     at org.apache.maven.cli.MavenCli.main (MavenCli.java:192)
>     at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
>     at sun.reflect.NativeMethodAccessorImpl.invoke
> (NativeMethodAccessorImpl.java:62)
>     at sun.reflect.DelegatingMethodAccessorImpl.invoke
> (DelegatingMethodAccessorImpl.java:43)
>     at java.lang.reflect.Method.invoke (Method.java:498)
>     at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
> (Launcher.java:282)
>     at org.codehaus.plexus.classworlds.launcher.Launcher.launch
> (Launcher.java:225)
>     at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
> (Launcher.java:406)
>     at org.codehaus.plexus.classworlds.launcher.Launcher.main
> (Launcher.java:347)
> Caused by: org.apache.maven.plugin.MojoExecutionException: Error during
> site generation
>     at org.apache.maven.plugins.site.render.SiteMojo.execute
> (SiteMojo.java:161)
>     at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:137)
>     at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:210)
>     at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:156)
>     at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:148)
>     at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:117)
>     at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:81)
>     at
>
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
> (SingleThreadedBuilder.java:56)
>     at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
> (LifecycleStarter.java:128)
>     at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
>     at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
>     at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
>     at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956)
>     at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:288)
>     at org.apache.maven.cli.MavenCli.main (MavenCli.java:192)
>     at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
>     at sun.reflect.NativeMethodAccessorImpl.invoke
> (NativeMethodAccessorImpl.java:62)
>     at sun.reflect.DelegatingMethodAccessorImpl.invoke
> (DelegatingMethodAccessorImpl.java:43)
>     at java.lang.reflect.Method.invoke (Method.java:498)
>     at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
> (Launcher.java:282)
>     at org.codehaus.plexus.classworlds.launcher.Launcher.launch
> (Launcher.java:225)
>     at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
> (Launcher.java:406)
>     at org.codehaus.plexus.classworlds.launcher.Launcher.main
> (Launcher.java:347)
> Caused by: java.io.FileNotFoundException:
>
> C:\git\commons-configuration\target\site\org.apache.commons_commons-configuration2_2.4C:\git\commons-configuration\target\commons-configuration2-2.5-SNAPSHOT.jar_output.html
> (The filename, directory name, or volume label syntax is incorrect)
>     at java.io.FileOutputStream.open0 (Native Method)
>     at java.io.FileOutputStream.open (FileOutputStream.java:270)
>     at java.io.FileOutputStream.<init> (FileOutputStream.java:213)
>     at java.io.FileOutputStream.<init> (FileOutputStream.java:162)
>     at org.codehaus.plexus.util.WriterFactory.newWriter
> (WriterFactory.java:175)
>     at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render
> (DefaultSiteRenderer.java:347)
>     at org.apache.maven.plugins.site.render.SiteMojo.renderLocale
> (SiteMojo.java:198)
>     at org.apache.maven.plugins.site.render.SiteMojo.execute
> (SiteMojo.java:147)
>     at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:137)
>     at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:210)
>     at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:156)
>     at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:148)
>     at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:117)
>     at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:81)
>     at
>
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
> (SingleThreadedBuilder.java:56)
>     at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
> (LifecycleStarter.java:128)
>     at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
>     at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
>     at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
>     at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956)
>     at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:288)
>     at org.apache.maven.cli.MavenCli.main (MavenCli.java:192)
>     at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
>     at sun.reflect.NativeMethodAccessorImpl.invoke
> (NativeMethodAccessorImpl.java:62)
>     at sun.reflect.DelegatingMethodAccessorImpl.invoke
> (DelegatingMethodAccessorImpl.java:43)
>     at java.lang.reflect.Method.invoke (Method.java:498)
>     at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
> (Launcher.java:282)
>     at org.codehaus.plexus.classworlds.launcher.Launcher.launch
> (Launcher.java:225)
>     at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
> (Launcher.java:406)
>     at org.codehaus.plexus.classworlds.launcher.Launcher.main
> (Launcher.java:347)
> [ERROR]
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions,
> please read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
>
> I get it when I run:
>
> mvn install site -DskipTests -Ddoclint=none -e
>
> Using:
>
> Apache Maven 3.6.1 (d66c9c0b3152b2e69ee9bac180bb8fcc8e6af555;
> 2019-04-04T15:00:29-04:00)
> Maven home: C:\Java\apache-maven-3.6.1\bin\..
> Java version: 1.8.0_212, vendor: Oracle Corporation, runtime: C:\Program
> Files\Java\jdk1.8.0_212\jre
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
>
> Gary
>
--
Matt Sicker <[hidden email]>
Reply | Threaded
Open this post in threaded view
|

[geometry] release

Sven Rathgeber
In reply to this post by garydgregory
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: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [geometry] release

Matt Juntunen
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 <[hidden email]>
Sent: Wednesday, May 22, 2019 3:23 AM
To: [hidden email]
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: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [geometry] release

Gilles Sadowski-2
Hi.

Le mer. 22 mai 2019 à 14:07, Matt Juntunen <[hidden email]> 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 <[hidden email]>
> Sent: Wednesday, May 22, 2019 3:23 AM
> To: [hidden email]
> 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: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Aw: Re: [geometry] release

Sven Rathgeber
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: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [geometry] release

Rob Tompkins
In reply to this post by Gilles Sadowski-2


> On May 23, 2019, at 7:25 AM, Gilles Sadowski <[hidden email]> wrote:
>
> Hi.
>
>> Le mer. 22 mai 2019 à 14:07, Matt Juntunen <[hidden email]> 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 <[hidden email]>
>> Sent: Wednesday, May 22, 2019 3:23 AM
>> To: [hidden email]
>> 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: [hidden email]
> For additional commands, e-mail: [hidden email]
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [geometry] release

Gilles Sadowski-2
Hi.

Le jeu. 23 mai 2019 à 15:37, Rob Tompkins <[hidden email]> a écrit :

>
>
>
> > On May 23, 2019, at 7:25 AM, Gilles Sadowski <[hidden email]> wrote:
> >
> > Hi.
> >
> >> Le mer. 22 mai 2019 à 14:07, Matt Juntunen <[hidden email]> 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: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [geometry] release

Rob Tompkins

On 5/23/2019 9:49 AM, Gilles Sadowski wrote:

> Hi.
>
> Le jeu. 23 mai 2019 à 15:37, Rob Tompkins <[hidden email]> a écrit :
>>
>>
>>> On May 23, 2019, at 7:25 AM, Gilles Sadowski <[hidden email]> wrote:
>>>
>>> Hi.
>>>
>>>> Le mer. 22 mai 2019 à 14:07, Matt Juntunen <[hidden email]> 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: [hidden email]
> For additional commands, e-mail: [hidden email]
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [geometry] release

Matt Juntunen
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 <[hidden email]>
Sent: Thursday, May 23, 2019 12:31 PM
To: [hidden email]
Subject: Re: [geometry] release


On 5/23/2019 9:49 AM, Gilles Sadowski wrote:

> Hi.
>
> Le jeu. 23 mai 2019 à 15:37, Rob Tompkins <[hidden email]> a écrit :
>>
>>
>>> On May 23, 2019, at 7:25 AM, Gilles Sadowski <[hidden email]> wrote:
>>>
>>> Hi.
>>>
>>>> Le mer. 22 mai 2019 à 14:07, Matt Juntunen <[hidden email]> 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: [hidden email]
> For additional commands, e-mail: [hidden email]
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]