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.
On Sat, Feb 21, 2015 at 2:52 PM, Mark Phippard-3 [via Tigris - SCM] <
> On Sat, Feb 21, 2015 at 1:19 PM, skyemoor <[hidden email]
> <http:///user/SendEmail.jtp?type=node&node=98383&i=0>> wrote:
>> After installing Subclipse and checking out my code, JDT seems to have
>> stopped working, and there is no more content assist, LookUpEnvironment,
>> other features that the Java perspective has provided before I started
>> I get these errors;
>> - Cannot obtain JDT's lookup environment (debug only)
>> - Cannot access LookUpEnvironment by reflection
>> - Exception during code completion
>> --- imageanalytics (note: my project) does not exist
>> None of the tutorials I looked at mentioned this. Is there a step I need
>> add to finish the transition over to a completed Subclipse install that
>> keeps a fully functioning Java perspective?
> Subclipse does not setup your project for you, it pulls down the files
> from your SVN repository. What most people do is check-in their Eclipse
> .project and .classpath files, along with the .settings folder. Then, when
> someone checks out the project it will already be configured.
> The other option, is take the option during Checkout to run the Create New
> Project wizard. This allows you to choose the Eclipse project type and
> configure it as part of the checkout process.
> If you not do either of these things then you just get what Eclipse calls
> a "Simple Project" which just has a basic file and folder structure but no
> compilers or other tools connected.
> Mark Phippard
> If you reply to this email, your message will be added to the discussion
> To unsubscribe from Eclipse no longer content-assists, checks code errors
> after Subclipse install, click here
View this message in context: http://tigris-scm.10930.n7.nabble.com/Eclipse-no-longer-content-assists-checks-code-errors-after-Subclipse-install-tp98382p98384.html
Sent from the subclipse - users mailing list archive at Nabble.com.
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subclipse.tigris.org].
Received on 2015-02-21 21:22:04 CET