Dear Greg, Thanks for you response, my comment have relation with a previus discution topic asociate to the user experience, in my point of view exist many issues, i download the latest version of river an try to start any lus (i dont see the binary folder) for my is not a problem run the platform, inclusive i make testing replacing the http server for jetty. Exist a group of person for work in this area (ux)? Best regards, Luis
El lunes, 17 de agosto de 2015, Greg Trasuk <tras...@stratuscom.com> escribió: > > Hello Luis: > > The examples folder inside the River starter kit is indeed quite > confusing, and will likely be removed in future releases. We’ve created > another example kit that is released but hasn’t been publicized on the web > page yet - You can get it at > https://dist.apache.org/repos/dist/release/river/river-examples-1.0/river-examples-1.0-source-release.zip > < > https://dist.apache.org/repos/dist/release/river/river-examples-1.0/river-examples-1.0-source-release.zip > > > > Unpack it using a zip file tool and read the “README.md” file at the > root. You’ll find that once you build the examples (using ‘mvn clean > install site’) it’s a better introduction to River. > > If you do want to use the examples in the JTSK starter kit, you need to > know that you should run the scripts from the example’s home directory, not > the ‘scripts’ directory. So for the command below, you should be in > > C:\ias\apache-river-2.2.2\examples\hello> > > and then the command would be ‘scripts\httpd.bat’. I realize that may > look funny, but it’s more in line with the Unix tradition, where the > command path usually doesn’t include the current directory (River runs just > fine on Windows, but it was originally developed on Solaris). > > Cheers, > > Greg Trasuk > > > On Aug 10, 2015, at 2:43 PM, Luis Arce <mastercracke...@mc3d.cl > <javascript:;>> wrote: > > > > Hi community, > > Is possible add in the new version of river a environment variable, for > the > > example scripts, ie: RIVER_HOME > > I download the current version then proceed to decompress for starting > the > > framework and is not possible find the classserver.jar > > C:\ias\apache-river-2.2.2\examples\hello\scripts>httpd.bat > > > > C:\ias\apache-river-2.2.2\examples\hello\scripts>java -jar > > ..\..\lib\classserver.jar -port 8080 -dir lib;..\..\lib-dl > > Error: Unable to access jarfile ..\..\lib\classserver.jar > > > > C:\ias\apache-river-2.2.2\examples\hello\scripts> > > > > > > i know is very simple move the folder, but is not clear. > > Best regards, > > Luis > > > > > > 2015-08-10 1:05 GMT-03:00 Patricia Shanahan <p...@acm.org <javascript:;> > >: > > > >> This is what I propose to file in the next couple of days. I have made > >> changes to reflect progress on the Release 3.0 issue. > >> > >> PMC Members - please vote on this report. Your affirmative vote will > both > >> indicate that we have an active PMC, and that this report is in line > with > >> its collective view of the status of River. > >> > >> =================================================================== > >> > >> Report from the Apache River committee [Patricia Shanahan] > >> > >> ## Description: > >> - Apache River is a Java-based Service Oriented Architecture, > >> implementing the Jini Specification and Jini Technology Starter Kit. > >> > >> ## Activity: > >> > >> - The main objectives are release 3.0 and an improved new user > >> experience. > >> > >> The release 3.0 source code provides a deep refactoring that addresses > >> performance, concurrency and scaling issues. It replaces sun.com.jini > >> and com.artima package names with new org.apache.river package names. > >> > >> Patricia Shanahan will drive preparing a release with support and > >> information from Greg Trasuk. > >> > >> The improved new user experience objective is supported by a release > >> candidate for new set of easy-to-run River examples. It is the subject > of > >> an on-going release vote. > >> > >> ## Health report: > >> - The project continues to make only slow progress, mainly due to lack > >> of time on the part of the committers. > >> > >> ## Issues: > >> - there are no issues requiring board attention at this time. > >> > >> ## LDAP committee group/Committership changes: > >> > >> - Currently 13 committers and 13 LDAP committee group members. > >> - No new changes to the LDAP committee group or committership since > >> last report. The last change in the PMC was in June 2014, when Patricia > >> Shanahan returned from emeritus to active status as a committer and PMC > >> member. > >> > >> > >> ## Releases: > >> > >> - Apache River 2.2.2 was released on November 18, 2013 > >> - Apache River 2.2.1 was released on May 2, 2013. > >> > >> > >> ## Mailing list activity: > >> > >> - dev@river.apache.org <javascript:;>: > >> - 96 subscribers (down -1 in the last 3 months): > >> - 80 emails sent to list (175 in previous quarter) > >> > >> - u...@river.apache.org <javascript:;>: > >> - 100 subscribers (down -1 in the last 3 months): > >> - 3 emails sent to list (15 in previous quarter) > >> > >
