We Keep Coding

Package presentation in Java EE perspective in eclipse

I have a problem when switching to my Java EE perspective in eclipse indigo.
In my Java perspective I have this layout:
But when I switch to Java EE perspective I get this:
I have tried this and this unsuccessfully. I want to have the first layout in the Java EE perspective. Is there a way to do it?

Package presentation can be found here :

These are my settings in eclipse 4.2 which result in the layout you want:
- folder presentation: grouped
- package presentation: flat

You can switch this using the "Package Presentation -> Flat" from the drop down menu in the project explorer.

You can also import your project by using "import existing maven projects" . It will then configure the folders to be flat.

The above answers do not really solve the real problem that most noobs experience in Eclipse. So I thought I would add an answer to this question since the questioner resolved to reinstalling eclipse which is not necessary nor a viable solution. The real issue is that when you created or rather imported this project, you picked the option to create a Project in eclipse, not a Java Project. If you pick Project, it creates it as a filesystem looking directory structure similar to what you see in windows explorer. To fix this, just re-import your project from the workspace as a "Java Project" and you can change the package structure as flat or hierarchical as per your viewing pleasure.. Hope this helps.

UML plugins in Netbeans6.8

Java: I tried to add the available plugins in netbeans6.8 but it ask for *.nbm file instead of jar files, Please guide me for the same and also provide the related download URL and steps for the same. I added this URL http://ea.ddns.com.br:8090/netbeans6.8/UML/catalog.xml in my Setting tab but still unable to find the plugins

The UML plugin for the NetBeans IDE is available for until version 6.7. Support was dropped after that.

I think UML was stopped after the 6.5 Netbeans release.
Download one of the previous build and you will be able to create diagrams.
You can also use Eclipse. The trick is to import your java project inside Eclipse and reverse engineer it in order to create diagrams. Once created you export your diagrams into image format such png, gif etc...Finally you copy your image into your netbeans project.
Nobody would ever guess that your diagrams are coming from Eclipse :-)

How to compare two eclipse installations for missing features?

I have two coexisting installations of eclipse on my machine. One is the plain eclipse and one is STS (Spring Source Tool Suite). For some strange reason (which would be too tedious to explain here) I have to use the plain eclipse. However, I want to import, use some of the plugins that already exist in STS.
Is there a way I can go about achieving this?

If you don't want to scan the filesystem for the plugins, the easier solution is to go to Help -> About Eclipse -> Click on "Installation Details". That should provide you all the installed plugins in Eclipse.

It is possible to install the STS-specific bundles into vanilla Eclipse. You need to follow the instructions outlined here:
http://dist.springsource.com/release/STS/doc/STS-installation_instructions.pdf
Look at the section called "Update site installation".

Standard Java Project Description Format

I'm coming from the .NET world where Visual Studio is pretty ubiquitous. VS has a .sln file which pretty exhaustively describes a project, including where to find source files, dependencies, etc.
Now I'm doing some java coding in a team. My problem is this: I'm using intellij and others are using eclipse (while others could be using some other IDE). Is there a standard project description file that can be shared among IDE's? I obviously don't want to put my intellij specific files to source control. So what I'm looking for is a standard that pretty much any self-respecting IDE would recognize which you could point it to and it would be able to interpret the project structure, how to find dependencies, the class paths, etc.

Maven should be able to do it (a project build manager and source control overlay), but alas, there is no standard project file. There are Maven plug-ins available for all the major IDEs. http://maven.apache.org/guides/getting-started/maven-in-five-minutes.html

Note quite. But you have a "way out". You can use Maven2. It has a unified pom file which contains all:
source folders (note: maven imposes a default convention on those, but they are still configurable)
compiler level
dependencies
build steps
etc..
(Of course that would require to install the maven plugins for both IDEs)
Another option would be to force either of the IDEs and commit their proprietary descriptors.

As others have posted, Ant and Maven are pretty much the de facto project spec utilities in the Java world. Those are both generally easy to learn -- a fair learning curve, but nothing dramatic -- and are pretty powerful. You could speak to your team members or leader and see how they've dealt with it -- I'm sure it isn't a new problem.
Aside from that, a lot of development teams (in my experience, at least) try to avoid putting project files in source control. The developers are required to basically create their own projects in whatever IDE they're using. It makes getting started on a project a little more difficult for a developer coming fresh into an existing project, but it also helps the developer get a little better acquainted with the project.
At my shop (very, very small team), we use Eclipse, but we still have to manage the workspaces (similar to VS solutions, but not quite the same) ourselves. I've created some Ant scripts for use on our continuous integration server, and that won't necessarily keep problems from arising, but it helps make them more obvious when they do.

There is no such standard project description file as far as I know. But intellij is able to take an eclipse and convert to an intellij project. Also you could look at maven.

There is not one. You could switch to an build system using ANT (similar to Make) but that has pitfalls of it's own. You will get the most mileage if you and your team standardize on an IDE though ...

I think what you want here is for a developer using Eclipse to edit the project settings and have those changes reflected in IDEA for some other developer. If that's the case, then Maven is what you want. IDEA 9.x has great support for Maven, and so does Eclipse. If a developer that uses Eclipse edits the dependencies in the Maven project files (pom.xml files), then IDEA can import the files and change it's project settings.
RE: ANT vs Maven - In this respect (syncing project settings) ANT build files won't work because they are imperative (script-like) rather than declarative.

Maven should be the preferred way but most IDE's now days support some kind of ant based project which is what most of the IDES use internally. Usually called free-form projects.

I'm not a Maven fan myself. I'd recommend Ant long before Maven.
If you're using IntelliJ, I'd argue that it does have a pretty standard idiom. And since it can import any Eclipse project file, you'll be on safe turf laying things out as IntelliJ does it.
I don't check in my IntelliJ project files, but the /src, /lib, /test, /resources etc. are all fair game.
The true answer should be that your team should huddle up and come up with a standard layout that you agree on regardless of IDE. You've got to check code into SVN sometime.
Your question is interesting to me, because I'm trying to go in the other direction (Java->C#, IntelliJ->Visual Studio), and I'm having trouble doing the mapping in the other direction.
I think it's just part of learning a language and its native IDE. I find that it's best to find an experienced guide.
One problem you'll have is that the .NET universe is isotropic (all things Microsoft), where even your small corner of the Java universe is heterogeneous (IntelliJ and Eclipse and NetBeans). You're less likely to find one true answer for all of Java.

Open eclipse svn project in netbeans

OK my problem is quite simple
Im about to start working with a team of programmers, and we are using a svn repository to store our code, thy files are set up as Eclipse Project as the rest of my team all like eclipse.
However I am die hard netbeans man, I have tried eclipse Iv given it some time but we do not gel as they say.
So my question is there a combination of plugins /hacks that i can use to access a Eclipse Project from an SVN repository inside Netbeans , without corrupting the eclipse project or causing problems for the rest of my team (I would rather suffer eclipse than do this to them)
Many thanks ^_^

In NetBeans 6.8 under File > Import Project there is both Eclipse Project and Resynchronize Eclipse Projects. I'm guessing this can be used to work together with people using Eclipse.
UPDATE: How the eclipse import function works.

As NA pointed out, there is a way to import your Eclipse projects into Netbeans. However, arguably, you shouldn't be checking in IDE-specific files into your repository unless you can guarantee everybody is using the same IDE. Otherwise, I would recommend only checking in the source code, resources, and additional libraries and keep the specific files on ignore and have each individual setup their own environment.
Another alternative, is to check in the IDE-specific files in a different folder in the repository so that an individual can grab them if they need them.