Guys,
We have uploaded release candidate to https://dist.apache.org/repos/dist/dev/incubator/ignite/1.1.0-rc3/ Tag name is ignite-1.1.0-incubating-rc3 We fixed rat issues and added "-incubating" to the version and many more changes which are described in devnotes (link below). DEVNOTES https://git-wip-us.apache.org/repos/asf?p=incubator-ignite.git;a=blob_plain;f=DEVNOTES.txt;hb=refs/tags/ignite-1.1.0-incubating-rc3 RELEASENOTES https://git-wip-us.apache.org/repos/asf?p=incubator-ignite.git;a=blob_plain;f=RELEASE_NOTES.txt;hb=refs/tags/ignite-1.1.0-incubating-rc3 Please start voting. +1 - to accept Apache Ignite (incubating) 1.1.0 0 - don't care either way -1 - DO NOT accept Apache Ignite (incubating) 1.1.0 (explain why) Thanks! --Yakov |
+1, looks good to me.
On Fri, May 8, 2015 at 5:26 PM, Yakov Zhdanov <[hidden email]> wrote: > Guys, > > We have uploaded release candidate to > https://dist.apache.org/repos/dist/dev/incubator/ignite/1.1.0-rc3/ > > Tag name is > ignite-1.1.0-incubating-rc3 > > We fixed rat issues and added "-incubating" to the version and many more > changes which are > described in devnotes (link below). > > DEVNOTES > > https://git-wip-us.apache.org/repos/asf?p=incubator-ignite.git;a=blob_plain;f=DEVNOTES.txt;hb=refs/tags/ignite-1.1.0-incubating-rc3 > > RELEASENOTES > > https://git-wip-us.apache.org/repos/asf?p=incubator-ignite.git;a=blob_plain;f=RELEASE_NOTES.txt;hb=refs/tags/ignite-1.1.0-incubating-rc3 > > Please start voting. > > +1 - to accept Apache Ignite (incubating) 1.1.0 > 0 - don't care either way > -1 - DO NOT accept Apache Ignite (incubating) 1.1.0 (explain why) > > Thanks! > > --Yakov > |
In reply to this post by yzhdanov
Unless it is my environment issue (which doesn't seem to be likely) -1 Here's the problem though: $ ./bin/ignite.sh ./bin/ignite.sh: line 61: /home/cos/workspaces/1.1.0-RC3/ignite-1.1.0-incubating-src/bin/include/target-classpath.sh: No such file or directory Error: Could not find or load main class org.apache.ignite.startup.cmdline.CommandLineRandomNumberGenerator Error: Could not find or load main class org.apache.ignite.internal.util.portscanner.GridJmxPortFinder Signatures are correct, but md5sum and sha1sum are malformed. They should look like $ md5sum ignite-1.1.0-incubating-src.zip 9a67c904b6ec129209b4ab00c6fa32b1 ignite-1.1.0-incubating-src.zip $ sha1sum ignite-1.1.0-incubating-src.zip f465d5928ea3da7199fb938de5af56e34706623e ignite-1.1.0-incubating-src.zip otherwise auto-checking won't work. Please fix in the next respin (if going to happen per above) or in the next release. Also needs to be documented. A somewhat minor issue: I thought that has been fixed long time ago, but running mvn clean package -DskipTests -Prelease,lgpl gives this [INFO] An Ant BuildException has occured: exec returned: 128 around Ant part ...<exec outputproperty="ignite.build" executable="git" failonerror="true">... @ 20:75 in /biggy/workspaces/1.1.0-RC3/ignite-1.1.0-incubating-src/modules/core/target/antrun/build-main.xml /biggy/workspaces/1.1.0-RC3/ignite-1.1.0-incubating-src/modules/core/target/antrun/build-main.xml:20: exec returned: 128 Although, of course, I have git in the $PATH. Thanks, Cos On Fri, May 08, 2015 at 05:26PM, Yakov Zhdanov wrote: > Guys, > > We have uploaded release candidate to > https://dist.apache.org/repos/dist/dev/incubator/ignite/1.1.0-rc3/ > > Tag name is > ignite-1.1.0-incubating-rc3 > > We fixed rat issues and added "-incubating" to the version and many more > changes which are > described in devnotes (link below). > > DEVNOTES > https://git-wip-us.apache.org/repos/asf?p=incubator-ignite.git;a=blob_plain;f=DEVNOTES.txt;hb=refs/tags/ignite-1.1.0-incubating-rc3 > > RELEASENOTES > https://git-wip-us.apache.org/repos/asf?p=incubator-ignite.git;a=blob_plain;f=RELEASE_NOTES.txt;hb=refs/tags/ignite-1.1.0-incubating-rc3 > > Please start voting. > > +1 - to accept Apache Ignite (incubating) 1.1.0 > 0 - don't care either way > -1 - DO NOT accept Apache Ignite (incubating) 1.1.0 (explain why) > > Thanks! > > --Yakov |
+1
./ignite.sh successfully started the node. Cos, you probably have incorrect IGNITE_HOME in environment. Git error is OK, build procedure tries to get values from Git, fails to do that, but doesn't stop and use default values (at least this is how it works for me). On Fri, May 8, 2015 at 5:51 PM, Konstantin Boudnik <[hidden email]> wrote: > > Unless it is my environment issue (which doesn't seem to be likely) > > -1 > > Here's the problem though: > $ ./bin/ignite.sh > ./bin/ignite.sh: line 61: > /home/cos/workspaces/1.1.0-RC3/ignite-1.1.0-incubating-src/bin/include/target-classpath.sh: > No such file or directory > Error: Could not find or load main class > org.apache.ignite.startup.cmdline.CommandLineRandomNumberGenerator > Error: Could not find or load main class > org.apache.ignite.internal.util.portscanner.GridJmxPortFinder > > Signatures are correct, but md5sum and sha1sum are malformed. They should > look > like > > $ md5sum ignite-1.1.0-incubating-src.zip > 9a67c904b6ec129209b4ab00c6fa32b1 ignite-1.1.0-incubating-src.zip > $ sha1sum ignite-1.1.0-incubating-src.zip > f465d5928ea3da7199fb938de5af56e34706623e ignite-1.1.0-incubating-src.zip > > otherwise auto-checking won't work. Please fix in the next respin (if > going to > happen per above) or in the next release. Also needs to be documented. > > > A somewhat minor issue: > > I thought that has been fixed long time ago, but running > mvn clean package -DskipTests -Prelease,lgpl > gives this > > [INFO] An Ant BuildException has occured: exec returned: 128 around Ant > part ...<exec outputproperty="ignite.build" executable="git" > failonerror="true">... @ 20:75 in > > /biggy/workspaces/1.1.0-RC3/ignite-1.1.0-incubating-src/modules/core/target/antrun/build-main.xml > /biggy/workspaces/1.1.0-RC3/ignite-1.1.0-incubating-src/modules/core/target/antrun/build-main.xml:20: > exec returned: 128 > > Although, of course, I have git in the $PATH. > > Thanks, > Cos > > On Fri, May 08, 2015 at 05:26PM, Yakov Zhdanov wrote: > > Guys, > > > > We have uploaded release candidate to > > https://dist.apache.org/repos/dist/dev/incubator/ignite/1.1.0-rc3/ > > > > Tag name is > > ignite-1.1.0-incubating-rc3 > > > > We fixed rat issues and added "-incubating" to the version and many more > > changes which are > > described in devnotes (link below). > > > > DEVNOTES > > > https://git-wip-us.apache.org/repos/asf?p=incubator-ignite.git;a=blob_plain;f=DEVNOTES.txt;hb=refs/tags/ignite-1.1.0-incubating-rc3 > > > > RELEASENOTES > > > https://git-wip-us.apache.org/repos/asf?p=incubator-ignite.git;a=blob_plain;f=RELEASE_NOTES.txt;hb=refs/tags/ignite-1.1.0-incubating-rc3 > > > > Please start voting. > > > > +1 - to accept Apache Ignite (incubating) 1.1.0 > > 0 - don't care either way > > -1 - DO NOT accept Apache Ignite (incubating) 1.1.0 (explain why) > > > > Thanks! > > > > --Yakov > |
On Fri, May 08, 2015 at 06:01PM, Valentin Kulichenko wrote:
> +1 > > ./ignite.sh successfully started the node. Cos, you probably have incorrect > IGNITE_HOME in environment. Clean env - new shell for RC validation. No IGNITE vars in the env. I am rebuilding once again just in case, but I really don't see that script in the bin/include from the RC3 src.zip, although it is presented in the git repo under release-1.0.0-RC3 tag Cos > Git error is OK, build procedure tries to get values from Git, fails to do > that, but doesn't stop and use default values (at least this is how it > works for me). > > On Fri, May 8, 2015 at 5:51 PM, Konstantin Boudnik <[hidden email]> wrote: > > > > > Unless it is my environment issue (which doesn't seem to be likely) > > > > -1 > > > > Here's the problem though: > > $ ./bin/ignite.sh > > ./bin/ignite.sh: line 61: > > /home/cos/workspaces/1.1.0-RC3/ignite-1.1.0-incubating-src/bin/include/target-classpath.sh: > > No such file or directory > > Error: Could not find or load main class > > org.apache.ignite.startup.cmdline.CommandLineRandomNumberGenerator > > Error: Could not find or load main class > > org.apache.ignite.internal.util.portscanner.GridJmxPortFinder > > > > Signatures are correct, but md5sum and sha1sum are malformed. They should > > look > > like > > > > $ md5sum ignite-1.1.0-incubating-src.zip > > 9a67c904b6ec129209b4ab00c6fa32b1 ignite-1.1.0-incubating-src.zip > > $ sha1sum ignite-1.1.0-incubating-src.zip > > f465d5928ea3da7199fb938de5af56e34706623e ignite-1.1.0-incubating-src.zip > > > > otherwise auto-checking won't work. Please fix in the next respin (if > > going to > > happen per above) or in the next release. Also needs to be documented. > > > > > > A somewhat minor issue: > > > > I thought that has been fixed long time ago, but running > > mvn clean package -DskipTests -Prelease,lgpl > > gives this > > > > [INFO] An Ant BuildException has occured: exec returned: 128 around Ant > > part ...<exec outputproperty="ignite.build" executable="git" > > failonerror="true">... @ 20:75 in > > > > /biggy/workspaces/1.1.0-RC3/ignite-1.1.0-incubating-src/modules/core/target/antrun/build-main.xml > > /biggy/workspaces/1.1.0-RC3/ignite-1.1.0-incubating-src/modules/core/target/antrun/build-main.xml:20: > > exec returned: 128 > > > > Although, of course, I have git in the $PATH. > > > > Thanks, > > Cos > > > > On Fri, May 08, 2015 at 05:26PM, Yakov Zhdanov wrote: > > > Guys, > > > > > > We have uploaded release candidate to > > > https://dist.apache.org/repos/dist/dev/incubator/ignite/1.1.0-rc3/ > > > > > > Tag name is > > > ignite-1.1.0-incubating-rc3 > > > > > > We fixed rat issues and added "-incubating" to the version and many more > > > changes which are > > > described in devnotes (link below). > > > > > > DEVNOTES > > > > > https://git-wip-us.apache.org/repos/asf?p=incubator-ignite.git;a=blob_plain;f=DEVNOTES.txt;hb=refs/tags/ignite-1.1.0-incubating-rc3 > > > > > > RELEASENOTES > > > > > https://git-wip-us.apache.org/repos/asf?p=incubator-ignite.git;a=blob_plain;f=RELEASE_NOTES.txt;hb=refs/tags/ignite-1.1.0-incubating-rc3 > > > > > > Please start voting. > > > > > > +1 - to accept Apache Ignite (incubating) 1.1.0 > > > 0 - don't care either way > > > -1 - DO NOT accept Apache Ignite (incubating) 1.1.0 (explain why) > > > > > > Thanks! > > > > > > --Yakov > > |
Nope, all the same. However if I copy the file from the git source tree -
everything starts working. In order to double-check me, please run unzip -l ignite-1.1.0-incubating-src.zip | grep "bin/include" Cos On Fri, May 08, 2015 at 06:17PM, Konstantin Boudnik wrote: > On Fri, May 08, 2015 at 06:01PM, Valentin Kulichenko wrote: > > +1 > > > > ./ignite.sh successfully started the node. Cos, you probably have incorrect > > IGNITE_HOME in environment. > > Clean env - new shell for RC validation. No IGNITE vars in the env. I am > rebuilding once again just in case, but I really don't see that script in the > bin/include from the RC3 src.zip, although it is presented in the git repo > under release-1.0.0-RC3 tag > > Cos > > > Git error is OK, build procedure tries to get values from Git, fails to do > > that, but doesn't stop and use default values (at least this is how it > > works for me). > > > > On Fri, May 8, 2015 at 5:51 PM, Konstantin Boudnik <[hidden email]> wrote: > > > > > > > > Unless it is my environment issue (which doesn't seem to be likely) > > > > > > -1 > > > > > > Here's the problem though: > > > $ ./bin/ignite.sh > > > ./bin/ignite.sh: line 61: > > > /home/cos/workspaces/1.1.0-RC3/ignite-1.1.0-incubating-src/bin/include/target-classpath.sh: > > > No such file or directory > > > Error: Could not find or load main class > > > org.apache.ignite.startup.cmdline.CommandLineRandomNumberGenerator > > > Error: Could not find or load main class > > > org.apache.ignite.internal.util.portscanner.GridJmxPortFinder > > > > > > Signatures are correct, but md5sum and sha1sum are malformed. They should > > > look > > > like > > > > > > $ md5sum ignite-1.1.0-incubating-src.zip > > > 9a67c904b6ec129209b4ab00c6fa32b1 ignite-1.1.0-incubating-src.zip > > > $ sha1sum ignite-1.1.0-incubating-src.zip > > > f465d5928ea3da7199fb938de5af56e34706623e ignite-1.1.0-incubating-src.zip > > > > > > otherwise auto-checking won't work. Please fix in the next respin (if > > > going to > > > happen per above) or in the next release. Also needs to be documented. > > > > > > > > > A somewhat minor issue: > > > > > > I thought that has been fixed long time ago, but running > > > mvn clean package -DskipTests -Prelease,lgpl > > > gives this > > > > > > [INFO] An Ant BuildException has occured: exec returned: 128 around Ant > > > part ...<exec outputproperty="ignite.build" executable="git" > > > failonerror="true">... @ 20:75 in > > > > > > /biggy/workspaces/1.1.0-RC3/ignite-1.1.0-incubating-src/modules/core/target/antrun/build-main.xml > > > /biggy/workspaces/1.1.0-RC3/ignite-1.1.0-incubating-src/modules/core/target/antrun/build-main.xml:20: > > > exec returned: 128 > > > > > > Although, of course, I have git in the $PATH. > > > > > > Thanks, > > > Cos > > > > > > On Fri, May 08, 2015 at 05:26PM, Yakov Zhdanov wrote: > > > > Guys, > > > > > > > > We have uploaded release candidate to > > > > https://dist.apache.org/repos/dist/dev/incubator/ignite/1.1.0-rc3/ > > > > > > > > Tag name is > > > > ignite-1.1.0-incubating-rc3 > > > > > > > > We fixed rat issues and added "-incubating" to the version and many more > > > > changes which are > > > > described in devnotes (link below). > > > > > > > > DEVNOTES > > > > > > > https://git-wip-us.apache.org/repos/asf?p=incubator-ignite.git;a=blob_plain;f=DEVNOTES.txt;hb=refs/tags/ignite-1.1.0-incubating-rc3 > > > > > > > > RELEASENOTES > > > > > > > https://git-wip-us.apache.org/repos/asf?p=incubator-ignite.git;a=blob_plain;f=RELEASE_NOTES.txt;hb=refs/tags/ignite-1.1.0-incubating-rc3 > > > > > > > > Please start voting. > > > > > > > > +1 - to accept Apache Ignite (incubating) 1.1.0 > > > > 0 - don't care either way > > > > -1 - DO NOT accept Apache Ignite (incubating) 1.1.0 (explain why) > > > > > > > > Thanks! > > > > > > > > --Yakov > > > |
On 09.05.2015 03:22, Konstantin Boudnik wrote:
> Nope, all the same. However if I copy the file from the git source tree - > everything starts working. In order to double-check me, please run > unzip -l ignite-1.1.0-incubating-src.zip | grep "bin/include" This would not have happened if package creation was properly automated ... as I've been suggesting for months. -- Brane |
In reply to this post by Konstantin Boudnik-2
Hello Cos.
>> Here's the problem though: >> $ ./bin/ignite.sh >> ./bin/ignite.sh: line 61: /home/cos/workspaces/1.1.0- RC3/ignite-1.1.0-incubating-src/bin/include/target-classpath.sh:>> >> No such file or directory >> Error: Could not find or load main class org.apache.ignite.startup. cmdline.CommandLineRandomNumberGenerator >> Error: Could not find or load main class org.apache.ignite.internal. util.portscanner.GridJmxPortFinder This happened because maven assemply plugin excluded this file from sources. Seems that we found bug at <groupId>org.apache.apache.resources</groupId> <artifactId>apache-source-release-assembly-descriptor</artifactId> <version>1.0.4</version> Which is used to generate source package. See apache:16 pom line 307 for details. I've deleted <exclude>%regex[(?!((?!${project.build.directory}/)[^/]+/)*src/).*${project.build.directory}.*]</exclude> at apache-source-release-assembly-descriptor-1.0.4.jar -> assemblies/source-shared.xml and this fixed "exclude issue". So, I renamed target-classpath.sh to build-classpath.sh. Hotfix will be available at next RC >> Signatures are correct, but md5sum and sha1sum are malformed. They should look >> like >> $ md5sum ignite-1.1.0-incubating-src.zip >> 9a67c904b6ec129209b4ab00c6fa32b1 ignite-1.1.0-incubating-src.zip >> $ sha1sum ignite-1.1.0-incubating-src.zip >> f465d5928ea3da7199fb938de5af56e34706623e ignite-1.1.0-incubating-src.zip >> otherwise auto-checking won't work. Please fix in the next respin (if going to >> happen per above) or in the next release. Also needs to be documented. I've checked another projects at https://dist.apache.org/repos/dist/ and found that most them used the same format as we use. For examplle: https://dist.apache.org/repos/dist/release/maven/maven-3/3.3.3/source/ https://dist.apache.org/repos/dist/release/camel/apache-camel/2.15.2/ Some use format specified by you: https://dist.apache.org/repos/dist/release/tomcat/tomcat-8/v8.0.22/src/ I think than first case is preferred because signature filename already contains document filename. Also this case is used to sign artifacts at maven repository. For example: https://repo.maven.apache.org/maven2/org/apache/hadoop/hadoop-main/2.7.0/ You can use command like "md5sum ignite-1.1.0-incubating-src.zip | awk '{print $1}'" to get md5 without filename inside file. On Sat, May 9, 2015 at 3:51 AM, Konstantin Boudnik <[hidden email]> wrote: > > Unless it is my environment issue (which doesn't seem to be likely) > > -1 > > Here's the problem though: > $ ./bin/ignite.sh > ./bin/ignite.sh: line 61: > /home/cos/workspaces/1.1.0-RC3/ignite-1.1.0-incubating-src/bin/include/target-classpath.sh: > No such file or directory > Error: Could not find or load main class > org.apache.ignite.startup.cmdline.CommandLineRandomNumberGenerator > Error: Could not find or load main class > org.apache.ignite.internal.util.portscanner.GridJmxPortFinder > > Signatures are correct, but md5sum and sha1sum are malformed. They should > look > like > > $ md5sum ignite-1.1.0-incubating-src.zip > 9a67c904b6ec129209b4ab00c6fa32b1 ignite-1.1.0-incubating-src.zip > $ sha1sum ignite-1.1.0-incubating-src.zip > f465d5928ea3da7199fb938de5af56e34706623e ignite-1.1.0-incubating-src.zip > > otherwise auto-checking won't work. Please fix in the next respin (if > going to > happen per above) or in the next release. Also needs to be documented. > > > A somewhat minor issue: > > I thought that has been fixed long time ago, but running > mvn clean package -DskipTests -Prelease,lgpl > gives this > > [INFO] An Ant BuildException has occured: exec returned: 128 around Ant > part ...<exec outputproperty="ignite.build" executable="git" > failonerror="true">... @ 20:75 in > > /biggy/workspaces/1.1.0-RC3/ignite-1.1.0-incubating-src/modules/core/target/antrun/build-main.xml > /biggy/workspaces/1.1.0-RC3/ignite-1.1.0-incubating-src/modules/core/target/antrun/build-main.xml:20: > exec returned: 128 > > Although, of course, I have git in the $PATH. > > Thanks, > Cos > > On Fri, May 08, 2015 at 05:26PM, Yakov Zhdanov wrote: > > Guys, > > > > We have uploaded release candidate to > > https://dist.apache.org/repos/dist/dev/incubator/ignite/1.1.0-rc3/ > > > > Tag name is > > ignite-1.1.0-incubating-rc3 > > > > We fixed rat issues and added "-incubating" to the version and many more > > changes which are > > described in devnotes (link below). > > > > DEVNOTES > > > https://git-wip-us.apache.org/repos/asf?p=incubator-ignite.git;a=blob_plain;f=DEVNOTES.txt;hb=refs/tags/ignite-1.1.0-incubating-rc3 > > > > RELEASENOTES > > > https://git-wip-us.apache.org/repos/asf?p=incubator-ignite.git;a=blob_plain;f=RELEASE_NOTES.txt;hb=refs/tags/ignite-1.1.0-incubating-rc3 > > > > Please start voting. > > > > +1 - to accept Apache Ignite (incubating) 1.1.0 > > 0 - don't care either way > > -1 - DO NOT accept Apache Ignite (incubating) 1.1.0 (explain why) > > > > Thanks! > > > > --Yakov > |
In reply to this post by Branko Čibej
On Sun, May 10, 2015 at 7:55 PM, Branko Čibej <[hidden email]> wrote:
> On 09.05.2015 03:22, Konstantin Boudnik wrote: > > Nope, all the same. However if I copy the file from the git source tree - > > everything starts working. In order to double-check me, please run > > unzip -l ignite-1.1.0-incubating-src.zip | grep "bin/include" > > This would not have happened if package creation was properly automated > ... as I've been suggesting for months. > Brane, I think package creation is fully automated right now. What this was is a bug in the automation process. > > -- Brane > > |
Free forum by Nabble | Edit this page |