On 9 Feb 07, at 1:21 PM 9 Feb 07, Bernhard C Gass wrote:
Hello,
I am not reading the mailing lists on a regular basis so please
forgive me if that issue was raised already.
I do not want to restructure the SCM, so I made a symbolic link to
the source code. That works fine with Maven in general, but the
eclipse plugin substitutes the link with the hard path and adds it
to the .classpath file when you call 'mvn eclipse:eclipse'. The
Eclipse IDE does not except folders outside of the project folder
and for that the generated Eclipse project cannot be opened in
Eclipse and returns an error.
My current workaround is a shell script that creates a <project
base>/src/main/java folder, calls 'mvn eclipse:eclipse' then
deletes the java folder and creates the <project base>/src/main/
java link to the sources.
Does anybody have a better suggestion?
Specify your actual source directory in your POM.
<project>
...
<build>
<sourceDirectory>src/whatever</sourceDirectory>
...
</build>
</project.
Avoid playing tricks in your file system and specify what you're
using, then all the plugins will work as expected. You can specify
this in your top-level POM if you have many projects so that you only
have to do it once.
Jason.
- Bernhard
Bernhard C Gass
Apple Computer Inc.
EAI Team
IS&T
T 408.974.3224
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
