Outside of the Ant/Maven discussion, I have just created RIVER-301 which describes this.
I'm still guessing that this is the right approach. :-) Cheers, Tom -----Original Message----- From: Tom Hobbs [mailto:[EMAIL PROTECTED] Sent: 08 December 2008 12:23 To: river-dev@incubator.apache.org Subject: RE: Deciding the Future I currently have a local version whereby I created a source directory inside of the River code and am gradually moving all the code out of the test project into this new source directory. I'm also changing how the tests are executed by shoe-horning them into JUnit TestCases. The biggest challenge I'm facing is retaining all the customisation that the current test harness allows and trying to keep the tests running successfully. I've made some changes to the harness code which is largely limited to altering the packages and associated class/constructor/method access modifiers to support the new structure. My goal is, in the next few weeks, to have moved all the TransactionManager tests over to this approach. Then I'll post a patch to show the changes which I would welcome feedback on. Then, I hope, it'll be a case of mostly cut-and-pasting the rest of the tests over. I believe that once this work is done further subdividing the packages/sources and changing the build tool (or not) will be much simpler - although I am open to correction. Cheers, Tom -----Original Message----- From: Greg Trasuk [mailto:[EMAIL PROTECTED] Sent: 08 December 2008 11:58 To: river-dev@incubator.apache.org Subject: Re: Deciding the Future This reminds me of that quote - "Some people, when confronted with a problem, think 'I know, I?ll use regular expressions.' Now they have two problems". I'm not in favour of Maven. I can see restructuring the build somewhat for Ant (remember, the structure really comes from being built with a makefile, before there was an Ant). Cheers, Greg. On Mon, 2008-12-08 at 03:44, Jools wrote: > +1 > > I've love to see the codebase move over to a maven build. > > Over the last 9 months we have moved all our projects over to maven, with > great success. > Our build and release procedures are greatly reduced, and getting developers > up and running with their ide's. > > I'd be happy to Log a JIRA and take a lead on this, what do others think ? > > --Jools > > > > > > 2008/12/8 Jeff Ramsdale <[EMAIL PROTECTED]> > > > Niclas, > > Once again I very much agree with you. Dan's got a good point about two > > jars > > (-dl and non-dl) resulting from each service component, though. > > > > I know this will induce groans from some parties but Apache River would > > really benefit from a Maven build. The dependencies between modules are > > complex as is the generation of the artifacts. Maven would allow for a > > restructuring that clarifies the source structure while supporting the > > generation of composite artifacts. You might look into the Maven Classdep > > Plugin that Chris Sterling introduced several years ago: < > > https://maven-classdep-plugin.dev.java.net/>. It could make sense to bring > > this plugin into the Apache River fold, incidentally. Use of this plugin > > could also help increase uptake among the Maven developer crowd as it > > simplifies the generation of artifacts for Jini services. > > > > A huge benefit of a Maven-based build is the ability to generate metadata > > for most of the popular IDEs. This has proven to be incredibly useful on my > > teams and allows for a multiplicity of IDEs to be used against the same > > codebase. > > > > -- Greg Trasuk, President StratusCom Manufacturing Systems Inc. - We use information technology to solve business problems on your plant floor. http://stratuscom.com www.sucden.co.uk Sucden (UK) Limited, 5 London Bridge Street, London SE1 9SG Telephone +44 20 7940 9400 Registered in England no. 1095841 VAT registration no. GB 446 9061 33 Authorised and Regulated by the Financial Services Authority (FSA) and entered in the FSA register under no. 114239 This email, including any files transmitted with it, is confidential and may be privileged. It may be read, copied and used only by the intended recipient. If you are not the intended recipient of this message, please notify [EMAIL PROTECTED] immediately and delete it from your computer system. We believe, but do not warrant, that this email and its attachments are virus-free, but you should check. Sucden (UK) Ltd may monitor traffic data of both business and personal emails. By replying to this email, you consent to Sucden's monitoring the content of any emails you send to or receive from Sucden. Sucden is not liable for any opinions expressed by the sender where this is a non-business email. The contents of this e-mail do not constitute advice and should not be regarded as a recommendation to buy, sell or otherwise deal with any particular investment. This message has been scanned for viruses by Mimecast. www.sucden.co.uk Sucden (UK) Limited, 5 London Bridge Street, London SE1 9SG Telephone +44 20 7940 9400 Registered in England no. 1095841 VAT registration no. GB 446 9061 33 Authorised and Regulated by the Financial Services Authority (FSA) and entered in the FSA register under no. 114239 This email, including any files transmitted with it, is confidential and may be privileged. It may be read, copied and used only by the intended recipient. If you are not the intended recipient of this message, please notify [EMAIL PROTECTED] immediately and delete it from your computer system. We believe, but do not warrant, that this email and its attachments are virus-free, but you should check. Sucden (UK) Ltd may monitor traffic data of both business and personal emails. By replying to this email, you consent to Sucden’s monitoring the content of any emails you send to or receive from Sucden. Sucden is not liable for any opinions expressed by the sender where this is a non-business email. The contents of this e-mail do not constitute advice and should not be regarded as a recommendation to buy, sell or otherwise deal with any particular investment. This message has been scanned for viruses by Mimecast.
