Hi folks, I've just submitted a couple of patches to make eclipse WTP configuration file generation work fully - see GRADLE-247. This actually makes the WTP support useful as with it one can now create an empty project with a project dependency and get a fully working, deployable WTP project at the end.
I've also opened an improvement GRADLE-247. There is now a fair amount of code duplication in the eclipse plugins around manipulating a dom4j tree to create xml configuration. As part of GRADLE-247, I think it would be a good idea to encapsulate the dom manipulation in a proper model. This would allow the following to be easily accomplished: Read existing configuration into EclipseProject or EclipseWtpConfiguration -> call addFacet, or addBuilder as required, invoke a save() method. Does this strike you as a good idea? If so I'll submit some additional patches. Phil. -- View this message in context: http://www.nabble.com/eclipse-WTP-fun-tp19770216p19770216.html Sent from the gradle-dev mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
