On Fri, Sep 5, 2008 at 5:48 PM, Eugene Kuleshov <[EMAIL PROTECTED]> wrote: > Schrodt, Martin wrote: >> >> Bouiaw, I agree with what you wrote, and your testcase. >> I want to add that I could kind of fake the missing feature by adding >> the exploded base WAR's folder to >> C:\WorkspaceMaven\testTapestry\.settings\org.eclipse.wst.common.componen >> t like this: >> >> <wb-resource deploy-path="/" source-path="/target/testTapestry"/> That might work for workspace resources but not for war files in your repository. These 'll have to be exploded somehow
>> >> That made WTP deploy the base WAR, but the overwriting of files from the >> base WAR which also exist in the overlayed WAR stops to work. > > This is actually kind of research we would like to see from the community. > If you can figure out how to manually configure Maven projects to work in > Eclipse and write it down on the wiki, it would help to figure out how to > automate this. >> >> Unfortunately, my knowledge about eclipse plugin development is limited, >> but I will try to follow Eugene's advice to get some kind of development >> environment running. > > Please give it a try and please don't hesitate to ask questions. Yes do it, it's fun you'll see :-) Look at me \o/ > > regards, > Eugene > > > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > > regards, Fred Bricon -- GMail rox! --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
