Re: [jbehave-dev] A request to improve adoption
The only difference between what you propose and what we have is that you need to execute a one-off command - ant copy-dependencies - to retrieve the jars from the external repos. It's a philosophical issue more than anything else. Ant tends to favour the duplication (and storage) of jars left and right - we think it's more valuable to keep them in one place in the repository and allow users to copy them when needed. Alternatively, you could use Ant with either Ivy or Maven Ant Tasks for the dependency management. In the trader example you can find an Ant build.xml that uses Maven Ant Tasks to copy the jars and build the Ant classpath, but you can easily adapt it to Ivy. To be honest checking out the examples source code and running it does not take hours. That's what the examples are meant to give you. If you execute the following you'll have a fully working Ant-based system in a few minutes: git clone git://github.com/jbehave/jbehave-core.git cd examples/trader ant You do need internet connection for the first time you run the Ant script. Cheers On 13/05/2011 17:13, M CHILDS wrote: When you see the bin distribution, it makes sense to you what is required to get started and get all needed jars. It seems easy and straightforward to you. To users new to jbehave and maven, who just want to go through an example or two on their machine to evaluate jbehave, it can take several hours just to get it working. On the other hand, users were able to download a zip of all the jars, it becomes a very straightforward matter for them and takes no time. In this way, users are more likely to evaluate jbehave and have a feeling of success and ease with it. Date: Fri, 13 May 2011 16:34:41 +0100 From: mauro.tal...@aquilonia.org To: dev@jbehave.codehaus.org Subject: Re: [jbehave-dev] A request to improve adoption The process is: 1. download bin distribution 2. unzip 3. cd lib 4. ant copy-dependencies Then you have all your dependencies (direct and transitive) and can use them manually with Ant however you see fit. To be honest I don't see the big difference with what you're proposing. We won't package all the dependencies in a single jar - it's plainly a bad practice for a number of reasons. But you are free to do so if you so wish once you have executed step 4 above. Cheers On 13/05/2011 16:28, M CHILDS wrote: I understand that maven collects dependencies and is useful. However, maven doesn't complete (I used mvn 2.2 this morning) with the provided pom.xml when I follow this process: 1. download stable core BIN distribution 2. Unzip 3. cd to lib folder 4. mvn clean install If it worked, I would still think the download page could use a 'here are the 4 steps you take to get the final jar(s), after you install maven'. Further, as valuable as maven is and ant + manual dependencies is, it sure would be nice to download 'jbehave-core.jar' and 'jbehave-dependencies.jar' in a single zip file and just drop those two jars into my classpath. This would benefit you. If people give up building because they can't get things working, then you're losing potential adopters. Date: Fri, 13 May 2011 08:22:41 +0200 From: mauro.tal...@aquilonia.org mailto:mauro.tal...@aquilonia.org To: dev@jbehave.codehaus.org mailto:dev@jbehave.codehaus.org Subject: Re: [jbehave-dev] A request to improve adoption Hi, the point of using Maven is that you don't need to build the jars, these are already available on Maven Central and will be automatically downloaded when you declare them in your pom.xml: http://repo2.maven.org/maven2/org/jbehave/jbehave-core/ If you don't use Maven, the binary distribution includes an Ant build.xml to allow you to copy all dependencies locally: http://jbehave.org/reference/preview/dependencies.html $cd lib $ant copy-dependencies If you are trying to build from source then you can find the build instructions: http://jbehave.org/reference/preview/building-source.html Also, current build requires Maven 2.2.x and the site part has not been fully migrated to 3.0.x (which is the major non-compat of Maven 2-3). Cheers On 13/05/2011 05:32, M CHILDS wrote: Could the binary release (I'm using 3.3.2) include a fully built jar file? I think this will improve the chances of people checking out and adopting jbehave. I request this because I've spent several hours and haven't gotten the binary release to build into something I can drop into my project. Each issue requires me to learn something brand new, so it is very frustrating, because all I want to do is
[jbehave-dev] [jira] Created: (JBEHAVE-515) Create trader-ant example
Create trader-ant example - Key: JBEHAVE-515 URL: http://jira.codehaus.org/browse/JBEHAVE-515 Project: JBehave Issue Type: Task Components: Ant Tasks Reporter: Mauro Talevi Assignee: Mauro Talevi Priority: Minor Fix For: 3.4 Move the examples of using Ant from trader to a new trader-ant example module, in order to make it easier for Ant users to identify it and get started. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-scm] jbehave-core branch, master, updated. jbehave-3.4-beta-4-11-g93f29ca
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project jbehave-core.
The branch, master has been updated
via 93f29cae5aa06aea2740d0b91d123484e3854368 (commit)
from 446cd08ba887cf6f5b08a8eacc121240c96fcead (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -
commit 93f29cae5aa06aea2740d0b91d123484e3854368
Author: Mauro Talevi mauro.tal...@aquilonia.org
Date: Sat May 14 14:13:42 2011 +0100
JBEHAVE-515: Moved Ant examples to trader-ant module.
---
Summary of changes:
.../src/site/content/examples-philosophy.html |1 +
.../src/site/content/running-examples.html | 27 +---
examples/pom.xml |1 +
examples/{trader = trader-ant}/build.xml |0
examples/{trader-stepdocs = trader-ant}/pom.xml | 25 +++---
examples/trader/pom.xml| 46
6 files changed, 40 insertions(+), 60 deletions(-)
rename examples/{trader = trader-ant}/build.xml (100%)
copy examples/{trader-stepdocs = trader-ant}/pom.xml (50%)
hooks/post-receive
--
jbehave-core
hr/
p
To unsubscribe from this list please visit:
/p
p
a
href=http://xircles.codehaus.org/manage_email;http://xircles.codehaus.org/manage_email/a
Re: [jbehave-dev] A request to improve adoption
The Ant example has now been moved to its own module (trader-ant). More explicit wording has been added to running-examples.html w.r.t. the Ant usecase, detailing how to get the dependencies (one-off) and run via Ant. This will make it hopefully easier for Ant users to get up to speed. Cheers On 14/05/2011 08:55, Mauro Talevi wrote: The only difference between what you propose and what we have is that you need to execute a one-off command - ant copy-dependencies - to retrieve the jars from the external repos. It's a philosophical issue more than anything else. Ant tends to favour the duplication (and storage) of jars left and right - we think it's more valuable to keep them in one place in the repository and allow users to copy them when needed. Alternatively, you could use Ant with either Ivy or Maven Ant Tasks for the dependency management. In the trader example you can find an Ant build.xml that uses Maven Ant Tasks to copy the jars and build the Ant classpath, but you can easily adapt it to Ivy. To be honest checking out the examples source code and running it does not take hours. That's what the examples are meant to give you. If you execute the following you'll have a fully working Ant-based system in a few minutes: git clone git://github.com/jbehave/jbehave-core.git cd examples/trader ant You do need internet connection for the first time you run the Ant script. Cheers On 13/05/2011 17:13, M CHILDS wrote: When you see the bin distribution, it makes sense to you what is required to get started and get all needed jars. It seems easy and straightforward to you. To users new to jbehave and maven, who just want to go through an example or two on their machine to evaluate jbehave, it can take several hours just to get it working. On the other hand, users were able to download a zip of all the jars, it becomes a very straightforward matter for them and takes no time. In this way, users are more likely to evaluate jbehave and have a feeling of success and ease with it. Date: Fri, 13 May 2011 16:34:41 +0100 From: mauro.tal...@aquilonia.org To: dev@jbehave.codehaus.org Subject: Re: [jbehave-dev] A request to improve adoption The process is: 1. download bin distribution 2. unzip 3. cd lib 4. ant copy-dependencies Then you have all your dependencies (direct and transitive) and can use them manually with Ant however you see fit. To be honest I don't see the big difference with what you're proposing. We won't package all the dependencies in a single jar - it's plainly a bad practice for a number of reasons. But you are free to do so if you so wish once you have executed step 4 above. Cheers On 13/05/2011 16:28, M CHILDS wrote: I understand that maven collects dependencies and is useful. However, maven doesn't complete (I used mvn 2.2 this morning) with the provided pom.xml when I follow this process: 1. download stable core BIN distribution 2. Unzip 3. cd to lib folder 4. mvn clean install If it worked, I would still think the download page could use a 'here are the 4 steps you take to get the final jar(s), after you install maven'. Further, as valuable as maven is and ant + manual dependencies is, it sure would be nice to download 'jbehave-core.jar' and 'jbehave-dependencies.jar' in a single zip file and just drop those two jars into my classpath. This would benefit you. If people give up building because they can't get things working, then you're losing potential adopters. Date: Fri, 13 May 2011 08:22:41 +0200 From: mauro.tal...@aquilonia.org mailto:mauro.tal...@aquilonia.org To: dev@jbehave.codehaus.org mailto:dev@jbehave.codehaus.org Subject: Re: [jbehave-dev] A request to improve adoption Hi, the point of using Maven is that you don't need to build the jars, these are already available on Maven Central and will be automatically downloaded when you declare them in your pom.xml: http://repo2.maven.org/maven2/org/jbehave/jbehave-core/ If you don't use Maven, the binary distribution includes an Ant build.xml to allow you to copy all dependencies locally: http://jbehave.org/reference/preview/dependencies.html $cd lib $ant copy-dependencies If you are trying to build from source then you can find the build instructions: http://jbehave.org/reference/preview/building-source.html Also, current build requires Maven 2.2.x and the site part has not been fully migrated to 3.0.x (which is the major non-compat of Maven 2-3). Cheers On 13/05/2011 05:32, M CHILDS wrote: Could the binary release (I'm using 3.3.2) include a fully built jar file? I think this will improve
[jbehave-scm] jbehave-core branch, master, updated. jbehave-3.4-beta-4-12-gbebac80
This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project jbehave-core. The branch, master has been updated via bebac806c4ff3ca3c97ce03163dac684f199ebe0 (commit) from 93f29cae5aa06aea2740d0b91d123484e3854368 (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log - commit bebac806c4ff3ca3c97ce03163dac684f199ebe0 Author: Mauro Talevi mauro.tal...@aquilonia.org Date: Sat May 14 16:37:44 2011 +0100 Lookup dependencies via search.maven.org. --- Summary of changes: distribution/src/site/content/dependencies.html | 22 +++--- 1 files changed, 11 insertions(+), 11 deletions(-) hooks/post-receive -- jbehave-core hr/ p To unsubscribe from this list please visit: /p p a href=http://xircles.codehaus.org/manage_email;http://xircles.codehaus.org/manage_email/a
[jbehave-scm] jbehave-web branch, master, updated. jbehave-web-3.3.2-2-g22e3754
This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project jbehave-web. The branch, master has been updated via 22e3754580734a9e76d0358ad366c433c2f7adce (commit) from 727a6f919013d1917640bcd4576af24385af6fc4 (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log - commit 22e3754580734a9e76d0358ad366c433c2f7adce Author: Mauro Talevi mauro.tal...@aquilonia.org Date: Sat May 14 16:40:49 2011 +0100 Lookup dependencies via search.maven.org. --- Summary of changes: distribution/src/main/site/content/download.html | 12 ++-- 1 files changed, 6 insertions(+), 6 deletions(-) hooks/post-receive -- jbehave-web hr/ p To unsubscribe from this list please visit: /p p a href=http://xircles.codehaus.org/manage_email;http://xircles.codehaus.org/manage_email/a
