Why is my Eclipse Java package being treated as a folder?

My Eclipse Ja开发者_如何转开发va package is treated as a folder; can anyone suggest what's wrong?

First, ensure that you're in the "Package Explorer" view of the Java Perspective.

Secondly, it needs to be made a Source Folder.

If you're in the Java Project, right click on the folder and select "Build Path" > "Use as Source Folder"

Something like what is shown here:

Observe that I am in Java perspective and see how the style of the folders "source" and "src" are different in appearance.

Well, I actually think you might don't even need the answer anymore (almost two years later) but I will share anyway to document (just found a solution that others could use).

The problem: while searching some packages I accidentally clicked "Add to build path" in a package and after I ctrl+z, the package had became a folder.

The solution I found was on the .classpath. There was a line there with the name of the package I had just added to the build path (even after the Ctrl+Z). Delete that line and after refreshing the project your whole src folder will be turned into a normal folder.

Then right click your src, following this path: src > Build Path > Use as Source Folder.

This solved the problem, I just tested the result. Hope it helps.

go into your javabuildpath in properties and remove the folder from your Exclusions

Worst case, you'll have to delete the folder and recreate as a java package.

• Save the Java classes somewhere else in your Java project by refactoring
• Delete the folder and the underlying folder structure
• Create a Java package
• Move the Java classes back under the Java package by refactoring

SIMPLE You are not in the Package Explorer View ( but in Navigator view) If not the above case, then create a new package under the project (staying in Package Explorer view) and move those classes to the newly created package. DONE.

Just switch to java perspective, in the ide (top right corner-> java...)

I tried mvn eclipse:eclipse and it worked. One to watch out is the .project file.

Right click on Project > Configure > Convert to Faceted Form > Click on apply and OK

This one has worked for me.

i had the exact same Problem after i added the packege in java build path -> libraries -> add class folder...

Dont ask why i did this ^^ but to resolve the Problem i just had to go to Project->Properties->java build path->Source

And there it was in the Excluded part. Just remove it from the exclusion pattern and perhaps also from the libraries section.

This kind of issue occur due to missing of java and test folder in the web application

solution is :

Right click on the project folder -> properties -> java build path -> order and export and select the java and test folder and add or apply -> ok

then you should able to add the package in the java folder

No Need of delete, re-create etc.

Just modify .classpath file

<classpath>
<classpathentry kind="src" output="target/classes" path="src/main/java">
    <attributes>
     ........

I have faced the same issue and found the solution, as to add Java Nature in .project file of the current application.

Project natures are used in the Eclipse IDE in order to configure projects in the workspace. One project may have several project natures. The most popular project nature is org.eclipse.jdt.core.javanature, which is used to indicate that a project is a Java project.

Add org.eclipse.jdt.core.javanature and its corresponding builder in the .project file of an application as shown below:

<projectDescription>
    <name>MyJavaApplication</name>
    <comment></comment>
    <projects></projects>
    <buildSpec>
        <buildCommand>
            <name>org.eclipse.jdt.core.javabuilder</name>
            <arguments></arguments>
        </buildCommand>
        <!-- ... -->
    </buildSpec>
    <natures>
        <nature>org.eclipse.jdt.core.javanature</nature>
        <!-- ... -->
    </natures>
</projectDescription>

Project view as Package structure:

Projects and its dependent modules as Hierarchical structure.

Package Explorer / View Menu / Package Presentation... / Hierarchical

Creating a package makes an older one instead.

I had the same problem, and I was not able to solve it. But I suggest this, as a possibility. After copying and moving classes between packages, any file, it could be that the classpath has different information and that it hasn't been updated.

After having read some comments above, I now am only using source folders instead the standard source Folder "src". Inserting packages in any new source folder always runs.

From the menu bar, select Navigate > Show In > Package Explorer.

This is what worked for me.

I had this on a maven project.

If it's a MAVEN project and this is a new module, you have to Import the module as maven project and it will work.

Right click -Import->Existing Maven Module...