On 7/8/05, Werner Punz <[EMAIL PROTECTED]> wrote: > Excellent idea, but for Eclipse somewhat problematic (see below).... > > I am not going to put a blank project online unless there really is a > demand, there is at least the Exadel plugin for eclipse 3.0 which is > totally free and several limited time versions for 3.x (and Exadel might > also do a free version for 3.1, all those basically give the IDE users a > good headstart, I just put references to those plugin collections into > the Wiki. That one might serve users better than giving them a blank > preconfigured project. > > The main problem I saw with doing that with Eclipse on a second though, > was, that Eclipse for now does not have any Webapp support at all, all > the webapp power has to be integrated via external plugins. > > So if you want to do serious webapp development, you have to start to > search for plugins anyway, and pointing them towards a blank webapp > project does not good in this case, if the user is a newby. > So pointing them towards a workable decent free or cheap plugin > collection which is able to generate a project structure might be better.
Of course, if the Eclipse IDE files are generated on the user's machine by Maven(2), then the user can have local configuration to tell the Maven(2) plugin which Eclipse webapp plugins are preferred, and this can influence the contents of the generated project files as necessary. Or we could open source the Maven2 JDeveloper Plugin and then you could generate the JDeveloper project files and do webapp development for free without searching for any plugins. :-) Kind Regards, John Fallows.
