facebook

Project Directory Structure Corrupted?

💡
Our Forums Have Moved

For help with installation, bugs reports or feature requests, please head over to our new forums.
Genuitec Community on GitHub

  1. MyEclipse IDE
  2.  > 
  3. General Development
Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #205428 Reply

    bigrodent
    Participant

    I installed MyEclipse, took me quite awhile but I copied over a large eclipse project into what you call a J2EE project. Used the deploy and eventually got everything working. Went to bed last night a happy camper and started MyEclipse this evening to find that it had moved all of the packages that I had in my src/ folder to the top level of my project and renamed them src.com.foo.bar.blah… It also created a classes folder that was disabled and had mirrors of my packages and they were all named classes.com.foo…. After I finished screaming, I renamed every single package removing the ‘src.’ from the package name and everything compiled again. I deleted the old src directory and created a new one by using ‘create new source folder’. The instant that I did that it took my packages that were at the top level and turned them into the normal directory structure com/foo/bar….. blah.java.

    What happened ??? This is really scary.

    Thanks

    #205432

    Riyad Kalla
    Member

    We do not do any package manipulation or project reorginzation. When you say that it moved your source files, when you open them, were the “package” directives at the top of the file actually changed as well, or were you just ‘seeing’ a different representation of your project?

    Also when you refer to J2EE project, are you talking about a EAP, EJB or Web Module project? Can you give us a quick outline of your project’s directory structure with labels of which ones you have set as Source/Output/Webroot/etc? (see http://www.myeclipseide.com/FAQ+index-myfaq-yes-id_cat-30.html#111 for an example of what I mean).

    #205475

    bigrodent
    Participant

    I think that I may have found the culprit. I went looking through the structure on the NT filesystem and I couldn’t find the .classpath file due to another process that I had running to copy out some files. Do you think that if the editor could not open the .classpath file that it would have acted this way?

    Thanks

    #205476

    support-michael
    Keymaster

    If the .classpath is not available then your J2EE project is basically hosed. The same goes for the .mymetadata file.

Viewing 4 posts - 1 through 4 (of 4 total)
Reply To: Project Directory Structure Corrupted?

You must be logged in to post in the forum log in