Great points – I would have zoomed into this level on my question had I known how well it would be answered :).
I think that if we look at the feature ‘absolutely’, then yes, redeployment of the WebRoot/ etc. does not seeem to really fit does it (particularly web.xml..). However, I think that it could be at least supported like a regular Java project is – in a way that copies the .class files into the compilation target directory of the dependant project, or jar them up like it does with other projects. That would satisfy my needs.
By the way, the basis of my question comes from trying to seperate my development into 2 logical parts – a framework portion (reusable portion) and then projects that all utilize it. The ‘issue’ as it were comes from assigning ‘web project’ properties to the framework which needs to be exported.
My current workaround was simply to bring the struts/other jars into the framework project as a library so that the compilation, and thus the redeploy steps worked. I am working on this logic concurrently, so having a working debug feature was the intent here. Thus, came my pondering … ‘gee, it sure would be cool if a web project worked just like a java project’ 😉
Cheers – maybe at least that subset will make it into myEclipse – great product!
— Jeremy