You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by Greg Stein <gs...@lyra.org> on 2003/08/15 02:22:54 UTC
global cvsignore (was: geronimo-dev Digest 14 Aug 2003 22:49:29 -0000 Issue 62)
On Thu, Aug 14, 2003 at 10:49:29PM -0000, geronimo-dev-digest-help@incubator.apache.org wrote:
>...
> From: Jason Dillon <ja...@coredevelopers.net>
> Subject: Re: [PATCH] Added maven.log, .project and .classpath into .cvsignore
> To: geronimo-dev@incubator.apache.org
> Date: Fri, 15 Aug 2003 05:27:13 +0700
>
> >Whats the global cvsignore?
>
> CVSROOT/cvsignore
>
> I would have done this, but I do not have access to CVSROOT.
Well, that wouldn't have been too friendly since the entire ASF shares that
CVSROOT. I would recommend bringing up the change on infrastructure. Maybe
asking the Jakarta PMC or something to see if the entire Java community
would buy off on the additions.
Cheers,
-g
p.s. I have access to make the change, but would wanna see some wider buyoff
from the larger community first.
--
Greg Stein, http://www.lyra.org/
Re: global cvsignore (was: geronimo-dev Digest 14 Aug 2003 22:49:29 -0000 Issue 62)
Posted by Jason Dillon <ja...@coredevelopers.net>.
> Well, that wouldn't have been too friendly since the entire ASF shares
> that
> CVSROOT. I would recommend bringing up the change on infrastructure.
> Maybe
> asking the Jakarta PMC or something to see if the entire Java community
> would buy off on the additions.
I would suggest moving away from that, so that each TLP can have more
control with out having to okay it with all other TLPs.
I would suggest if we start to play with maven that it be setup as such
if there are similar issues, note I have only played with svn a little,
but really want to play more.
--jason
Re: global cvsignore (was: geronimo-dev Digest 14 Aug 2003 22:49:29 -0000 Issue 62)
Posted by James Strachan <ja...@yahoo.co.uk>.
On Friday, August 15, 2003, at 09:04 am, Alex Blewitt wrote:
> On Friday, Aug 15, 2003, at 01:44 Europe/London, Henri Yandell wrote:
>
>> Definitely got my support. maven.log is an easy no-no, and the
>> reasons for
>> having .project and .classpath would only really hold if either:
>>
>> a) project has all its dependencies in a lib/
>> b) project assumes the user will set a MAVEN_REPO variable in eclipse
>> and
>> have the values found there.
>
> This would probably be a good convention IMHO; I've had to hard-code
> them in my path.
>
> Plus, if you had a new depedency added by developer X, and developer X
> commits the .classpath, then I don't need to update my Eclipse runtime
> to notice the new libraries other than doing a refresh.
>
> Of course, it may be possible to auto-generate the .classpath from the
> maven file :-)
It already is.
maven eclipse
which uses the MAVEN_REPO so that you can share the .classpath with
other users.
>
>> Do you want me to take it to the Jakarta PMC? Alternatively we could
>> just
>> float the idea on Jakarta General and Maven Users/Dev and see what
>> happens. Also, as Eclipse is not just Java, I assume the .project
>> file is
>> applicable to all projects.
>
> Yes, the .project gives the project name and build types (i.e.
> Java/Plain/Whatever). The only time we might run into problems is in a
> system where I'm using WSAD (built on top of Eclipse) and the .project
> lists it as (say) a Web Project; I'd therefore have a different (and
> incompatible) .project than Eclipse users.
Yep. I'd be happy if we can all just use Maven to generate project
files. Though right now there are problems with multi-maven-project
eclipse projects (am taking this over to the eclipse thread for more
detail).
James
-------
http://radio.weblogs.com/0112098/
Re: global cvsignore (was: geronimo-dev Digest 14 Aug 2003 22:49:29 -0000 Issue 62)
Posted by Alex Blewitt <Al...@ioshq.com>.
On Friday, Aug 15, 2003, at 01:44 Europe/London, Henri Yandell wrote:
> Definitely got my support. maven.log is an easy no-no, and the reasons
> for
> having .project and .classpath would only really hold if either:
>
> a) project has all its dependencies in a lib/
> b) project assumes the user will set a MAVEN_REPO variable in eclipse
> and
> have the values found there.
This would probably be a good convention IMHO; I've had to hard-code
them in my path.
Plus, if you had a new depedency added by developer X, and developer X
commits the .classpath, then I don't need to update my Eclipse runtime
to notice the new libraries other than doing a refresh.
Of course, it may be possible to auto-generate the .classpath from the
maven file :-)
> Do you want me to take it to the Jakarta PMC? Alternatively we could
> just
> float the idea on Jakarta General and Maven Users/Dev and see what
> happens. Also, as Eclipse is not just Java, I assume the .project file
> is
> applicable to all projects.
Yes, the .project gives the project name and build types (i.e.
Java/Plain/Whatever). The only time we might run into problems is in a
system where I'm using WSAD (built on top of Eclipse) and the .project
lists it as (say) a Web Project; I'd therefore have a different (and
incompatible) .project than Eclipse users.
Alex.
Re: global cvsignore (was: geronimo-dev Digest 14 Aug 2003 22:49:29
-0000 Issue 62)
Posted by Henri Yandell <ba...@generationjava.com>.
Definitely got my support. maven.log is an easy no-no, and the reasons for
having .project and .classpath would only really hold if either:
a) project has all its dependencies in a lib/
b) project assumes the user will set a MAVEN_REPO variable in eclipse and
have the values found there.
Neither seems likely to be default for a project, and would constantly see
pain caused by accidental committings.
Do you want me to take it to the Jakarta PMC? Alternatively we could just
float the idea on Jakarta General and Maven Users/Dev and see what
happens. Also, as Eclipse is not just Java, I assume the .project file is
applicable to all projects.
Hen
On Thu, 14 Aug 2003, Greg Stein wrote:
> On Thu, Aug 14, 2003 at 10:49:29PM -0000, geronimo-dev-digest-help@incubator.apache.org wrote:
> >...
> > From: Jason Dillon <ja...@coredevelopers.net>
> > Subject: Re: [PATCH] Added maven.log, .project and .classpath into .cvsignore
> > To: geronimo-dev@incubator.apache.org
> > Date: Fri, 15 Aug 2003 05:27:13 +0700
> >
> > >Whats the global cvsignore?
> >
> > CVSROOT/cvsignore
> >
> > I would have done this, but I do not have access to CVSROOT.
>
> Well, that wouldn't have been too friendly since the entire ASF shares that
> CVSROOT. I would recommend bringing up the change on infrastructure. Maybe
> asking the Jakarta PMC or something to see if the entire Java community
> would buy off on the additions.
>
> Cheers,
> -g
>
> p.s. I have access to make the change, but would wanna see some wider buyoff
> from the larger community first.
>
> --
> Greg Stein, http://www.lyra.org/
>