Tried to reproduce the issue and don't get it anymore .... Sorry for the noise.
2008/2/5, simon <[EMAIL PROTECTED]>: > > > On Tue, 2008-02-05 at 19:33 +0000, Niall Pemberton wrote: > > On Feb 5, 2008 7:26 PM, nicolas de loof <[EMAIL PROTECTED]> wrote: > > > Hello > > > > > > I've got a strange behavior of Eclipse when using maven to configure > my > > > environment. The .classpath includes the project root as a source > folder to > > > match the commons-parent-7.pom <resource>. > > > > > > This has the side effect that the "new class" wizard appends " > src.main.java." > > > to the extended class in imports. Not blocking, but not very nice. > > > > > > Did I miss something in my conf ? > > > Do you all use Idea ? > > > Why not put those required files in src/main/resources/META-INF as the > > > natural place for them ? > > > > Only natural in the m2 world, which most of commons pre-dates. Plus we > > need/want them in the root for the source and binary distros. Commons > > parent <resource> means you don't have to define them and also theres > > a hack to copy them from there to make sure they're included in the > > -javadoc.jar - so IMO better for monitor to move them there. > > We want NOTICE/LICENSE in the root so that people who browse the source > see them. Hiding them three directories down does not constitute good > documentation. > > As Niall says, src/main/resources/META-INF is only natural for Maven. > > But if the entire root directory is defined as a source folder then that > is wrong. What project is doing that? Or are you using something like > MEVENIDE? > > I use eclipse and have no problem with any commons project I've worked > on so far, but only use eclipse:eclipse and not any other plugins. > > Regards, > Simon > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
