trayDesktop build path not correctly set when working with Eclipse

[GoogleCodeExporter]

What steps will reproduce the problem?
1. create a fresh workspace using m2e
2. use m2e checkout maven projects from scm
3. wait the workspace to build everything

What is the expected output? What do you see instead?

One would expect the workspace to compile all the projects. The trayDesktop 
project is not built properly because the target/generated-sources directory is 
not in the build path.

The fix for the user is trivial: add target/generated-sources in the buildpath 
(build path/use as source folder).

The current issue arises because eclipse specific settings are not stored on 
SVN.

Storing the .classpath file for trayDesktop on svn would partly solve the 
problem.

However, the target/generated-sources directory only appears after running a 
full build. If that directory is not present when checking out, Eclipse will 
show an error in the project anyway :(

Original issue reported on code.google.com by daniel.l...@gmail.com on 26 Jan 2011 at 8:41

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

The last year many students developed on fsnet using netbeans, this was not my 
preferred IDE but many students prefered netbeans simply because it provides a 
native maven experience. 
Stay independant of any IDE is a good thing in my opinion.

Further, We use m2eclipse so there is no reason to store eclipse-specific files 
on the SVN. M2eclipse genrates and manage this files.

Note that you can also use Eclipse settings to run maven on project import 
(Windows -> preferences -> Goals to run on project import)

Original comment by mat.boni...@gmail.com on 26 Jan 2011 at 9:27

[GoogleCodeExporter]

The problem is that checking out the project in the classroom ends up with a 
broken install. That's bad.
Having to do an extra step as described in the wiki is not a reasonable 
workaround.
Now that m2e is an eclipse project, I hope we can find a nice fix for this :)

Original comment by daniel.l...@gmail.com on 26 Jan 2011 at 9:33

[GoogleCodeExporter]

Please all vote for this bug:
https://issues.sonatype.org/browse/MNGECLIPSE-1833

Original comment by daniel.l...@gmail.com on 26 Jan 2011 at 10:28

[GoogleCodeExporter]

As notfified here : http://code.google.com/p/fsnet/source/detail?r=1553 

You should checkout this (french) article :

http://blog.xebia.fr/2011/01/19/configurer-automatiquement-eclipse-avec-maven/

Original comment by mat.boni...@gmail.com on 1 Feb 2011 at 9:26

[GoogleCodeExporter]

It is not a problem on our side.

Original comment by daniel.l...@gmail.com on 9 Mar 2011 at 8:27

• Changed state: WontFix