You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cayenne.apache.org by Andrus Adamchik <an...@objectstyle.org> on 2012/09/10 19:54:33 UTC
Removing Eclipse files from maven modules
How would everyone feel if we remove .project/.classpath/.settings from version control?
We've been going back and force on that in the past, and I usually preferred to have them in SVN. However now that m2eclipse plugin is so much better than it was in the past, and also we have many Eclipse versions with incompatible project files, I think we should reconsider that.
Andrus
Re: Removing Eclipse files from maven modules
Posted by Michael Gentry <mg...@masslight.net>.
I've been wondering why they are checked in, so I'd be +1 for removing them.
Thanks,
mrg
On Mon, Sep 10, 2012 at 1:54 PM, Andrus Adamchik <an...@objectstyle.org> wrote:
> How would everyone feel if we remove .project/.classpath/.settings from version control?
>
> We've been going back and force on that in the past, and I usually preferred to have them in SVN. However now that m2eclipse plugin is so much better than it was in the past, and also we have many Eclipse versions with incompatible project files, I think we should reconsider that.
>
> Andrus
Re: Removing Eclipse files from maven modules
Posted by Michael Gentry <mg...@masslight.net>.
This is my current one:
target/
.metadata
tar.gz
.classpath
.project
.settings/
.DS_Store
*~
Has a few extra things in it (and doesn't have some of yours).
mrg
On Mon, Dec 17, 2012 at 1:56 AM, Andrus Adamchik <an...@objectstyle.org>wrote:
> No objections to .gitignore. For myself I developed a routine setting up
> any new git-svn repo:
>
> git config svn-remote.svn.automkdirs false
> git config svn.rmdir true
> echo ".classpath
> .project
> .settings
> .externalToolBuilders
> .DS_Store
> target
> derby.log" >> .git/info/exclude
>
> Should probably put it on the site.
>
> Andrus
>
> On Dec 16, 2012, at 11:39 PM, Michael Gentry <mg...@masslight.net>
> wrote:
>
> > Definitely. That's what I do in my repos.
> >
> >
> > On Sat, Dec 15, 2012 at 5:58 PM, John Huss <jo...@gmail.com> wrote:
> >
> >> I think we should add the eclipse files to .gitignore. They are
> getting in
> >> the way now. Thoughts?
> >>
> >>
> >> On Fri, Sep 14, 2012 at 8:37 PM, Andrus Adamchik <
> andrus@objectstyle.org
> >>> wrote:
> >>
> >>> Done (see CAY-1740). If you already have Cayenne projects in Eclipse,
> you
> >>> should first delete them from workspace (or better - switch to a new
> >> clean
> >>> workspace), then update the code from command line, and then "Import >
> >>> Existing Maven Projects".
> >>>
> >>> DO NOT import cayenne-server and cayenne-client - those are confusing
> to
> >>> Eclipse (and not only to Eclipse ;)).
> >>>
> >>> Andrus
> >>>
> >>>
> >>>
> >>> On Sep 10, 2012, at 7:34 PM, Andrus Adamchik <an...@objectstyle.org>
> >>> wrote:
> >>>
> >>>> That was sure one of the reasons to keep the files under version
> >>> control. I don't think we are actually doing it though. There are no
> >>> per-project formatting settings in our Eclipse profiles IIRC. The
> problem
> >>> is also that there are different versions of Eclipse. And then there
> are
> >>> people using IDEA (I have at least 2 in my office alone :)). So this
> >> seems
> >>> like a losing battle. Something IDE-agnostic like checkstyle is
> probably
> >>> more appropriate for this.
> >>>>
> >>>> Andrus
> >>>>
> >>>>
> >>>>
> >>>> On Sep 10, 2012, at 7:23 PM, Aristedes Maniatis <ar...@maniatis.org>
> >>> wrote:
> >>>>
> >>>>> I forget which one, but there is a file which is responsible for
> >>> setting indent preferences, wrapping, etc. That's quite useful to
> leave
> >> in
> >>> the project so that everyone keeps the same preferences for the
> project.
> >>>>>
> >>>>> Ari
> >>>>>
> >>>>> On 11/09/12 3:54am, Andrus Adamchik wrote:
> >>>>>> How would everyone feel if we remove .project/.classpath/.settings
> >>> from version control?
> >>>>>>
> >>>>>> We've been going back and force on that in the past, and I usually
> >>> preferred to have them in SVN. However now that m2eclipse plugin is so
> >> much
> >>> better than it was in the past, and also we have many Eclipse versions
> >> with
> >>> incompatible project files, I think we should reconsider that.
> >>>>>>
> >>>>>> Andrus
> >>>>>>
> >>>>>
> >>>>> --
> >>>>> -------------------------->
> >>>>> Aristedes Maniatis
> >>>>> GPG fingerprint CBFB 84B4 738D 4E87 5E5C 5EFA EF6A 7D2E 3E49 102A
> >>>>>
> >>>>
> >>>>
> >>>
> >>>
> >>
>
>
Re: Removing Eclipse files from maven modules
Posted by Andrus Adamchik <an...@objectstyle.org>.
No objections to .gitignore. For myself I developed a routine setting up any new git-svn repo:
git config svn-remote.svn.automkdirs false
git config svn.rmdir true
echo ".classpath
.project
.settings
.externalToolBuilders
.DS_Store
target
derby.log" >> .git/info/exclude
Should probably put it on the site.
Andrus
On Dec 16, 2012, at 11:39 PM, Michael Gentry <mg...@masslight.net> wrote:
> Definitely. That's what I do in my repos.
>
>
> On Sat, Dec 15, 2012 at 5:58 PM, John Huss <jo...@gmail.com> wrote:
>
>> I think we should add the eclipse files to .gitignore. They are getting in
>> the way now. Thoughts?
>>
>>
>> On Fri, Sep 14, 2012 at 8:37 PM, Andrus Adamchik <andrus@objectstyle.org
>>> wrote:
>>
>>> Done (see CAY-1740). If you already have Cayenne projects in Eclipse, you
>>> should first delete them from workspace (or better - switch to a new
>> clean
>>> workspace), then update the code from command line, and then "Import >
>>> Existing Maven Projects".
>>>
>>> DO NOT import cayenne-server and cayenne-client - those are confusing to
>>> Eclipse (and not only to Eclipse ;)).
>>>
>>> Andrus
>>>
>>>
>>>
>>> On Sep 10, 2012, at 7:34 PM, Andrus Adamchik <an...@objectstyle.org>
>>> wrote:
>>>
>>>> That was sure one of the reasons to keep the files under version
>>> control. I don't think we are actually doing it though. There are no
>>> per-project formatting settings in our Eclipse profiles IIRC. The problem
>>> is also that there are different versions of Eclipse. And then there are
>>> people using IDEA (I have at least 2 in my office alone :)). So this
>> seems
>>> like a losing battle. Something IDE-agnostic like checkstyle is probably
>>> more appropriate for this.
>>>>
>>>> Andrus
>>>>
>>>>
>>>>
>>>> On Sep 10, 2012, at 7:23 PM, Aristedes Maniatis <ar...@maniatis.org>
>>> wrote:
>>>>
>>>>> I forget which one, but there is a file which is responsible for
>>> setting indent preferences, wrapping, etc. That's quite useful to leave
>> in
>>> the project so that everyone keeps the same preferences for the project.
>>>>>
>>>>> Ari
>>>>>
>>>>> On 11/09/12 3:54am, Andrus Adamchik wrote:
>>>>>> How would everyone feel if we remove .project/.classpath/.settings
>>> from version control?
>>>>>>
>>>>>> We've been going back and force on that in the past, and I usually
>>> preferred to have them in SVN. However now that m2eclipse plugin is so
>> much
>>> better than it was in the past, and also we have many Eclipse versions
>> with
>>> incompatible project files, I think we should reconsider that.
>>>>>>
>>>>>> Andrus
>>>>>>
>>>>>
>>>>> --
>>>>> -------------------------->
>>>>> Aristedes Maniatis
>>>>> GPG fingerprint CBFB 84B4 738D 4E87 5E5C 5EFA EF6A 7D2E 3E49 102A
>>>>>
>>>>
>>>>
>>>
>>>
>>
Re: Removing Eclipse files from maven modules
Posted by Michael Gentry <mg...@masslight.net>.
Definitely. That's what I do in my repos.
On Sat, Dec 15, 2012 at 5:58 PM, John Huss <jo...@gmail.com> wrote:
> I think we should add the eclipse files to .gitignore. They are getting in
> the way now. Thoughts?
>
>
> On Fri, Sep 14, 2012 at 8:37 PM, Andrus Adamchik <andrus@objectstyle.org
> >wrote:
>
> > Done (see CAY-1740). If you already have Cayenne projects in Eclipse, you
> > should first delete them from workspace (or better - switch to a new
> clean
> > workspace), then update the code from command line, and then "Import >
> > Existing Maven Projects".
> >
> > DO NOT import cayenne-server and cayenne-client - those are confusing to
> > Eclipse (and not only to Eclipse ;)).
> >
> > Andrus
> >
> >
> >
> > On Sep 10, 2012, at 7:34 PM, Andrus Adamchik <an...@objectstyle.org>
> > wrote:
> >
> > > That was sure one of the reasons to keep the files under version
> > control. I don't think we are actually doing it though. There are no
> > per-project formatting settings in our Eclipse profiles IIRC. The problem
> > is also that there are different versions of Eclipse. And then there are
> > people using IDEA (I have at least 2 in my office alone :)). So this
> seems
> > like a losing battle. Something IDE-agnostic like checkstyle is probably
> > more appropriate for this.
> > >
> > > Andrus
> > >
> > >
> > >
> > > On Sep 10, 2012, at 7:23 PM, Aristedes Maniatis <ar...@maniatis.org>
> > wrote:
> > >
> > >> I forget which one, but there is a file which is responsible for
> > setting indent preferences, wrapping, etc. That's quite useful to leave
> in
> > the project so that everyone keeps the same preferences for the project.
> > >>
> > >> Ari
> > >>
> > >> On 11/09/12 3:54am, Andrus Adamchik wrote:
> > >>> How would everyone feel if we remove .project/.classpath/.settings
> > from version control?
> > >>>
> > >>> We've been going back and force on that in the past, and I usually
> > preferred to have them in SVN. However now that m2eclipse plugin is so
> much
> > better than it was in the past, and also we have many Eclipse versions
> with
> > incompatible project files, I think we should reconsider that.
> > >>>
> > >>> Andrus
> > >>>
> > >>
> > >> --
> > >> -------------------------->
> > >> Aristedes Maniatis
> > >> GPG fingerprint CBFB 84B4 738D 4E87 5E5C 5EFA EF6A 7D2E 3E49 102A
> > >>
> > >
> > >
> >
> >
>
Re: Removing Eclipse files from maven modules
Posted by John Huss <jo...@gmail.com>.
I think we should add the eclipse files to .gitignore. They are getting in
the way now. Thoughts?
On Fri, Sep 14, 2012 at 8:37 PM, Andrus Adamchik <an...@objectstyle.org>wrote:
> Done (see CAY-1740). If you already have Cayenne projects in Eclipse, you
> should first delete them from workspace (or better - switch to a new clean
> workspace), then update the code from command line, and then "Import >
> Existing Maven Projects".
>
> DO NOT import cayenne-server and cayenne-client - those are confusing to
> Eclipse (and not only to Eclipse ;)).
>
> Andrus
>
>
>
> On Sep 10, 2012, at 7:34 PM, Andrus Adamchik <an...@objectstyle.org>
> wrote:
>
> > That was sure one of the reasons to keep the files under version
> control. I don't think we are actually doing it though. There are no
> per-project formatting settings in our Eclipse profiles IIRC. The problem
> is also that there are different versions of Eclipse. And then there are
> people using IDEA (I have at least 2 in my office alone :)). So this seems
> like a losing battle. Something IDE-agnostic like checkstyle is probably
> more appropriate for this.
> >
> > Andrus
> >
> >
> >
> > On Sep 10, 2012, at 7:23 PM, Aristedes Maniatis <ar...@maniatis.org>
> wrote:
> >
> >> I forget which one, but there is a file which is responsible for
> setting indent preferences, wrapping, etc. That's quite useful to leave in
> the project so that everyone keeps the same preferences for the project.
> >>
> >> Ari
> >>
> >> On 11/09/12 3:54am, Andrus Adamchik wrote:
> >>> How would everyone feel if we remove .project/.classpath/.settings
> from version control?
> >>>
> >>> We've been going back and force on that in the past, and I usually
> preferred to have them in SVN. However now that m2eclipse plugin is so much
> better than it was in the past, and also we have many Eclipse versions with
> incompatible project files, I think we should reconsider that.
> >>>
> >>> Andrus
> >>>
> >>
> >> --
> >> -------------------------->
> >> Aristedes Maniatis
> >> GPG fingerprint CBFB 84B4 738D 4E87 5E5C 5EFA EF6A 7D2E 3E49 102A
> >>
> >
> >
>
>
Re: Removing Eclipse files from maven modules
Posted by Andrus Adamchik <an...@objectstyle.org>.
Done (see CAY-1740). If you already have Cayenne projects in Eclipse, you should first delete them from workspace (or better - switch to a new clean workspace), then update the code from command line, and then "Import > Existing Maven Projects".
DO NOT import cayenne-server and cayenne-client - those are confusing to Eclipse (and not only to Eclipse ;)).
Andrus
On Sep 10, 2012, at 7:34 PM, Andrus Adamchik <an...@objectstyle.org> wrote:
> That was sure one of the reasons to keep the files under version control. I don't think we are actually doing it though. There are no per-project formatting settings in our Eclipse profiles IIRC. The problem is also that there are different versions of Eclipse. And then there are people using IDEA (I have at least 2 in my office alone :)). So this seems like a losing battle. Something IDE-agnostic like checkstyle is probably more appropriate for this.
>
> Andrus
>
>
>
> On Sep 10, 2012, at 7:23 PM, Aristedes Maniatis <ar...@maniatis.org> wrote:
>
>> I forget which one, but there is a file which is responsible for setting indent preferences, wrapping, etc. That's quite useful to leave in the project so that everyone keeps the same preferences for the project.
>>
>> Ari
>>
>> On 11/09/12 3:54am, Andrus Adamchik wrote:
>>> How would everyone feel if we remove .project/.classpath/.settings from version control?
>>>
>>> We've been going back and force on that in the past, and I usually preferred to have them in SVN. However now that m2eclipse plugin is so much better than it was in the past, and also we have many Eclipse versions with incompatible project files, I think we should reconsider that.
>>>
>>> Andrus
>>>
>>
>> --
>> -------------------------->
>> Aristedes Maniatis
>> GPG fingerprint CBFB 84B4 738D 4E87 5E5C 5EFA EF6A 7D2E 3E49 102A
>>
>
>
Re: Removing Eclipse files from maven modules
Posted by Andrus Adamchik <an...@objectstyle.org>.
That was sure one of the reasons to keep the files under version control. I don't think we are actually doing it though. There are no per-project formatting settings in our Eclipse profiles IIRC. The problem is also that there are different versions of Eclipse. And then there are people using IDEA (I have at least 2 in my office alone :)). So this seems like a losing battle. Something IDE-agnostic like checkstyle is probably more appropriate for this.
Andrus
On Sep 10, 2012, at 7:23 PM, Aristedes Maniatis <ar...@maniatis.org> wrote:
> I forget which one, but there is a file which is responsible for setting indent preferences, wrapping, etc. That's quite useful to leave in the project so that everyone keeps the same preferences for the project.
>
> Ari
>
> On 11/09/12 3:54am, Andrus Adamchik wrote:
>> How would everyone feel if we remove .project/.classpath/.settings from version control?
>>
>> We've been going back and force on that in the past, and I usually preferred to have them in SVN. However now that m2eclipse plugin is so much better than it was in the past, and also we have many Eclipse versions with incompatible project files, I think we should reconsider that.
>>
>> Andrus
>>
>
> --
> -------------------------->
> Aristedes Maniatis
> GPG fingerprint CBFB 84B4 738D 4E87 5E5C 5EFA EF6A 7D2E 3E49 102A
>
Re: Removing Eclipse files from maven modules
Posted by Aristedes Maniatis <ar...@maniatis.org>.
I forget which one, but there is a file which is responsible for setting indent preferences, wrapping, etc. That's quite useful to leave in the project so that everyone keeps the same preferences for the project.
Ari
On 11/09/12 3:54am, Andrus Adamchik wrote:
> How would everyone feel if we remove .project/.classpath/.settings from version control?
>
> We've been going back and force on that in the past, and I usually preferred to have them in SVN. However now that m2eclipse plugin is so much better than it was in the past, and also we have many Eclipse versions with incompatible project files, I think we should reconsider that.
>
> Andrus
>
--
-------------------------->
Aristedes Maniatis
GPG fingerprint CBFB 84B4 738D 4E87 5E5C 5EFA EF6A 7D2E 3E49 102A