Hi Luc, Luc Maisonobe wrote:
> This is a [VOTE] for releasing Apache Commons Math 3.4.1 from release > candidate 1. > > Tag name: > MATH_3_4_1_RC1 (signature can be checked from git using 'git tag -v') > > Tag URL: > > <https://git-wip-us.apache.org/repos/asf?p=commons-math.git;a=commit;h=ef6e0f882819e7c5230aece1610297e67775cca2> > > Commit ID the tag points at: > ef6e0f882819e7c5230aece1610297e67775cca2 > > Site: > <http://people.apache.org/~luc/commons-math-3.4.1-RC1-site> > > Distribution files: > https://dist.apache.org/repos/dist/dev/commons/math/ > > Distribution files hashes (SHA1): > 165244fec72fa874ac5efe2d3b7926ab853e0783 commons-math3-3.4.1-bin.tar.gz > 2e9b1df32db85e3bc290d06eda26a01ef5ed6182 commons-math3-3.4.1-bin.zip > 5068444e55b27a506183a86b2df071b3868b0104 commons-math3-3.4.1-src.tar.gz > 2c4f0742a235a71f9b3cb09dee1946e270055d43 commons-math3-3.4.1-src.zip > > KEYS file to check signatures: > http://www.apache.org/dist/commons/KEYS > > Maven artifacts: > > <https://repository.apache.org/content/repositories/orgapachecommons-1075/org/apache/commons/commons-math3/3.4.1/> > > [ ] +1 Release it. > [ ] +0 Go ahead; I don't care. > [ ] -0 There are a few minor glitches: ... > [ ] -1 No, do not release it because ... > > This vote will close in 72 hours, at 2015-01-11T19:30:00Z (this is UTC > time). there are oddities in the build now. Due to the maven-jgit-buildnumber- plugin you have to use now Java 6 to build. Additionally this plugin gives every time a big error, when you build from the source tar ball: =================== %< ===================== [INFO] --- maven-jgit-buildnumber-plugin:1.2.8:extract-buildnumber (default) @ commons-math3 --- [ERROR] java.lang.IllegalArgumentException: One of setGitDir or setWorkTree must be called. at org.eclipse.jgit.lib.BaseRepositoryBuilder.requireGitDirOrWorkTree(BaseRepositoryBuilder.java:582) at org.eclipse.jgit.lib.BaseRepositoryBuilder.setup(BaseRepositoryBuilder.java:550) at org.eclipse.jgit.storage.file.FileRepositoryBuilder.build(FileRepositoryBuilder.java:89) at ru.concerteza.util.buildnumber.BuildNumberExtractor.extract(BuildNumberExtractor.java:38) at ru.concerteza.util.buildnumber.JGitBuildNumberMojo.execute(JGitBuildNumberMojo.java:124) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:132) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80) at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:120) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:347) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:154) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:582) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:214) at org.apache.maven.cli.MavenCli.main(MavenCli.java:158) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37) at java.lang.reflect.Method.invoke(Method.java:611) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356) =================== %< ===================== Fortunately the build does not fail. However, it seems that we determine the build number twice now: =================== %< ===================== [INFO] --- buildnumber-maven-plugin:1.2:create (default) @ commons-math3 --- [INFO] Checking for local modifications: skipped. [INFO] Updating project files from SCM: skipped. [INFO] Executing: /bin/sh -c cd /home/joehni/tmp/download/commons- math3-3.4.1-src && git rev-parse --verify HEAD [INFO] Working directory: /home/joehni/tmp/download/commons-math3-3.4.1-src [INFO] Storing buildNumber: ?????? at timestamp: 1420792613249 [INFO] Executing: /bin/sh -c cd /home/joehni/tmp/download/commons- math3-3.4.1-src && git rev-parse --verify HEAD [INFO] Working directory: /home/joehni/tmp/download/commons-math3-3.4.1-src [INFO] Storing buildScmBranch: UNKNOWN_BRANCH [INFO] [INFO] --- maven-jgit-buildnumber-plugin:1.2.8:extract-buildnumber (default) @ commons-math3 --- [ERROR] =================== %< ===================== So, do we need this plugin at all? Nevertheless, I could build and test from the source tar ball with my complete compiler zoo. +1 Cheers, Jörg Cheers, Jörg --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
