[jira] [Updated] (GIRAPH-131) enable creation of test-jars to simplify testing in downstream projects
[
https://issues.apache.org/jira/browse/GIRAPH-131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Charles updated GIRAPH-131:
Attachment: GIRAPH-131-source-test-jar.patch
GIRAPH-131-source-test-jar.patch allows the deployment of the test-jar sources
(see also GIRAPH-129).
No much, but can be useful to run tests from a 3rd party project and debug in
the giraph sources.
enable creation of test-jars to simplify testing in downstream projects
---
Key: GIRAPH-131
URL: https://issues.apache.org/jira/browse/GIRAPH-131
Project: Giraph
Issue Type: Improvement
Reporter: André Kelpe
Assignee: André Kelpe
Priority: Minor
Fix For: 0.1.0
Attachments: GIRAPH-131-source-test-jar.patch, GIRAPH-131.patch
Attached patch enables the creation of test-jars, which are the tests
packaged in a separate jar file. This makes it possible to use the
super-useful test infrastructure in MockUtils in downstream projects. If you
add the patch, you will get a ${giraph.version}-tests.jar, which can be used
for downstream testing like this:
dependency
groupIdorg.apache.giraph/groupId
artifactIdgiraph/artifactId
version${giraph.version}/version
typetest-jar/type
scopetest/scope
/dependency
P.S.: The patch also resets the version to 0.1-SNAPSHOT as discussed in
GIRAPH-129
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [VOTE] Release Giraph 0.1-incubating (rc0)
+1. I'm fine with this. Avery On 1/31/12 8:45 PM, Jakob Homan wrote: I think these concerns preclude the entire idea of a release. As mentioned above, we're releasing a tag (a specific svn revision). That is what the release is. Both src .tar.gz and binary files are courtesies. A release should be something that users can use as a dependency. . .like a maven coordinate. A source release in no way prevents us from creating jars of the release and adding them to Apache's maven repo. In fact, we can't add a jar until we have a release. I think you guys should wait until you have made these decisions If you would like to assist with moving away from the munging, there is an open JIRA to do so. Any effort would be appreciated. To address the issues of binaries, could we release multiple binaries of Giraph that coincide with the different versions of Hadoop? Adding in external dependencies for a binary release (and even just for a source release with jars that couldn't be brought in via maven/sbt) caused significant delay recently for Kafka. I'd like to avoid that here. Also, since we intend to release early and often, there's no reason we can't follow up with a 0.2 in short order - there are going to be a lot of patches in the next few weeks. On Tue, Jan 31, 2012 at 8:17 PM, Avery Chingach...@apache.org wrote: To address the issues of binaries, could we release multiple binaries of Giraph that coincide with the different versions of Hadoop? On 1/31/12 7:44 PM, David Garcia wrote: I think these concerns preclude the entire idea of a release. A release should be something that users can use as a dependency. . .like a maven coordinate. I think you guys should wait until you have made these decisions. . .and then cut a binary. On 1/31/12 5:36 PM, Jakob Homanjgho...@gmail.comwrote: Giraphers- I've created a candidate for our first release. It's a source release without a binary for two reasons: first, there's still discussion going on about what needs to be done for the NOTICE and LICENSE files for projects that bring in transitive dependencies to the binary release (http://www.mail-archive.com/general@incubator.apache.org/msg32693.html) and second because we're still munging our binary against three types of Hadoop, which would mean we'd need to release three different binary artifacts, which seems suboptimal. Hopefully both of these issues will be addressed by 0.2. I've tested the release against an unsecure 20.2 cluster. It'd be great to test it against other configurations. Note that we're voting on the tag; the files are provided as a convenience. Release notes: http://people.apache.org/~jghoman/giraph-0.1.0-incubating-rc0/RELEASE_NOTE S.html Release artifacts: http://people.apache.org/~jghoman/giraph-0.1.0-incubating-rc0/ Corresponding svn tag: http://svn.apache.org/repos/asf/incubator/giraph/tags/release-0.1-rc0/ Our signing keys (my key doesn't seem to be being picked up by http://people.apache.org/keys/group/giraph.asc): http://svn.apache.org/repos/asf/incubator/giraph/KEYS The vote runs for 72 hours, until Friday 4pm PST. After a successful vote here, Incubator will vote on the release as well. Thanks, Jakob
Re: [VOTE] Release Giraph 0.1-incubating (rc0)
Are you +1ing the release, or just the idea of having a source release in general? The vote ends tomorrow, so it would be great if the committers and mentors could take a look... On Thu, Feb 2, 2012 at 2:18 PM, Avery Ching ach...@apache.org wrote: +1. I'm fine with this. Avery On 1/31/12 8:45 PM, Jakob Homan wrote: I think these concerns preclude the entire idea of a release. As mentioned above, we're releasing a tag (a specific svn revision). That is what the release is. Both src .tar.gz and binary files are courtesies. A release should be something that users can use as a dependency. . .like a maven coordinate. A source release in no way prevents us from creating jars of the release and adding them to Apache's maven repo. In fact, we can't add a jar until we have a release. I think you guys should wait until you have made these decisions If you would like to assist with moving away from the munging, there is an open JIRA to do so. Any effort would be appreciated. To address the issues of binaries, could we release multiple binaries of Giraph that coincide with the different versions of Hadoop? Adding in external dependencies for a binary release (and even just for a source release with jars that couldn't be brought in via maven/sbt) caused significant delay recently for Kafka. I'd like to avoid that here. Also, since we intend to release early and often, there's no reason we can't follow up with a 0.2 in short order - there are going to be a lot of patches in the next few weeks. On Tue, Jan 31, 2012 at 8:17 PM, Avery Chingach...@apache.org wrote: To address the issues of binaries, could we release multiple binaries of Giraph that coincide with the different versions of Hadoop? On 1/31/12 7:44 PM, David Garcia wrote: I think these concerns preclude the entire idea of a release. A release should be something that users can use as a dependency. . .like a maven coordinate. I think you guys should wait until you have made these decisions. . .and then cut a binary. On 1/31/12 5:36 PM, Jakob Homanjgho...@gmail.com wrote: Giraphers- I've created a candidate for our first release. It's a source release without a binary for two reasons: first, there's still discussion going on about what needs to be done for the NOTICE and LICENSE files for projects that bring in transitive dependencies to the binary release (http://www.mail-archive.com/general@incubator.apache.org/msg32693.html) and second because we're still munging our binary against three types of Hadoop, which would mean we'd need to release three different binary artifacts, which seems suboptimal. Hopefully both of these issues will be addressed by 0.2. I've tested the release against an unsecure 20.2 cluster. It'd be great to test it against other configurations. Note that we're voting on the tag; the files are provided as a convenience. Release notes: http://people.apache.org/~jghoman/giraph-0.1.0-incubating-rc0/RELEASE_NOTE S.html Release artifacts: http://people.apache.org/~jghoman/giraph-0.1.0-incubating-rc0/ Corresponding svn tag: http://svn.apache.org/repos/asf/incubator/giraph/tags/release-0.1-rc0/ Our signing keys (my key doesn't seem to be being picked up by http://people.apache.org/keys/group/giraph.asc): http://svn.apache.org/repos/asf/incubator/giraph/KEYS The vote runs for 72 hours, until Friday 4pm PST. After a successful vote here, Incubator will vote on the release as well. Thanks, Jakob
[jira] [Commented] (GIRAPH-136) Erorr message for bin/giraph could be improved
[
https://issues.apache.org/jira/browse/GIRAPH-136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13199482#comment-13199482
]
Jakob Homan commented on GIRAPH-136:
@Avery - how does this one look?
Erorr message for bin/giraph could be improved
--
Key: GIRAPH-136
URL: https://issues.apache.org/jira/browse/GIRAPH-136
Project: Giraph
Issue Type: Improvement
Affects Versions: 0.1.0
Reporter: Jakob Homan
Assignee: Jakob Homan
Fix For: 0.2.0
Attachments: GIRAPH-136-b.patch, GIRAPH-136.patch
Currently when one just runs bin/giraph without the required jar, the message
isn't very helpful:
{noformat}[tardis giraph-0.1]$ bin/giraph
Can't find user jar to execute.{noformat}
It would be better to have a more in-depth message explaining Giraph and what
is expected.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [VOTE] Release Giraph 0.1-incubating (rc0)
I also checked the compile, all tests pass, gpg sign, and md5 sign. +1 for both the source release and the binary tarball release. -- Hyunsik Choi On Wed, Feb 1, 2012 at 8:36 AM, Jakob Homan jgho...@gmail.com wrote: Giraphers- I've created a candidate for our first release. It's a source release without a binary for two reasons: first, there's still discussion going on about what needs to be done for the NOTICE and LICENSE files for projects that bring in transitive dependencies to the binary release ( http://www.mail-archive.com/general@incubator.apache.org/msg32693.html) and second because we're still munging our binary against three types of Hadoop, which would mean we'd need to release three different binary artifacts, which seems suboptimal. Hopefully both of these issues will be addressed by 0.2. I've tested the release against an unsecure 20.2 cluster. It'd be great to test it against other configurations. Note that we're voting on the tag; the files are provided as a convenience. Release notes: http://people.apache.org/~jghoman/giraph-0.1.0-incubating-rc0/RELEASE_NOTES.html Release artifacts: http://people.apache.org/~jghoman/giraph-0.1.0-incubating-rc0/ Corresponding svn tag: http://svn.apache.org/repos/asf/incubator/giraph/tags/release-0.1-rc0/ Our signing keys (my key doesn't seem to be being picked up by http://people.apache.org/keys/group/giraph.asc): http://svn.apache.org/repos/asf/incubator/giraph/KEYS The vote runs for 72 hours, until Friday 4pm PST. After a successful vote here, Incubator will vote on the release as well. Thanks, Jakob
Re: [VOTE] Release Giraph 0.1-incubating (rc0)
Hi Jakob, NP, I'll take a look tomorrow. Cheers, Chris On Feb 2, 2012, at 2:26 PM, Jakob Homan wrote: Are you +1ing the release, or just the idea of having a source release in general? The vote ends tomorrow, so it would be great if the committers and mentors could take a look... On Thu, Feb 2, 2012 at 2:18 PM, Avery Ching ach...@apache.org wrote: +1. I'm fine with this. Avery On 1/31/12 8:45 PM, Jakob Homan wrote: I think these concerns preclude the entire idea of a release. As mentioned above, we're releasing a tag (a specific svn revision). That is what the release is. Both src .tar.gz and binary files are courtesies. A release should be something that users can use as a dependency. . .like a maven coordinate. A source release in no way prevents us from creating jars of the release and adding them to Apache's maven repo. In fact, we can't add a jar until we have a release. I think you guys should wait until you have made these decisions If you would like to assist with moving away from the munging, there is an open JIRA to do so. Any effort would be appreciated. To address the issues of binaries, could we release multiple binaries of Giraph that coincide with the different versions of Hadoop? Adding in external dependencies for a binary release (and even just for a source release with jars that couldn't be brought in via maven/sbt) caused significant delay recently for Kafka. I'd like to avoid that here. Also, since we intend to release early and often, there's no reason we can't follow up with a 0.2 in short order - there are going to be a lot of patches in the next few weeks. On Tue, Jan 31, 2012 at 8:17 PM, Avery Chingach...@apache.org wrote: To address the issues of binaries, could we release multiple binaries of Giraph that coincide with the different versions of Hadoop? On 1/31/12 7:44 PM, David Garcia wrote: I think these concerns preclude the entire idea of a release. A release should be something that users can use as a dependency. . .like a maven coordinate. I think you guys should wait until you have made these decisions. . .and then cut a binary. On 1/31/12 5:36 PM, Jakob Homanjgho...@gmail.comwrote: Giraphers- I've created a candidate for our first release. It's a source release without a binary for two reasons: first, there's still discussion going on about what needs to be done for the NOTICE and LICENSE files for projects that bring in transitive dependencies to the binary release (http://www.mail-archive.com/general@incubator.apache.org/msg32693.html) and second because we're still munging our binary against three types of Hadoop, which would mean we'd need to release three different binary artifacts, which seems suboptimal. Hopefully both of these issues will be addressed by 0.2. I've tested the release against an unsecure 20.2 cluster. It'd be great to test it against other configurations. Note that we're voting on the tag; the files are provided as a convenience. Release notes: http://people.apache.org/~jghoman/giraph-0.1.0-incubating-rc0/RELEASE_NOTE S.html Release artifacts: http://people.apache.org/~jghoman/giraph-0.1.0-incubating-rc0/ Corresponding svn tag: http://svn.apache.org/repos/asf/incubator/giraph/tags/release-0.1-rc0/ Our signing keys (my key doesn't seem to be being picked up by http://people.apache.org/keys/group/giraph.asc): http://svn.apache.org/repos/asf/incubator/giraph/KEYS The vote runs for 72 hours, until Friday 4pm PST. After a successful vote here, Incubator will vote on the release as well. Thanks, Jakob ++ Chris Mattmann, Ph.D. Senior Computer Scientist NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA Office: 171-266B, Mailstop: 171-246 Email: chris.a.mattm...@nasa.gov WWW: http://sunset.usc.edu/~mattmann/ ++ Adjunct Assistant Professor, Computer Science Department University of Southern California, Los Angeles, CA 90089 USA ++
