Re: Jtreg tests.
On 23-01-12 01:57, Peter Firmstone wrote: A number of jtreg tests a failing due to expired certificates. Are these included in the QA build on builds? Do they fail there, but are disabled or so? Gr. Sim -- QCG, Software voor het MKB, 071-5890970, http://www.qcg.nl Quality Consultancy Group b.v., Leiderdorp, Kvk Den Haag: 28088397
Re: Surrogate
Maven archetypes are the way to go. IDE agnostic and all IDEs support Maven. Dennis Reedy with Rio has done a lot of work with Maven and Jini services, using multi-module projects to write services, keeping interface, proxy, service, and UI classpaths distinct and managing dependencies, etc. It's a huge improvement over building multiple jars from the same batch of code using classdep-type approaches. -jeff On Mon, Jan 23, 2012 at 9:01 AM, Greg Trasuk tras...@stratuscom.com wrote: On Sat, 2012-01-21 at 22:54, Peter Firmstone wrote: Greg, Are there any areas where you could use some help with the Surrogate implementation? This year, we could make an impact with fresh releases for River, Surrogate and the LDJ Kit. Cheers, Peter. Well, there's probably lot's to do, but I'm thinking it's best if I finish off the first-cut myself (it's one of those not sure of the architecture til the first pass is done things). There's really only the security manager integration left to make it a functional container (as it sits in the source tree now, it can host Reggie successfully, including hosting the codebase server). I'm planning on working on it this week and part of next week, so with some luck, it'll be ready for demo soon. Once the first cut is done, then we'll have all kinds of usability features that folks can dig in to. I'll tell you what the outside world really needs, though: IDE integration. We need to get to the point where you can go to Netbeans and select New...Jini Service Project and then go into your web app and select New...Jini client. Anybody interested in Netbeans or Eclipse integration? My personal taste is for Netbeans, and I suspect it'll be relatively easy to add in a Jini project template, given the Ant-driven nature of it, but I haven't looked too deeply. Cheers, Greg.
Re: Jtreg tests.
Simon IJskes - QCG wrote: On 23-01-12 01:57, Peter Firmstone wrote: A number of jtreg tests a failing due to expired certificates. Are these included in the QA build on builds? Do they fail there, but are disabled or so? Gr. Sim No, they've got a GPL platform library dependency, jtreg. To run them cd to the qa directory and $ant jtreg.
Re: Jtreg tests.
On 23-01-12 21:56, Peter Firmstone wrote: Simon IJskes - QCG wrote: On 23-01-12 01:57, Peter Firmstone wrote: A number of jtreg tests a failing due to expired certificates. Are these included in the QA build on builds? Do they fail there, but are disabled or so? Gr. Sim No, they've got a GPL platform library dependency, jtreg. To run them cd to the qa directory and We could put this to apache-legal. Not distributing GPL does not mean not using IMHO. gr. Sim
Re: Jtreg tests.
Simon IJskes - QCG wrote: On 23-01-12 21:56, Peter Firmstone wrote: Simon IJskes - QCG wrote: On 23-01-12 01:57, Peter Firmstone wrote: A number of jtreg tests a failing due to expired certificates. Are these included in the QA build on builds? Do they fail there, but are disabled or so? Gr. Sim No, they've got a GPL platform library dependency, jtreg. To run them cd to the qa directory and We could put this to apache-legal. Not distributing GPL does not mean not using IMHO. gr. Sim I think we'd need to ask whoever is responsible for Hudson, I've got the jtreg library installed on my machine, it's a platform requirement. We can't distribute the library with Apache River, because it' s GPL, so it has to be a platform requirement. Perhaps we could write an ant target to download the library? It isn't very large, so we could download it, unpack install, then discard it for every run on Hudson. Cheers, Peter.
Re: Surrogate
One big benefit is that a new developer can just checkout from svn, then open a project with their IDE and it's all recognised, ready to rock 'n roll. And there's very little work to do to achieve that. River supports the use of Maven, even though internally we use ant. Incidentally you can build using Maven or Gradle. So not only is it IDE agnostic, but it's build tool agnostic as well. I'd certainly encourage people to follow the way Dennis bundles and structures his service dependencies as a guide, I'll be doing this for my own projects. ClassDep can be used to determine dependencies in existing software, to assist restructuring by hand to support Maven or Gradle builds (with the same build structure). No one's written any tools to automate the process so it's better to start that way than try to migrate later. Cheers, Peter. Jeff Ramsdale wrote: Maven archetypes are the way to go. IDE agnostic and all IDEs support Maven. Dennis Reedy with Rio has done a lot of work with Maven and Jini services, using multi-module projects to write services, keeping interface, proxy, service, and UI classpaths distinct and managing dependencies, etc. It's a huge improvement over building multiple jars from the same batch of code using classdep-type approaches. -jeff On Mon, Jan 23, 2012 at 9:01 AM, Greg Trasuk tras...@stratuscom.com wrote: On Sat, 2012-01-21 at 22:54, Peter Firmstone wrote: Greg, Are there any areas where you could use some help with the Surrogate implementation? This year, we could make an impact with fresh releases for River, Surrogate and the LDJ Kit. Cheers, Peter. Well, there's probably lot's to do, but I'm thinking it's best if I finish off the first-cut myself (it's one of those not sure of the architecture til the first pass is done things). There's really only the security manager integration left to make it a functional container (as it sits in the source tree now, it can host Reggie successfully, including hosting the codebase server). I'm planning on working on it this week and part of next week, so with some luck, it'll be ready for demo soon. Once the first cut is done, then we'll have all kinds of usability features that folks can dig in to. I'll tell you what the outside world really needs, though: IDE integration. We need to get to the point where you can go to Netbeans and select New...Jini Service Project and then go into your web app and select New...Jini client. Anybody interested in Netbeans or Eclipse integration? My personal taste is for Netbeans, and I suspect it'll be relatively easy to add in a Jini project template, given the Ant-driven nature of it, but I haven't looked too deeply. Cheers, Greg.
