You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by nicolas de loof <ni...@apache.org> on 2008/02/05 20:26:57 UTC
LICENSE & NOTICE at project root ?
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 ?
Nico.
Re: LICENSE & NOTICE at project root ?
Posted by nicolas de loof <ni...@apache.org>.
Tried to reproduce the issue and don't get it anymore ....
Sorry for the noise.
2008/2/5, simon <si...@chello.at>:
>
>
> On Tue, 2008-02-05 at 19:33 +0000, Niall Pemberton wrote:
> > On Feb 5, 2008 7:26 PM, nicolas de loof <ni...@apache.org> 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: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>
Re: LICENSE & NOTICE at project root ?
Posted by simon <si...@chello.at>.
On Tue, 2008-02-05 at 19:33 +0000, Niall Pemberton wrote:
> On Feb 5, 2008 7:26 PM, nicolas de loof <ni...@apache.org> 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: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: LICENSE & NOTICE at project root ?
Posted by Niall Pemberton <ni...@gmail.com>.
On Feb 5, 2008 7:26 PM, nicolas de loof <ni...@apache.org> 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.
Niall
> Nico.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org