[stevelopez]

We have a web project committed CVS. I’d like to attach to the project so Ican work on it.

When I use “New -> Project from CVS’ I am able to download the project. However, MyEclipse seems to lose the fact that the project is a web project. Instead of having a single WebRoot and single src folder MyEclipse prepends these folder names onto every dirctory structure in the project. So if our project has 10 folders inside ‘WebRoot’ MyEclipse creates 10 new root folders, each starting with WebRoot.

I’ve confirmed that the committed project is a web project and has a .project file

Thank you for assistance,
Steve

[support-tony]

Steve,

I wasn’t able to replicate your problem. Could you try adding one of our examples on demand, as I did? Try to create a new project from CVS, as you’ve done before but select the MyEclipse Examples cvs repository. I used the MyBlogJSFJPAExample sample and the project got created as expected.

If the MyEclipse Examples cvs repository is not in the list, try first adding an example via MyEclipse->Examples on Demand. After this you should have the MyEclipse Examples repository available when you try to create a project from CVS.

If you can add the sample project then there might be something odd with your own CVS project and we’ll have to explore what that might be. In that case, please post your installation details (MyEclipse->Installation Summary, then click the Installation Details button).

Do you have other development team members who experience this problem?

[stevelopez]

Tony,

Creating the project from the MyEclipse CVS worked properly. I tried again to create our internal project from CVS and got the same error (I had previously deleted the malformed project from disk). I did get some build errors once the project was created. They may be unrelated but I’ve included them here just in case. I’ve also included the installation summary below.

Note: This issue is actually occuring on an employees PC. We’re trying to get him setup so he is pointing to the CVS-based project which I committed.

BUILD ERRORS:
Errors occurred during the build.
Errors running builder ‘Integrated External Tool Builder’ on project ‘RegattaCentral’.
Launch configuration type id “org.maven.ide.eclipse.Maven2BuilderConfigurationType” does not exist.
Possible causes:
Missing specification of a launch type (missing plug-in)
Incorrect launch configuration XML
Launch configuration type id “org.maven.ide.eclipse.Maven2BuilderConfigurationType” does not exist.
Possible causes:
Missing specification of a launch type (missing plug-in)
Incorrect launch configuration XML
Errors running builder ‘Integrated External Tool Builder’ on project ‘RegattaCentral’.
Launch configuration type id “org.maven.ide.eclipse.Maven2BuilderConfigurationType” does not exist.
Possible causes:
Missing specification of a launch type (missing plug-in)
Incorrect launch configuration XML
Launch configuration type id “org.maven.ide.eclipse.Maven2BuilderConfigurationType” does not exist.
Possible causes:
Missing specification of a launch type (missing plug-in)
Incorrect launch configuration XML
Errors running builder ‘Integrated External Tool Builder’ on project ‘RegattaCentral’.
Launch configuration type id “org.maven.ide.eclipse.Maven2BuilderConfigurationType” does not exist.
Possible causes:
Missing specification of a launch type (missing plug-in)
Incorrect launch configuration XML
Launch configuration type id “org.maven.ide.eclipse.Maven2BuilderConfigurationType” does not exist.
Possible causes:
Missing specification of a launch type (missing plug-in)
Incorrect launch configuration XML
Errors running builder ‘Integrated External Tool Builder’ on project ‘RegattaCentral’.
Launch configuration type id “org.maven.ide.eclipse.Maven2BuilderConfigurationType” does not exist.
Possible causes:
Missing specification of a launch type (missing plug-in)
Incorrect launch configuration XML
Launch configuration type id “org.maven.ide.eclipse.Maven2BuilderConfigurationType” does not exist.
Possible causes:
Missing specification of a launch type (missing plug-in)
Incorrect launch configuration XML
Errors running builder ‘Integrated External Tool Builder’ on project ‘RegattaCentral’.
Launch configuration type id “org.maven.ide.eclipse.Maven2BuilderConfigurationType” does not exist.
Possible causes:
Missing specification of a launch type (missing plug-in)
Incorrect launch configuration XML
Launch configuration type id “org.maven.ide.eclipse.Maven2BuilderConfigurationType” does not exist.
Possible causes:
Missing specification of a launch type (missing plug-in)
Incorrect launch configuration XML

INSTALLATION DETAILS
*** Date:
Monday, August 15, 2011 9:27:44 AM EDT

** System properties:
OS=WindowsVista
OS version=6.1.0
Java version=1.6.0_13

*** MyEclipse details:
MyEclipse Enterprise Workbench
Version: 9.1
Build id: 9.1-20110701

*** Eclipse details:
MyEclipse Enterprise Workbench

Version: 9.1
Build id: 9.1-20110701

Eclipse startup command=-os
win32
-ws
win32
-arch
x86
-showsplash
-launcher
C:\Users\consultant\AppData\Local\Genuitec\MyEclipse 9\myeclipse.exe
-name
Myeclipse
–launcher.library
C:\Users\consultant\AppData\Local\Genuitec\MyEclipse 9\../Common/plugins/org.eclipse.equinox.launcher.i18n.win32.win32.x86_3.2.0.v201103301700\eclipse_3215.dll
-startup
C:\Users\consultant\AppData\Local\Genuitec\MyEclipse 9\../Common/plugins/org.eclipse.equinox.launcher_1.1.0.v20100507.jar
-install
C:\Users\consultant\AppData\Local\Genuitec\MyEclipse 9
-configuration
C:\Users\consultant\AppData\Local\Genuitec\MyEclipse 9\configuration
-vm
C:\Users\consultant\AppData\Local\Genuitec\Common\binary\com.sun.java.jdk.win32.x86_1.6.0.013\jre\bin\client\jvm.dll

[stevelopez]

Tony,

I was able to identify the problem and can now create the project from CVS without issues.

The problem was that I hadn’t committed the project’s .classpath file to CVS. So MyEclipse was creating its own .classpath file and for whatever reason wasn’t setting the path for src to “src”. (instead it seems to default to ‘bin’, which is strange since src seems to be the default I see on most Eclipse environments.

In any case, its working now.

Thanks,
Steve

[support-tony]

Steve,

Thanks for letting us know what the problem was and I’m glad it’s all working now.

[Author]

Posts