Re: Eclipse no longer content-assists, checks code errors after Subclipse install
Mark Phippard <[email protected]> Sat, 21 Feb 2015 15:29:33 -0500
| Newsgroups | gmane.comp.version-control.subversion.subclipse.user |
|---|---|
| Message-ID | <CAHFaGCpWvdSSj-E6x8NaF7a5wEyd3b59-Ux==fjJ5guEa-qggA@mail.gmail.com> |
------=_Part_1662_2071778348.1424550615131 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit On Sat, Feb 21, 2015 at 3:14 PM, skyemoor <[email protected]> wrote: > Mark, > > Your comments are very helpful, thanks. > > So for option 1, it sounds like I can continue to work on a project, > tagging it as I go, able to roll back at any time. > > For option 2, it sounds like I create a new project for each baseline (?) > > It sounds like option 1 is the most attractive. I've been making changes > to a couple of files, but I plan to insert them into my previous Eclipse > project fileset that I saved off in backup, delete the current SVN > repository, then check-in the project and move forward from there. > > Personally, I always use option 1. Usually the only time people do not is when they are in a team using mixed IDE's and there is objection to having the Eclipse IDE files part of the repository. Also, I believe some tools like Maven can generate the Eclipse IDE files for you. That way you manage your project using only the Maven POM and let it generate the IDE-specific files as needed. -- Thanks Mark Phippard http://markphip.blogspot.com/ ------------------------------------------------------ http://subclipse.tigris.org/ds/viewMessage.do?dsForumId=1047&dsMessageId=3100394 To unsubscribe from this discussion, e-mail: [[email protected]]. ------=_Part_1662_2071778348.1424550615131 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr">On Sat, Feb 21, 2015 at 3:14 PM, skyemoor <span dir=3D"ltr= "><<a href=3D"mailto:[email protected]" target=3D"_blank">will.st= [email protected]</a>></span> wrote:<br><div class=3D"gmail_extra"><div = class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margin:0 0= 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div>= <div><div><div><div><div>Mark,<br><br></div>Your comments are very helpful,= thanks.<br><br></div>So for option 1, it sounds like I can continue to wor= k on a project, tagging it as I go, able to roll back at any time.<br><br><= /div>For option 2, it sounds like I create a new project for each baseline = (?)<br><br></div>It sounds like option 1 is the most attractive. I've b= een making changes to a couple of files, but I plan to insert them into my = previous Eclipse project fileset that I saved off in backup, delete the cur= rent SVN repository, then check-in the project and move forward from there.= </div></div><div><br></div></div></blockquote><div><br></div><div>Personall= y, I always use option 1.=C2=A0 Usually the only time people do not is when= they are in a team using mixed IDE's and there is objection to having = the Eclipse IDE files part of the repository.=C2=A0 Also, I believe some to= ols like Maven can generate the Eclipse IDE files for you.=C2=A0 That way y= ou manage your project using only the Maven POM and let it generate the IDE= -specific files as needed.</div><div><br></div><div><br></div></div><div><b= r></div>-- <br><div class=3D"gmail_signature">Thanks<br><br>Mark Phippard<b= r><a href=3D"http://markphip.blogspot.com/">http://markphip.blogspot.com/</= a></div> </div></div> ------=_Part_1662_2071778348.1424550615131--