We have a major headache for #4, as pointed out in http://www.mail-archive.com/[email protected]/msg51801.html
This might be the right time to get it resolved, before we put significant efforts in that direction. Request each of you to post your views & suggestions on http://www.mail-archive.com/[email protected]/msg51801.html . Once we have clarity, implementation will not be difficult. - Shiva On 9/28/07, Donald Woods <[EMAIL PROTECTED]> wrote: > > #1 and #4 sound good to me. > #2 should be to updated the build and prereqs to use WTP 2.0.1 and Eclipse > 3.3.1 (which should ship any day now) and we can then point users to the > WTP > 2.0.1 all-in-one bundle, to simplify everyones setup. > > #3 is lower priority and shouldn't hold up a maintenance release. As far > as > the samples, we should pick some of the Server provided samples to update > to > work in Eclipse, w/ readme updates on how to import them into > Eclipse. Some > minimal unit testing would be nice, but lets not take months adding tests > at > the expense of fixing users problems and adding long missing features.... > > > -Donald > > Tim McConnell wrote: > > Hi, I would like to starting discussing what we think should be included > > in the 2.0.1 release of the Geronimo Eclipse Plugin. I have some very > > preliminary thoughts that I have listed below but would like to > > encourage input from others. My initial thoughts are: > > > > 1. High priority JIRAs > > 2. Inclusion of the latest WTP release candidate > > 3. Build and test infrastructure improvements (e.g., build > > cleanup/improvements, execution of testcases during the build, a > > testsuite framework for the plugin, and a useful set of samples). > > 4. Full support for the Geronimo 2.0 deployment plans > > > >
