Hello, My first thought was that in order to use several Castor checkouts parallel in Eclipse it was already necessary to use an additional command[1]. When m2eclipse will work I am +1 for stopping manual editing and using m2eclipse instead. + This would save a lot of time for Werner and Andras. + Although when upgrading a dependency no more manual editing is needed and Eclipse related files could remain in the project.
> How about if everybody tried this once, and then provide feedback. Just > delete .classpath, .project and .settings directory before you rnu the Maven > commands. * svn co http://svn.codehaus.org/castor/castor/trunk * I removed .classpath, .project and .settings * mvn clean compile * mvn eclipse:eclipse Instead of having one project trunk I do have a project per module. That's not what we want, is it? I tried the way Udai mentioned above. It didn't work out for me. Maybe you could help me on this. Here is what I did: * svn co http://svn.codehaus.org/castor/castor/trunk. * I installed m2eclipse [2]. * Like Udai explained I edited .classpath * To enable m2eclipse nature I added following buildCommand and nature to .project <buildCommand> <name>org.maven.ide.eclipse.maven2Builder</name><arguments></arguments> </buildCommand> <nature>org.maven.ide.eclipse.maven2Nature</nature> * mvn clean compile * mvn eclipse:eclipse * In Eclipse I did 'Import existing Project into Workspace' I get one big project and 11569 cannot be resolved to type-errors. I already tried 'mvn install' [3] and 'Import existing Maven Project' instead of the simple import I did before. As far as I see there is no difference between this two ways of importing. In both of there is a Classpath Container in the project. It is called 'Maven Dependencies'. The properties of Maven Dependencies says to use Maven Project Settings to configure some Maven Dependency Resolution. How do I get rid of these errors? What did I miss to do in order to get this working? Cheers, Philipp [1] http://castor.org/contributing.html#Several-Castor-checkouts-parallel-in-Eclipse [2] http://m2eclipse.sonatype.org/installing-m2eclipse.html [3] http://old.nabble.com/org.maven.ide.eclipse.MAVEN2_CLASSPATH_CONTAINER-to9470746.html On Thu, May 6, 2010 at 10:46 AM, Robert Thurnher <r.thurn...@gmail.com> wrote: > Hi, > > On 1 May 2010 16:20, Werner Guttmann <wgut...@codehaus.org> wrote: >> Hi everybody, >> >> I'd really like to see .classpath and .project being removed from our SVN >> repository. I know there's some resistance, so let's use this thread to get >> an complete overview on any objections. > > Like Andras I'm currently only working on Castor within the scope of a > university course, yet, I'd like to share my 2 cents here as well: > > In our case, the present state of included Eclipse project files in > Castor's Subversion repo turned out to be actually rather cumbersome > than really useful when first checking out the project. > > That is, members of our group using Eclipse were struggling a bit in > the beginning getting a project setup working mainly due to > before-mentioned included .classpath etc. files. > Just when they removed and subsequently generated them via `mvn > eclipse:eclipse` these issues were resolved. > > Moreover, members of our group using other IDEs (namely, IntelliJ IDEA > and NetBeans; i.e., equipped with built-in Maven support), naturally, > weren't confronted with such issues at all. > > Consequently and generally, I'm all +1 for not bundling any > IDE-specific project files within its source code repo (especially, > when the overhead of having to manage them manually can be avoided). > > -- Robert > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > > --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
