It is unclear to me why the resources folder can not include a META-INF directory containing the licence and notice files. This would avoid nesting the META-INF output inside the output folder target and seems to work fine for me.
I would like to understand this more so if someone could explain why this is a bad idea I would appreciate it. thanks, Robbie On 9/5/06, Robbie Minshall <[EMAIL PROTECTED]> wrote:
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
-- * * * 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
