Re: [Subclipse-users] Eclipse no longer content-assists, checks code errors after Subclipse install

On Sat, Feb 21, 2015 at 3:14 PM, skyemoor <will.stewart1a_at_gmail.com> 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: [users-unsubscribe_at_subclipse.tigris.org].