Hi, Robbie.
Thank you for looking into this issue. I think the problem has been fixed
(to be precise, worked around) by Jeremy using a profile-based property. The
ideal solution is to fix the maven eclipse plugin to handle overlapping
source folders with inclusion/exclusion patterns. Please see the discussions
we had on this thread before.
I used the following shell script from Rick before the fix was checked in.
It automates the workaround you just suggested.
for i in `/usr/bin/find . -name .classpath`
do
echo $i
sed -e "/classpathentry kind=\"src\" path=\"\.\"/d" $i>$i.new && mv -f
$i.new $i
done
Thanks,
Raymond
----- Original Message -----
From: "Robbie Minshall" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Tuesday, September 05, 2006 1:53 PM
Subject: Re: mvn -Peclipse eclipse:eclipse doesn't work any more
As a workaround to get my projects into eclipse from recent builds I had
to
remove the following line from the .classpath folder
<classpathentry kind="src" path="." output="target/classes/META-INF"/>
since eclipse did not like have the output folder META-INF nested under
the
output folder target.
Robbie
On 8/31/06, Raymond Feng <[EMAIL PROTECTED]> wrote:
Hi,
It seems that we added "." to the resource folder in pom.xml in recent
checkins as follows:
<resource>
<directory>.</directory>
<targetPath>META-INF</targetPath>
<filtering>true</filtering>
<includes>
<include>LICENSE.txt</include>
<include>NOTICE.txt</include>
</includes>
</resource>
This breaks the maven eclipse plugin and the generated classpaths are
messed up. I guess we need to apply the eclipse profile hack.
Thanks,
Raymond
--
* * * Charlie * * *
Check out some pics of little Charlie at
http://www.flickr.com/photos/[EMAIL PROTECTED]/sets/
* * * Addresss * * *
1914 Overland Drive
Chapel Hill
NC 27517
* * * Number * * *
919-225-1553
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
