If it is easy to generate the Eclipse project files via Maven (and everybody who knows Maven seems to know this already) then perhaps I should remove them from the source release files.
Any objections? - Dave On Mon, Apr 4, 2011 at 8:47 AM, Susanne Gladén <[email protected]> wrote: > I get the same error when trying to import all projects as Existing > Maven projects. > > /Susanne > > 2011/4/4 Susanne Gladén <[email protected]>: >> If I remove .project, .classpath, .settings files from the project. And then: >> mvn -Dwtpversion=2.0 compile eclipse:eclipse on the project >> >> Then "import existing maven project into workspace" works >> >> >> /Susanne >> >> 2011/4/4 Susanne Gladén <[email protected]>: >>> Hi, >>> >>> I just started to test the RC5 relese but I encountered som problems. >>> >>> 1. I downloaded the RC5 source. >>> 2. Imported the project into eclipse >>> 3. maven clean >>> 4. maven install >>> 5. Import Existing Maven Project and choosed only to import >>> weblogger-webapp and weblogger-web. >>> When importing the maven projects I get and error "Could not write >>> file: weblogger-webapp\.classpath (access denied)" and "Could not >>> write file: weblogger-web\.classpath (access denied)" >>> >>> I can edit that file outside of eclipse. >>> >>> I googled the problem and I found that several wrote that this problem >>> might be because there is an error in the project >>> >>> Anyone know? >>> >>> I run on Windows >>> >>> /Susanne >>> >> >
