facebook

Package Name Screw-up

💡
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 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • #305271 Reply

    Glenn Puckett
    Participant

    I am currently using MyEclipse 6.0.1.GA.

    I have been using MyEclipse for years. It has worked great and I plan to continue to use it. I know I need to update but I have been too caught up in project work to upgrade. And I am not going to to the upgrade right in the middle of a project.

    Late last week I brought up MyEclipse to make a quick fix to production code and found thousands of syntax errors that were not there before. The bottom line is that a specific package name has gotten screwed up. I have an Enterprise application with an EJB and Web project. I also have a “common” project where I put common code and other supporting code. One of the package names that contains classes used by almost every class in both EJB and Web projects has gotten screwed up.

    The name of the package is supposed to be com.cama.misc. Now what shows up is a package named com.cama with a directory under com.cama named misc. In the physical directory structure of the project it looks fine. But now every class that includes a class within the com.cama.misc package fails with class not found. I have tried a number of different ways to try to rename that back to the original package name and it always ends up back with the directory under the package. I even tried renaming the current package to something totally different then adding new package com.cama.misc. It still ends up as a directory under a package.

    ***Update***

    The only solution I could come up with was to create a totally new package (com.cama.common) and move every java class in the misc “directory” to the new class then perform a mass change in all java code to change from com.cama.misc to com.cama.common. Then go in manually and fix any remaining issues. Of course this meant I had to promote virtually every class in the application which has messed up my versioning a bit.

    I really need to know how this could have happened so that I can prevent it from hapenning again. Also I would really like to rename this back to com.cama.misc but am somewhat afraid to try because I might get myself back to the original problem.

    #305285

    This message has not been recovered.

Viewing 2 posts - 1 through 2 (of 2 total)
Reply To: Package Name Screw-up

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